How to debug a '0069' error?

sidsamant · New User Joined: 22 Oct 2006 Posts: 2

I having been recently handling faults and the biggest problem is '0069'. The leads from IDMS dumps are useless. Anyone got a magic trick to resolve this?

priyesh.agrawal · Posted: Mon Oct 23, 2006 6:16 am Post subject: Re: How to debug a '0069' error?

sidsamant,

Put out some more meaningful messages from abend log. "0069" only doesn't help to answer.

sidsamant · New User Joined: 22 Oct 2006 Posts: 2

The latest one is a CICS transaction abend. The abend screen consists of the transaction id, the DML-sequence where the abend coccurred and the IDMS error code '0069'.
The IDMS dump shows a lot of messages. Which one would u like to analyse?

sushma.vasisht · New User Joined: 12 Nov 2006 Posts: 2

0069 occurs usually when the run unit has lost communications with the IDMS CV, it can be due to following reasons:

1) The CV is not active, or the CV went down while your job was running. 2) The CV is not accepting new run units (at max-tasks)
3) The program is not registered
4) Proper BIND statement not issued by the program.
5) Maximum external wait time has been exceeded (too long between calls to IDMS, such as CPU loop, waiting on tape or other resource). 'EXTERNAL WAIT' time is defined in the SYSGEN.
5) The subschema-control block could have been overlaid (double check for array/subscripting problems and or subroutine linkage problems)
6) a nn29 or nn79 error status has been encountered (ending the run unit), but the program failed to check for (or properly handle) these status values
7) Look at the CV log for further associated messages! Often a D002, D003, or other 4 digit serious IDMS ABEND code will show-up (such as an 1143 for a corrupt index).
8) VDB VSAM shadow file could be full..