IBM Mainframe Forum

by **gopal_NKP** » Mon Aug 29, 2011 4:30 pm

I am getting the following warning messages while job execution . Job is executing fine. But I want to resolve the following warning messages. Please suggest me, how to prevent the following warning messages.

IEC161I 056-084..............
076 IEC161I
IEC161I 056-084
077 IEC161I
IEC161I 062-086
078 IEC161I

thanks

by **BillyBoyo** » Mon Aug 29, 2011 4:48 pm

Can you post the full text of the messages for your step, and your JCL. In the Code tags, please. Paste the stuff into the input box, higlight it, click on Code button, click on Preview to see what it looks like, make any necessary adjustments and submit it.

You might want to start by looking-up what the messages mean yourself, including the "reason codes". Google can help with the messages.

by **Robert Sample** » Mon Aug 29, 2011 4:51 pm

From the Messages and Codes manual on IEC161I for 056:

Specific Information for This Return Code

The last request to close this data set was not completed successfully. (OPENIND is on in the catalog). A previous VSAM job might have ended abnormally and left the data set open. This is a normal message for system data set during IPL.

System Action: OPEN processing continues. The error flag (ACBERFLG) in the ACB (access method block) for the data set is set to 116 (X'74').

Application Programmer Response: If the error occurred at a time other than during IPL, use the access method services VERIFY command to make sure the end-of-file marker in the data set entry in the catalog is correct. Note that it is not valid to use VERIFY on a linear data set. If you ignore the warning and try to process the data set, the results are unpredictable. For example, you could cause lost records. If you use the VERIFY command, this message can appear when VERIFY processing opens the data set. If VERIFY processing then successfully closes the data set, it issues condition code 0.

and for the 062:

Specific Information for This Return Code

VERIFY has been successfully run by OPEN to determine the end of a VSAM data set which was not previously closed successfully.

System Action: OPEN processing continues. The error flag (ACBERFLG) in the ACB (access method block) for the data set is set to 118 (X'76'). If the data set was opened for output, then the catalog will be updated when the data set is successfully closed. If the data set is opened for input, the catalog will not be updated by close and VERIFY will again be run by OPEN the next time the data set is opened.

Application Programmer Response: The last request to close this data set was not successful. OPEN has attempted to verify the end of the data set and the VERIFY completed without errors. The catalog will be updated when the data set has successfully been opened for output and then successfully closed. You should verify that all of the expected records are in the data set. For additional information on VERIFY processing, see z/OS DFSMS Using Data Sets.

What this all means is that the last process to open the VAM file did not successfully close it. Unless you can identify which process (started task, TSO user, batch job, or whatever) did this, you have absolutely no hope of completely resolving this.

Furthmore, why do you care? The messages are telling you that the system fixed the problem itself. You could always add a VERIFY step to your JCL before the step getting thiese messages but if the file is being opened as shared by another job while yours is running, it is quite possible that you cannot prevent the messages from appearing.

by **BillyBoyo** » Mon Aug 29, 2011 5:06 pm

I'm a little more hopeful than Robert on this (the sun is shining here, good morning Robert :-)

).

Especially as this might be your VSAM file.

Are you reading the file from a Cobol program? If so, you would have got a non-zero file status on the OPEN for the file, which would mean you are not checking the file status for the OPEN. If you are not doing that, you are probably not checking the file status on any of your IO. File statuses should always be checked, and appropriate action taken when you get an unexpected result. It is possible to even treat the file status for this condition as OK when you do the open. As Robert has said, the system has made the file usable already.

However, whatever was using the file before your program ran left the file open for some reason. This might point to a problem.

by **gopal_NKP** » Tue Sep 06, 2011 3:32 pm

Hi,

First of all, thanks to all of you for your help.

I am getting the following JES messages in job log .

Select all

18.05.54 JOB13383 IEC161I 056-084,ABCDE,ABCDE137ABCAB1,RABVHIST,,,RABL.BVHST.A
229 IEC161I RABL.BVHST.DATA.A,ICFCAT.PRODE
18.05.54 JOB13383 IEC161I 056-084,ABCDE,ABCDE137ABCAB1,RABVHIST,,,RABL.BVHST.A
230 IEC161I RABL.BVHST.INDEX.A,ICFCAT.PRODE
18.05.54 JOB13383 IEC161I 062-086,ABCDE,ABCDE137ABCAB1,RABVHIST,,,RABL.BVHST.A
231 IEC161I RABL.BVHST.DATA.A,ICFCAT.PRODE

ABCDE is job name
ABCDE137 is step name
ABCAB1 is step name in JCL, which called the proc
RABVHIST is the dd name
RABL.BVHST.A is the VSAM dataset name.

The error messages have been coming for different VSAM datasets in each day, even though not for the same dataset.
I have to prevent these messages.

Please tell me, how to add a verify step to check these. (with example if possible)

once again, thanks for your help.

thanks
vgl

by **NicC** » Tue Sep 06, 2011 4:04 pm

They are NOT error messages they are informational messges (the I at the end of the error message identifier tells you that). The VERIFY command can be issued via IDCAMS so just add a step at the front of the job to verify the datasets. What I cannot remember is whether these messages will be issued for the VERIFY. If they are then you have a lot of research to do to find out what programs/jobs left these datasets in this state.

by **BillyBoyo** » Tue Sep 06, 2011 4:37 pm

Please try to describe everything. Where are you getting the messages? CICS? Some batch job? Where? If they are different names from day-to-day are they from the same job, etc?

As NicC says, VERIFY is just IDCAMS. But I think you may need to know why files are being left open.

by **gopal_NKP** » Tue Sep 06, 2011 4:52 pm

Hi,

Thanks for your response.

All are batch jobs.
Some VSAM (KSDS) files are used in only one batch job(in different steps) and some VSAM (KSDS) files are used in more than one job.
Actually, we have a COBOL program(standard) for each VSAM(KSDS) file.
This COBOL program is called using some linkage variables to perform any type of operation on the VSAM (KSDS) file.

Can you please tell me, how to prevent those messages? I want to prevent those messages. Please let me know in detail .

thanks
vgl

by **gopal_NKP** » Tue Sep 06, 2011 4:54 pm

Hi,

In addition to my previous post, some files are being used in online(developed using CLIST and not CICS) also .

thanks

by **Robert Sample** » Tue Sep 06, 2011 5:06 pm

Can you please tell me, how to prevent those messages? I want to prevent those messages. Please let me know in detail .

Depending upon your site and precisely what is causing the messages, it may not be possible to prevent the messages. You could add an IDCAMS step to your JCL to run a VERIFY on the VSAM file before your program accesses it, but that does not guarantee you won't get the messages.

Bottom line: either fix EVERY process accessing the VSAM files to ensure they NEVER abend, NEVER quit with wihtout closing the VSAM files -- or accept that what you want to do (get rid of the messages) cannot be done and learn to live with them.

IBM Mainframe Forum

VSAM Error/Warning messages

VSAM Error/Warning messages

Re: VSAM Error/Warning messages

Re: VSAM Error/Warning messages

Re: VSAM Error/Warning messages

Re: VSAM Error/Warning messages

Re: VSAM Error/Warning messages

Re: VSAM Error/Warning messages

Re: VSAM Error/Warning messages

Re: VSAM Error/Warning messages

Re: VSAM Error/Warning messages