Runtime Message Issued by the Cross Reference Processor

Runtime Error Messages › Runtime Message Issued by the Cross Reference Processor

Runtime Message Issued by the Cross Reference Processor

Nonfatal

```
ILLEGAL ALIAS FOR PROG-ID
```
The name following the equal sign (=) in the LIBRARY option in the parameter statement is missing.
```
ILLEGAL DELIMITER
```
Statement keywords are not delimited by the required comma or blank.
```
ILLEGAL MEMBER NAME
```
Member name is missing as the operand of the LIBRARY option in the parameter statement.
```
ILLEGAL PROGRAM-ID 'NEW NAME'
```
The name following the equal sign (=) in the PROGRAM-ID option in the parameter statement is missing.
```
OPTION/SELECT NOT RECOGNIZED
```
A statement keyword is not valid as expressed.
```
TOO MANY LIBRARY NAMES
```
More than 99 library members are specified.
```
TOO MANY PROGRAM-IDS
```
More than 39 source program names are changed to new names in the PROGRAM-ID option.

Fatal

```
BAD IDMSUTIO RETURN CODE - PARMINTF - return-code - CSFCDSPL
```
IDMSUTIO issued the reported return code; the job ended with a user abend code of 100. This message reports a system internal error; rerun the job.
```
BAD RETURN CODE - module-name - return-code
```
The error originated in the named module (either IDMSUTIO or IDMSDLIO). The module issued the listed return code. The jog ended with a user abend code of 100. This message reports a system internal error; rerun the job.
```
INPUT FILE PRANREF WILL NOT OPEN
```
The job ended with a user abend code of 2000. Check the JCL to see if PRANREF is specified correctly.
```
INPUT FILE SYSIPT WILL NOT OPEN
```
The job ended with a user abend code of 2000. Check the JCL to see if SYSIPT is specified correctly.
```
MEMBER NOT FOUND IN LIBRARY (z/VSE users only)
```
The job ended with a user abend code of 100. Check the member name specified in the LIBRARY option.
```
OUTPUT FILE SYSLST WILL NOT OPEN
```
The job ended with a user abend code of 2000. Check the JCL to see if SYSLST is specified correctly.

Other fatal messages

Note that the Cross Reference Processor may issue an additional class of fatal messages. These messages are generated by the utility module IDMSSORT and report system internal errors.

IDMSSORT messages

IDMSSORT error messages are write-to-operator messages that are displayed on the console log. When the Cross Reference Processor transmits an IDMSSORT message, the run abends with a user abend code of 3134 and a two-line message appears in the following format:

+IDMS 999000L IDMSSORT -  message-text
+IDMS 208001L 0100

Examples

Four examples of message text that can appear in this message are shown below:

INVALID KEYWORD PASSED TO IDMSSORT
UNSUPPORTED SORT CONTROL STATEMENT PASSED
NO keyword-type KEYWORD ON SORT record-name STATEMENT
NO keyword-length KEYWORD ON SORT record-name STATEMENT

Although the user cannot take corrective action to resolve IDMSSORT error conditions (because such errors are system internal), the user can retry the run. In some cases, the internal error will disappear. If the error condition persists, consult with the person responsible for tracking system errors.