Previous Topic

Next Topic

Book Contents

Book Index

Messages UPDJ00 through UPDJxx

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

UPDJ01E UPD INTERNAL ERROR. TYPE type

Explanation: An internal error of the specified type occurred during processing of the UPD subtask.

The Control-M Application Server shuts down.

Corrective Action: Contact BMC Customer Support.

UPDJ02E OVERRUN OF THE UPDATE MESSAGES QUEUE. TRANSMISSION TOO SLOW OR NOT ENOUGH MEMORY

Explanation: The storage available for database update messages is full.

New database update messages have overwritten old messages that have not yet been sent. This may be due to a lack of memory or may happen when a large number (usually several thousand) of update messages have been accumulated without being sent, due to slow transmission of the messages.

Slow transmission may be due to one of the following:

The Control-M Application Server shuts down.

Corrective Action: If message xxxJ07E (for example, UPDJ07E) precedes this message, implement the User Action from that message. Otherwise, determine where the bottleneck is and resolve it.

UPDJ03E ADD INTERNAL ERROR. TYPE type

Explanation: An internal error of the type type occurred during processing of the CTWADD subroutine.

The Control-M Application Server shuts down.

Corrective Action: Contact BMC Customer Support.

UPDJ04E DEL INTERNAL ERROR. TYPE type

Explanation: An internal error of the type type occurred during processing of the CTWDEL subroutine.

The Control-M Application Server shuts down.

Corrective Action: Contact BMC Customer Support.

UPDJ05E READ INTERNAL ERROR. TYPE type

Explanation: An internal error of the type type occurred during processing of the CTWREAD subroutine.

The Control-M Application Server shuts down.

Corrective Action: Contact BMC Customer Support.

UPDJ06E LOCK OF UPD CHAIN FAILED. STD=std FUNC=func

Explanation: Locking of the update messages chain has failed.

Access to the update messages chain is serialized by a locking mechanism. Subtask number std in function func attempted to lock the chain several times but was unsuccessful.

The Control-M Application Server shuts down.

Corrective Action: Contact BMC Customer Support.

UPDJ07E GETMAIN FOR UPD MESSAGE FAILED. OLDEST MESSAGE(S) WILL BE DELETED

Explanation: The storage available for database update messages is full.

New database update messages have overwritten old messages that have not yet been sent. This happens when a large number (usually several thousand) of update messages have been accumulated without being sent, due to slow transmission of the messages.

Slow transmission may be due to one of the following:

Storage space is made available for these messages by deleting the oldest message not yet sent. The Control-M Application Server continues processing. As long as there is a lack of storage space, old messages not yet sent will continue to be deleted to make room for new messages.

Corrective Action: Increase the storage space available by increasing the REGION size of the Control-M Application Server. If slow transmission is a problem, determine where the bottleneck is and resolve it.

UPDJ08E MAXIMUM MESSAGES IN UPD CHAIN REACHED. OLDEST MESSAGE WILL BE DELETED

Explanation: The storage available for database update messages is full.

New database update messages have overwritten old messages that have not yet been sent. This happens when a large number (usually several thousand) of update messages have been accumulated without being sent, due to slow transmission of the messages.

Slow transmission may be due to one of the following:

Storage space is made available for these messages by deleting the oldest message not yet sent. The Control-M Application Server continues processing. As long as there is a lack of storage space, old messages not yet sent will continue to be deleted to make room for new messages.

Corrective Action: Determine where the bottleneck is and resolve it.

UPDJ50I CTWUPD STARTED

Explanation: This information message indicates that the Control-M Application Server started the CTWUPD subtask.

Corrective Action: No action is required.

UPDJ51I LOGICAL CONNECTION IS SUSPENDED WHILE THE ACTIVE JOBS FILE IS BEING FORMATTED

Explanation: This information message indicates that the logical connection between the Control-M Application Server and the Workstation Gateway is temporarily suspended, because the Active Jobs file is currently being formatted.

The workstation database is not up-to-date, and no requests issued by the Enterprise Controlstation Control Application will be handled, until the format of the Active Jobs file is completed.

Corrective Action: No action is required.

UPDJ52I LOGICAL CONNECTION RESUMED

Explanation: This information message indicates that the logical connection between the Control-M Application Server and the Workstation Gateway has been resumed.

The workstation database may now request synchronization, and other requests issued by the Enterprise Controlstation Control Application will now be handled.

Corrective Action: No action is required.

UPDJ53I LOGICAL CONNECTION SUSPENDED DUE TO STOPLINK MODIFY COMMAND

Explanation: This information message indicates that the Control-M Application Server received a STOPLINK modify command.

The STOPLINK modify command causes disconnection until a STARTLINK modify command is received.

The Control-M Application Server stops transferring updates and disconnects from the Enterprise gateway.

Corrective Action: Enter a STARTLINK modify command.

UPDJ58E DATABASE UPDATES SENT TO THE WORKSTATION GATEWAY HAVE NOT BEEN CONFIRMED IN TIME

Explanation: The Control-M Application Server sent database updates to the Enterprise Controlstation Workstation Gateway, but did not receive confirmation for them in time.

This error message is issued by the Control-M Application Server program and is due to one of the following:

Corrective Action: Check if the workstation is hanging and if there are any error messages at the workstation which indicate the cause of the problem. If the workstation is not hanging, there must be some performance bottleneck in the system. Try to determine whether this bottleneck is at the workstation side, in the communication media, or at the mainframe.

UPDJ59E CONFIRMATION SEQUENCE NUMBER ERROR. EXPECTED=exp_num RECEIVED=rcv_num

Explanation: The Control-M Application Server has received an out of sequence confirmation of a database update.

This error message is issued by the Control-M Application Server. The Mainframe Gateway expects to receive confirmations for database updates in increasing order, but a confirmation with a sequence number of rcv_num has been received, when a confirmation with a sequence number of at least exp_num was expected.

The Control-M Application Server continues executing.

Corrective Action: Contact BMC Customer Support.

UPDJ60E DATA BASE UPDATE TYPE msgType HAS BEEN REJECTED BY THE WORKSTATION GATEWAY

Explanation: The Enterprise Controlstation gateway rejected a message of the msgType type from the Control-M Application Server.

This message is issued each time a database update message is rejected by the Enterprise Controlstation gateway.

Possible values for msgType are:

msgType

Meaning

A

Update of full Active Jobs file record.

B

Short update of an Active Jobs file record.

N

New job that was added to the Active Jobs file.

O

Update of full Active Jobs file record.

X

Update of only the fixed part of an active jobs.

C

Condition update.

R

Control resource update.

Q

Quantitative resource update.

T

Alert (Shout message) to workstation.

The gateway continues processing. Rejected database updates are written to the file referenced by the DASNAP DD statement.

Corrective Action: Look for error messages on the workstation side and correct the problem accordingly. Review the rejected database updates in the file referenced by DASNAP.

Parent Topic

UPD messages