Checking return codes from the Parse Service Routine

When the Parse Service Routine returns control to its caller, general register 15 contains one of the following return codes:

Table 1. Return codes from the Parse Service Routine
Return code dec(Hex)	Meaning
0(0)	Parse completed successfully.
4(4)	The command operands were incomplete and parse was unable to prompt.
8(8)	Parse did not complete because an attention interruption occurred during parse processing.
12(C)	Parse did not complete; the parse parameter list contains not valid information.
16(10)	Parse did not complete; no space was available.
20(14)	Parse did not complete; a validity checking routine requested termination by returning to parse with a return code of 12.
24(18)	Parse did not complete; conflicting operands were found on the IKJTERM, IKJOPER, or IKJRSVWD macro instruction.
28(1C)	Parse did not complete; the user's terminal has been disconnected or a serious error has occurred in z/OSMF ISPF.
32(20)	Parse did not complete; a verify exit routine requested termination by returning to parse with a return code of 16.
36(24)	Parse did not complete; an out-of-range DBCS character was found.
40(28)	Parse did not complete; an odd number of bytes was found in a DBCS character string.
44(2C)	Parse did not complete; a shift-out character was found with no corresponding shift-in character.
48(30)	Parse did not complete; a nested shift-out character was found.

If the Parse Service Routine returns to your Command Processor with a return code of zero, indicating that it has completed successfully, the PPLANS field in the parse parameter list contains the address of a fullword containing a pointer to the parameter descriptor list (PDL). See Examining the PDL returned by the Parse Service Routine for information on how to use the PDL to examine the results from the Parse Service Routine.

If the Parse Service Routine does not complete successfully, your Command Processor should issue a message except when the return code from parse is 4, 20 or 32. When the return code is 4, parse has already issued a message. When the return code is either 20 or 32, the validity checking routine or verify exit routine, respectively, has issued a message before it requested that parse terminate.

Your Command Processor can invoke the GNRLFAIL routine to issue meaningful error messages for the other parse return codes. See Analyzing error conditions with GNRLFAIL/VSAMFAIL.

Figure 1. Control flow between Command Processor and the Parse Service Routine