EQQM314E EQQM322E
EQQM314E VALUE FOR PARALLEL SERVERS MUST BE 0 - 99
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQM315I INTERVAL PREVIEW
Explanation: Table result is merged from modified and planned intervals. The table is built from the modified and
planned intervals according to the workstation.
System action: Processing continues.
User response: The END command will cause the displayed table to be used. ENTER will cause the table to be
displayed without this message.
|EQQM316I PENDING STATUS RESET
|Explanation: The job for which the catalog management action has been invoked, contains no SYSOUT information,
|so that only a job level restart is possible. The job level restart does not require any action on the JOB data sets.
|However, some data sets (those in flushed steps or those allocated in the job but referenced in previous steps) need
|to be checked and removed from the CP before a rerun can be performed. Otherwise, the message EQQM323W
|CATALOG MANAGEMENT PENDING will be displayed.
|System action: Processing continues.
|User response: Make sure that the necessary datasets are discarded from the current plan.
EQQM320W DATASET AND JOBLOG INFORMATION ARE BOTH MISSING
Explanation: Information about datasets defined in the JCL and JES joblogs have not been passed back to the
controller. As a result, no catalog management action is possible. There are a number of reasons why you can
receive this message:
CATMGT(NO) was specified, or defaulted, in the OPCOPTS initialization statement when the operation started
The catalog management indicator for the operation specifies N
Dataset information for the operation has been filtered by EQQUX004
The job or started task did not alter the catalog status of any DD defined dataset.
System action: Processing continues.
User response: None.
EQQM321I THE CATALOG MANAGEMENT PROCESS HAS ALREADY BEEN STARTED
Explanation: You have tried to initiate the catalog management process for the current operation. The process has
already been started by TME 10 OPC, and cannot be started again.
System action: The request is ignored.
User response: None.
EQQM322E OPC/ESA CANNOT INITIATE THE CATALOG MANAGEMENT FUNCTION
Explanation: You have tried to initiate catalog management for the current operation, but the process cannot start.
This is because either TME 10 OPC has no contact with the tracker or the catalog management subtask is not active
at the controller.
System action: No catalog management action is initiated for this operation
User response: Contact your systems programmer.
System programmer response: Check whether the tracker at the destination defined for the current workstation is
operational or not. If it is not, retry the process when it becomes available again. Make sure that CATMGT(YES) is
specified on the OPCOPTS initialization statement of the controller, and that the controller, or catalog management
subtask, has been restarted since CATMGT(YES) was specified. Also check that the catalog management subtask
has not been stopped by an MVS modify command, or ended because of an error, after TME 10 OPC was started. If
the problem persists, contact your IBM representative.
Chapter 16. EQQMnnn Messages 189