Messages and Codes - e IBM Tivoli Composite - IBM

EQQM920E EQQM923I
EQQM920E EXTERNAL DEPENDENCY ALREADY EXISTS APPLICATION: APPL OPERATION: OPER
PREDECESSOR: PREDA OPERATION: PREDO
Explanation: A modify current plan request attempted to add a dependency that already exists.
The application IDs and operation numbers are listed. The operation numbers are given in hexadecimal form. Use
HEX ON when browsing the Tivoli OPC message log.
System action: The request is rejected and message EQQM025E is issued.
Problem determination: Dependency data has probably been changed during the dialog session.
| If the message is not in the controller message log, review the dump dataset (ddname EQQDUMP) for more
| information.
System programmer response: If the error reoccurs, investigate the failing occurrence to see if any abnormal
activities have been associated with it. Report the error to your IBM representative.
EQQM921E DELETE OF INTERNAL PREDECESSOR CONNECTION FAILED, REASON: RS APPLICATION:
APPL, IA, OPERATION: OPER, DEPENDENCY: PREOP
Explanation: A request for current plan modification would result in an invalid occurrence. The following reason
codes (RS) indicate why:
921 The last internal dependency cannot be deleted.
922 The delete would have resulted in a split into two networks.
923 The predecessor specification is not found.
System action: The request is rejected and the requestor is notified of the error with a message.
Problem determination: The last line of the message identifies the occurrence and the internal dependency that
was to be deleted.
| If the message is not in the controller message log, review the dump dataset (ddname EQQDUMP) for more
| information.
System programmer response: If the error reoccurs, investigate the failing occurrence to see if any abnormal
activities have been associated with it. Report the error to your IBM representative.
EQQM922E REQUEST TO DELETE SPECIAL RESOURCE THAT DOES NOT EXIST OPERATION: APPL, OPER
SPECIAL RESOURCE: SPR
Explanation: A modify current plan request to delete a special resource failed because the requested special
resource does not exist in the operation. The application ID and operation number are listed together with the special
resource name.
System action: The request is rejected and message EQQM025E is issued.
| Problem determination: If the message is not in the controller message log, review the dump dataset (ddname
| EQQDUMP) for more information.
User response: Check that the correct special resources are defined for the operation.
EQQM923I JOBLOG FOR JOBN (JOBNUM) ARRIVED
Explanation: You have made a catalog management request or a browse-joblog request on a Tivoli OPC subsystem
activated for step-level restart and where the required job logs are retrieved at the time of your request. Tivoli OPC
requested the tracker to retrieve the job log and SYSOUT has been returned to the controller.
System action: The message is displayed as a TSO broadcast message to the requesting user at the first
interaction after the message is sent.
User response: Either use the Catalog Management dialog to make a step-level restart or enter a browse-joblog
command.
252 Tivoli OPC Messages and Codes