Topic manager messages (CSQT...)
- CSQT806I
csect-name Queued Pub/Sub Daemon started
- Severity
- 0
- Explanation
Queued Pub/Sub Daemon started
- System action
None
- System programmer response
None
- CSQT807I
csect-name Queued Pub/Sub Daemon ended
- Severity
- 0
- Explanation
The Queued Pub/Sub Daemon has ended.
- System programmer response
None
- CSQT809E
csect-name Unable to process publication, Queued Pub/Sub stream queue queue-name is GET(DISABLED)
- Severity
- 8
- Explanation
The stream queue, queue-name, has been GET(DISABLED) preventing the Queued Pub/Sub Daemon from processing publication messages.
- System action
The Queued Pub/Sub Daemon will continue to process publication messages on other stream queues and subscriptions on all streams.
- System programmer response
To resume processing publication messages alter the stream queue to be GET(ENABLED).
To quiesce the stream remove its name from SYSTEM.QPUBSUB.QUEUE.NAMELIST.
To quiesce the Queued Pub/Sub Daemon alter the queue manager to have PSMODE(COMPAT).
- CSQT810E
csect-name Unable to process subscription requests, Queued Pub/Sub control queue is GET(DISABLED)
- Severity
- 8
- Explanation
The SYSTEM.BROKER.CONTROL.QUEUE has been GET(DISABLED) preventing the Queued Pub/Sub Daemon from processing subscription requests.
- System action
The Queued Pub/Sub Daemon will continue to process publication messages on stream queues.
- System programmer response
To resume processing subscription requests alter the SYSTEM.BROKER.CONTROL.QUEUE to be GET(ENABLED).
To quiesce the Queued Pub/Sub Daemon alter the queue manager to have PSMODE(COMPAT).
- CSQT814E
csect-name Unable to resolve parent queue_manager_name
- Severity
- 8
- Explanation
In establishing a publish/subscribe hierarchy, the Queued Pub/Sub Daemon has been unable to resolve the parent queue_manager_name.
- System action
The status of the publish/subscribe parent connection will be set to error.
- System programmer response
Check that the parent queue manager is correctly specified.
Ensure that broker is able to resolve the queue manager name of the parent broker.
To resolve the queue manager name, at least one of the following resources must be configured:
- A transmission queue with the same name as the parent queue manager name.
- A queue manager alias definition with the same name as the parent queue manager name.
- A cluster with the parent queue manager a member of the same cluster as this queue manager.
- A cluster queue manager alias definition with the same name as the parent queue manager name.
- A default transmission queue, modify the parent queue manager name to blank, then set with the parent queue manager name.
- CSQT816E
csect-name Unable to open Queued Pub/Sub control queue MQCC=mqcc MQRC=mqrc (mqrc-text)
- Severity
- 8
- Explanation
The queue manager failed to open the Queued Publish/Subscribe control queue, SYSTEM.BROKER.CONTROL.QUEUE. The attempt to open the queue failed with completion code mqcc and reason mqrc. The most likely reasons for this error are that an application program has opened the control queue for exclusive access, or that the control queue has been defined incorrectly.
- System action
The Queued Publish/Subscribe Daemon terminates.
- System programmer response
Refer to API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form), then correct the problem and restart the Queued Publish/Subscribe interface.
- CSQT817E
csect-name An invalid stream queue has been detected, queue queue-name
- Severity
- 8
- Explanation
- The Pub/Sub Daemon attempted to use queue queue-name as a stream queue. The most likely reason for this error is that the queue is:
- Not a local queue.
- A shareable queue.
- A temporary dynamic queue.
- System programmer response
Correct the problem with the queue queue-name or, if we do not intend to use it as a stream queue, remove it from the namelist SYSTEM.QPUBSUB.QUEUE.NAMELIST.
- CSQT818E
csect-name Unable to open Queued Pub/Sub stream, queue queue-name MQCC=mqcc MQRC=mqrc (mqrc-text)
- Severity
- 8
- Explanation
- The queue manager has failed to open a stream queue queue-name. The attempt to open the queue failed with completion code mqcc and reason mqrc. The most likely reasons for this error are:
- A new stream name has been added to SYSTEM.QPUBSUB.QUEUE.NAMELIST but the stream queue does not exist.
- An application has the queue open for exclusive access.
- System programmer response
Refer to API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form).
- CSQT819E
csect-name Queued Pub/Sub stream stream-name ended abnormally, reason=mqrc
- Severity
- 8
- Explanation
The Pub/Sub Daemon stream (stream-name) has ended abnormally for reason mqrc. The mqrc could be an internal return code. The queue manager will attempt to restart the stream. If the stream should repeatedly fail then the Pub/Sub Daemon will progressively increase the time between attempts to restart the stream.
- System programmer response
Investigate why the problem occurred and take appropriate action to correct the problem. If the problem persists, save any generated output files and use the MQ Support site to see whether a solution is already available. If you are unable to find a match, contact your IBM® support center.
- CSQT820E
csect-name Queued Pub/Sub stream stream-name restarted
- Severity
- 8
- Explanation
The queue manager has restarted a stream that ended abnormally. This message will frequently be preceded by message CSQT819E indicating why the stream ended.
- System programmer response
Correct the problem.
- CSQT821E
csect-name Unable to contact parent queue_manager_name, reason=mqrc
- Severity
- 8
- Explanation
In establishing a publish/subscribe hierarchy, the Queued Pub/Sub Daemon is unable to send a message to the parent queue_manager_name for reason mqrc.
- System action
The status of the publish/subscribe parent connection will be set to error.
- System programmer response
Investigate why the problem occurred and determine a resolution.
To reattempt a parent queue manager connection:
- Set the parent queue manager name to blank.
- Take appropriate action to correct the problem.
- Re-specify the parent queue manager name
- CSQT822E
csect-name Failed to register with parent queue_manager_name, reason mqrc (mqrc-text)
- Severity
- 8
- Explanation
The Queued Pub/Sub Daemon started and the PARENT queue manager was set to queue_manager_name in a queue manager attribute. The queue manager attempted to register as a child of the parent, but received an exception response indicating that it was not possible. The queue manager will retry to register periodically as a child. The child may not be able to process global publications or subscriptions correctly until this registration process has completed normally.
- System programmer response
Investigate why the problem occurred and take appropriate action to correct the problem. The problem is likely to be caused by the parent queue manager not yet existing, or a problem with the transmission queue at the parent queue manager.
- CSQT824I
csect-name Topic topic-1 is dependent on PROXYSUB(FORCE) of topic topic-2 from a different Pub/Sub hierarchy stream
- Severity
- 4
- Explanation
Topic object topic-1 is a publish/subscribe hierarchy stream. Topic object topic-2 is higher in the topic tree and has been configured with PROXYSUB(FORCE), which results in a single wildcard proxy subscription being sent to the neighboring queue managers in the publish/subscribe hierarchy that support the topic-2 stream. No further individual proxy subscriptions will be sent for any subscriptions made below topic-2 in the topic tree, including below topic object topic-1. If a neighboring queue manager supports the topic-1 stream, but not the topic-2 stream, publications will not be sent to subscriptions to topic topic-1 on this queue manager from that neighbor.
- System programmer response
If the behavior described in the explanation is intended then no action is required. If not, alter the PROXYSUB attribute on topic topic-1, or topic-2, so both, or neither topics, are configured with the value FORCE.
- CSQT826E
csect-name Failed to propagate subscription, stream stream-name, to queue manager qm-name, MQCC=mqcc MQRC=mqrc (mqrc-text)
- Severity
- 8
- Explanation
The queue manager failed to propagate subscription to stream stream-name at queue manager queue_manager_name with reason code mqrc. An application has either registered or unregistered a subscription to stream stream-name. The queue manager has attempted to propagate the subscription change to the queue manager, but the request has not been successful. Messages published on the stream through the queue manager might not reach this queue manager.
- System programmer response
Refer to API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form).
Investigate why the problem occurred and take appropriate action to correct the problem.
Use the following command to refresh proxy subscriptions:REFRESH QMGR TYPE(PROXYSUB)
- CSQT827E
csect-name Queued Pub/Sub internal subscription failed. Stream stream-name to queue manager queue_manager_name reason=reason MQRC= mqrc
- Severity
- 8
- Explanation
The queue manager failed to subscribe to stream stream-name at queue manager queue_manager_name with reason code mqrc. Related queue managers learn about each others configuration by subscribing to information published by each other. A queue manager discovered that one of these internal subscriptions has failed. The queue manager will reissue the subscription immediately. The queue manager cannot function correctly without knowing some information about neighboring queue managers. The information that this broker has about queue manager queue_manager_name is not complete and this could lead to subscriptions and publications not being propagated around the network correctly.
- System programmer response
Investigate why the problem occurred and take appropriate action to correct the problem. The most likely cause of this failure is a problem with the transmission queue at the queue manager queue_manager_name or a problem with the definition of the route between this queue manager and queue manager queue_manager_name
- CSQT831E
csect-name Unable to make subscription, reason=mqrc (mqrc-text), subscription name sub-name, topic topic-string
- Severity
- 8
- Explanation
A failure occurred while attempting to create a subscription to topic string topic-string using the subscription name sub-name. The associated reason code is mqrc. The mqrc could be an internal return code.
- System programmer response
Refer to API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form).
- CSQT833E
csect_name Queue manager queue_manager_name introduced a loop into the Pub/Sub hierarchy
- Severity
- 8
- Explanation
The queue manager queue_manager_name introduced a loop in the Pub/Sub hierarchy. The Queued Publish/Subscribe Daemon on this queue manager will terminate immediately.
- System programmer response
Remove queue manager queue_manager_name from the hierarchy, either by deleting the queue manager, or by removing knowledge of the queue manager's parent, using the ALTER QMGR PARENT(' ') command, or in exceptional circumstances, RESET QMGR TYPE(PUBSUB) PARENT( queue_manager_name).
- CSQT834E
csect-name Conflicting queue manager names in the Pub/Sub hierarchy
- Severity
- 8
- Explanation
The names of the queue managers (queue_manager_name) and (queue_manager_name) in the Pub/Sub hierarchy both start with the same 12 characters. The first 12 characters of a queue manager name should be unique to ensure that no confusion arises within the hierarchy, and to guarantee unique message ID allocation.
- CSQT835E
csect-name Unable to inform parent parent-name of new relation queue_manager_name, reason=mqrc (mqrc-text)
- Severity
- 8
- Explanation
The queue manager failed to notify its parent queue manager parent-name of the relation queue_manager_name in the Pub/Sub hierarchy. The notification message will be put to the parent's dead-letter queue. A failure to notify a queue manager of a new relation will mean that no loop detection can be performed for the new relation.
- System programmer response
Diagnose and correct the problem on the parent queue manager. One possible reason for this is that the parent queue manager does not yet exist.
- CSQT836E
csect-name Duplicate queue manager name queue_manager_name located in the Pub/Sub hierarchy
- Severity
- 8
- Explanation
Multiple instances of the queue manager name queue_manager_name have been located. This could either be the result of a previously resolved loop in the Pub/Sub hierarchy, or multiple queue managers in the Pub/Sub hierarchy having the same name.
- System programmer response
If this queue manager introduced a loop in the hierarchy (typically identified by message CSQT833E), this message can be ignored. It is strongly recommended that every queue manager in a Pub/Sub hierarchy has a unique name. It is not recommended that multiple queue managers use the same name.
- CSQT839E
csect-name Unexpected topology information received from queue manager queue_manager_name
- Severity
- 8
- Explanation
A queue manager has received a distributed publish/subscribe communication that it did not expect. The message was sent by queue manager queue_manager_name. The message will be processed according to the report options in that message. The most likely reason for this message is that the queue manager topology has been changed while distributed publish/subscribe communication messages were in transit (for example, on a transmission queue) and that a message relating to the previous queue manager topology has arrived at a queue manager in the new topology. This message may be accompanied by an informational FFST including details of the unexpected communication.
- System programmer response
If the queue manager topology has changed and the queue manager named in the message is no longer related to the queue manager issuing this message, this message can be ignored. If the RESET QMGR TYPE(PUBSUB) command was issued to unilaterally remove knowledge of queue manager queue_manager_name from this queue manager, the RESET QMGR TYPE(PUBSUB) command should also be used to remove knowledge of this queue manager from queue manager queue_manager_name.
- CSQT844E
csect-name The relation with queue_manager_name is unknown
- Severity
- 8
- Explanation
The RESET QMGR TYPE(PUBSUB) command has been issued in an attempt to remove a queue manager's knowledge of a relation of that queue manager. The relative queue_manager_name is unknown at queue manager queue_manager_name. If the parent KEYWORD was specified, the queue manager does not currently have a parent. If the CHILD keyword was specified, the queue manager does not recognize the named child.
- System programmer response
Investigate why the queue manager is unknown.
- CSQT848E
csect-name Failed to register proxy subscription for queue manager qmgr-name, stream stream-name, topic string topic-string, reason=mqrc (mqrc-text)
- Severity
- 8
- Explanation
The queue manager received a proxy subscription request for stream stream-name and topic topic-string from queue manager qmgr-name. The attempt to register the subscription was unsuccessful for reason mqrc (mqrc-text provides the MQRC in textual form). Messages published upon this topic will not be delivered to subscriptions on the relation queue manager.
- System programmer response
Use the reason code to investigate why the failure occurred and take appropriate action to correct the problem. Use the command REFRESH QMGR TYPE(PROXYSUB) on the relation queue manager to refresh it's proxy subscriptions.
- CSQT852E
csect-name Unable to propagate delete publication command, topic topic-name, stream stream-name, to queue manager queue_manager_name, reason=mqrc (mqrc-text)
- Severity
- 8
- Explanation
The queue manager failed to propagate delete publication command for stream stream-name to related queue manager queue_manager_name for reason mqrc. When an application issues a delete publication command to delete a global publication, the command has to be propagated to all queue managers in the sub-hierarchy supporting the stream. The queue manager reporting the error has failed to forward a delete publication command to a related queue manager queue_manager_name who supports stream stream-name. Delete publication commands are propagated without MQRO_DISCARD_MSG and the command message might have been written to a dead-letter queue. The topic for which the delete publication has failed is topic-name.
- System programmer response
Refer to API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form).
If the delete publication has failed because the stream has been deleted at the related queue manager, this message can be ignored. Investigate why the delete publication has failed and take the appropriate action to recover the failed command.
- CSQT853E
csect-name Unable to propagate delete publication command, topic topic-name, stream stream-name, relation relation-name, reason = mqrc (mqrc-text)
- Severity
- 8
- Explanation
The queue manager failed to propagate a delete publication command for stream stream-name to a previously related queue manager relation-name. In some cases the stream or the relation cannot be determined and so is shown as '????'.
When an application issues a delete publication command to delete a global publication, the command is propagated to all queue managers in the sub-hierarchy supporting the stream. The queue manager topology was changed after deleting the publication, but before a queue manager removed by the topology change processed the propagated delete publication message. The topic for which the delete publication has failed is topic-name. In some cases the topic cannot be determined and so is shown as '????'.
- System programmer response
Refer to API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form).
It is the user's responsibility to quiesce queue manager activity before changing the queue manager topology using the RESET QMGR TYPE(PUBSUB) command. Investigate why this delete publication activity was not quiesced. The delete publication command will have been written to the dead-letter queue at the queue manager that was removed from the topology. In this case, further action might be necessary to propagate the delete publication command that was not quiesced before the RESET QMGR TYPE(PUBSUB) command was issued.
- CSQT854E
csect-name Unable to propagate delete publication command, topic topic-name, stream stream-name to queue manager queue_manager_name
- Severity
- 8
- Explanation
When an application issues a delete publication command, the command has to be propagated to all queue managers in the sub-hierarchy supporting the stream. At the time the delete publication was propagated, queue manager queue_manager_name was a known relation of this message queue manager supporting stream stream-name. Before the delete publication command arrived at the related queue manager, the queue manager topology was changed so that queue manager queue_manager_name no longer supported stream stream-name. The topic for which the delete publication has failed is topic-name.
- System programmer response
It is the user's responsibility to quiesce queue manager activity before changing the stream topology of the queue manager. Investigate why this delete publication activity was not quiesced. The delete publication command will have been written to the dead-letter queue at queue manager queue_manager_name.
- CSQT855E
csect-name Queued Pub/Sub Daemon failed, reason=mqrc
- Severity
- 8
- Explanation
An attempt has been made to run the queued publish/subscribe interface (Queued Pub/Sub Daemon) but the interface has ended for reason mqrc.
If mqrc is a number in the range of 2000 - 3000, it is an API reason code. If it is of the form 5nnn, it is a queued publish/subscribe message code associated with the message CSQT nnnE, which is normally issued previously.
- System programmer response
If mqrc is an API reason code, see API completion and reason codes for more information about the mqrc. If mqrc is a queued publish/subscribe message code, see the corresponding message explanation for more information. Where no such message exists, see Queued Publish/Subscribe message codes for the corresponding message number.
Determine why the queued publish/subscribe daemon ended. The message logs for the Channel Initiator might contain more detailed information about why the queued publish/subscribe daemon cannot be started. Resolve the problem that is preventing the daemon from completing and restart the Channel Initiator.
- CSQT856E
csect-name Unable to process publish command message for stream stream-name, reason=mqrc (mqrc-text)
- Severity
- 8
- Explanation
The Queued Pub/Sub Daemon failed to process a publish message for stream stream-name. The queue manager was unable to write the publication to the dead-letter queue and was not permitted to discard the publication. The queue manager will temporarily stop the stream and will restart the stream and consequently retry the publication after a short interval.
- System programmer response
Investigate why the error has occurred and why the publication cannot be written to the dead-letter queue. Either manually remove the publication from the stream queue, or correct the problem that is preventing the queue manager from writing the publication to the dead-letter queue.
- CSQT857E
csect-name Unable to process control command message, reason=mqrc (mqrc-text)
- Severity
- 8
- Explanation
The Queued Pub/Sub Daemon failed to process a command message on the SYSTEM.BROKER.CONTROL.QUEUE. The queue manager was unable to write the command message to the dead-letter queue and was not permitted to discard the command message. The queue manager will temporarily stop the stream and will restart the stream and consequently retry the command message after a short interval. Other queue manager control commands cannot be processed until this command message has been processed successfully or removed from the control queue.
- System programmer response
Investigate why the error has occurred and why the command message cannot be written to the dead-letter queue. Either, manually remove the command message from the stream queue, or correct the problem that is preventing the broker from writing the command message to the dead-letter queue.
- CSQT858E
csect-name Unable to send publication to subscriber queue, queue queue-name, to queue manager queue_manager_name, reason=mqrc (mqrc-text)
- Severity
- 8
- Explanation
A failure has occurred sending a publication to subscriber queue queue-name at queue manager queue_manager_name for reason mqrc. The broker configuration options prevent it from recovering from this failure by discarding the publication or by sending it to the dead-letter queue. Instead the queue manager will back out the unit of work under which the publication is being sent and retry the failing command message a fixed number of times. If the problem still persists, the queue manager will then attempt to recover by failing the command message with a negative reply message. If the issuer of the command did not request negative replies, the queue manager will either discard or send to the dead-letter queue the failing command message. If the queue manager configuration options prevent this, the queue manager will restart the affected stream, which will reprocess the failing command message again. This behavior will be repeated until such time as the failure is resolved. During this time the stream will be unable to process further publications or subscriptions.
- System programmer response
Refer to API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form).
Usually the failure will be due to a transient resource problem, for example, the subscriber queue, or an intermediate transmission queue, becoming full. Use reason code mqrc to determine what remedial action is required. If the problem persists for a long time, you will notice the stream being continually restarted by the queue manager. Evidence of this occurring will be a large number of CSQT820E messages, indicating stream restart, being written to the Channel Initiator log. In such circumstances, manual intervention will be required to allow the queue manager to dispose of the failing publication. To do this, you will need to end the Queued Pub/Sub Daemon using the ALTER QMGR PSMODE(COMPAT), change the appropriate queue manager attributes; PSNPMSG, PSNPRES, PSSYNCPT, and restart it using ALTER QMGR PSMODE(ENABLED). This will allow the publication to be sent to the rest of the subscribers, while allowing the Queued Pub/Sub Daemon to discard or send to the dead-letter queue the publication that could not be sent.
- CSQT859E
csect-name Queued Pub/Sub stream stream-name terminating, reason=mqrc (mqrc-text)
- Severity
- 8
- Explanation
The stream stream-name has run out of internal resources and will terminate with reason code mqrc (mqrc-text provides the MQRC in textual form). If the command in progress was being processed under syncpoint control, it will be backed out and retried when the stream is restarted by the queue manager. If the command was being processed out of syncpoint control, it will not be able to be retried when the stream is restarted.
- System programmer response
This message should only be issued in very unusual circumstances. If this message is issued repeatedly for the same stream, and the stream is not especially large in terms of subscriptions, topics, and retained publications, save all generated diagnostic information and use either the IBM MQ Support site, or IBM Support Assistant (ISA) to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.
- CSQT864E
csect-name Unable to put a reply message, queue queue-name queue manager(qm-name) MQCC=mqcc MQRC=mqrc (mqrc-text)
- Severity
- 8
- Explanation
While processing a publish/subscribe command, the queue manager could not send a reply message to the queue queue-name at the queue manager qm-name for MQRC=mqrc. The queue manager was also unable to write the message to the dead-letter queue. Since the command is being processed under syncpoint control, the queue manager will attempt to retry the command in the hope that the problem is only of a transient nature. If, after a set number of retries, the reply message still could not be sent, the command message will be discarded if the report options allow it. If the command message cannot be discarded, the stream will be restarted, and processing of the command message recommenced.
- System programmer response
Refer to API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form).
Use reason code mqrc to determine what remedial action is required. If the failure is due to a resource problem (for example, a queue being full), you might find that the problem has already cleared itself. If not, this message will be issued repeatedly each time the command is retried. In this case you are strongly advised to define a dead-letter queue to receive the reply message so that the Queued Pub/Sub Daemon can process other commands while the problem is being investigated. Check the application from which the command originated and ensure that it is specifying its reply-to queue correctly.
- CSQT866E
csect-name Queued Pub/Sub command message discarded. Reason=mqrc (mqrc-text)
- Severity
- 8
- Explanation
The queue manager failed to process a publish/subscribe command message, which has now been discarded. The queue manager will begin to process new command messages again.
- System programmer response
Look for previous error messages to indicate the problem with the command message. Correct the problem to prevent the failure from happening again.
- CSQT875E
csect-name Unable to put message to the dead-letter-queue, reason=mqrc (mqrc-text) (DLH reason=mqrc2 (mqrc2-text))
- Severity
- 8
- Explanation
The queue manager attempted to put a message to the dead-letter queue queue-name but the message could not be written to the dead-letter queue for reason mqrc (mqrc-text provides the MQRC in textual form). The message was being written to the dead-letter-queue with a reason of mqrc2 (mqrc2-text provides the MQRC in textual form).
- System programmer response
Determine why the message cannot be written to the dead-letter-queue. Also, if the message was not deliberately written to the dead-letter-queue, for example by a channel exit, determine why the message was written to the dead-letter-queue and resolve the problem that is preventing the message from being sent to its destination.
- CSQT876E
csect-name Parent conflict detected in Pub/Sub hierarchy with queue manager queue_manager_name
- Severity
- 8
- Explanation
The queue manager queue_manager_name has been started, naming this queue manager as its parent. This queue manager has already named queue manager queue_manager_name as its parent. The queue manager will send an exception message to the queue manager queue_manager_name indicating that a conflict has been detected. The most likely reason for this message is that the queue manager topology has been changed while distributed publish/subscribe communication messages were in transit (for example, on a transmission queue) and that a message relating to the previous queue manager topology has arrived at a queue manager in the new topology. This message might be accompanied by an informational FFST including details of the unexpected communication.
- System programmer response
If the queue manager topology has changed and the queue manager named in the message no longer identifies this queue manager as its parent, this message can be ignored - for example, if the command ALTER QMGR PARENT(' ') was issued. If queue manager queue_manager_name has been defined as this queue manager's parent, and this queue manager has been defined as queue manager queue_manager_name's parent, the ALTER QMGR command should be used to resolve the conflict by specifying the correct PARENT.
- CSQT882E
csect-name Message written to the dead-letter queue, for reason=mqrc (mqrc-text)
- Severity
- 8
- Explanation
The queue manager has written a message to the dead-letter queue for reason mqrc (mqrc-text provides the MQRC in textual form). Note. After the first occurrence of this message for a stream, it will only be written periodically.
- System programmer response
Determine why the message was written to the dead-letter queue, and resolve the problem that is preventing the message from being sent to its destination.
- CSQT883E
csect-name Queued Pub/Sub state not recorded
- Severity
- 0
- Explanation
The Queued Pub/Sub state on stream stream-name not recorded while processing a publication outside of syncpoint. A nonpersistent publication has requested a change to either a retained message or a publisher registration. This publication is being processed outside of syncpoint because the queue manager has been configured with the queue manager attribute PSSYNCPT set to IFPER. A failure has occurred hardening either the publisher registration or the retained publication to the queue manager's local queue. All state changes attempted as a result of this publication will be backed-out. Processing of the publication will continue and the queue manager will attempt to deliver it to all subscribers.
- System programmer response
Investigate why the failure occurred. It is probably due to a resource problem occurring on the queue manager. The most likely cause is 'queue full' on a queue. If your publications also carry state changes, you are advised to send them either as persistent publications or set the queue manager attribute PSSYNCPT to YES. In this way, they will be carried out under syncpoint and the queue manager can retry them in the event of a failure such as this.
- CSQT884E
csect-name Queued Pub/Sub control queue is not a local queue
- Severity
- 8
- Explanation
The queue manager has detected that the queue SYSTEM.BROKER.CONTROL.QUEUE exists and is not a local queue. This makes the queue unsuitable for use as the control queue. The Pub/Sub Daemon task will terminate immediately.
- System programmer response
Delete the definition of the existing queue and, if required, re-create the queue to be of type MQQT_LOCAL.
- CSQT895I
csect-name Queued Pub/Sub Daemon detected missing retained messages
- Severity
- 4
- Explanation
The Queued Pub/Sub Daemon uses retained messages to communicate with other members of publish subscribe hierarchies.
The retained message was missing and has been republished.
- System action
Retained messages seem to have been removed from the SYSTEM.RETAINED.PUB.QUEUE. The Queued Pub/Sub Daemon has attempted to recover by republishing retained messages.
- System programmer response
If you are unaware of a reason why retained messages have been removed this might be a symptom of a more serious problem that requires further investigation.
- CSQT899E
csect-name Unable to establish parent relationship to child queue manager qmname
- Severity
- 8
- Explanation
The queue manager is unable to establish the requested parent relationship to queue manager qmname because that queue manager is already a child.
- System action
The existing child relationship to queue manager qmname remains unaffected.
- System programmer response
To prevent this message being issued, the parent definition on the queue manager must be removed by issuing the ALTER QMGR PARENT(' ') MQSC command. To ensure that the required topology is established, review the existing parent definitions and update appropriately.
- CSQT960I
csect-name Distributed Pub/Sub command processor stopped
- Severity
- 0
- Explanation
- The distributed Pub/Sub command processor stopped. This may be for one of three reasons:
- The channel initiator is stopping.
- The channel initiator is starting and the queues used by the distributed Pub/Sub command processor have not been defined because distributed Pub/Sub command processor is not required.
- An error has occurred
- System action
Processing continues, but distributed Pub/Sub is not available.
- System programmer response
If an error has occurred, investigate the problem reported in the preceding messages.
- CSQT961I
csect-name Distributed Pub/Sub publication processor stopped
- Severity
- 0
- Explanation
- The distributed Pub/Sub publication processor stopped. This can be for one of three reasons:
- The channel initiator is stopping.
- The channel initiator is starting and the queues used by the distributed Pub/Sub command processor have not been defined because distributed Pub/Sub publication processor is not required.
- An error has occurred
- System action
Processing continues, but distributed Pub/Sub is not available.
- System programmer response
If an error has occurred, investigate the problem reported in the preceding messages.
- CSQT962I
csect-name Distributed Pub/Sub proxy-subscription fan out processor stopped
- Severity
- 0
- Explanation
- The distributed Pub/Sub proxy-subscription stopped. This can be for one of three reasons:
- The channel initiator is stopping.
- The channel initiator is starting and the queues used by the distributed pub/sub proxy-subscription fan out processor have not been defined because distributed pub/sub proxy-subscription fan out processor is not required.
- An error has occurred
- System action
Processing continues, but distributed Pub/Sub is not available.
- System programmer response
If an error has occurred, investigate the problem reported in the preceding messages.
- CSQT963E
csect-name Queued pub/sub daemon unavailable
- Severity
- 8
- Explanation
The Distributed publish/subscribe process was unable to contact the Queued Pub/Sub Daemon. The problem will be reported in preceding messages.
- System action
Hierarchical connections cannot be processed until the problem is rectified.
- System programmer response
Investigate the problem reported in the preceding messages. When the Daemon becomes available, it might be necessary to issue the REFRESH QMGR TYPE(PROXYSUB) command to resynchronize subscriptions.
- CSQT964I
csect-name Pub/Sub hierarchy relation connected, (queue manager qmgr-name)
- Severity
- 0
- Explanation
A publish/subscribe hierarchy connection has been established with child or parent queue manager qmgr-name.
- CSQT965I
csect-name Pub/Sub hierarchy relation disconnected, (queue manager qmgr-name)
- Severity
- 0
- Explanation
A publish/subscribe hierarchy connection has ended with child or parent queue manager qmgr-name.
- CSQT966E
csect-name A previous publication is being incorrectly processed again
- Severity
- 8
- Explanation
A publication, previously processed by this queue manager, has been received.
This is caused by an invalid configuration of a hierarchy and a pub/sub cluster.
- System action
This message will not be re-published and will be processed according to the message's report options. Additional messages might be written if this publication is sent to the dead-letter queue.
- System programmer response
Correct the configuration to remove the loop. Check the message properties in the dead-letter queue to determine the route taken.
- CSQT967E
csect-name Unable to deliver proxy subscription to queue manager queue_manager_name, reason=mqrc (mqrc-text)
- Severity
- 8
- Explanation
Unable to deliver proxy subscription to queue manager queue_manager_name. Reason code: mqrc (mqrc-text provides the MQRC in textual form).
This might result in subscriptions not receiving publications from queue_manager_name.
- System programmer response
Correct the configuration to allow proxy subscriptions to be delivered to queue_manager_name. When the problem has been resolved, it will be necessary to perform a REFRESH QMGR TYPE(PROXYSUB) to resynchronize subscriptions.
- CSQT968I
csect-name Topic topic-1 in cluster cluster_name is dependent on PROXYSUB(FORCE) of topic topic-2
- Severity
- 4
- Explanation
Topic object topic-1 is defined in cluster cluster_name, and is below topic object topic-2 in the topic tree. Topic object topic-2 has been configured with PROXYSUB(FORCE) to generate a wildcard proxy subscription, so no further individual proxy subscriptions are sent for any subscriptions made below topic-2 in the topic tree. However, topic-2 is not in the same cluster as topic-1, and the wildcard proxy subscription is not sent to neighboring queue managers in the cluster in which topic-1 is defined. Therefore, publications from cluster cluster_name might not be sent to subscriptions to topic-1 on this queue manager.
- System programmer response
If the behavior described in the explanation is intended no action is required. If not, alter the PROXYSUB attribute on topic topic-1, or topic-2, so both, or neither topics, are configured with the value FORCE.
- CSQT971E
csect-name task failed to quiesce
- Severity
8
- Explanation
The indicated Distributed Publish/Subscribe task was requested to quiesce but failed to do so within the timeout interval.
There are four classes of task:
- Distributed Pub/Sub Publish Task
- Receives publications from remote queue managers in a Publish/Subscribe cluster and republishes into the local queue manager
- Distributed Pub/Sub Command Task
- Receives command messages from remote queue managers in a Publish/Subscribe cluster to create or cancel proxy subscriptions on behalf of remote queue managers.
- Distributed Pub/Sub Fan Out Task
- Sends command messages to remote queue managers in Publish/Subscribe clusters and Publish/Subscribe hierarchies in response to changes in the local queue manager state.
- Distributed Pub/Sub Controller
- Controls the starting and stopping of the Distributed Publish/Subscribe tasks during channel initiator startup and shutdown and also when enabling and disabling Publish/Subscribe.
- System action
The Queued Pub/Sub Daemon will be forcibly closed.
- System programmer response
Check the job log for additional messages, or an FFST™, that might explain why the task has failed to quiesce.
- CSQT972E
csect-name Unable to put Distributed Pub/Sub fan-out request to q-name, reason=mqrc (mqrc-text)
- Severity
- 8
- Explanation
An attempt to put a subscription fan-out request on the distributed publish/subscribe fan-out request queue q-name failed with reason code mqrc (mqrc-text provides the MQRC in textual form).
- CSQT973E
csect-name Distributed Pub/Sub subscribing inhibited, topic string topic-string, (queue manager qm-name)
- Severity
- 8
- Explanation
Topic topic-string has been disabled for subscribe. This prevents distributed publish/subscribe from creating a subscription on behalf of another queue manager qm-name within the topology.
- CSQT974E
csect-name Distributed Pub/Sub publication inhibited, topic string topic-string
- Severity
- 8
- Explanation
Topic topic-string has been disabled for publish. This prevents distributed publish/subscribe from publishing a message received from another queue manager within the topology. This message will not be re-published and will be processed according to the report options in the message. Additional messages will be written if this publication is sent to the dead-letter queue.
- CSQT975I
csect-name task has started
- Severity
- 0
- Explanation
The indicated Distributed Publish/Subscribe task has started. This message typically occurs during channel initiator startup, or when enabling Publish/Subscribe.
There are four classes of task:
- Distributed Pub/Sub Publish Task
- Receives publications from remote queue managers in a Publish/Subscribe cluster and republishes into the local queue manager
- Distributed Pub/Sub Command Task
- Receives command messages from remote queue managers in a Publish/Subscribe cluster to create or cancel proxy subscriptions on behalf of remote queue managers.
- Distributed Pub/Sub Fan Out Task
- Sends command messages to remote queue managers in Publish/Subscribe clusters and Publish/Subscribe hierarchies in response to changes in the local queue manager state.
- Distributed Pub/Sub Controller
- Controls the starting and stopping of the Distributed Publish/Subscribe tasks during channel initiator startup and shutdown, and also when enabling and disabling Publish/Subscribe.
- System action
None.
- System programmer response
None.
- CSQT976I
csect-name task has stopped
- Severity
- 0
- Explanation
The indicated Distributed Publish/Subscribe task has stopped. This message typically occurs during channel initiator shutdown, or when disabling Publish/Subscribe.
There are four classes of task:
- Distributed Pub/Sub Publish Task
- Receives publications from remote queue managers in a Publish/Subscribe cluster and republishes into the local queue manager
- Distributed Pub/Sub Command Task
- Receives command messages from remote queue managers in a Publish/Subscribe cluster to create or cancel proxy subscriptions on behalf of remote queue managers.
- Distributed Pub/Sub Fan Out Task
- Sends command messages to remote queue managers in Publish/Subscribe clusters and Publish/Subscribe hierarchies in response to changes in the local queue manager state.
- Distributed Pub/Sub Controller
- Controls the starting and stopping of the Distributed Publish/Subscribe tasks during channel initiator startup and shutdown and also when enabling and disabling Publish/Subscribe.
- System action
None.
- System programmer response
None.
- CSQT977I
csect-name Establishing Pub/Sub hierarchy relation, (queue manager qmgr-name)
- Severity
- 0
- Explanation
The queue manager is establishing a Publish/Subscribe hierarchy connection with a child or parent queue manager qmgr-name.
- System action
None.
- System programmer response
None.
- CSQT978E
csect-name Unable to create/cancel proxy subscription, for queue manager queue_manager_name, topic string topic-string, reason=mqrc (mqrc-text)
- Severity
- 8
- Explanation
The Distributed Pub/Sub Command Task is unable to create or cancel a proxy subscription for queue manager queue_manager_name on topic topic-string for reason code mqrc (mqrc-text provides the MQRC in textual form).
A failure to create or cancel a proxy subscription will result in this queue manager not having a correct knowledge of subscriptions on other queue managers in the Publish/Subscribe topology. This may result in this queue manager not delivering publications to other queue managers.
- System programmer response
Correct the cause of the indicated reason code.
Once the problem has been resolved it may be necessary to perform a REFRESH QMGR TYPE(PROXYSUB) command to resynchronise any subscriptions.
- CSQT979E
- csect-name Distributed Pub/Sub proxy subscription from qmgr-name rejected due to PSCLUS(DISABLED)
- Explanation
A cluster subscription has been sent to this queue manager over a channel from qmgr-name but the queue manager attribute PSCLUS has been set to DISABLED, indicating that Publish/Subscribe activity is not expected between queue managers in this cluster.
- System action
The proxy subscription request is ignored and no subscription is locally registered.
- System programmer response
To enable publish/subscribe clustering, alter the PSCLUS attribute on all queue managers in the cluster to ENABLED. You may also need to issue REFRESH CLUSTER and REFRESH QMGR commands as detailed in the documentation for the PSCLUS attribute. If you are not using publish/subscribe clusters you should delete the clustered topic object, and ensure PSCLUS is DISABLED on all queue managers.
- CSQT980I
csect-name Distributed Pub/Sub proxy subscription re-synchronization completed
- Severity
- 0
- Explanation
During restart processing the Distributed Pub/Sub process was unable to determine that the proxy subscription state was consistent so a re-synchronization with remote queue managers has been performed.
This is usually seen when a queue manager was not quiesced cleanly during its previous shutdown, or when the system was particularly busy at that time.
- System action
Processing continues.
- System programmer response
None.
- CSQT981E
csect-name Distributed Pub/Sub disabled whilst in a Pub/Sub cluster
- Severity
- 4
- Explanation
This queue manager is a member of a Publish/Subscribe cluster but Publish/Subscribe has been disabled.
- System action
Other queue managers within the Publish/Subscribe Cluster will continue to send publications and proxy subscriptions to this queue manager. They will accumulate on the Publish/Subscribe Cluster system queues and will not be processed until Publish/Subscribe is enabled. If these queues become full channel failure may occur, which will affect the operation of Publish/Subscribe on other queue managers in the cluster. This will also affect the delivery of other messages, unrelated to Publish/Subscribe, that are sent to this queue manager from other queue managers within the cluster.
- System programmer response
Enable Publish/Subscribe by setting PSMODE to ENABLED or COMPAT with the ALTER QMGR command then the REFRESH QMGR TYPE(PROXYSUB) command should be issued to resynchronise subscriptions.
- CSQT982E
csect-name Queued Pub/Sub disabled whilst in a Pub/Sub hierarchy
- Severity
- 4
- Explanation
This queue manager is a member of a Publish/Subscribe hierarchy but Queued Publish/Subscribe has been disabled.
- System action
Any parent-child relations within the Publish/Subscribe hierarchy will continue to send publications and proxy subscriptions to this queue manager. They will accumulate on the Queued Publish/Subscribe system queues and will not be processed until Queued Publish/Subscribe is enabled. If the Queued Publish/Subscribe system queues become full channel failure may occur, which will affect the operation of Publish/Subscribe on parent-child relations sending messages to this queue manager. This will also affect the delivery of other messages, unrelated to Publish/Subscribe, that are to be delivered using the same channels.
- System programmer response
Enable Queued Publish/Subscribe by setting PSMODE to ENABLED with the ALTER QMGR command. Once Queued Publish/Subscribe has been restarted, use the DISPLAY PUBSUB ALL command to confirm this has completed, the REFRESH QMGR TYPE(PROXYSUB) command must be issued to resynchronize
- CSQT983E
csect-name task failed, reason mqrc (mqrc-text), retry in n minutes
- Severity
- 4
- Explanation
The task encountered a problem and will retry the command in n minutes. Earlier messages might have been issued in the queue manager or system error logs providing additional detail.
This message might be issued by a number of tasks:
- Distributed Pub/Sub Publish Task
- Other queue managers within the cluster will continue to send publications to this queue manager. The publications will accumulate on the Publish/Subscribe Cluster system queue (SYSTEM.INTER.QMGR.PUBS) and will not be processed until the problem is resolved. If these queues become full channel failure might occur, which will affect the operation of Publish/Subscribe on other queue managers in the cluster. This will also affect the delivery of other messages, unrelated to Publish/Subscribe, that are sent to this queue manager from other queue managers in the cluster.
- Distributed Pub/Sub Command Task
- Other queue managers within the cluster will continue to send proxy subscriptions to this queue manager. Subscriptions will accumulate on the Publish/Subscribe Cluster system queue (SYSTEM.INTER.QMGR.CONTROL) and will not be processed until the problem is resolved. Other queue managers will not receive publications from this queue manager on topics for which proxy subscriptions have yet to be processed. If the Publish/Subscribe Cluster system queue becomes full channel failure might occur, which will affect the operation of Publish/Subscribe on other queue managers in the cluster. This will also affect the delivery of other messages, unrelated to Publish/Subscribe, that are sent to this queue manager from other queue managers in the cluster.
- Distributed Pub/Sub Fan Out Task
- This task will not send proxy subscription messages to other queue managers in a Publish/Subscribe Cluster or parent-child relations within a Publish/Subscribe hierarchy until the problem is rectified. On topics for which proxy subscriptions have yet to be sent, this queue manager will not receive publications from other queue managers in a Publish/Subscribe Cluster, or parent-child relations in a Publish/Subscribe hierarchy.
- System action
None
- System programmer response
If possible, rectify the identified problem, or contact your IBM support center.
When the problem has been rectified wait for task to retry the command.
- CSQT984E
csect-name task has encountered n occurrences of reason mqrc (mqrc-text) while attempting to process a message.
- Severity
- 4
- Explanation
The task is currently unable to process a message due to reason mqrc (mqrc-text provides the MQRC in textual form). The task has encountered this n times; it will continue to retry the command until the problem has been rectified.
This message might be issued by a number of tasks:
- Distributed Pub/Sub Publish Task
- Other queue managers within the cluster will continue to send publications to this queue manager. Publications will accumulate on the Publish/Subscribe Cluster system queue (SYSTEM.INTER.QMGR.PUBS) and will not be processed until the problem is resolved. If these queues become full channel failure might occur, which will affect the operation of Publish/Subscribe on other queue managers in the cluster. This will also affect the delivery of other messages, unrelated to Publish/Subscribe, that are sent to this queue manager from other queue managers within the cluster.
- Distributed Pub/Sub Command Task
- Other queue managers within the cluster will continue to send proxy subscriptions to this queue manager. Subscriptions will accumulate on the Publish/Subscribe Cluster system queue (SYSTEM.INTER.QMGR.CONTROL) and will not be processed until the problem is resolved. Other queue managers will not receive publications from this queue manager on topics for which proxy subscriptions have yet to be processed. If the Publish/subscriber Cluster system queue becomes full channel failure might occur, which will affect the operation of Publish/Subscribe on other queue managers in the cluster. This will also affect the delivery of other messages, unrelated to Publish/Subscribe, that are sent to this queue manager from other queue managers within the cluster.
- Distributed Pub/Sub Fan Out Task
- This task will not send proxy subscription messages to other queue managers in a Publish/Subscribe Cluster or parent-child relations within a Publish/Subscribe hierarchy until the problem is rectified. On topics for which proxy subscriptions have yet to be sent this queue manager will not receive publications from other queue managers in a Publish/Subscribe Cluster or parent-child relations within a Publish/Subscribe hierarchy.
- System action
None
- System programmer response
If possible, rectify the identified problem, or contact your IBM support center.
When the problem has been rectified wait for task to retry the command.
- CSQT987E
csect-name task failed due to reason mqrc (mqrc-text) Retry in n minutes
- Severity
- 4
- Explanation
The task encountered a problem. Earlier messages might have been issued in the queue manager or system error logs providing additional detail. The task will retry the command in n minutes.
Other queue managers within the cluster will continue to send proxy subscriptions to this queue manager. They will accumulate on the Publish/Subscribe cluster system queue and will not be processed until the problem is resolved.
Other queue managers will not receive publications from this queue manager on topics for which proxy subscriptions have yet to be processed.
If the Publish/subscriber cluster system queue becomes full, channel failure might occur, which will affect the operation of Publish/Subscribe on other queue managers in the cluster. This will also affect the delivery of other messages, unrelated to Publish/Subscribe, that are sent to this queue manager from other queue managers within the cluster.
- System action
None
- System programmer response
If possible, rectify the identified problem, or contact your IBM support center.
When the problem has been rectified wait for task to retry the command.
- CSQT988E
csect-name task failed due to reason mqrc (mqrc-text) Retry in n minutes
- Severity
- 4
- Explanation
The task encountered a problem. Earlier messages might have been issued in the queue manager or system error logs providing additional detail. The task will retry the command in n minutes.
This task will not send proxy subscription messages to other queue managers in a Publish/Subscribe cluster or parent-child relations within a Publish/Subscribe hierarchy until the problem is rectified.
On topics for which proxy subscriptions have yet to be sent, this queue manager will not receive publications from other queue managers in a Publish/Subscribe cluster or parent-child relations within a Publish/Subscribe hierarchy.
- System action
None
- System programmer response
If possible, rectify the identified problem, or contact your IBM support center.
When the problem has been rectified wait for task to retry the command.
- CSQT989E
csect-name task has encountered n occurrences of reason mqrc (mqrc-text) while attempting to process a message.
- Severity
- 4
- Explanation
The task is currently unable to process a message due to reason mqrc (mqrc-text). Note that ((mqrc-text) provides the MQRC in textual form).
The task has encountered this n times. The task continues to retry the command until the problem has been rectified.
Other queue managers within the cluster continue to send proxy subscriptions to this queue manager. The subscriptions will accumulate on the Publish/Subscribe cluster system queue and will not be processed until the problem is resolved.
Other queue managers will not receive publications from this queue manager on topics for which proxy subscriptions have yet to be processed.
If the Publish/subscriber cluster system queue becomes full, channel failure might occur, which will affect the operation of Publish/Subscribe on other queue managers in the cluster.
This will also affect the delivery of other messages, unrelated to Publish/Subscribe, that are sent to this queue manager from other queue managers within the cluster.
- System action
None
- System programmer response
If possible, rectify the identified problem, or contact your IBM support center.
When the problem has been rectified wait for task to retry the command.
- CSQT990E
csect-name task has encountered n occurrences of reason mqrc (mqrc-text) while attempting to process a message.
- Severity
- 4
- Explanation
The task is currently unable to process a message due to reason mqrc (mqrc-text). Note that ((mqrc-text) provides the MQRC in textual form).
The task has encountered this n times. The task continues to retry the command until the problem has been rectified.
This task will not send proxy subscription messages to other queue managers in a Publish/Subsccribe Cluster or parent-child relations within a Publish/Subscribe hierarchy until the problem is rectified.
On topics for which proxy subscriptions have yet to be sent this queue manager will not receive publications from other queue managers in a Publish/Subscribe cluster or parent-child relations within a Publish/Subscribe hierarchy.
- System action
None
- System programmer response
If possible, rectify the identified problem, or contact your IBM support center.
When the problem has been rectified wait for task to retry the command.
- CSQT991I
csect-name task has recovered from previous error condition
- Severity
- 0
- Explanation
The task has recovered from the previously reported error condition.
- System action
Processing continues.
- System programmer response
None.
- CSQT992E
csect-name task has written a message to the dead-letter queue, reason mqrc (mqrc-text)
- Severity
- 8
- Explanation
The task has written a message to the dead-letter queue due to reason mqrc (mqrc-text provides the MQRC in textual form).
If task is the Distributed Pub/Sub Command Task, other queue managers will not receive publications from this queue manager on any topics for which this message is requesting proxy subscriptions be created.
If task is the Distributed Pub/Sub Fan Out Task, this queue manager will not receive publications from other queue managers on any topics for which this is requesting a proxy subscription be created.
- System programmer response
Determine why the message was written to the dead-letter queue, and resolve the problem that is preventing the message from being sent to its destination.
If task is the Distributed Pub/Sub Command Task, or the Distributed Pub/Sub Fan Out Task, it may be necessary to issue the REFRESH QMGR TYPE(PROXYSUB) command when the problem has been resolved to resynchronize the subscription state with other queue managers.
- CSQT996E
csect-name Creation of proxy subscription failed on queue manager qmgr-name, cluster cluster_name, topic string topic-string, reason=mqrc (mqrc-text)
- Severity
- 8
- Explanation
The proxy subscription in publish/subscribe cluster cluster_name on topic topic-string could not be created on queue manager qmgr-name due to reason mqrc (mqrc-text provides the MQRC in textual form). The failure to create the proxy subscription will prevent publications made on queue manager qmgr-name to topic topic-string being delivered to subscriptions on this queue manager. If this queue manager is also participating as a member of a publish/subscribe hierarchy any subscriptions to topic topic-string on other members of the publish/subscribe hierarchy will not receive publications from queue manager qmgr-name.
- System programmer response
Correct the cause of the indicated reason code on queue manager qmgr-name. When the problem has been resolved issue the REFRESH QMGR TYPE(PROXYSUB) command on the remote queue manager to resynchronize the subscription state with other queue managers.
- CSQT997E
csect-name Cancellation of proxy subscription failed on queue manager qmgr-name, cluster cluster_name, topic string topic-string, reason=mqrc (mqrc-text)
- Severity
- 8
- Explanation
The proxy subscription in publish/subscribe cluster cluster_name on topic topic-string could not be canceled on queue manager qmgr-name due to reason mqrc (mqrc-text provides the MQRC in textual form). The failure to cancel the proxy subscription will result in publications made on queue manager qmgr-name to topic topic-string to continue being delivered to this queue manager.
- System programmer response
Correct the cause of the indicated reason code on queue manager qmgr-name. When the problem has been resolved issue the REFRESH QMGR TYPE(PROXYSUB) command on the remote queue manager to resynchronize the subscription state with other queue managers.
- CSQT998E
csect-name Proxy subscription re-synchronization failed on queue manager qmgr-name, cluster cluster_name, reason=mqrc (mqrc-text)
- Severity
- 8
- Explanation
The request to resynchronize the subscription state with other queue managers in publish/subscribe cluster cluster_name failed on queue manager qmgr-name due to reason mqrc (mqrc-text provides the MQRC in textual form). There might be topic strings for which proxy subscriptions have not been created. Publications made on queue manager qmgr-name to those topics will not be delivered to subscriptions on this queue manager. If this queue manager is also participating as a member of a publish/subscribe hierarchy any subscriptions to those topics on other members of the publish/subscribe hierarchy will not receive publications from queue manager qmgr-name. There might also be topic strings for which proxy subscriptions have not been canceled on queue manager qmgr-name. Any publications made on that queue manager will continue to be delivered to this queue manager.
- System programmer response
Correct the cause of the indicated reason code on queue manager qmgr-name. When the problem has been resolved issue the REFRESH QMGR TYPE(PROXYSUB) command on the remote queue manager to resynchronize the subscription state with other queue managers.
- CSQT999E
csect-name task has encountered a message that is not valid on queue queue
- Severity
- 4
- Explanation
The queue queue is for exclusive use by the internal queue manager task task, and is used to maintain a distributed publish/subscribe topology. The task has encountered a message on the queue that is not valid
- System action
The message is processed according to its report options. Additional console messages might be output if the message is put to the dead-letter queue.
An informational FFST, including details of the message that is not valid, might also be generated.
- System programmer response
Ensure no applications put messages directly to the named queue, and ensure message exits do not alter system messages put to the queue. If the problem persists contact your IBM support center.