Abend codes and error messages for DFH$MOLS

Start of changeThe DFH$MOLS program can fail with one of the following abend codes or error messages. Note that abend codes 111 and 115 are no longer used, because the input monitoring data is always sorted before processing.End of change

101
INVALID, DUPLICATE, OR MISSING CONTROL CARD INFORMATION
Explanation:

The DFH$MOLS control statement scan routines produce this message. It occurs immediately after processing an invalid control card, and the last control statement printed contains the error. Some of the causes are:

The message is followed by a U101 abend, without a dump.

102
ERROR - INCOMPATIBLE CONTROL CARD OPTIONS REQUESTED
Explanation:

Some of the selected control statement options are in conflict. The DFH$MOLS program has detected that the stop date specified on the DATE control statement is before the start date on the DATE control statement.

The error is followed by a U102 abend without a dump.

103
SORT ENDED WITH NON-ZERO RET CODE; REPORT IS TERMINATED
Explanation:

The MVS™ SORT utility has returned an error code after being invoked. This may be due to missing or incorrect job control statements. The SORT utility writes a message to SYSOUT defining the error.

The message is followed by an MVS abend U103, with a dump.

104
NO DATA FOR THIS CICS DATA SECTION; REPORT IS TERMINATED
Explanation:

The DFH$MOLS program has detected a CICS 110 monitoring record that does not contain any data rows within the data section. The DFH$MOLS program detects this by validating the contents for field SMFMNDRN in the SMF product section.

The message is followed by an MVS abend U104 with a dump.

105
UNKNOWN CLASS IN CICS DATA SECTION; REPORT IS TERMINATED
Explanation:

The DFH$MOLS program has detected a CICS 110 monitoring record that does not contain a valid data section. The DFH$MOLS program detects this by validating the contents for field SMFMNCL in the SMF product section, which should indicate that the data section contains either dictionary data, performance data, transaction resource data, or exception data.

The message is followed by an MVS abend U105 with a dump.

106
NO VALID MONITORING RECORDS WERE READ; REPORT IS TERMINATED
Explanation:

There is no valid CICS monitoring data in the input data set.

The message is followed by an MVS abend U106, without a dump.

107
NO MONITORING RECORDS WERE SELECTED FOR PROCESSING; REPORT IS TERMINATED
Explanation:

Valid CICS monitoring records have been read, but no records are eligible for processing because of SELECT/IGNORE control statements.

This message is followed by an MVS abend U107 without a dump.

108
X‘nnnn’ - CONNECTOR NOT DEFINED; REPORT IS TERMINATED
Explanation:

A CICS 110 monitoring performance class record has a connector number that is not in the current dictionary.

This message is followed by an MVS abend U108 with a dump.

109
NO DICTIONARY ESTABLISHED; REPORT IS TERMINATED
Explanation:

The first CICS 110 monitoring performance class record read by the DFH$MOLS program has not been preceded by the corresponding dictionary record. This abend is issued if a dictionary record does not exist or if the dictionary record, created by DFHMNDUP, has a DATE (SMF record date: SMFMNDTE) and TIME (SMF record time: SMFMNTME) later than the DATE and TIME of the first monitoring record read. DFH$MOLS sorts the monitoring data into the sequence described below to enable it to process the data correctly.

The DFH$MOLS program must establish a dictionary record for each APPLID before it can correctly analyze any associated monitoring performance class records. (See Monitoring dictionary utility program (DFHMNDUP) and Monitoring dictionary record.)

This message is followed by an MVS abend U109 without a dump.

110
NO DICTIONARY ESTABLISHED FOR NEW APPLID xxxxxxxx; REPORT IS TERMINATED
Explanation:

The DFH$MOLS program has detected a change of APPLID in CICS 110 monitoring performance class data before it has read the corresponding dictionary record for the new APPLID. The DFH$MOLS program must establish the new dictionary record for the new APPLID before it can correctly analyze any associated monitoring performance class records.

This message is followed by an MVS abend U110 without a dump.

112
There is no message text, but MVS abends U112 without a dump.
Explanation:

The DFH$MOLS program was unable to open the data set specified on the SYSPRINT DD statement. Ensure that the JCL for the job is correct. A sample set of JCL to execute the DFH$MOLS sample program is contained in Figure 35.

113
UNABLE TO OPEN DDNAME ‘INPUT’; REPORT IS TERMINATED
Explanation:

The DFH$MOLS program was unable to open the data set specified on the INPUT DD statement. Ensure that the JCL for the job was correct. A sample set of JCL to execute the DFH$MOLS sample program is contained in Figure 35.

This message is followed by an MVS abend U113 without a dump.

114
UNABLE TO OPEN DDNAME ‘xxxxxxxx’; REPORT IS TERMINATED
Explanation:

The DFH$MOLS program was unable to open the data set specified on the DD statement used for the UNLOAD control statement. ‘xxxxxxxx’ is either SYSUT4, the default, or the ddname specified by the DDNAME= parameter on the UNLOAD control statement. Ensure that the JCL for the job was correct. A sample set of JCL to execute the DFH$MOLS sample program is contained in Figure 35.

This message is followed by an MVS abend U114 without a dump.

Related reference
Sample monitoring data print program (DFH$MOLS)
Sample job stream for DFH$MOLS
Control statements of DFH$MOLS -- overview
Rules for coding DFH$MOLS control statements
DFH$MOLS control statement descriptions
[[ Contents Previous Page | Next Page Index ]]