EQQM972E EQQM975E
EQQM972E MCP WAS UNABLE TO ADD APPLICATION
APPL
BECAUSE AN MCP CONTROL BLOCK (MT0)
COULD NOT CONTAIN ALL SUCCESSOR DEPENDENCIES TO APPLICATION

SUCC

Explanation: The MCP service processor was unable to add any more successor dependencies to the MT0 block
that is used to define MCP processing. The maximum size of an MT0 block is 32768 bytes.
System action: MCP abandons the attempt to add current occurrence.
Problem determination: This message indicates that very many different operations in different applications have
defined operations in current application as external predecessors. If the message is unexpected, review the contents
of the AD data base and remove old predecessor definitions that should no longer be used.
User response: When using the MCP dialog to add new occurrences of the application defined by this message do
not request MCP to automatically add successor dependencies. The same recommendation applies if the occurrence
is being added as a result of ETT trigger processing or by a PIF program. Instead, add successor dependencies to
the occurrence after it has been added to the plan.
EQQM973I CATALOG MANAGEMENT HAS BEEN DISCARDED FOR THE FOLLOWING OPERATION: APPL:
APPL
IA:
IAD
IAT
OPERATION:
OPER
Explanation: Changing status from Error to Complete indicates that no catalog management action is needed. The
operation had the catalog management attribute set to deferred.
System action: The action is flagged as discarded for the operation.
User response: None.
EQQM974I CATALOG MANAGEMENT ACTION HAS STARTED FOR THE FOLLOWING OPERATION: APPL:
APPL
IA:
IAD
IAT
OPERATION:
OPER
Explanation: The catalog management action had already started when the status change request was done.
System action: The catalog management action continues until complete.The action statuses are set accordingly.
The operation status will be changed.
User response: None.
EQQM975E FAILED TO ADD APPLICATION
ADID
BECAUSE MAXIMUM NUMBER OF OCCURRENCES
REACHED. REQUESTING FUNCTION IS
FUNC
.
|Explanation: No more occurrences can be added to the Current Plan because the maximum number of
|occurrences—32767 or the number specified in the MAXOCCNUM option of the JTOPTS statement—has been
|reached.
ADID
identifies the application that failed to be added.
FUNC
identifies the function that requested the add,
and is one of the following:
A Automatic Recovery
D MCP dialog
EEvent Triggered Tracking
P Program Interface
System action: The request is rejected.
Problem determination: If you use ETT, PIF, or Automatic Recovery, check that these functions are working
correctly. For example, make sure that you do not have an endless ETT loop, where the availability of a special
resource is set to YES by a job that ETT adds, when it detects that this same resource is set to YES. Check the
Current Plan for instances of an unusually high number of occurrences of a particular application. If you see such an
application, look in the application description data base and make sure that the run cycles for the application are
correct. When you specify PREVRES(YES) on the BATCHOPT initialization statement, information about completed
and deleted occurrences is carried forward, for reporting purposes, into a new Current Plan. If your Current Plan
regularly contains a large number of occurrences, and you specify YES for PREVRES, you should consider changing
this value to NO.
User response: Check that the Current Plan does not contain any occurrences that should not be in the plan. If you
find any such occurrences, complete or delete them. Replan the Current Plan to remove all completed and deleted
Chapter 16. EQQMnnn Messages 211