Because of the type of error, processing cannot continue. For all codes except U0024, see the last error message printed on the MSGPRINT DD statement for an explanation of why CADisk has terminated processing. The following is a list of the user abend codes:
CADisk has terminated abnormally because no MSGPRINT DD statement was present in the step's JCL. CADisk was tying to print a message but cannot. Add the following DD statement to the JCL and rerun the job: //MSGPRINT DD SYSOUT=A
CADisk has terminated processing due to the reason indicated by the last message printed. A system dump accompanies this abend.
CADisk has terminated processing due to the reason indicated by the last message printed. A system dump does not accompany this abend because the error message should be enough to solve the problem.
CADisk has terminated processing due to the reason indicated by the last message printed. A system dump accompanies these abends. Usually, they show a problem in getting or freeing memory. Increase the region size. If the problem continues, contact CA Technical Support for assistance.
CADisk has terminated processing due to a security violation.
CADisk has terminated processing due to possible write errors and the reason indicated by message 2132 generated in module ADSUT037.
Note: For more information, refer CADisk message 2132 or applicable IBM guides.
CADisk has terminated processing due to an internal error. A calling (or using) routine has presented an undefined option. The abend reason code is the call-option (or case) value. A system dump accompanies this abend.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|