Filter
Top Products
System action: Execution is terminated at the point of
the error.
User response: Redefine storage and reissue the
command.
The following are the REXX error messages:
CICREX218E Error 46 Invalid variable reference
Explanation: Within an ARG, DROP, PARSE, PULL,
or PROCEDURE instruction, the syntax of a variable
reference (a variable whose value is to be used,
indicated by its name being enclosed in parentheses) is
incorrect. The right parenthesis that should immediately
follow the variable name may be missing.
System action: Execution stops.
User response: Make the necessary corrections.
CICREX219E Error 47 Unexpected label
Explanation: A label, being used incorrectly, was
encountered in the expression being evaluated for an
INTERPRET instruction or in an expression entered
during interactive debug.
System action: Execution stops.
User response: Do not use a label in these
expressions.
CICREX449E Error 22 running fn ft, line nn: Invalid
character string
Explanation: A character string scanned with
OPTIONS ETMODE in effect contains one of the
following:
v Unmatched shift-out (SO) and shift-in (SI) control
characters
v An odd number of bytes between the shift-out (SO)
and shift-in (SI) characters.
System action: Execution stops.
User response: Correct the incorrect character string
in the EXEC file.
CICREX450E Error 5 running fn ft, line nn: User
storage exhausted or request exceeds
limit
Explanation: While trying to process a program, the
language processor was unable to get the resources it
needed to continue. (For example, it could not get the
space needed for its work areas, variables, and so on.)
The program that called the language processor may
already have used up most of the available storage
itself. Or a request for storage may have been for more
than the implementation maximum.
System action: Execution stops.
User response: Run the exec or macro on its own, or
check a program issuing NUCXLOAD for a possible
loop that has not terminated properly. See your system
administrator for additional storage requirements.
CICREX451E Error 3 running fn ft: Program is
unreadable
Explanation: The REXX program could not be read.
This is probably due to bad data in the exec file or an
I/O error.
System action: Execution stops.
User response: Examine and correct the exec file.
Note: Sequence numbers are not allowed in columns
73 through 80 in a REXX exec.
CICREX452E Error 4 running fn ft, line nn: Program
interrupted
Explanation: The system interrupted execution of your
REXX program. Certain utility modules may force this
condition if they detect a disastrous error condition.
System action: Execution stops.
User response: Look for a problem with a utility
module called in your exec or macro.
CICREX453E Error 6 running fn ft, line nn:
Unmatched “/*” or quote
Explanation: A comment or literal string was started
but never finished. This could be because the language
processor detected:
v The end of the file (or the end of data in an
INTERPRET statement) without finding the ending
“*/” for a comment or the ending quote for a literal
string
v The end of the line for a literal string.
System action: Execution stops.
User response: Edit the exec and add the closing “*/”
or quote. You can also insert a TRACE SCAN statement
at the top of your program and rerun it. The resulting
output should show where the error exists.
CICREX454E Error 7 running fn ft, line nn: WHEN or
OTHERWISE expected
Explanation: The language processor expects a
series of WHENs and an OTHERWISE within a
SELECT statement. This message is issued when any
other instruction is found or if all WHEN expressions are
found to be false and an OTHERWISE is not present.
The error is often caused by forgetting the DO and END
instructions around the list of instructions following a
WHEN. For example:
WRONG RIGHT
Select Select
Error Numbers and Messages
380
CICS TS for VSE/ESA: REXX Guide