IRX0005I Machine storage exhausted
Rexx terminated execution due to lack of storage. (See IRX0005I in the z/OS® TSO/E Messages.)
Attempt one of the following options:
Error reading file ssssssss.
Error occurred while reading file ssssssss.
Validate file accessibility.
Error erasing file ssssssss.
Error occurred while erasing file ssssssss.
Validate file accessibility.
Error writing file ssssssss.
Error occurred while writing file ssssssss.
Validate file accessibility.
Bad filename ssssssss: forward slash not allowed at the end of a filename.
Filenames are not allowed to end with forward slashes.
Modify the filename to not end with a forward slash.
Option x requires an argument.
Option specified must be accompanied by an argument.
Specify an argument with the option.
Invalid option = x. Valid options are: CIPScdls.
Invalid option specified.
Specify zero or more valid options.
Bad data set name ssssssss.
The data set name is not correctly specified.
Validate the name of the data set is correct.
CSECT name ssssssss is greater than 63 characters.
The CSECT name ssssssss is greater than 63 characters and will cause an error during assembly.
Make sure the CSECT name is 63 characters or less.
CSECT name ssssssss does not begin with a letter, $, #, @ or underscore (_).
The CSECT name ssssssss does not begin with a letter, $, #, @ or underscore (_) and will cause an error during assembly.
Make sure that the CSECT name ssssssss begins with a letter, $, #, @ or underscore (_).
ssssssss SCRIPT not found on any accessed disk.
The SCRIPT file with the name ssssssss does not exist.
Make sure the name is given correctly and is accessible.
Error on line nnn in message nnnn Insert number greater than mmmm.
An insert number greater than the allowable maximum was specified. The current maximum allowable insert number is 9.
Specify an insert number of 9 or less.
Error on line nnn Duplicate :FACID. tags found with the given script file.
Only one facility ID can be specified in the SCRIPT file.
Specify only one facility ID in the SCRIPT file.
No :FACID. tag found within the given script file.
A 3-character facility ID must be specified in the SCRIPT file with the :facid. tag.
Specify a 3-character facility ID with the :facid. tag.
Error on line nnn Message number nnnn found out of range mmmm to mmmm.
A message was found with a number outside the valid range. The current valid range is 0 to 9999.
Correct the invalid message number on the given line of the SCRIPT file.
Number of hex digits not divisible by 2 on line nnn in message nnnn.
Hexadecimal strings must contain an even number of digits.
Specify an even number of digits for the hexadecimal string.
Invalid hexadecimal digits on line nnn in message nnnn.
Valid hexadecimal digits are 0–9 and A–F. Invalid digits were detected.
Specify only digits 0–9 and A–F within a hexadecimal string.
Number of DBCS bytes not divisible by 2 on line nnn in message nnnn.
Doublebyte character strings must contain an even number of bytes.
Specify an even number of bytes for the doublebyte character string.
PLAS out_file name must be longer than the message facility ID pppp.
The ASSEMBLE file name must be greater than 3 characters.
Specify an ASSEMBLE out_file name of greater than 3 characters.
Message facility ID pppp on line nnn was longer than 4 characters.
Facility ID must be exactly 3 characters long, with no blanks.
Specify a 3-character facility ID.
Message class on line nnn was not a valid message class type: IWESCFA.
Message class must be one of the valid message classes.
Specify a valid message class.
Tag not recognized on line nnn.
A tag that was not recognized was encountered.
Check the tag for proper spelling and use.
The first tag was not a :FACID. tag on line nnn.
The first tag of the SCRIPT file must be the facility ID tag.
Specify the facility ID tag as the first tag in the SCRIPT file.
Unexpected tag found on line nnn.
A valid tag was found in an unexpected location in the SCRIPT file; it is likely out of order.
Check the order of the tags in the SCRIPT file.
Duplicate tags ttt found on line nnn.
Duplicate :msgname., :msgclass., or :msgsubid. tags were found for a single message.
Remove the extra tag from the message script.
No :MSGNO. tags found within the given SCRIPT file.
A message file must have at least one message in it, and it must be denoted by a :msgno. tag.
Specify at least one message in the message file.
No :MSGCLASS. (or :MSGCL.) tag found for message nnnn.
A :msgclass. (or :msgcl.) tag was not found for message nnnn.
Specify a :msgclass. tag to indicate the severity code of the message and verify the tag is located after the :msgno. tag. Alternatively you can use the -c (CLASS) option to provide a default value for messages which have no :msgclass. (or :msgcl.) tag specified.
Insert number was not provided or was less than 1 on line nnn.
A positive insert number must be provided for each insert.
Specify a positive insert number of 9 or less for the insert.
Message subid was out of the range mmmm to mmmm on line nnn.
A message subid was found with a number outside the valid range. The current valid range is 0 to 9999.
Correct the invalid message subid on the given line of the SCRIPT file.
Existing secondary file, ssssssss, found, but not on A-disk.
A secondary file with the name ssssssss doe not exist on A-disk.
Make sure the name is given correctly and is accessible.
The current ADDRESS environment not CMS, TSO/E, or z/OS UNIX.
CEEBLDTX utility is not being executed in a supported environment.
Transport the utility to either CMS, TSO/E, or z/OS UNIX environment and try executing again.
Undefined error number nnn issued.
An undefined error was encountered.
Contact your service representative.