Return Codes

Introduction › Messages and Codes Layout › Return Codes

Return Codes

Additionally, CA IDMS components generate the following return codes that approximate the standard IBM return codes:

Code	Description
0000	The job has completed successfully. If this code is issued from IDMSATCO or RHDCATCD, the attached subroutine (IDMSATCM) has communicated successfully with the system or the system is active.
0004	Warning messages have been issued by a DML processor or a DDL compiler. Review the messages on SYSLST, make the necessary corrections; then recompile. This code is issued only in the z/OS operating environment.
0008	The compiler has detected an E-level error in a source statement. Use the input statement listing to determine the cause of this error, make the necessary corrections; then recompile.
0016	A compiler has detected a fatal error in a source input statement. Use the input statement listing to determine the cause of the error, make the necessary corrections; then recompile.

Message Text

Under certain conditions, it is possible for the text of a message to differ from the documented content. An example of this is when a deadlock condition exists. If a message is to be issued for a task which is currently in a deadlock state, no attempt is made to retrieve the message text from the message dictionary. This results in the common text of the message not being available for display, and writes the parameters passed during the message write request without any identifying text or labels.

Another example is when any of the parameters passed resolve to non-printable values. When this occurs, the message facility replaces those characters with spaces. This can result in a message that contains no apparent variable text when written to the console.

In an extreme case, if both of these conditions occur for a task at the same time, the message issued could result in nothing more than the message number being written to the target destinations.