REXX return codes
Where to find information about REXX return codes.
Return codes that are specific to a command are described in the reference topic of that command.
A command might also return a return code that is listed in Return codes not associated with a specific command.
Panel facility return codes are described in Panel facility return code information.
CICS return codes
- -521
- Command not supported
- -522
- Invalid command or keyword
- -523
- Option must be specified
- -524
- Unsupported option specified
- -525
- Conflicting options specified
- -526
- Implied option not specified
- -527
- Redundant specification for option
- -528
- Value for option not specified
- -529
- Value specified for option which should not have a value
- -530
- Value specified for option is not numeric
- -531
- Invalid value
- -532
- Value specified is too long
- -533
- Value specified is too short
- -534
- Value not specified
- -535
- Variable table overflow
- -536
- Number of variables exceeds variable table limit
- -537
- Argument must be a variable
- -538
- Variable does not exist
- -539
- Invalid variable name
- -540
- Main system trace flag must be on for tracing
- -541
- Parsing error
- -542
- Generic name is invalid
- -543
- Missing right parenthesis
- -544
- Ambiguous value/keyword
- -545
- RIDFLD must be fullword variable
- -546
- RIDFLd must be variable
- -547
- Invalid GETVAR return code
- -548
- Internal GETVAR error
- -549
- Bad PUTVAR return code
- -550
- PUTVAR failed
- -551
- Unable to obtain storage
- -552
- Exec CICS® command table not found
SQL return codes
- n
- An SQLCODE if the SQL statement resulted in an error or warning
- 0
- The SQL statement was processed by the EXECSQL environment
- 30
- There was not enough memory to build the SQLDSECT variable
- 31
- There was not enough memory to build the SQL statement area
- 32
- There was not enough memory to build the SQLDA variable
- 33
- There was not enough memory to build the results area for the SELECT statement
Db2 return codes
- n
- A positive value that indicates the results of the call to the Db2® instrumentation facility interface (IFI). If the RC from the Db2 IFI is not zero, the REXX variable DB2_RC2 contains the Db2 IFI reason code. The DB2_RC2 value is used in conjunction with the RC by using Db2 codes in Db2 for z/OS product documentation for error determination.
- 0
- The Db2 command was processed by the Db2 IFI.
- 50
-
The specified Db2 command is either too short or too long to be accepted for processing by the Db2 IFI. The Db2 command cannot be less than 6 or greater than 4092 characters long.
- 51
- There was not enough memory to build the output area for the Db2 IFI.
- 52
- There was not enough memory to build the communications area for the Db2 IFI.
- 53
- There was not enough memory to build the return area for the Db2 IFI.
- 54
- The DB2_RC2 REXX variable could not be built.
- 55
- The DB2_BNM REXX variable could not be built.
- 56
- The DB2_OUTPUT.n REXX variable could not be built.
- 57
- The DB2_OUTPUT.0 REXX variable could not be built.
Return codes not associated with a specific command
- -3
- Exec not found or unrecognized command.
- -4
- User not an authorized user, or EXEC not allowed to use authorized commands.
- -5
- TWA size was not specified, or TWA size specified was less than 4 characters in length for this CICS transaction definition.
- -6
- REXX for CICS started with a CICS LINK and less than 16 characters provided in the communications area. Or REXX for CICS started with a CICS XCTL and either the communications area does not contain an MVS SIB type 1 control block, or the communications area length is less than 16 characters.
- -99
- Internal error