Runtime Messages Issued by the DDDL Generator

Runtime Error Messages › Runtime Messages Issued by the DDDL Generator

Runtime Messages Issued by the DDDL Generator

Nonfatal messages

```
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
```
The member name is missing as the operand of the LIBRARY option.
```
LINE EXCEEDS 72 CHARACTERS
```
The length of a generated DDDL statement exceeds 72 characters. The statement must be edited by the user before being input to the DDDL compiler.
```
MORE THAN 5 PROGRAMS IN GROUPING STATEMENT
```
A grouping statement specified more than five program names. The DDDL Generator accepted the first five, ignored the additional program names, and continued processing.
```
MORE THAN 100 DIFFERENT PROGRAMS CALLED - TABLE EXCEEDED
```
A program being processed by the DDDL Generator called more than 100 other different programs. The DDDL Generator generated ADD PROGRAM statements for the first 100 programs called, ignored additional program calls, and continued processing.
```
OPTION/SELECT NOT RECOGNIZED
```
A statement keyword is not valid as expressed.
```
TOO MANY LIBRARY NAMES
```
More than 99 library members are specified.

Fatal

```
BAD RETURN CODE -  module-name - return-code
```
The error originated in the named module (either IDMSUTIO or IDMSFLIO). The module issued the listed return code. The job 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.
```
OUTPUT FILE SYSPCH WILL NOT OPEN
```
The job ended with a user abend code of 2000. Check the JCL to see if SYSPCH is specified correctly.

Additional fatal messages

Note that the DDDL Generator 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 and in the JES message listing. When the DDDL Generator 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

Four examples of message text that can appear in the message are:

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.