MVSFORUMS.com

ravikumar_sri2001 · Posted: Fri Mar 05, 2004 8:52 am Post subject: Backout problem for ESDS file

Experts,

I have ESDS file defined with "RECOVERY(NONE)".

But when the program abends, DTB is applied to the ESDS

Message from JESMSGLG of CICS start up job :

DFHFC4701 R3AACICS 230
03/05/04 08:16:26 R3AACICS Backout failed for transaction EG21, VSAM
file QEGHF, unit of work X'BADF2631F48A5680', task 01382, base
QCARE.TSTCDEV1.EGHF.EEI.HIST.ESDF, path
QCARE.TSTCDEV1.EGHF.EEI.HIST.ESDF, failure code X'FE'.

And CICS tries to the backout the ESDS file by shunting the UOW.

Uowstate( Backout )
Waitstate(Shunted)
Transid(EG21)
Taskid(0001382)
Age(00001848)
Termid(RVA0)
Netname(T02GRVA0)
Userid(RXS5549)
Waitcause(Dataset)
Link()
Sysid()
Netuowid(..GAA.T02GRVA0...4.........)

Dsname(QCARE.TSTCDEV1.EGHF.EEI.HIST.ESDF)
Cause(Dataset)
Reason(Failedbkout)
Uow(BADF2631F48A5680)
Sysid()
Netname()
Rlsaccess(Notrls)

When i try to access the ESDS file in online program very next day (assume that a uow is shunted for backout previous day), the program
gives "UNABLED" status for the file.

If i try to open the file using CEMT transaction, i am facing "OPEN/CLOSED" error.

Please let me know how to overcome this problem.

Thanks,
Ravikumar.

kolusu · Posted: Fri Mar 05, 2004 9:22 am Post subject:

Ravikumar,

The failure code is X'FE' which mean an error occurred which is not expected to be possible during backout. An exception trace point is written, message DFHFC4700 is issued and a system dump is taken. Use these to determine the cause of the error. It might be worth retrying the backout, using SET DSNAME RETRY, since the problem could have been some transient condition which has since cleared.

Check this link for DFHFC4700 error message description
Hope this helps...

Cheers

Kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu

ravikumar_sri2001 · Posted: Mon Mar 08, 2004 8:08 am Post subject:

Kolusu,

Thanks for your explanation.

How to avoid the backout for ESDS files.

Thanks,
Ravikumar.

Mike Chantrey · Posted: Mon Mar 08, 2004 9:42 am Post subject:

Are you sure there are not multiple FCT entries pointing to this file, with at least one of them NOT set to RECOVERY(NONE)? If all entries are set correctly to RECOVERY(NONE), this problem should never occur and if it does, indicates a CICS problem which should be reported to IBM as a possible bug.

ravikumar_sri2001 · Posted: Tue Mar 09, 2004 5:34 am Post subject:

Mike Chantrey · Posted: Mon Mar 15, 2004 8:27 am Post subject:

Does the dataset have any paths or aixs (different DSNs) defined to CICS with recovery not equal to 'none'? This would cause this problem. FILEAID 3.5 or LISTCAT can tell you if the base has paths/aixs associated if you don't know.

ravikumar_sri2001 · Posted: Tue Mar 16, 2004 7:41 am Post subject:

no path and no aix defined

thanks,
Ravikumar.

Mike Chantrey · Posted: Tue Mar 16, 2004 9:03 am Post subject:

All I can suggest now is that you talk to your CICS sysprogs about getting this reported to IBM as a possible bug. Backout processing should not be occuring for this file.

ravikumar_sri2001 · Posted: Wed Mar 17, 2004 3:25 am Post subject:

My onsite task coordinator says "The ESDS problem was due to a system change made a few weeks ago for record level sharing."

Is it possible ???.

Thanks,
Ravikumar.

Mike Chantrey · Posted: Mon Mar 22, 2004 11:32 am Post subject:

If you convert a file to RLS, the backout options on the file definition override the CICS-defined backout options. To determine if this is the case use LISTCAT ALL on the VSAM file and look for the value of the LOG option (explained in the AMS manual here: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/DGT1I211/14.1.2?SHELF=&DT=20001016161533&CASE= )
If this is set to UNDO or ALL then it will cause backout processing to be attempted on the ESDS in CICS. If this is the case, you have two options:
1/ Change the file definition with IDCAMS ALTER to LOG(NONE)
2/ Get the CICS sysprogs to write a 'logical ESDS delete' exit which will actually perform ESDS backout processing.

However, I don't understand how this could actually be the case because the CEMT info you gave above seems to idnicate this file has not been converted to RLS.

Mike Chantrey · Posted: Mon Mar 22, 2004 11:37 am Post subject:

Kolusu,
Followed the 'VSAM' link from the front page while looking at this question and I noticed that it points to the DFSMS V1.5 version of the Access Method Services manual (pre-dates RLS). As this version of SMS is out of support, do you think this link should be updated e.g. to the OS/390 2.10 version ? I think OS/290 2.10 is the oldest supported version now.

kolusu · Posted: Mon Mar 22, 2004 11:55 am Post subject:

Mike,

I could not find the manual for os/390 2.10 version. Do you have a link. Actually I am more inclined to have this link for vsam manual.

VSAM Demystified

I would really appreciate if you can provide the link for OS/390 2.10 version.

Thanks

Kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu