Batch Abends U1000, U1001, U1002

When the batch report processor encounters a severe error condition in STAE environments, it issues user abends 1000, 1001, or 1002. Analyzing the problem with the following factors in mind might help you identify the cause of the problem and its solution.

CICS PA also issues a message indicating that a STAE exit was invoked.

Note: The STAE environment allows you to signal a logical end-of-file to record processors when an unexpected error occurs. The data accumulated up to the point of the error is then available for reports. Without logical end-of-file, the data would be lost.

User abends issued by the STAE exit processing frequently mask the real problem. When CICS PA encounters an error condition, such as a protection exception, it tries to recover and produce as many reports as possible, without reading any more data. It then abnormally terminates with one of these user abends.

Logic errors are generally easier to diagnose if processing stops immediately. When a STAE exit runs, memory and register values change, making the cause of the abend harder to identify. If you need a dump for analysis by IBM® support, be sure to specify PARM=NOSTAE on the EXEC statement of your JCL.

If you specify NOSTAE and still get user abends, check the error messages. Some severe CICS PA messages cause user abends 1000, 1001, or 1002 after they are issued. NOSTAE does not affect these user abends. If you need to call IBM support, make sure you know which message causes you to stop processing.


Information Information

Feedback


Timestamp icon Last updated: Friday, 8 February 2013


http://pic.dhe.ibm.com/infocenter/cicsts/v5r1/topic//abends.htm