30

You have tried to address an invalid or inactive command environment (using an ADDRESS statement in your REXX program).

-8

There was not enough memory to process the command.

-7

The statement invoking the command processor contained an invalid session name or type, or the session does not support the requested operation.

-6

The statement invoking the command processor was missing a required argument.

-5

The statement invoking the command processor contained an invalid argument.

-4

The statement invoking the command processor contained too many arguments or mutually exclusive arguments.

-2

CA Automation Point encountered an invalid delimiter while parsing the command.

The problem occurs when CA Automation Point expects to see a certain character as a delimiter and finds another character instead. For example, using this statement in a REXX program produces a return code of -2 because CA Automation Point expects parentheses (not single quotes) to enclose the text string.

"SETVAR REXX_MESSAGE 'THIS IS A REXX MESSAGE'"

CA Automation Point recognizes the following delimiters if you issue its commands from REXX programs:

• Single quotation marks
• Parentheses
• Spaces not contained in quotation marks or parentheses
• The end of the line

This return code could also indicate that you have exceeded the maximum length of a variable name in a command processor statement.

-1

CA Automation Point does not recognize an operand in the command processor, probably because its name is misspelled. CA Automation Point also returns this code if you issue operating system commands without specifying CMD as the target environment.

If you issue a command through a CA Automation Point REXX program, you must use the REXX ADDRESS command to target commands to other REXX environments because CA Automation Point becomes the default environment to REXX. For example, to use the operating system to copy a file, issue a command that looks like this:

ADDRESS CMD COPY filename1 filename2

0

The command processor executed without errors.

3

An error occurred when processing the command:

• The CONFIG command fails to reload configuration or reloads it partially.
• The LOADRULES command generates a return code of 3 if the rule file cannot be opened.
• READBUF, CLOSEBUF, and OPENBUF commands generate a return code of 3 if a buffer does not exist for the session that you specify, or if another REXX program currently owns the specified session's buffer.
• The SESSCNTL command generates a return code of 3 if you attempt to restart automation in a session while global automation pause is in effect.
• The SESSCONFIG command generates a return code of 3 if you specify an invalid session definition set name or the associated file cannot be opened.

9

The LOADRULES command processor did not enable the rules file that you specified because one or more rules in the file contained syntax errors.

32

The SESSCMD command processor timed out because the keyboard in the specified session was locked (in an X state) and did not clear soon enough.

36

A SESSCMD command locked the host keyboard and the keyboard did not clear soon enough; the host could not respond before SESSCMD timed out.

150

The PLOT command referenced an undefined graph. Be sure that you have specified the correct plot and that you have spelled it correctly.

151

The PLOT command attempted to define a line or bar that already exists.

152

The PLOT command attempted to delete a line or bar that does not exist.

153

You specified an invalid range in a PLOT command statement. For example, you may have specified a minimum value that exceeded a maximum value.

154

You tried to define more than eight lines in a PLOT command statement.

155

You tried to define more than one bar in a PLOT command statement.

156

The PLOT command referenced an invalid or undefined TICK value.

157

You defined an illegal tick mark.

158

You specified an invalid scale in a PLOT command statement. For example, you may have specified a start value that exceeded a stop value, or you may have tried to apply a TIME scale to an axis defined as NUMERIC.

159

The PLOT command exceeded the maximum number of label lines for an axis or title label.

303

An incorrect key operation was specified.