gtpm5m1w | Messages (Online) |
MQSC0001I | DEFINE PROFILE SUCCESSFUL |
Explanation: This is the normal response to the ZMQSC DEF MQP command.
System Action: The TPF MQSeries profile is created in the TPF system.
User Response: None.
See TPF Operations for more information about the ZMQSC DEF MQP command.
MQSC0002I | ALTER PROFILE SUCCESSFUL |
Explanation: This is the normal response to the ZMQSC ALT MQP command.
System Action: The TPF MQSeries profile is changed in the TPF system.
User Response: Do the following:
MQSC0003E | PROFILE ALREADY EXISTS |
Explanation: The ZMQSC DEF MQP command was entered to create the TPF MQSeries profile. However, the TPF MQSeries profile is already defined to the TPF system.
System Action: The command is rejected.
User Response: Enter the ZMQSC ALT MQP command to change the TPF MQSeries profile.
See TPF Operations for more information about the ZMQSC DEF MQP and ZMQSC ALT MQP commands.
MQSC0004I | DEFINE CHANNEL SUCCESSFUL |
Explanation: This is the normal response to the ZMQSC DEF CHL command.
System Action: A message channel for TPF MQSeries is created.
User Response: None.
See TPF Operations for more information about the ZMQSC DEF CHL command.
MQSC0005E | CHANNEL DEFINITION ALREADY EXISTS |
Explanation: The channel name specified in the ZMQSC DEF CHL command already exists in the TPF system.
System Action: The command is rejected.
User Response: Do one of the following:
See TPF Operations for more information about the ZMQSC DEF CHL and ZMQSC ALT CHL commands.
MQSC0006I | ALTER CHANNEL DEFINITION SUCCESSFUL |
Explanation: This is the normal response to the ZMQSC ALT CHL command.
System Action: The TPF MQSeries channel definition is changed in the TPF system.
User Response: None.
See TPF Operations for more information about the ZMQSC ALT CHL command.
MQSC0007E | CHANNEL DEFINITION DOES NOT EXIST |
Explanation: The TPF MQSeries channel definition specified in a ZMQSC command does not exist.
System Action: The command is rejected.
User Response: Enter the ZMQSC command again specifying a valid TPF MQSeries channel definition.
See TPF Operations for more information about the ZMQSC commands.
MQSC0009E | SYSTEM MUST BE IN NORM STATE |
Explanation: A ZMQSC command was entered below NORM state.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0010I | DELETE CHANNEL DEFINITION SUCCESSFUL |
Explanation: This is the normal response to the ZMQSC DEL command with the CHL parameter specified.
System Action: The TPF MQSeries channel definition is deleted from the TPF system.
User Response: None.
See TPF Operations for more information about the ZMQSC DEL command.
MQSC0012E | TARGQ REQUIRED FOR ALIAS Q DEFINITION |
Explanation: The ZMQSC DEF QA command was entered without specifying the TARGQ parameter.
System Action: The command is rejected.
User Response: Enter the ZMQSC DEF QA command again specifying the TARGQ parameter.
See TPF Operations for more information about the ZMQSC DEF QA command.
MQSC0013E | PARAMETER VALUE parmval NOT RECOGNIZED - MUST BE ON OR OFF |
Where:
Explanation: The ZMQSC TRACE command was entered with the CONSOLE or TAPE parameter specified, but the value specified was incorrect.
System Action: The command is rejected.
User Response: Enter the ZMQSC TRACE command again specifying a correct value for the CONSOLE or TAPE parameter.
See TPF Operations for more information about the ZMQSC TRACE command.
MQSC0014I | DELETE ALIAS QUEUE SUCCESSFUL |
Explanation: This is the normal response to the ZMQSC DEL command with the QA parameter specified.
System Action: The TPF MQSeries alias queue is deleted.
User Response: None.
See TPF Operations for more information about the ZMQSC DEL command.
MQSC0018I | DELETE REMOTE QUEUE SUCCESSFUL |
Explanation: This is the normal response to the ZMQSC DEL command with the QR parameter specified.
System Action: The remote MQSeries queue definition is deleted from the TPF system.
User Response: None.
See TPF Operations for more information about the ZMQSC DEL command.
MQSC0019I | START QUEUE MANAGER SUCCESSFUL |
Explanation: This is the normal response to the ZMQSC START command with the QMGR parameter specified.
System Action: The TPF MQSeries queue manager is started in the TPF system.
User Response: None.
See TPF Operations for more information about the ZMQSC START command.
MQSC0020I | STOP QUEUE MANAGER SUCCESSFUL |
Explanation: This is the normal response to the ZMQSC STOP command with the QMGR parameter specified.
System Action: The TPF MQSeries queue manager is stopped in the TPF system.
User Response: None.
See TPF Operations for more information about the ZMQSC STOP command.
MQSC0026W | MANAGER ALREADY STARTED |
Explanation: The ZMQSC START command with the QMGR parameter specified was entered to start the TPF MQSeries queue manager. However, the queue manager is already started.
System Action: The command is rejected.
User Response: None.
See TPF Operations for more information about the ZMQSC START command.
MQSC0027E | PROFILE NOT DEFINED |
Explanation: A ZMQSC command was entered and an error occurred because the TPF MQSeries profile has not been defined.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0028I | CHANNEL name ADDED TO FUNCTION TRACE TABLE |
Where:
Explanation: This is the normal response to the ZMQSC TRACE command with the CHL or CHANNEL parameter and the FUNCTION and ON parameters specified.
System Action: The specified channel name is added to the function trace table.
User Response: None.
See TPF Operations for more information about the ZMQSC TRACE command.
MQSC0029I | CHANNEL name REMOVED FROM FUNCTION TRACE TABLE |
Where:
Explanation: This is the normal response to the ZMQSC TRACE command with the CHL or CHANNEL parameter and the FUNCTION and OFF parameters specified.
System Action: The specified channel name is removed from the function trace table.
User Response: None.
See TPF Operations for more information about the ZMQSC TRACE command.
MQSC0030I | QUEUE qname ADDED TO FUNCTION TRACE TABLE |
Where:
Explanation: This is the normal response to the ZMQSC TRACE command with the QUEUE and ON parameters specified.
System Action: The specified queue name is added to the function trace table.
User Response: None.
See TPF Operations for more information about the ZMQSC TRACE command.
MQSC0031I | QUEUE name REMOVED FROM FUNCTION TRACE TABLE |
Where:
Explanation: This is the normal response to the ZMQSC TRACE command with the QUEUE and OFF parameters specified.
System Action: The specified queue name is removed from the function trace table.
User Response: None.
See TPF Operations for more information about the ZMQSC TRACE command.
MQSC0032I | CHANNEL name ADDED TO COMMS TRACE TABLE |
Where:
Explanation: This is the normal response to the ZMQSC TRACE command with the CHL or CHANNEL parameter and the COMMS and ON parameters specified.
System Action: The specified channel name is added to the communications trace table.
User Response: None.
See TPF Operations for more information about the ZMQSC TRACE command.
MQSC0033I | CHANNEL name REMOVED FROM COMMS TRACE TABLE |
Where:
Explanation: This is the normal response to the ZMQSC TRACE command with the CHL or CHANNEL parameter and the COMMS and OFF parameters specified.
System Action: The specified channel name is removed from the communications trace table.
User Response: None.
See TPF Operations for more information about the ZMQSC TRACE command.
MQSC0035E | THE ENTRY WAS NOT FOUND IN THIS TRACE TABLE |
Explanation: The ZMQSC TRACE command was entered with the CHL, CHANNEL, or QUEUE parameter and the OFF parameter specified to remove a name from the trace table. However, the name specified does not exist in the trace table.
System Action: The command is rejected.
User Response: Do one of the following:
See TPF Operations for more information about the ZMQSC TRACE command.
MQSC0036W | THE TRACE STATUS WAS NOT SAVED TO EXTERNAL STORAGE AND WILL BE RESET TO ITS PREVIOUS SETTING IF THE QUEUE MANAGER IS RESTARTED. |
Explanation: The ZMQSC TRACE command was entered to change the trace parameters, but the changed parameters were not written to external storage. If the queue manager is restarted, the trace parameters will be reset to their previous settings.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZMQSC TRACE command.
MQSC0042E | MAXMSGL EXCEEDS THE MAXIMUM DEFINED IN PROFILE |
Explanation: A ZMQSC command was entered with a value specified for the MAXMSGL parameter that was greater than the specified maximum in the TPF MQSeries profile.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0045E | CHANNEL- name IS STILL ACTIVE |
Where:
Explanation: The ZMQSC DEL command with the CHL parameter specified was entered to delete a TPF MQSeries channel definition. However, the specified channel is active and cannot be deleted.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC DEL andZMQSC STOP commands.
MQSC0046W | THE TRACE STATUS COULD NOT BE RESTORED |
Explanation: An error occurred when the ZMQSC START command was entered with the QMGR parameter specified because the trace status information could not be restored.
System Action: Processing of the ZMQSC START command continues.
User Response: Enter the ZMQSC TRACE command with the appropriate parameters specified to reset the trace settings you want to use.
See TPF Operations for more information about the ZMQSC START and ZMQSC TRACE commands.
MQSC0047I | TRACE PARAMETERS ALTERED SUCCESSFULLY |
Explanation: This is the normal response to the ZMQSC TRACE command with one of the following parameters specified:
System Action: The specified trace parameter is changed.
User Response: None.
See TPF Operations for more information about the ZMQSC TRACE command.
MQSC0048I | TRACE STARTED |
Explanation: This is the normal response to the ZMQSC TRACE command with the START parameter specified.
System Action: Tracing starts according to the current trace parameters.
User Response: None.
See TPF Operations for more information about the ZMQSC TRACE command.
MQSC0049I | TRACE STOPPED |
Explanation: This is the normal response to the ZMQSC TRACE command with the STOP parameter specified.
System Action: Tracing stops.
User Response: None.
See TPF Operations for more information about the ZMQSC TRACE command.
MQSC0050E | PURGE VALUE MUST BE ALL FOR COMMON QUEUE qname |
Where:
Explanation: The ZMQSC DEL command was entered with the QL and PURGE parameters specified for a processor shared queue, but the value for the PURGE parameter was not ALL.
System Action: The command is rejected.
User Response: Enter the ZMQSC DEL command again and specify a value of ALL for the PURGE parameter.
See TPF Operations for more information about the ZMQSC DEL command.
MQSC0057I | QUEUE SWING OF tqname HAS BEEN RESET |
Where:
Explanation: The ZMQSC SWQ command was entered with the same transmission queue name specified for the FROMQ and TOQ parameters.
System Action: The swing status of the queue is reset.
User Response: None.
See TPF Operations for more information about the ZMQSC SWQ command.
MQSC0058E | NEW QUEUE MANAGER NAME IS ALREADY IN USE |
Explanation: One of the following occurred:
System Action: The command is rejected.
User Response: Enter the appropriate command again and specify a different name for the NEWNAME or RQMNAME parameter.
See TPF Operations for more information about the ZMQSC commands.
MQSC0060E | INCORRECT MIGRATION STATE |
Explanation: The ZMQSC MIGRATE command was entered with the BEGIN parameter specified and one of the following occurred:
System Action: The command is rejected.
User Response: Do one of the following:
See TPF Operations for more information about the ZMQSC MIGRATE command.
MQSC0061E | QUEUE MANAGER NOT STARTED |
Explanation: A ZMQSC command was entered to perform a task that requires the TPF MQSeries queue manager to be started. However, the queue manager has not been started.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0064E | QUEUE qname IS BEING DELETED |
Where:
Explanation: The ZMQSC DEF QA, QL, or QR, or ZMQSC ALT QA, QL, or QR, or ZMQSC DEL command with the QA, QL, or QR parameter was entered without the PURGE parameter specified. However, a previous ZMQSC DEL command with the QA, QL, or QR parameter specified was processed for a queue of the same name.
System Action: The queue has not been completely deleted. The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0065W | QUEUE qname IS REPLACED IN MEMORY TABLE |
Where:
Explanation: The ZMQSC DEF QA, QL, or QR command was entered and the queue name was not in use in the queue definition dictionary, but a nondeleted queue of the same name existed in the queue definition table in memory. The definition in memory was replaced by the new definition.
System Action: The queue is defined successfully.
User Response: None.
See TPF Operations for more information about the ZMQSC DEF QA, QL, or QR command.
MQSC0066E | NO HEAP AVAILABLE |
Explanation: The ZMQSC START command was entered with the QMGR parameter specified, but the request failed because there are not enough heap frames in the TPF system.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZCTKA ALTER and ZMQSC START commands.
MQSC0067E | xxx FAILED FOR QUEUE qname, ERROR CODE nn |
Where:
Explanation: The ZMQSC DEF QA, QL, or QR, ZMQSC ALT QA, QL, or QR, or the ZMQSC DEL command with the QA, QL, or QR parameter specified was entered on this or another processor, but the memory copy of the queue definition could not be updated.
System Action: The queue definition is defined or updated on file, but not in memory.
User Response: See your IBM service representative.
See TPF Operations for more information about the ZMQSC commands.
MQSC0069I | LOCAL QUEUE qname DEFINED |
Where:
Explanation: The ZMQSC DEF QL command for the specified queue was processed successfully.
System Action: The local queue has been defined.
User Response: None.
See TPF Operations for more information about the ZMQSC DEF QLcommand.
MQSC0070E | QUEUE qname ALREADY DEFINED |
Where:
Explanation: The ZMQSC DEF QA, QL, or QR command was entered for the queue indicated in the message, but this queue is already defined and not deleted.
System Action: The command is rejected.
User Response: Verify the spelling of the queue name and do one of the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0073E | QUEUE qname IS NOT AN ALIAS QUEUE |
Where:
Explanation: The ZMQSC ALT QA command or else the ZMQSC DEL or ZMQSC DISPLAY command with the QA parameter specified was entered, but the specified queue is not an alias queue.
System Action: The command is rejected.
User Response: Do one of the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0078E | QUEUE qname IS NOT A REMOTE QUEUE |
Where:
Explanation: The ZMQSC ALT QR command or else the ZMQSC DISPLAY or ZMQSC DEL command with the QR parameter specified was entered. However, the specified queue is not a remote queue.
System Action: The command is rejected.
User Response: Do one of the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0079E | QUEUE qname IS NOT A LOCAL QUEUE |
Where:
Explanation: The ZMQSC ALT QL command or else the ZMQSC DISPLAY or ZMQSC DEL command with the QL parameter specified was entered. However, the specified queue is not a local queue.
System Action: The command is rejected.
User Response: Do one of the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0080I | RECEIVER CHANNEL name STARTED |
Where:
Explanation: This is the normal response when a receiver channel has started.
System Action: None.
User Response: None.
MQSC0081E | REQUEST RECEIVED TO START RECEIVER CHANNEL name RECEIVER CHANNEL FAILED TO START - RC retcode |
Where:
Explanation: This message is displayed when an unexpected error causes the receiver channel to fail to start.
System Action: None.
User Response: See your system programmer to determine the cause of the problem.
MQSC0083E | QUEUE qname HAS BEEN SWUNG TO THIS QUEUE |
Where:
Explanation: The ZMQSC DEL command with the QL parameter specified was entered to delete a queue. However, the queue is the object of a swing from another queue.
System Action: The queue is not deleted.
User Response: Enter the ZMQSC SWQ command with the FROMQ parameter specified using the queue name indicated in this message and the TOQ parameter specified as a queue name other than the one you are deleting.
See TPF Operations for more information about the ZMQSC DEL and ZMQSC SWQ commands.
MQSC0085I | CHANNEL - name action |
Where:
Explanation: This is the normal response to the ZMQSC DISPLAY command with the CHS parameter specified.
System Action: The current status of the specified channel is displayed.
User Response: None.
See TPF Operations for more information about the ZMQSC DISPLAY command.
MQSC0086E | PARAMETER VALUE value NOT VALID |
Where:
Explanation: A ZMQSC command was entered with a parameter value specified that is not valid.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0088I | QUEUE SWING xxx TO yyy SUCCESSFUL |
Where:
Explanation: This is the normal response to the ZMQSC SWQ command.
System Action: Messages from the sending queue are placed on the receiving queue.
User Response: None.
See TPF Operations for more information about the ZMQSC SWQ command.
MQSC0090E | REMOTE QUEUE name USES THIS XMIT QUEUE |
Where:
Explanation: The ZMQSC DEL command was entered to delete a transmission queue. However, the transmission queue is being used by a remote queue.
System Action: The command is rejected.
User Response: Do one of the following:
See TPF Operations for more information about the ZMQSC DEL and ZMQSC ALT QR commands.
MQSC0092E | QUEUE SWING FAILED - QUEUE qname IS NOT SUBJECT OF SWINGQ |
Where:
Explanation: The ZMQSC SWQ command with the FROMQ and TOQ parameters specified, was entered with the same queue name. This form of the message is intended to undo the effects of a previous ZMQSC SWQ command that was entered, but the specified queue is not currently having its messages sent to another queue.
System Action: The command is rejected.
User Response: None.
See TPF Operations for more information about the ZMQSC SWQ command.
MQSC0093E | QUEUE SWING FAILED - FROMQ fqname IS NOT DEFINED |
Where:
Explanation: The ZMQSC SWQ command with the FROMQ parameter specified was entered, but the queue is not defined.
System Action: The command is rejected.
User Response: Enter the ZMQSC SWQ command again specifying an existing transmission queue for the FROMQ parameter.
See TPF Operations for more information about the ZMQSC SWQ command.
MQSC0094E | QUEUE SWING FAILED - TOQ tqname IS NOT DEFINED |
Where:
Explanation: The ZMQSC SWQ command with the TOQ parameter specified was entered, but the queue name is not defined.
System Action: The command is rejected.
User Response: Enter the ZMQSC SWQ command again specifying an existing transmission queue for the TOQ parameter.
See TPF Operations for more information about the ZMQSC SWQ command.
MQSC0095E | QUEUE SWING FAILED - FROMQ fqname IS NOT A TRANSMIT QUEUE |
Where:
Explanation: The ZMQSC SWQ command with the FROMQ parameter specified was entered, but the queue name is not a transmission queue.
System Action: The command is rejected.
User Response: Enter the ZMQSC SWQ command again specifying an existing transmission queue for the FROMQ parameter.
See TPF Operations for more information about the ZMQSC SWQ command.
MQSC0096E | QUEUE SWING FAILED - TOQtqname IS NOT A TRANSMIT QUEUE |
Where:
Explanation: The ZMQSC SWQ command with the TOQ parameter specified was entered, but the queue name is not a transmission queue.
System Action: The command is rejected.
User Response: Enter the ZMQSC SWQ command again specifying an existing transmission queue for the TOQ parameter.
See TPF Operations for more information about the ZMQSC SWQ command.
MQSC0097E | QUEUE SWING FAILED - FROMQ fqname IS SUBJECT OF SWINGQ |
Where:
Explanation: The ZMQSC SWQ command was entered with the FROMQ parameter specified. However, the queue name was specified for the FROMQ parameter in a previous ZMQSC SWQ command.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC SWQ command.
MQSC0098E | QUEUE SWING FAILED - FROMQ fqname IS OBJECT OF SWINGQ FROM QUEUE qname |
Where:
Explanation: The ZMQSC SWQ command was entered with the FROMQ parameter specified. However, the queue name was specified for the TOQ parameter in a previous ZMQSC SWQ command.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC SWQ command.
MQSC0099E | QUEUE SWING FAILED - TOQ tqname IS SUBJECT OF SWINGQ |
Where:
Explanation: The ZMQSC SWQ command was entered with the TOQ parameter specified. However, the queue name was specified for the FROMQ parameter in a previous ZMQSC SWQ command.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC SWQ command.
MQSC0100E | QUEUE SWING FAILED - TOQ tqname MAXMSGL IS SMALLER THAN FROMQ fqname. |
Where:
Explanation: The ZMQSC SWQ command was entered with the TOQ and FROMQ parameters specified, but the maximum message length allowed for the TOQ queue name is smaller than that for the FROMQ queue name.
System Action: The command is rejected.
User Response: Do one of the following:
See TPF Operations for more information about the
ZMQSC SWQ and ZMQSC ALT QL commands.
Explanation:
ZMQSC ALT CHL or ZMQSC DEF CHL was entered with the LOCALIP parameter specified, but the Internet
Protocol (IP) address specified is not valid.
System Action: The command is rejected
User Response: Do the following:
See TPF Operations for more information about the
ZMQSC ALT CHL and ZMQSC DEF CHL commands.MQSC0101E INCORRECT LOCAL IP ADDRESS SPECIFIED
MQSC0102E | UNEXPECTED DASH |
Explanation: A ZMQSC command was entered with an unexpected dash.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0103E | UNEXPECTED LEFT PAREN |
Explanation: A ZMQSC command was entered with an unexpected left parenthesis.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0104E | UNEXPECTED RIGHT PAREN |
Explanation: A ZMQSC command was entered with an unexpected right parenthesis.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0105E | UNEXPECTED COMMA |
Explanation: A ZMQSC command was entered with an unexpected comma.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0106E | UNEXPECTED NUMBER num |
Where:
Explanation: A ZMQSC command was entered with an unexpected number specified.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0107E | PRIMARY PARAMETER parm NOT VALID |
Where:
Explanation: A ZMQSC command was entered specifying a parameter that was not valid.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0108E | SECONDARY PARAMETER NOT SPECIFIED |
Explanation: A ZMQSC command was entered without specifying the secondary parameter.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0109E | SECONDARY PARAMETER parm NOT VALID |
Where:
Explanation: A ZMQSC command was entered with a secondary parameter specified that was not valid.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0110E | parm NOT VALID FOR THIS COMMAND |
Where:
Explanation: A ZMQSC command was entered with a parameter specified that is not valid.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0111E | parm - DASH EXPECTED |
Where:
Explanation: A ZMQSC command was entered without a dash following the specified parameter.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0112E | value - STRING EXPECTED |
Where:
Explanation: A ZMQSC command was entered with a character string value that was not valid.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0113E | name -CONTAINS INCORRECT CHARACTERS |
Where:
Explanation: When a ZMQSC command was entered, the value that was specified for the object name contains characters that are not valid for TPF MQSeries objects.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0115E | PARAMETER parm NOT VALID |
Where:
Explanation: A ZMQSC command was entered with a parameter specified that is not valid.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0116E | CHLTYPE MUST BE SPECIFIED AFTER CHANNEL NAME |
Explanation: When the ZMQSC DEF CHL command was entered, the CHLTYPE parameter did not follow the channel name.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC DEF CHL command.
MQSC0117E | value - NUMBER EXPECTED |
Where:
Explanation: A ZMQSC command was entered without specifying a numeric value.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0118E | value - VALUE OUT OF RANGE |
Where:
Explanation: A ZMQSC command was entered with a numeric value that was not valid.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0119E | PLUS CHARACTER NOT VALID IN PARAMETER VALUE |
Explanation: A ZMQSC command was entered with a plus (+) character in the value specified for the object name. Plus characters are not valid for TPF MQSeries objects.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0123E | VALUE TYPE value NOT SUPPORTED |
Where:
Explanation: A ZMQSC command was entered, but the parameter specified was not valid.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0125E | PARAMETER parm TOO LONG |
Where:
Explanation: A ZMQSC command was entered with a parameter specified that exceeded the maximum parameter length allowed.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0126E | NUMBER value TOO LONG |
Where:
Explanation: A ZMQSC command was entered with a numeric value that exceeds the maximum number length allowed.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0127E | TERMINATOR OF NUMBER value NOT VALID |
Where:
Explanation: A ZMQSC command was entered, but an alphabetic character was found within the numeric value specified.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0128E | CHARACTER char NOT VALID |
Where:
Explanation: A ZMQSC command was entered with a character specified that is not a valid part of a numeric value.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0129E | STRING string TOO LONG |
Where:
Explanation: A ZMQSC command was entered with a string value specified that exceeds the maximum length allowed.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0130E | STRING string ENDED UNEXPECTEDLY |
Where:
Explanation: A ZMQSC command was entered with a string value specified that ended unexpectedly.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0131E | TOO MANY ATTRIBUTES |
Explanation: A ZMQSC command was entered with a number of attributes specified that exceeds the maximum number allowed.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0132E | CHARACTER ATTRIBUTE BUFFER EXCEEDED |
Explanation: A ZMQSC command was entered, but the parameter specified exceeds the maximum buffer length.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0133E | ON OR OFF MUST BE SPECIFIED |
Explanation: The ZMQSC TRACE command was entered with the CHL, CHANNEL, QUEUE, ADMIN, or ALL parameter specified, but the ON or OFF parameter was not specified.
System Action: The command is rejected.
User Response: Enter the ZMQSC TRACE command again and specify either the ON or OFF parameter.
See TPF Operations for more information about the ZMQSC TRACE command.
MQSC0134E | CONFLICTING PARAMETERS SPECIFIED (parm1/parm2) |
Where:
Explanation: A ZMQSC command was entered with two parameters specified that conflict with each other. For example, this message occurs if you enter the ZMQSC TRACE command with both the ON and OFF parameters specified.
System Action: The command is rejected.
User Response: Do one of the following:
MQSC0135E | COMMON NOT VALID FOR TRANSMIT QUEUE qname |
Where:
Explanation: The ZMQSC DEF QL command was entered with the XMITQ value specified for the USAGE parameter and the YES value specified for the COMMON parameter. The YES value is allowed only for a normal queue.
System Action: The command is rejected.
User Response: Do one of the following:
See TPF Operations for more information about the ZMQSC DEF QL command.
MQSC0136E | CPU ID NOT VALID |
Explanation: The ZMQSC command was entered with a processor identifier (ID) specified for the CPU parameter that was not valid.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0137E | MAXMSGL FOR LOCAL QUEUE qname EXCEEDS THE MAXIMUM DEFINED IN THE MQSERIES PROFILE |
Where:
Explanation: The ZMQSC DEF QL or ZMQSC ALT QL command was entered with the MAXMSGL parameter specified, but the value specified for this parameter was greater than the limit specified or implied for the queue manager in the ZMQSC DEF MQP or ZMQSC ALT MQP command.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0138E | LOW STORAGE ERROR |
Explanation: When a ZMQSC command was entered, TPF system storage could not be obtained to process the request.
System Action: The command is rejected.
User Response: See your system programmer to determine why the TPF system storage could not be obtained.
See TPF Operations for more information about the ZMQSC commands.
MQSC0139E | CHANNEL DOES NOT EXIST IN MEMORY |
Explanation: The ZMQSC DISPLAY command with the CHS parameter specified or the ZMQSC START command with the CHL parameter specified was entered to access a specified TPF MQSeries channel. However, the channel does not exist in memory.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0142E | CHANNELxxx FOR QUEUE qname MUST BE STOPPED AND NOT IN DOUBT |
Where:
Explanation: The ZMQSC SWQ command was entered, but the source transmission queue name specified for the FROMQ parameter is associated with a channel that is either not stopped or is in an in-doubt condition.
System Action: The command is rejected.
User Response: Do one of the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0143I | ALIAS QUEUE qname DEFINED |
Where:
Explanation: The ZMQSC DEF QA command for the queue indicated was processed successfully.
System Action: The alias queue is defined.
User Response: None.
See TPF Operations for more information about the ZMQSC DEF QA command.
MQSC0144E | QUEUE MANAGER NAME DOES NOT EXIST IN TPF |
Explanation: The ZMQSC ALT MQP command was entered referencing a TPF MQSeries queue manager that is not defined to the TPF system.
System Action: The command is rejected.
User Response: Enter the ZMQSC ALT MQP command with the correct queue manager name.
See TPF Operations for more information about the ZMQSC ALT MQP command.
MQSC0145I | REMOTE QUEUE qname DEFINED |
Where:
Explanation: The ZMQSC DEF QR command for the queue indicated in the message was processed successfully.
System Action: The remote queue is defined.
User Response: None.
See TPF Operations for more information about the ZMQSC DEF QR command.
MQSC0146I | LOCAL QUEUE qname ALTERED |
Where:
Explanation: The ZMQSC ALT QL command for the queue indicated was processed successfully.
System Action: The local queue definition is changed.
User Response: None.
See TPF Operations for more information about the ZMQSC ALT QL command.
MQSC0147E | QUEUE qname DOES NOT EXIST |
Where:
Explanation: The ZMQSC ALT QA, QL, or QR command or ZMQSC DEL command with the QA, QL, or QR parameter specified was entered, but the queue indicated in the message does not exist.
System Action: The command is rejected.
User Response: Verify the spelling of the queue name and do one of the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0148I | ALIAS QUEUE qname ALTERED |
Where:
Explanation: The ZMQSC ALT QA command for the queue indicated was processed successfully.
System Action: The alias queue definition is changed.
User Response: None.
See TPF Operations for more information about the ZMQSC ALT QA command.
MQSC0149I | REMOTE QUEUE qname ALTERED |
Where:
Explanation: The ZMQSC ALT QR command for the queue indicated was processed successfully.
System Action: The remote queue definition is changed.
User Response: None.
See TPF Operations for more information about the ZMQSC ALT QR command.
MQSC0153E | INCORRECT ZMQSC FUNCTION ENTERED |
Explanation: A ZMQSC command was entered that is not valid.
System Action: The command is rejected.
User Response: Enter ZMQSC HELP to determine the correct format of the command.
See TPF Operations for more information about the
ZMQSC commands.
Where:
Explanation: A ZMQSC command was entered and completed successfully, but errors
occurred. The TPF system sends an additional message for each error,
describing the nature of the error.
System Action: None.
User Response: None.
See TPF Operations for more information about the
ZMQSC commands.MQSC0156W command OPERATION COMPLETED, BUT ERRORS OCCURRED
MQSC0157E | QUEUE DEFINITION DOES NOT EXIST |
Explanation: The ZMQSC DISPLAY command was entered with the QA, QL, or QR parameter specified. However, the queue referenced is not defined to the TPF system.
System Action: The command is rejected.
User Response: Do one of the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0159I | QUEUES DEFINED: |
Explanation: This is the normal response to the ZMQSC DISPLAY command with the QUEUE and ALL parameters specified.
System Action: A list of all the queue definitions in the TPF system is displayed.
User Response: None.
See TPF Operations for more information about the ZMQSC DISPLAY command.
MQSC0162E | NAME CANNOT BE ALL |
Explanation: The ZMQSC DEF CHL, ZMQSC DEF QA, ZMQSC DEF QL, or ZMQSC DEF QR command was entered to define a channel or queue with a name of ALL. The name ALL cannot be used as the channel or queue name.
System Action: The command is rejected.
User Response: Do one of the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0163E | XMITQ AND CONNAME REQUIRED FOR SENDER CHANNEL |
Explanation: The ZMQSC DEF CHL command was entered to define a sender channel. However, the XMITQ and CONNAME parameters were not specified.
System Action: The command is rejected.
User Response: Enter the ZMQSC DEF CHL command with the XMITQ and CONNAME parameters specified.
See TPF Operations for more information about the ZMQSC DEF CHL command
MQSC0164E | ACTION PARAMETER REQUIRED |
Explanation: The ZMQSC RESOLVE command was entered to resolve a sender channel. However, the ACTION parameter was not specified.
System Action: The command is rejected.
User Response: Enter the ZMQSC RESOLVE command with the ACTION parameter (either COMMIT or BACKOUT) specified.
See TPF Operations for more information about the ZMQSC RESOLVE command
MQSC0166E | THIS NAME IS ALREADY IN THE TRACE TABLE |
Explanation: The ZMQSC TRACE command was entered with a CHL, CHANNEL, or QUEUE parameter and the ON parameter specified to add a name to the trace table. However, the name specified already exists in the trace table.
System Action: The command is rejected.
User Response: Do one of the following:
See TPF Operations for more information about the
ZMQSC TRACE command.
Where:
Explanation: A ZMQSC command was entered before migration was committed.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about ZMQSC MIGRATE and other ZMQSC commands.MQSC0167E command REJECTED - MIGRATE COMMIT REQUIRED
MQSC0168E | MQSERIES CHECKPOINT RECORDS NOT ALLOCATED |
Explanation: A ZMQSC command was entered, but the #IMQCK record type was not allocated in the file address compute (FACE) table.
System Action: The command is not processed.
User Response: Modify the FACE table definition to include the #IMQCK record type and restart the TPF system.
See TPF Operations for more information about the ZMQSC commands.
MQSC0169E | QUEUE MANAGER MUST BE STOPPED |
Explanation: The ZMQSC MIGRATE command was entered with the FALLBACK parameter specified, but the queue manager on the processor where the command was entered was not stopped.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC MIGRATE and ZMQSC STOP commands.
MQSC0170E | THIS PROCESSOR HAS NOT MIGRATED |
Explanation: The ZMQSC START command was entered with the QMGR parameter specified, but the processor on which the command was entered has not been migrated.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC MIGRATE and ZMQSC START commands.
MQSC0171E | THE FOLLOWING PROCESSORS HAVE NOT MIGRATED: x |
Where:
Explanation: The ZMQSC MIGRATE command was entered with the COMMIT parameter specified, but one or both of the following conditions exists for the specified processors:
System Action: The command is rejected.
User Response: Do one of the following:
See TPF Operations for more information about the ZMQSC MIGRATE command.
MQSC0172E | PROCESSOR NOT IN MIGRATE UNCOMMITTED STATE |
Explanation: The ZMQSC MIGRATE command was entered with the FALLBACK parameter specified, but either migration has already been committed or the processor has not been migrated.
System Action: The command is rejected.
User Response: Do one of the following:
See TPF Operations for more information about the ZMQSC MIGRATE command.
MQSC0173I | ALL QUEUES SUCCESSFULLY MIGRATED |
Explanation: The ZMQSC MIGRATE command with the BEGIN parameter specified was processed successfully.
System Action: All old format queues have been converted to the new format and their messages have been moved to the new queues.
User Response: None.
See TPF Operations for more information about the ZMQSC MIGRATE command.
MQSC0174E | NO CHANGE PARAMETERS SPECIFIED |
Explanation: The ZMQSC ALT MQP command was entered with no parameters specified.
System Action: The command is rejected.
User Response: Enter the ZMQSC ALT MQP command again, specifying at least one parameter.
See TPF Operations for more information about the ZMQSC ALT MQP command.
MQSC0175E | QUEUE qname IS DELETED |
Where:
Explanation: The ZMQSC ALT QA, QL, or QR, or ZMQSC DEL QA, QL, or QR command, or ZMQSC DISPLAY command with the QA, QL, or QR parameter specified was entered, but the queue indicated in the message was deleted previously.
System Action: The command is rejected.
User Response: Verify the spelling of the queue name. If it is spelled correctly, then do one of the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0176E | XMITQ, CONNAME, AND LOCALIP ONLY APPLY TO SENDER CHANNEL |
Explanation: Either the ZMQSC ALT CHL or the ZMQSC DEF CHL command was entered with the XMITQ, CONNAME, or LOCALIP parameter specified, but the XMITQ, CONNAME, and LOCALIP parameters are only valid with a sender channel.
System Action: The command is rejected.
User Response: Enter the ZMQSC ALT CHL or the ZMQSC DEF CHL command again without specifying the XMITQ, CONNAME, or LOCALIP parameter.
See TPF Operations for more information about the ZMQSC ALT CHL and ZMQSC DEF CHL commands.
MQSC0177I | TRACE STATUS DISPLAY |
Explanation: This is the normal response to the ZMQSC TRACE command with the DISPLAY parameter specified.
System Action: The current trace status is displayed.
User Response: None.
See TPF Operations for more information about the ZMQSC TRACE command.
MQSC0178E | GET SYNC RECORD FAILED |
Explanation: This message is displayed if the process of obtaining a synchronization record fails while checkpointing a receiver channel during the TPF MQSeries checkpoint process.
System Action: The current checkpoint channel process exits.
User Response: None. The TPF system will automatically restart the checkpoint process when it reaches the checkpoint interval.
MQSC0179E | SWEEP NOT VALID FOR COMMON QUEUE qname |
Where:
Explanation: One of the following occurred:
System Action: The command is rejected.
User Response: Do one of the following:
See TPF Operations for more information about the ZMQSC ALT QL and ZMQSC DEF QL commands.
MQSC0180E | UNABLE TO SET UP RECOUP INDEX FOR MQSERIES |
Explanation: One of the following occurred:
System Action: The command is rejected.
User Response: See your IBM service representative.
See TPF Operations for more information about the ZMQSC DEF MQP, ZMQSC MIGRATE, or ZMQSC START command.
MQSC0181E | ERROR CREATING RECOUP INDEX FOR TRACE ENTRY |
Explanation: Either the ZMQSC DEF MQP, the ZMQSC MIGRATE command with the BEGIN parameter specified, or the ZMQSC START command with the QMGR parameter specified was entered, but an error occurred while retrieving a list of valid CPU IDs that are used to create one or more entries in the TPF collection support (TPFCS) data store (DS) user dictionary recoup index for the TPF MQSeries trace structure.
System Action: The command is rejected, but entries in the TPFCS DS user dictionary recoup index for TPF MQSeries trace records will not be created. TPF recoup will not find these records, and database corruption may occur if pool records being used by TPF MQSeries are allowed to be processed.
User Response: Have your system programmer determine why storage is depleted or why a list of valid CPU IDs could not be obtained.
See TPF Operations for more information about the ZMQSC DEF MQP, ZMQSC MIGRATE, or ZMQSC START command.
MQSC0200I | REMOTE QUEUE DISPLAY: |
Explanation: This is the normal response to the ZMQSC DISPLAY command with the QR parameter specified, or with the QUEUE parameter with a remote queue name specified.
System Action: The definition for the specified remote queue is displayed.
User Response: None.
See TPF Operations for more information about the ZMQSC DISPLAY command.
MQSC0201I | LOCAL QUEUE DISPLAY: |
Explanation: This is the normal response to the ZMQSC DISPLAY command with the QL parameter specified, or with the QUEUE parameter with a local queue name specified.
System Action: The definition for the specified local queue is displayed.
User Response: None.
See TPF Operations for more information about the ZMQSC DISPLAY command.
MQSC0202I | CHANNEL DEFINITION DISPLAY: |
Explanation: This is the normal response to the ZMQSC DISPLAY command with the CHL parameter specified.
System Action: The definition for the specified channel is displayed.
User Response: None.
See TPF Operations for more information about the ZMQSC DISPLAY command.
MQSC0203I | QUEUE MANAGER PROFILE DISPLAY |
Explanation: This is the normal response to the ZMQSC DISPLAY command with the QMGR parameter specified.
System Action: The current TPF MQSeries profile is displayed.
User Response: None.
See TPF Operations for more information about the ZMQSC DISPLAY command.
MQSC0204I | ALIAS QUEUE DISPLAY: |
Explanation: This is the normal response to the ZMQSC DISPLAY command with the QA parameter specified.
System Action: The definition for the specified alias queue is displayed.
User Response: None.
See TPF Operations for more information about the ZMQSC DISPLAY command.
MQSC0205I | ALL CHANNELS STOPPING |
Explanation: This is the normal response to the ZMQSC STOP command when ALL is specified for the CHL parameter. This message is displayed immediately after entering the command and throughout the stopping process.
System Action: The TPF system begins stopping all TPF MQSeries channels.
User Response: None.
See TPF Operations for more information about the ZMQSC STOP command.
MQSC0206I | ALL CHANNELS STOPPED |
Explanation: This is the normal response to the ZMQSC STOP command when ALL is specified for the CHL parameter. This message is displayed when the stopping process is completed successfully.
System Action: All TPF MQSeries channels are stopped.
User Response: None.
See TPF Operations for more information about the ZMQSC STOP command.
MQSC0207E | NO CHANNELS DEFINED |
Explanation: The ZMQSC STOP command was entered to stop all TPF MQSeries channels, but no channels were defined.
System Action: The command is rejected.
User Response: Enter ZMQSC DISPLAY CHL ALL to verify if any channels have been defined.
See TPF Operations for more information about the ZMQSC STOP and the ZMQSC DISPLAY commands.
MQSC0208I | CHANNEL STATUS DISPLAY: |
Explanation: This is the normal response to the ZMQSC DISPLAY command when ALL is specified for the CHS parameter.
System Action: The current status of all channels is displayed.
User Response: None.
See TPF Operations for more information about the ZMQSC DISPLAY command.
MQSC0210E | MIGRATE FAILED BECAUSE OF INDOUBT CHANNELS: |
Explanation: The ZMQSC MIGRATE command was entered with the BEGIN or FALLBACK parameter specified, but in-doubt sender channels were detected.
System Action: The command is rejected.
User Response: Do one of the following:
See TPF Operations for more information about the ZMQSC MIGRATE or ZMQSC RESOLVE commands.
MQSC0211E | MIGRATE FAILED BECAUSE OF TPF COLLECTION SUPPORT ERRORS |
Explanation: The ZMQSC MIGRATE command was entered, but TPF collection support (TPFCS) errors occurred while retrieving channel definitions from TPFCS.
System Action: The command is rejected.
User Response: See your IBM service representative.
See TPF Operations for more information about the ZMQSC MIGRATE command.
MQSC0212E | ALTER CHANNEL DEFINITION FAILED - CHANNEL IS ACTIVE |
Explanation: The ZMQSC ALT CHL command was entered, but the specified channel name is active and cannot be changed.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC STOP and ZMQSC ALT CHL commands.
MQSC0213E | ALTER CHANNEL DEFINITION FAILED - CHANNEL IS INDOUBT |
Explanation: The ZMQSC ALT CHL command was entered, but the specified channel name has outstanding batches that have not been processed completely.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC RESOLVE and ZMQSC ALT CHL commands.
MQSC0217E | QUEUE - qname IS NOT VALID FOR MOVE |
Where:
Explanation: The ZMQSC MOVEMSGS command was entered, but the specified queue is not a processor unique normal local queue.
System Action: The command is rejected.
User Response: Enter the ZMQSC MOVEMSGS command again and specify a valid queue.
See TPF Operations for more information about the ZMQSC MOVEMSGS command.
MQSC0218E | PROCESSOR NOT DEACTIVATED |
Explanation: The ZMQSC MOVEMSGS command was entered, but the processor associated with the CPU ID is not deactivated.
System Action: The command is rejected.
User Response: Enter the ZMQSC MOVEMSGS command again and specify a deactivated processor for the CPU ID.
See TPF Operations for more information about the
ZMQSC MOVEMSGS command.
Where:
Explanation: This is the normal response to the ZMQSC CLEAR QL
command
System Action: None.
User Response: None.
See TPF Operations for more information about the
ZMQSC CLEAR QL command.MQSC0219I ALL MESSAGES REMOVED FROM LOCAL QUEUE qname
MQSC0220I | number MESSAGES MOVED FROM QUEUE-qname SUCCESSFULLY |
Where:
Explanation: The ZMQSC MOVEMSGS command for the specified queue was processed successfully.
System Action: The messages on the specified queue are moved from the processor specified for the CPU parameter.
User Response: None.
See TPF Operations for more information about the ZMQSC MOVEMSGS command.
MQSC0221E | MOVE MESSAGES FAIL, MOVE ABORTED |
Explanation: The ZMQSC MOVEMSGS command was entered, but an error occurred during the move.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC MOVEMSGS command.
MQSC0222E | number MESSAGES MOVED FROM QUEUE-qname, MOVE ABORTED, UNABLE TO GET MESSAGES WITH REASON CODE rcode |
Where:
Explanation: The ZMQSC MOVEMSGS command was entered to move the messages on the specified queue name, but an error occurred because a TPF MQSeries API function call was unable to move the message from the queue.
System Action: TPF MQSeries continues to try to move the messages for 15 minutes. If it cannot move the messages, the command fails and the messages are lost.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC MOVEMSGS command.
MQSC0223E | number MESSAGES MOVED FROM QUEUE-qname, MOVE ABORTED, UNABLE TO PUT MESSAGES WITH REASON CODE rcode |
Where:
Explanation: The ZMQSC MOVEMSGS command was entered to move the messages on the specified queue name, but an error occurred because a TPF MQSeries API function call was unable to put the message to the target queue.
System Action: TPF MQSeries continues to try to move the messages for 15 minutes. If it cannot move the messages, the command fails and the messages are lost.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC MOVEMSGS command.
MQSC0224E | MOVE MESSAGES IS IN PROGRESS, MOVE ABORTED |
Explanation: The ZMQSC MOVEMSGS command was entered, but an outstanding move is processing or ended with an error.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the
ZMQSC MOVEMSGS command.
Where:
Explanation: This is the normal response when you enter ZMQSC DISPLAY CHL-ALL.
System Action: None.
User Response: None.
See TPF Operations for more information about the
ZMQSC DISPLAY command. Explanation:
ZMQSC DEF CHL or ZMQSC ALT CHL was entered with the MREXIT or MRDATA parameter specified, but
CHLTYPE-RCVR was not specified.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the
ZMQSC DEF CHL and ZMQSC ALT CHL commands.
Explanation:
ZMQSC DISPLAY CHS-ALL was entered with the IPADDR
or SOCKET parameter specified, but neither parameter is allowed when CHS-ALL
is specified.
System Action: The command is rejected
User Response: Do one of the following:
See TPF Operations for more information about the
ZMQSC DISPLAY command.MQSC0225I CHANNEL DISPLAY FOR PROCESSOR cpuid:
MQSC0226E MREXIT AND MRDATA VALID FOR RECEIVER CHANNEL ONLY
MQSC0227E IPADDR OR SOCKET CANNOT BE USED WITH CHS-ALL
MQSC0230I | ALL CHANNELS STARTED |
Explanation: This is the normal response when ZMQSC START CHL-ALL is entered, indicating that all channels have been started.
System Action: None.
User Response: None.
See TPF Operations for more information about the
ZMQSC START command.
Explanation:
ZMQSC ALT CHL was entered with the CHLTYPE
parameter specified, but that channel type does not match the channel
definition for the specified channel.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the
ZMQSC ALT CHL command.
Explanation:
ZMQSC DISPLAY CHS-name was entered with
the IPADDR or SOCKET parameter specified, but the specified channel name is
not a server connection channel.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the
ZMQSC DISPLAY command.
Where:
Explanation:
ZMQSC DISPLAY CHS-name was entered with
IPADDR-ALL specified, but the specified channel name is not defined or is not
active.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the
ZMQSC DISPLAY command.
Where:
Explanation: This is the normal response when you enter ZMQSC DISPLAY CHS-name with the IPADDR-ALL parameter specified.
System Action: None.
User Response: None.
See TPF Operations for more information about the
ZMQSC DISPLAY command.
Explanation:
ZMQSC DEF CHL or ZMQSC ALT CHL was entered with the BATCHSZ or SEQWRAP parameter specified, but the
BATCHSZ and SEQWRAP parameters are not allowed for a server connection
channel.
System Action: The command is rejected.
User Response: Enter the ZMQSC DEF CHL or ZMQSC ALT CHL command again without specifying the
BATCHSZ or SEQWRAP parameter.
See TPF Operations for more information about the
ZMQSC DEF CHL and ZMQSC ALT CHL commands.
Explanation:
ZMQSC DISPLAY CHS-name was entered with
the IPADDR-ALL and SOCKET parameters specified, but this is not
allowed.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the
ZMQSC DISPLAY command.MQSC0232E ALTER CHANNEL DEFINITION FAILED - CHANNEL HAS DIFFERENT CHANNEL TYPE
MQSC0233E IPADDR AND SOCKET NOT VALID FOR THE SPECIFIED CHANNEL
MQSC0234E CHANNEL name NOT DEFINED OR ACTIVE
MQSC0235I CHANNEL INSTANCE DISPLAY FOR name:
MQSC0236E BATCHSZ AND SEQWRAP DO NOT APPLY TO A SVRCONN CHANNEL
MQSC0237E SOCKET CANNOT BE SPECIFIED WITH IPADDR-ALL PARAMETER
MQSC0301E | START SENDER CHANNEL - name FAILED SOCKET ERROR |
Where:
Explanation: An attempt was made to start a TPF MQSeries sender channel, but a socket error occurred when the message channel agent (MCA) tried to issue a socket call.
System Action: None.
User Response: Determine if any Transmission Control Protocol/Internet Protocol (TCP/IP) malfunctions caused the socket error.
See TPF Operations for more information about the ZMQSC commands.
MQSC0304E | START SENDER CHANNEL - name FAILED SETSOCKETOPT ERROR |
Where:
Explanation: When an attempt was made to start a TPF MQSeries sender channel, the message channel agent (MCA) tried to reuse the socket that caused the error.
System Action: None.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0305E | START SENDER CHANNEL - name FAILED BIND ERROR |
Where:
Explanation: An attempt was made to start a TPF MQSeries sender channel. The message channel agent received an error when issuing BIND to the local socket.
System Action: None.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0306E | START SENDER CHANNEL - name FAILED UNABLE TO CONNECT TO REMOTE HOST |
Where:
Explanation: An attempt was made to start a TPF MQSeries sender channel. The message channel agent (MCA) received an error when issuing CONNECT to the remote system that has MQSeries installed.
System Action: None.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0307E | START SENDER CHANNEL - name FAILED COMMUNICATIONS ERRORS |
Where:
Explanation: An attempt was made to start a TPF MQSeries sender channel. The message channel agent received generic Transmission Control Protocol/Internet Protocol (TCP/IP) errors on issuing socket calls.
System Action: None.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0308E | START SENDER CHANNEL - name FAILED INCORRECT CONFIGURATION |
Where:
Explanation: An attempt was made to start a TPF MQSeries sender channel. The message channel agent (MCA) received generic Transmission Control Protocol/Internet Protocol (TCP/IP) errors on issuing socket calls.
System Action: None.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0309E | START SENDER CHANNEL - name FAILED ROUTING PROBLEM |
Where:
Explanation: An attempt was made to start a TPF MQSeries sender channel. The message channel agent (MCA) received an error when issuing CONNECT to the remote system that has MQSeries installed.
System Action: The network may be unable to connect to the remote host because of network problems.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0310E | CHANNEL - name NOT ACTIVE |
Where:
Explanation: The ZMQSC STOP command with the CHL parameter specified was entered to stop a TPF MQSeries channel. However, the channel is not active.
System Action: The command is rejected.
User Response: None.
See TPF Operations for more information about the ZMQSC STOP command.
MQSC0311I | CHANNEL - name STOPPED |
Where:
Explanation: This is the normal response to the ZQMSC STOP command.
System Action: The specified channel is stopped.
User Response: None.
See TPF Operations for more information about the ZMQSC STOP command.
MQSC0312E | START CHANNEL FAILED FOR name BAD CHANNEL TYPE FOUND |
Where:
Explanation: One of the following occurred:
System Action: If the request was entered by a command, the command is rejected; otherwise no system action occurs.
User Response: Ensure that the channel name is defined correctly at both ends of the connection.
See TPF Operations for more information about the ZMQSC START command.
MQSC0313E | RECEIVER CHANNEL - name STOPPED |
Where:
Explanation: This is a normal response when a request was received to stop the channel.
System Action: None.
User Response: None.
MQSC0314E | CHANNEL name IS ACTIVE |
Where:
Explanation: An attempt was made to start a TPF MQSeries sender channel. However, the channel is already active.
System Action: None.
User Response: None.
MQSC0315I | START SENDER CHANNEL - name SUCCESSFUL |
Where:
Explanation: This is the normal response to the ZMQSC START command with the CHL parameter specified.
System Action: The specified channel is started.
User Response: None.
See TPF Operations for more information about the ZMQSC START command.
MQSC0316I | CHANNEL - name HAS BEEN RESET |
Where:
Explanation: This is the normal response to the ZMQSC RESET command with the CHL parameter specified.
System Action: The specified channel is reset.
User Response: None.
See TPF Operations for more information about the ZMQSC RESET command.
MQSC0317E | CHANNEL - name RESET FAILED BECAUSE OF INCORRECT SEQUENCE NUMBER |
Where:
Explanation: The ZMQSC RESET command with the CHL parameter specified was entered to reset a TPF MQSeries sender channel. However, the number specified is not valid.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC RESET command.
MQSC0318E | CHANNEL - name STOPPED ABNORMALLY |
Where:
Explanation: The active channel detected a communications error. The remote system may have closed the channel's socket.
System Action: The channel is stopped.
User Response: Investigate the communications trace from the remote MQSeries to determine the cause of the error.
MQSC0319E | START SENDER CHANNEL - name FAILED CHANNEL IS INDOUBT |
Where:
Explanation: An attempt was made to start a TPF MQSeries sender channel. The message channel agent (MCA) tried to resolve the channel that is in doubt (an outstanding batch of messages left from the previous session has not been sent completely).
System Action: None.
User Response: Enter the ZMQSC RESOLVE command with the CHL, ACTION, and BACKOUT parameters specified to resolve the sender channel.
See TPF Operations for more information about the ZMQSC RESOLVE command.
MQSC0320I | RESOLVE CHANNEL - name SUCCESSFUL |
Where:
Explanation: This is the normal response to the ZMQSC RESOLVE command with the CHL parameter specified.
System Action: The specified channel is resolved.
User Response: None.
See TPF Operations for more information about the ZMQSC RESOLVE command.
MQSC0321E | RESOLVE CHANNEL - name FAILED NOT SENDER CHANNEL |
Where:
Explanation: The ZMQSC RESOLVE command was entered with the CHL parameter specified to resolve a TPF MQSeries sender channel. However, the channel name specified is not a sender channel.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC RESOLVE command.
MQSC0322E | CHANNEL - name IS NOT INDOUBT |
Where:
Explanation: The ZMQSC RESOLVE command with the CHL parameter specified was entered to resolve a TPF MQSeries sender channel. However, the channel is not in doubt.
System Action: The command is rejected.
User Response: Do one of the following:
See TPF Operations for more information about the ZMQSC RESOLVE command.
MQSC0323E | RESOLVE CHANNEL - name FAILED CHANNEL DEFINITION HAS BEEN CHANGED RESOLVE WITH BACKOUT REQUIRED |
Where:
Explanation: The ZMQSC RESOLVE command was entered with the CHL, ACTION, and COMMIT parameters specified to resolve a TPF MQSeries sender channel. However, the channel definition has been changed.
System Action: The command is rejected.
User Response: Enter the ZMQSC RESOLVE command again with the BACKOUT parameter specified.
See TPF Operations for more information about the ZMQSC RESOLVE command.
MQSC0324E | CHANNEL - name IS IN USE |
Where:
Explanation: The ZMQSC RESET command was entered with the CHL parameter specified or the ZMQSC RESOLVE command was entered with the CHL parameter specified to reset or resolve a TPF MQSeries sender channel. However, the channel is active.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0325E | START CHANNEL FAILED FOR name CHANNEL NOT DEFINED |
Where:
Explanation: A request was received to start a TPF MQSeries channel from a remote MQSeries system, but the channel name is not defined in the TPF MQSeries system.
System Action: None.
User Response: Do the following:
MQSC0326E | CHANNEL - name STOPPED DUE TO TO2 ERRORS |
Where:
Explanation: The TPF MQSeries channel detected TPF collection support (TPFCS) errors and is unable to continue.
System Action: None.
User Response: Determine the cause of the TPFCS errors.
MQSC0327E | RESOLVE CHANNEL - name FAILED RESOLVE WITH BACKOUT REQUIRED |
Where:
Explanation: The ZMQSC RESOLVE command was entered with the CHL, ACTION, and COMMIT parameters specified to resolve a TPF MQSeries sender channel.
System Action: The command is rejected and the message channel agent (MCA) is unable to resolve the channel.
User Response: Enter the ZMQSC RESOLVE command again with the BACKOUT parameter specified to resolve the TPF MQSeries sender channel.
See TPF Operations for more information about the ZMQSC RESOLVE command.
MQSC0328E | RESOLVE CHANNEL - name FAILED DUE TO TO2 ERRORS |
Where:
Explanation: The ZMQSC RESOLVE command with the ACTION and BACKOUT parameters specified was entered to resolve the channel. However, TPF collection support (TPFCS) errors were detected.
System Action: The command is rejected.
User Response: Determine the cause of the TPFCS errors.
See TPF Operations for more information about the ZMQSC RESOLVE command.
MQSC0329E | START CHANNEL FAILED FOR name QUEUE MANAGER NOT STARTED |
Where:
Explanation: A request was received to start a TPF MQSeries channel from a remote MQSeries system, but the TPF MQSeries queue manager is not started.
System Action: None.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC START command.
MQSC0330E | RESOLVE CHANNEL - name FAILED BATCH LIST CORRUPTED |
Where:
Explanation: The ZMQSC RESOLVE command with the ACTION and BACKOUT parameters specified was entered to resolve the channel. However, the batch list is corrupted.
System Action: Messages in the batch are lost.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC RESOLVE command.
MQSC0332E | CHANNEL - name STOPPED CHANNEL SECURITY CHECK FAILED |
Where:
Explanation: The channel was not started because of one of the following causes:
System Action: The channel is not started. If a command was entered, it is rejected.
User Response: Ensure that the channel security data defined at both ends of the channel are correct.
See TPF Operations for more information about the ZMQSC START command.
MQSC0333E | START SENDER CHANNEL - name FAILED CHANNEL STARTUP IN PROGRESS |
Where:
Explanation: The ZMQSC START command with the CHL parameter specified was entered to start a TPF MQSeries sender channel, but the channel is already being started.
System Action: The command is rejected.
User Response: Do one of the following:
See TPF Operations for more information about the ZMQSC START command.
MQSC0334E | START RECEIVER CHANNEL - name FAILED CHANNEL DISABLED |
Where:
Explanation: A request from a remote MQSeries system was received to start a TPF MQSeries receiver channel, but the channel is disabled.
System Action: The request is rejected.
User Response: Enter the ZMQSC START command with the CHL parameter specified to enable the receiver channel.
See TPF Operations for more information about the ZMQSC START command.
MQSC0335I | RECEIVER CHANNEL - name ENABLED |
Where:
Explanation: This is the normal response to the ZMQSC START command with the CHL parameter specified for a receiver channel that was disabled.
System Action: The specified receiver channel is enabled.
User Response: None.
See TPF Operations for more information about the ZMQSC START command.
MQSC0336E | RECEIVER CHANNEL - name ALREADY ENABLED |
Where:
Explanation: A ZMQSC START command with the CHL parameter specified was entered to enable a TPF MQSeries receiver channel, but the channel is not disabled.
System Action: The command is rejected.
User Response: Do one of the following:
See TPF Operations for more information about the ZMQSC START command.
MQSC0337I | RECEIVER CHANNEL - name DISABLED |
Where:
Explanation: This is the normal response to the ZMQSC STOP command with the CHL parameter specified for a receiver channel.
System Action: The specified receiver channel is disabled.
User Response: None.
See TPF Operations for more information about the ZMQSC STOP command.
MQSC0338E | START SENDER CHANNEL - name FAILED TRANSMISSION QUEUE NOT DEFINED |
Where:
Explanation: A ZMQSC START command with the CHL parameter specified was entered to start a TPF MQSeries sender channel. However, the transmission queue associated with the sender channel is not defined.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC DEF QL and ZMQSC START commands.
MQSC0339E | START SENDER CHANNEL - name FAILED TRANSMISSION QUEUE NOT DEFINED CORRECTLY |
Where:
Explanation: A ZMQSC START command with the CHL parameter specified was entered to start a TPF MQSeries sender channel. However, the transmission queue associated with the sender channel is not defined as a type XMITQ.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0340E | START SENDER CHANNEL - name FAILED TRANSMISSION QUEUE BEING USED BY ANOTHER SENDER CHANNEL |
Where:
Explanation: A ZMQSC START command with the CHL parameter specified was entered to start a TPF MQSeries sender channel. However, the transmission queue associated with the sender channel is being used by another sender channel.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about theZMQSC DISPLAY, ZMQSC STOP, and ZMQSC START commands.
MQSC0341E | START SENDER CHANNEL - name FAILED NO SYSTEM HEAP MEMORY AVAILABLE FOR ALLOCATING BATCH LISTS |
Where:
Explanation: An attempt was made to start a TPF MQSeries sender channel. However, the amount of TPF system heap storage was not enough to allocate batch lists for the channel.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC START command. See the ZCTKA DISPLAY command in TPF Operations for more information on system heap storage.
MQSC0342E | START SENDER CHANNEL - name FAILED XMITQ HAVING OUTSTANDING BATCHES WITH A PREVIOUS CHANNEL |
Where:
Explanation: An attempt was made to start a TPF MQSeries sender channel. However, the transmission queue associated with the channel was previously used by another channel that has outstanding batches.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0343E | START SENDER CHANNEL - name FAILED INCORRECT CONNECTION NAME |
Where:
Explanation: The ZMQSC START CHL command was entered in an attempt to start a TPF MQSeries sender channel. The message channel agent (MCA) determined that either the Internet Protocol (IP) address or the remote host name was not valid.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC ALT CHL andZMQSC START commands.
MQSC0344E | CHANNEL - name STOPPED BECAUSE OF NO TEMPORARY STORAGE AVAILABLE |
Where:
Explanation: The specified channel name was stopped because of a shortage of temporary storage for holding input/output (I/O) messages.
System Action: The specified channel is stopped.
User Response: Do the following:
MQSC0345W | CHANNEL - name RESTART IS IN PROGRESS BECAUSE OF BROKEN CONNECTION |
Where:
Explanation: The specified sender channel is attempting to restart because the channel connection was taken down by the network or a remote channel receiver.
System Action: The TPF MQSeries system attempts to start the sender channel automatically.
User Response: None.
MQSC0346E | CHANNEL - name STOPPED BECAUSE OF MESSAGE CONVERSION FAILURE |
Where:
Explanation: The specified channel name was stopped because the conversion of either an input or an output message failed.
System Action: The specified channel name is stopped.
User Response: Investigate the local and remote coded character set identifiers (CCSIDs) associated with the channel to determine if the TPF system supports the code page for the CCSID message conversion.
MQSC0347E | CHANNEL - name STOPPED BECAUSE OF MESSAGE SEQUENCE ERRORS |
Where:
Explanation: The specified channel name was stopped because the input messages received from a remote MQSeries sender channel did not carry the sequence numbers as the receiver channel expected.
System Action: The specified channel name is stopped.
User Response:
See TPF Operations for more information about the ZMQSC RESET command.
MQSC0348E | CHANNEL - name STOPPED BECAUSE OF PROTOCOL ERRORS |
Where:
Explanation: The specified channel name was stopped because the input message violated MQSeries protocol.
System Action: The specified channel name is stopped.
User Response: Do the following:
MQSC0349E | CHANNEL - name STOPPED NO DEAD LETTER QUEUE |
Where:
Explanation: The specified channel name was stopped because an attempt was made to place the input message on the dead-letter queue (DLQ). The DLQ that is defined in the TPF MQSeries profile does not exist.
System Action: The specified channel name is stopped.
User Response: Do the following:
MQSC0350E | CHANNEL - name START ERROR - exitname |
Where:
Explanation: The channel was not started because one of the following occurred:
System Action: The channel is not started. If a command was entered, it is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC START command. See TPF System Installation Support Reference for more information about the channel user exit.
MQSC0351I | SVRCONN CHANNEL - name ENABLED |
Where:
Explanation: This is the normal response to the ZMQSC START command.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZMQSC START command.
MQSC0352E | SVRCONN CHANNEL - name ALREADY ENABLED |
Where:
Explanation: The ZMQSC START command was entered with the CHL parameter specified, but the server connection channel was aready started.
System Action: The command is rejected.
User Response: None.
See TPF Operations for more information about the ZMQSC START command.
MQSC0353I | SVRCONN CHANNEL - name DISABLED |
Where:
Explanation: This is the normal response to the ZMQSC STOP command.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZMQSC STOP command.
MQSC0354E | CHANNEL OF TYPE SVRCONN CANNOT BE RESET |
Explanation: The ZMQSC RESET command was entered, but the channel is a server connection channel, which cannot be reset.
System Action: The command is rejected.
User Response: None.
See TPF Operations for more information about the ZMQSC RESET command.
MQSC0355E | CHANNEL - name STOPPED PUT TO DEAD LETTER QUEUE FAILED |
Where:
Explanation: The channel tried to put a message to the dead-letter queue, but could not because the dead letter queue is not defined, is disabled, or has some other problem.
System Action: The message stays on the transmission queue.
User Response: Do the following:
MQSC0401E | CHANNEL - name STOPPED REMOTE CHANNEL DEFINITION NOT FOUND |
Where:
Explanation: A request was made to start a TPF MQSeries sender channel. However, the receiver channel in the remote system that has MQSeries installed is not defined.
System Action: The command is rejected.
User Response: Ensure that the channel name is defined as a receiver channel in the remote system that has MQSeries installed.
MQSC0402E | CHANNEL - name STOPPED REMOTE CHANNEL TYPE INCORRECT |
Where:
Explanation: A request was made to start a TPF MQSeries sender channel. However, the channel name defined in the remote system that has MQSeries installed is not a receiver channel.
System Action: The command is rejected.
User Response: Do the following:
MQSC0403E | CHANNEL - name STOPPED REMOTE QUEUE MANAGER NOT AVAILABLE |
Where:
Explanation: A request was made to start a TPF MQSeries sender channel. However, the remote queue manager is not available.
System Action: The command is rejected.
User Response: Do the following:
MQSC0404E | CHANNEL - name STOPPED MESSAGE OUT OF SEQ, EXPECTED SEQUENCE NUMBER - nextnum FIRST MESSAGE SEQUENCE NUMBER IN THE LAST BATCH SENT - firstnum |
Where:
Explanation: A request was made to start a TPF MQSeries sender channel. However, the remote system that has MQSeries installed rejected the previous batch because the message sequence number is not in sequence.
System Action: The command is rejected.
User Response: Enter the ZMQSC RESET command with the CHL and SEQNUM parameters specified to reset a new sequence number for the channel and to restart the sender channel.
See TPF Operations for more information about the ZMQSC commands.
MQSC0405E | CHANNEL - name STOPPED REMOTE QUEUE MANAGER TERMINATING |
Where:
Explanation: The remote queue manager is stopping and acknowledges that the channel is being closed.
System Action: None.
User Response: None.
MQSC0406E | CHANNEL - name STOPPED REMOTE QUEUE MANAGER CANNOT STORE MESSAGE |
Where:
Explanation: The remote queue manager cannot store received messages because of storage constraints.
System Action: None.
User Response: None.
MQSC0407I | CHANNEL - name STOPPED CHANNEL HAS BEEN CLOSED BY USER |
Where:
Explanation: The remote queue manager acknowledges that the channel has been closed by the MQSeries applications.
System Action: None.
User Response: None.
MQSC0408E | CHANNEL - name STOPPED CHANNEL CLOSED BECAUSE TIMEOUT EXPIRED |
Where:
Explanation: No messages were sent by the channel for a specified period of time, so the remote queue manager closed the channel.
System Action: None.
User Response: None.
MQSC0409E | CHANNEL - name STOPPED RECEIVING MCA WAS NOT ABLE TO OPEN THE TARGET QUEUE |
Where:
Explanation: The remote queue manager acknowledged that the target queue specified by MQSeries cannot be opened for MQPUT.
System Action: None.
User Response: Do the following:
MQSC0410E | CHANNEL - name STOPPED PROTOCOL ERROR - UNKNOWN SEGMENT TYPE |
Where:
Explanation: The remote MQSeries acknowledged that the messages sent by MQSeries are not valid.
System Action: None.
User Response: See your IBM representative to determine the cause of the error and to correct the problem.
MQSC0411E | CHANNEL - name STOPPED PROTOCOL ERROR - DATA LENGTH ERROR |
Where:
Explanation: The remote MQSeries acknowledged that the data length of the entire message sent by TPF MQSeries is incorrect.
System Action: None.
User Response: See your IBM representative to determine the cause of the error and to correct the problem.
MQSC0412E | CHANNEL - name STOPPED PROTOCOL ERROR - INCORRECT DATA |
Where:
Explanation: The remote MQSeries acknowledged that the messages sent by TPF MQSeries contain incorrect data.
System Action: None.
User Response: See your IBM representative to determine the cause of the error and to correct the problem.
MQSC0413E | CHANNEL - name STOPPED PROTOCOL ERROR - SEGMENTATION ERROR |
Where:
Explanation: The remote system that has MQSeries installed acknowledged that the segmented messages sent by TPF MQSeries are incorrect.
System Action: None.
User Response: See your IBM representative to determine the cause of the error and to correct the problem.
MQSC0414E | CHANNEL - name STOPPED PROTOCOL ERROR - ID EYECATCHER ERROR |
Where:
Explanation: The remote system that has MQSeries installed acknowledged that the message sent by TPF MQSeries may be corrupted.
System Action: None.
User Response: See your IBM representative to determine the cause of the error and to correct the problem.
MQSC0415E | CHANNEL - name STOPPED PROTOCOL ERROR - MSH EYECATCHER ERROR |
Where:
Explanation: The remote system that has MQSeries installed acknowledged that the message sent by TPF MQSeries may be corrupted.
System Action: None.
User Response: See your IBM representative to determine the cause of the error and to correct the problem.
MQSC0416E | CHANNEL - name STOPPED PROTOCOL ERROR - GENERAL FAILURE |
Where:
Explanation: The remote system that has MQSeries installed acknowledged that the message sent by TPF MQSeries may be corrupted.
System Action: None.
User Response: See your IBM representative to determine the cause of the error and to correct the problem.
MQSC0417E | CHANNEL - name STOPPED BATCH SIZE FAILURE |
Where:
Explanation: The remote system that has MQSeries installed acknowledged that the size of batch messages sent by TPF MQSeries does not follow the protocol.
System Action: None.
User Response: See your IBM representative to determine the cause of the error and to correct the problem.
MQSC0418E | CHANNEL - name STOPPED MESSAGE LENGTH ERROR |
Where:
Explanation: The remote system that has MQSeries installed acknowledged that the length of the message sent by TPF MQSeries is incorrect.
System Action: None.
User Response: See your IBM representative to determine the cause of the error and to correct the problem.
MQSC0419E | CHANNEL - name STOPPED SEGMENT NUMBER ERROR |
Where:
Explanation: The remote system that has MQSeries installed acknowledged that the segment number of a segmented message sent by TPF MQSeries is incorrect.
System Action: None.
User Response: See your IBM representative to determine the cause of the error and to correct the problem.
MQSC0420E | CHANNEL - name STOPPED SECURITY FAILURE |
Where:
Explanation: The remote system that has MQSeries installed acknowledged that a security check failure occurred when receiving the message sent by TPF MQSeries.
System Action: None.
User Response: See your IBM representative to determine the cause of the error and to correct the problem.
MQSC0421E | CHANNEL - name STOPPED CHANNEL SEQUENCE NUMBER WRAP VALUE ERROR LOCAL VALUE value REMOTE VALUE value |
Where:
Explanation: The remote system that has MQSeries installed acknowledged that the sequence number wrap value is incorrect.
System Action: None.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC DISPLAY and ZMQSC ALT CHL commands.
MQSC0422E | CHANNEL - name STOPPED REMOTE CHANNEL UNAVAILABLE |
Where:
Explanation: The remote system that has MQSeries installed acknowledged that the receiver channel is not currently available.
System Action: None.
User Response: Determine why the remote channel is not available and correct the problem.
MQSC0512W | QUEUEqname HIGHWATER MARK nummsg WAS EXCEEDED BY numover |
Where:
Explanation: The total number of messages on the TPF MQSeries queue is above the user-defined number.
System Action: This message is sent to the operator at each scan time as defined by the ZMQSC DEF MQP command with the QDT parameter specified until the number of messages in the queue becomes less than or equal to the user-defined number.
User Response:
If the queue name is a normal local queue, ensure that the TPF application that services the queue is operational. If the queue name is a transmission queue, do one of the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0600E | MAXDEPTH NOT VALID FOR COMMON QUEUE qname |
Where:
Explanation: One of the following occurred:
System Action: The command is rejected.
User Response: Enter the ZMQSC DEF QL or ZMQSC ALT QL command again without specifying the MAXDEPTH parameter.
See TPF Operations for more information about the ZMQSC DEF QL and ZMQSC ALT QL commands.
MQSC0601E | QDEPTHHI NOT VALID FOR COMMON QUEUE qname |
Where:
Explanation: One of the following occurred:
System Action: The command is rejected.
User Response: Enter the ZMQSC DEF QL or ZMQSC ALT QL command again without specifying the QDEPTHHI parameter.
See TPF Operations for more information about the ZMQSC DEF QL and ZMQSC ALT QL commands.
MQSC0602E | UNCOMMITTED MSGS EXIST ON QUEUES - END ALL TRANSACTIONS OR SPECIFY FORCE |
Explanation: A ZMQSC MIGRATE command was entered with the FALLBACK parameter specified while uncommitted messages still existed in queues.
System Action: The command is rejected.
User Response: Do one of the following:
See TPF Operations for more information about the ZMQSC MIGRATE command.
MQSC0603E | QUEUE qname IS ALREADY DELETED |
Where:
Explanation: The ZMQSC DEL command was entered with the QA, QL, or QR parameter specified, but the queue specified had already been deleted.
System Action: The command is rejected.
User Response: Do one of the following:
See TPF Operations for more information about the ZMQSC DEL command.
MQSC0604E | qname CANNOT BE USED AS A QUEUE NAME |
Where:
Explanation: The ZMQSC DEF QA, QR, or QL command was entered with a reserved queue name specified.
System Action: The command is rejected.
User Response: Enter the ZMQSC DEF QA, QR, or QL command again and specify a different queue name.
See TPF Operations for more information about the ZMQSC DEF QA, QR, or QL commands.
MQSC0605E | QUEUE qname CANNOT BE ALTERED |
Where:
Explanation: The ZMQSC ALT QL command was entered for a reserved queue name.
System Action: The command is rejected.
User Response: None.
See TPF Operations for more information about the ZMQSC ALT QL command.
MQSC0606E | QUEUE qname CANNOT BE DELETED |
Where:
Explanation: The ZMQSC DEL command was entered with the QL parameter specified, but the queue to be deleted was required by the TPF system.
System Action: The command is rejected.
User Response: None.
See TPF Operations for more information about the ZMQSC DEL command.
MQSC0607I | DELETION OF QUEUE qname STARTED |
Where:
Explanation: The ZMQSC DEL command was entered with the QL parameter specified for a queue that still has messages on it, or that is used by an active channel on one of the processors.
System Action: The TPF system waits until the queue is empty and no active channels are using it before it is deleted. Before it is deleted, no messages can be added to the queue and a queue of the same name cannot be defined.
User Response: None
See TPF Operations for more information about the ZMQSC DEL command.
MQSC0608I | DELETION OF QUEUE qname COMPLETE |
Where:
Explanation: One of the following occurred:
System Action: The queue is deleted.
User Response: None.
See TPF Operations for more information about the ZMQSC DEL command.
MQSC0609I | DELETION OF QUEUE qname WAITING FOR PROCESSORS x, y,... |
Where:
Explanation: Five minutes have elapsed since message MQSC0607I was displayed and there is at least one processor preventing the queue from being deleted.
System Action: The TPF system continues to check the queue and deletes it when and if all processors indicate that it can be deleted.
User Response: Do one of the following:
See TPF Operations for more information about the ZMQSC DISPLAY and ZMQSC DEL commands.
MQSC0610I | MIGRATE FALLBACK COMPLETED SUCCESSFULLY |
Explanation: The ZMQSC MIGRATE command with the FALLBACK parameter specified was processed successfully.
System Action: All new format queues have been deleted and their messages moved to the old format queues.
User Response: None.
See TPF Operations for more information about the ZMQSC MIGRATE command.
MQSC0611I | MIGRATE COMMIT COMPLETED SUCCESSFULLY |
Explanation: The ZMQSC MIGRATE command with the COMMIT parameter specified was processed successfully.
System Action: Migration is now committed. All old format queues have been deleted.
User Response: None.
See TPF Operations for more information about the ZMQSC MIGRATE command.
MQSC0612I | MIGRATE STATUS DISPLAY |
Explanation: This is the normal response when the ZMQSC MIGRATE command is entered with the STATUS parameter specified.
System Action: The current queue migration status is displayed.
User Response: None.
See TPF Operations for more information about the ZMQSC MIGRATE command.
MQSC0613E | EMPTY THE DEAD LETTER QUEUE OR SPECIFY FORCE |
Explanation: The ZMQSC MIGRATE command was entered with the COMMIT parameter specified, but the old version of the dead-letter queue still has messages on it.
System Action: The command is rejected.
User Response: Do one of the following:
See TPF Operations for more information about the ZMQSC MIGRATE command.
MQSC0614E | qname CANNOT BE USED AS A BASE QUEUE |
Where:
Explanation: The ZMQSC DEF QA or ZMQSC ALT QA command was entered with the TARGQ parameter, but the TARGQ parameter specifies a reserved queue name.
System Action: The command is rejected.
User Response: Enter the ZMQSC DEF QA or ZMQSC ALT QA command again, specifying a different name for the TARGQ parameter.
See TPF Operations for more information about the ZMQSC DEF QA and ZMQSC ALT QA commands.
MQSC0615E | FROMQ PARAMETER REQUIRED |
Explanation: The ZMQSC SWQ command was entered, but the FROMQ parameter was not specified.
System Action: The command is rejected.
User Response: Enter the ZMQSC SWQ command again, specifying both the FROMQ and TOQ parameters.
See TPF Operations for more information about the ZMQSC SWQ command.
MQSC0616E | TOQ PARAMETER REQUIRED |
Explanation: The ZMQSC SWQ command was entered, but the TOQ parameter was not specified.
System Action: The command is rejected.
User Response: Enter the ZMQSC SWQ command again, specifying both the FROMQ and TOQ parameters.
See TPF Operations for more information about the ZMQSC SWQ command.
MQSC0617E | FROMQ tqname IS DELETED |
Where:
Explanation: The ZMQSC SWQ command was entered with the FROMQ parameter specified, but the transmission queue specified has been deleted or is in the process of being deleted.
System Action: The command is rejected.
User Response: Enter the ZMQSC SWQ command again with a different queue name.
See TPF Operations for more information about the ZMQSC SWQ command.
MQSC0618E | TOQ tqname IS DELETED |
Where:
Explanation: The ZMQSC SWQ command was entered with the TOQ parameter specified, but this transmission queue has been deleted or is in the process of being deleted.
System Action: The command is rejected.
User Response: Enter the ZMQSC SWQ command again, specifying a different queue for the TOQ parameter.
See TPF Operations for more information about the ZMQSC SWQ command.
MQSC0619E | xxx FAILED FOR QUEUE MANAGER, ERROR CODE nn |
Where:
Explanation: The ZMQSC DEF MQP or ZMQSC ALT MQP command was entered on this or another processor, but the memory copy of the queue manager profile could not be updated.
System Action: The queue manager profile is defined or updated on file, but not in memory.
User Response: See your IBM service representative.
See TPF Operations for more information about the ZMQSC DEF MQP and ZMQSC ALT MQP commands.
MQSC0700I | PROCESS-processname DEFINITION COMPLETED SUCCESSFULLY |
Where:
Explanation: This is the normal response to the ZMQSC DEF PROCESS command.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZMQSC DEF PROCESS command.
MQSC0701I | MQSERIES TABLES SUCCESSFULLY REBUILT FROM PREVIOUS IPL |
Explanation: MQSeries control tables used by TPF MQSeries local queue manager support have been successfully rebuilt during TPF system restart.
System Action: None.
MQSC0702W | MQSERIES TABLES INITIALIZED ON FILE |
Explanation: During TPF system restart, the MQSeries queue manager (QM) determined that the MQSeries control tables on file did not exist yet. Therefore, the MQSeries QM initialized these tables and saved them to file.
System Action: The MQSeries control records on file are initialized.
MQSC0703W | numrec IMQCK RECORDS BELOW SUGGESTED MINIMUM OF min |
Where:
Explanation: The TPF system detected that the number of #IMQCK records allocated for the MQSeries checkpoint is below the suggested minimum. The suggested minimum is equivalent to twice the number of system work blocks (SWBs) allocated to the TPF system.
System Action: None.
User Response: Do the following:
See TPF Database Reference for more information about the #IMQCK fixed file record ordinals.
MQSC0704E | PROCESS-processname ALREADY EXISTS |
Where:
Explanation: ZMQSC DEF PROCESS-processname was entered, but the specified process already exists.
System Action: The command is rejected.
User Response: Do one of the following:
See TPF Operations for more information about the ZMQSC DEF PROCESS and ZMQSC DISPLAY commands.
MQSC0705E | PROCESS-processname DEFINITION DOES NOT EXIST |
Where:
Explanation: A ZMQSC command was entered with a process name specified that does not exist.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about ZMQSC commands.
MQSC0706I | MQSERIES TRANSACTIONS SUCCESSFULLY RECOVERED FOR CPU cpuid |
Where:
Explanation: During TPF system restart, or in response to the ZPSMS command with the PR and DEACT parameters specified, the MQSeries resource manager (RM) determined that there were oustanding MQSeries transaction branches to recover on the recovery log.
System Action: All outstanding transactions are successfully recovered.
User Response: None.
See TPF Operations for more information about the ZPSMS command.
MQSC0707E | MQSERIES ACTIVITY PROHIBITED FOR PROCESSOR cpuid |
Where:
Explanation: During TPF system restart, or while processing the ZMQSC DEF MQP command, the TPF system detected that there are no fixed files of record type #IMQCK defined for this processor.
System Action: No MQSeries activity is allowed for this TPF processor.
User Response: Do the following:
See TPF Operations for more information about the
ZMQSC DEF MQP command. See TPF Database Reference for more information about #IMQCK
fixed file records.
Where:
Explanation: While attempting to lock MQSeries dynamic link library (DLL) CMQS into memory,
the getpc function failed with return code x.
System Action: The TPF restart program continues.
User Response: Determine why the getpc function failed.
See theTPF C/C++ Language Support User's
Guide for a description of the errors returned by the getpc
function.MQSC0708E MQSERIES GETPC ERROR x LOCKING CMQS IN MEMORY
MQSC0721I | PROCESS-processname DEFINITION ALTERED SUCCESSFULLY |
Where:
Explanation: This is the normal response when you enter ZMQSC ALT PROCESS-processname.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZMQSC ALT PROCESS command.
MQSC0722I | TPF MQSERIES PROCESS DISPLAY |
Explanation: This is the normal response when you enter ZMQSC DISPLAY PROCESS-processname.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZMQSC DISPLAY command.
MQSC0723I | PROCESS-processname DELETED SUCCESSFULLY |
Where:
Explanation: This is the normal response when you enter ZMQSC DEL PROCESS-processname.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZMQSC DEL command.
MQSC0724E | parm NOT VALID FOR XMITQ queuename |
Where:
Explanation: A ZMQSC command was entered with a parameter that is not allowed with the XMITQ parameter.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMQSC commands.
MQSC0725E | PROCESS DEFINITION TABLES ARE NOT INITIALIZED |
Explanation: A ZMQSC command was entered with the PROCESS parameter specified, but the process definition tables are not initialized. Process definition tables are initialized by stopping and starting the queue manager after enhancements to TPF MQSeries local queue manager support code have been installed.
System Action: The command is rejected.
User Response: Do the following:
See TPF Migration Guide: Program Update Tapes for more information about enhancements to TPF MQSeries local queue manager support. See TPF Operations for more information about the ZMQSC commands.
MQSC0801I | SWEEP FOR qname IS COMPLETED |
Where:
Explanation: The messages on this queue have been moved from memory to file. The next access of the queue will move the messages from file back to memory.
System Action: None.
User Response: None.
MQSC0802I | UNSWEEP FOR qname IS COMPLETED |
Where:
Explanation: When the queue was accessed again, it moved the messages from file back to memory.
System Action: None.
User Response: No action is necessary. Note: If you're getting this message too frequently, you may want to change your sweeptime with the ZMQSC ALT QL command.
See TPF Operations for more information about the
ZMQSC ALT QL command.
Explanation: This is the normal response to the ZMQSC DBREBUILD
command.
System Action: None.
User Response: None.
See TPF Operations for more information about the
ZMQSC DBREBUILD command.
Explanation: The ZMQSC DBREBUILD command was entered, but one or
more errors were found that prevented the TPF system from rebuilding all of
the TPF MQSeries definitions.
System Action: Some TPF MQSeries definitions were not rebuilt, but the definitions that were
not rebuilt are still stored in their original collections. The TPF
system sends an additional message for each error, describing the nature of
the error.
User Response: Do the following:
See TPF Operations for more information about the
ZMQSC DBREBUILD command.
Where:
Explanation: A ZMQSC command was entered, but more than one processor is active in a
loosely coupled environment.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about
ZMQSC commands.
Explanation: The ZMQSC DBREBUILD command was entered, but the
TPF MQSeries queue manager is active on the subsystem where you entered the
command.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the
ZMQSC DBREBUILD and ZMQSC STOP commands. Where:
Explanation: An unexpected logic error occurred during processing.
System Action: The MQSeries function that was being processed has ended and an error
condition has been reported to the application that started the
function.
User Response: See your IBM service representative and provide the information that was
included in the error message.
Where:
Explanation: An unexpected logic error occurred during processing.
System Action: The MQSeries function that was being processed has ended and an error
condition has been reported to the application that started the
function.
User Response: See your IBM service representative and provide the information that was
included in the error message.MQSC0900I DBREBUILD COMPLETED SUCCESSFULLY
MQSC0901E DBREBUILD FAILED
MQSC0950E command REJECTED - MORE THAN ONE PROCESSOR ACTIVE
MQSC0951E DBREBUILD REJECTED - QMGR NOT STOPPED
MQSC9996E MQSERIES UNEXPECTED TO2 ERROR source_file
mqseries_routine TO2_error
MQSC9997E MQSERIES UNEXPECTED COMMIT ROLLBACK ERROR source_file
mqseries_routine tx return code=n
MQSC9998E | UNEXPECTED CHANNEL ERROR errornum |
Where:
Explanation: An unexpected error occurred during channel processing. Generally these represent logic errors.
System Action: Channel processing does not complete successfully.
User Response: See your IBM representative to determine the cause of the error and to correct the problem.
See TPF Operations for more information about the ZMQSC commands.
MQSC9999E | UNEXPECTED ERROR errornum |
Where:
Explanation: A ZMQSC command was entered, but an unexpected error occurred. Generally these represent logic errors.
System Action: The command is rejected.
User Response: See your IBM representative to determine the cause of the error and to correct the problem.
See TPF Operations for more information about the ZMQSC commands.