Diagnosis file and user ABEND 3999
Use the diagnosis file to find the name of the failing CSECT.
The diagnosis file
When CICS® VR internal validity checking detects errors, diagnostic information is written to the CICS VR diagnosis file (DWWDUMP) before user abend code 3999 is issued.Diagnostic information consists of message DWW0000T, which gives the name of the module in error and the reason for the exit, in two 8-byte character strings. You can use this information to build the keyword string for the problem type; see Using keywords to describe a problem for more information. CICS VR also writes a formatted version of the CICS VR trace table to the diagnosis file and snap dumps the data that it considers to be in error.
Locating the failing CSECT
- Locate save area 1; the address is in register 13.
- Locate save area 2; the address is at offset X'4' from save area 1.
- Locate save area 3; the address is at offset X'4' from save area 2.
- Locate save area 4; the address is at offset X'4' from save area 3.
- Locate the address of the failing module at offset X'40' from save area 4. This failing module contains the contents of register 11 at the time the error condition was detected.
Determine the name and compilation date of the failing CSECT from this value, using the same procedure described in Finding the CSECT.
Finding the BIB
The address of the BIB is at offset X'48' from save area 2 or save area 3.
BIB

If CICS VR VSAM batch logging was enabled and your batch job received a 3999 condition code, see operator messages DWW251I-DWW260I, or DWW262I for more information on the reason for the termination. Take a backup of the sphere to ensure recoverability. See Detecting batch logging error conditionsCICS VR Implementation Guide and Reference for information on how to set up your batch jobs to automatically take a backup when a 3999 condition code is received.