Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
DFSORT messages and return codes z/OS DFSORT Application Programming Guide SC23-6878-00 |
|
You can determine, during installation or run-time, whether DFSORT writes messages to the message data set, to the master console, or to both. You can also direct an Extended Function Support program to write messages to the message data set. Messages written to the message data set can be either critical error messages, informational error messages, or diagnostic messages, as determined during installation or run-time. Messages written to the master console can be either critical error messages or informational error messages, as determined during installation. See z/OS DFSORT Messages, Codes and Diagnosis Guide for complete information about DFSORT messages. For successful completion, DFSORT passes back a return code of 0 or 4 to the operating system or the invoking program. For unsuccessful completion due to an unsupported operating system, DFSORT passes back a return code of 24 to the operating system or the invoking program. For unsuccessful completion with NOABEND in effect, DFSORT passes back a return code of 16, 20 or 28 to the operating system or the invoking program. For unsuccessful completion with ABEND in effect, DFSORT issues a user abend with the appropriate code as specified by the ABCODE installation option (either the error message number or a number between 1 and 99). The meanings of the return codes that DFSORT passes back (in register
15) are:
|
Copyright IBM Corporation 1990, 2014
|