Cause: The command submitted to REXX could not be recognized.
The command cannot be processed.
Action: Verify that the command is a valid SQL statement and rerun the procedure. Note that all commands must be in uppercase.
Cause: The user specified an incorrect cursor name.
The command cannot be processed.
Action: Verify that the cursor name is one of the form "c1" through "c100".
Cause: The user has specified an incorrect statement name.
The command cannot be processed.
Action: Verify that the statement name is of the form "s1" through "s100".
Cause: REXX was unable to parse the command string submitted.
The command cannot be processed.
Action: Use proper command syntax.
Cause: An OPEN statement was attempted without a declaring a cursor.
The command cannot be processed.
Action: Insert a DECLARE statement before the OPEN statement and rerun the procedure.
Cause: The statement contains a not valid keyword "<keyword>".
The command cannot be processed.
Action: Specify the correct keyword format.
Cause: A REXX variable that did not exist in the REXX variable pool was passed.
The command cannot be processed.
Action: Verify that all variable names in the host-variable list are assigned before the command that failed. Then run the procedure again.
Cause: A variable that contained inconsistent data was passed to REXX.
The command cannot be processed.
Action: If the variable is an SQLDA, verify that the data and length fields have been assigned correctly. If it is a REXX variable, verify that the type of data is appropriate to the command where it is being used.
Cause: The variable "<variable>" passed to REXX contained inconsistent data. The data string from "<variable>" was truncated.
The command cannot be processed.
Action: Verify that the data length is consistent with the length given in the input SQLDA, and run the procedure again.
Cause: The scan ID "<variable>" passed to REXX did not exist or contained inconsistent or missing data.
The command cannot be processed.
Action: Verify that the data contained in the scan ID has been assigned correctly, and run the procedure again.
Cause: The parameter "<parameter>" is required by REXX command syntax but was not specified.
The command cannot be processed.
Action: Specify the required parameter value, and run the procedure again.
Cause: Isolation level (ISL) may not be changed while connected to a database.
The command is ignored.
Action: If a change in isolation level is necessary, disconnect from the current database, then set the isolation level and connect to the database.
Cause: In REXX, the cursor and statement name form must be 'cnn' and 'snn,' where 'nn' is a number from 1 to 100. The numbers must be the same for a cursor and statement pair. Also, c1 through c50 are declared without hold and c51 through c100 with hold.
The command is ignored.
Action: Verify that the cursor and statement numbers match and rerun the procedure.
Cause: In REXX, the first component of a compound host variable lists a number which is not equal to the actual number of components defined.
The command is ignored.
Action: Verify that the number in the first component matches the number of components actually defined and rerun the procedure.
Cause: The variable name specified is not valid in REXX. The name must conform to the language requirements.
The command cannot be processed.
Action: Change the name to one that conforms to the REXX requirements and resubmit the command.
The command cannot be processed.
Cause: Invalid syntax was provided to the SQLDB2 interface, e.g. both an input file and a command were specified.
Action: Look up the related error code for more information.
Cause: A REXX internal error has occurred.
The command cannot be processed.
Action: Verify that REXX is installed properly and rerun the procedure. If the error continues, note the error number and call the dealer.