An internal WebSphere MQ data collection service failed.
During WebSphere MQ component initialization, no MQ subsystems were found.
While attempting to select or connect to an MQ queue manager, no active queue manager was found.
An internal WebSphere MQ data collection service failed to successfully issue a PCF command.
While attempting to select or connect to an MQ queue manager, no active queue manager was found.
This message indicates that the selected queue manager is now the current target queue manager. MQ commands are always directed to to the current target queue manager.
An attempt to verify the target queue manager's asid failed. This can occur if the target queue manager was stopped or restarted before a data collection request was completed.
This message is issued when a line command entered from the current display cannot be processed due to the current state of the selected queue manager. For example, stopping a queue manager that is already stopped, or was never started.
This message is issued after the PCF command error message if there are PCF message attributes to be displayed. Each attribute in the PCF message is displayed with one or more of these messages.
This message indicates that the connect command failed because there is already a connection to the target queue manager.
This message indicates that the disconnect command failed because there is no connection to the target queue manager.
This message indicates that there is no output for the target queue manager.
This message indicates that you are not authorized to view any of the queue manager's output or no output exists.
This message indicates that the target queue manager failed to respond to a data collection request. See the MQMSGLOG for details.
The command was entered with an invalid parameter specified.
This message is displayed following execution of the MQCLEAN command. MQCLEAN is issued to clean up any reply-to-queues allocated as part of normal operation. Typically, these queues are automatically unless the system shuts down abnormally.
This message is displayed when an undefined queue name is specified as a command argument.
This message is displayed when a non-local queue name is specified as an command argument to a command that requires a local queue command argument. Examples are MQBROWSE <local-qname> and MQCLEAR <local-qname>.
This message is displayed when the target queue name specified on the MQCLEAR command has opened processes. Queues cannot be cleared if they are in use.
This message indicates that the queue selected as the target of the MQCLEAR command has no messages queued.
This message indicates that the selected message cannot be copied or forwarded to the destination Queue/Qmgr. A message in the MQ Dead Letter Queue cannot be redirected without an MQ Dead Letter Header using command <cmd>.
This message indicates that the MQCLEAR command has completed and the target queue has been cleared of all messages.
This message indicates that an invalid line command has been issued for the selected queue manager.
This message indicates that the START QMGR failed because the selected queue manager is already active.
This message indicates that the START CHINIT failed because the associated queue manager is not active. The queue manager must be started before the channel initiator.
This message indicates that the START CHINIT command failed because the queue manager channel initiator is already active.
This message indicates that the selected queue manager cannot be stopped because it is not active.
This message indicates that the channel initiator, associated with <qmgr>, cannot be stopped because it is not active.
This message typically indicates that the selected resource has been deleted or is not a valid target for the command entered.
This message indicates that the command was entered with an unrecognized parameter. This typically occurs on the DEFINE subcommand entered from any of the WebSphere MQ object displays.
An attempt to START or STOP a WebSphere MQ resource failed because the resource may already be started or stopped. For more information, see the Line Commands section on the HELP MQDQMGR display.
An attempt was made to STOP a WebSphere MQ resource, from the MQDQMGR display, but the resource is not active. For more information see the Line Commands section on the HELP MQDQMGR display.
The START LISTENER TRPTYPE(TCP) failed because and invalid port number was specified.
The START LISTENER TRPTYPE(LU62) failed because the LU name parameter is not specified.
An attempt to define an MQ object failed because the object is already defined.
An attempt to define a WebSphere MQ object, using an existing object of the same type, failed because the model object cannot be found.
The command failed. See the MQMSGLOG for details.
The delete queue failed because the queue either has queued messages or active processes using it.
The delete queue failed because the queue has queued messages. Try the PURGE command.
Objects reserved by the WebSphere MQ subsystem cannot be defined or deleted.
This message shows the status of the last command executed.
The define command failed because the LIKE keyword has an invalid or missing parameter. Use LIKE to specify a model for the object being defined.
The define failed because the model object is not the same type as the object being defined.
The define failed because no default attributes for this object type were found. Use the LIKE keyword to specify a model with the desired attributes.
An active channel cannot be deleted.
The specified object already exists.
The MQ API load module CSQBSTUB was not found at the location specified in the MQSERIES PARMLIB member. Check the setting of API-LOAD-LIBRARY.
The command failed because the command syntax is incomplete.
The command failed because the command argument is not sufficiently qualified.
The command failed because the command argument is not a valid object or attribute.
The value entered exceeds the maximum length for the field selected.
The value specified is invalid for the selected keyword.
The value entered exceeds the maximum length for the field selected.
The selected field or parameter value requires a numeric value and the value specified is not numeric.
The value entered is less that the minimum allowable value for the selected field.
The value entered is greater than the maximum allowable value for the selected field.
The value entered is shorter that the minimum allowable length for the selected field.
The value entered is longer that the maximum allowable length for the selected field.
The syntax specified is invalid for the selected field.
The syntax specified is invalid for the selected field.
The command failed due to an editing error. See MQMSGLOG for details.
The DEFINE command that was generated for this object is too long for the command server to process.
Reduce the size of the data in one of the long variables that that is allowed to be altered after the object is defined. Use the MQALTER command to alter the value after the object has been defined.
The command failed because the queue is disabled for GET. Enable it by altering the GET attribute and try again. See HELP MQALTER for details.
The selected message no longer exists. This may occur when the message is removed or deleted before the display is refreshed.
The "MQCLEAR" command succeeded.
The number of messages read is limited by the BROWSE-MSG-COUNT-MAXIMUM parameter in the MQSERIES parmlib member. Increase the value if you wish to see all the messages currently queued.
A dead letter queue is not defined on the target queue manager.
The connection to the target queue manager has been broken. Reconnect using the MQCONN command.
An invalid keyword is specified. See the information line for the list of available options.
This message is issued when a call to an WebSphere MQ service routine has been issued.
This message is issued upon successful completion of a call to an WebSphere MQ service routine.
This message indicates a warning in an WebSphere MQ service routine.
This message indicates a failure in an WebSphere MQ service routine.
This message indicates an abend in an WebSphere MQ service routine.
This message indicates the selected line command was already processed for the selected message.
This message indicates the selected message was unsuccessfully copied or forwarded to the destination Queue/Qmgr. Issue the MQMSGLOG command to see the details.
This message indicates the selected message was unsuccessfully copied or forwarded to the destination Queue/Qmgr because the selected message is not unique.
The specified command failed because the selected message is no longer in the queue. The message may have been deleted or forwarded to another queue.
WebSphere MQ initialization failed because the required SVC services are not available.
Specify a queue manager name and try again.
During command processing, we discard messages from the command reply-to-queue because the correlation ID did not match. This can be the result of a "response not received" or "timeout" condition that occurred on a previous command.
The command is not supported at the target queue manager version of WebSphere MQ.
The specified keyword is not supported at the target queue manager version of WebSphere MQ.
An I/O error occurred while doing a directory search (BLDL) for the MQ API module CSQBSTUB. Check the setting of API-LOAD-LIBRARY in the MQSERIES PARMLIB member.
The subcommand is not valid for the current display. Go to the Subcommands Section of the HELP screen for the display to see the list of valid subcommands.
An invalid line command was entered for the current display. Type HELP and then go to the line commands section to see the list of valid line commands.
The command entered is not valid for the object type specified.
The specified object could not be found or the object attribute is not a valid attribute for the object type selected.
The specified object could not be found.
The command entered is invalid in this context.
More than one object with the same name exists. In order to qualify the object, add the CHLTYPE parameter and try again.
This may occur if we are to determine the command level of the target queue manager. Typically, the command level is determined when a queue manager connection is established. See MQMSGLOG for details.
This may occur if we are is unable to determine the command level of the target queue manager. Typically, the command level is determined when a queue manager connection is established. See MQMSGLOG for details.
The specified command is valid only for cluster queue managers.
The specified command is invalid because the current state of the target queue manager may not be appropriate for the command.
The specified command is valid only for a repository cluster queue manager.
This message number is used to issue messages received from other sources, such as, WebSphere MQ itself.
This message indicates that a connection to the specified queue manager is being established.
The connection to the specified queue manager is established.
The specified queue is being opened.
The queue specified in the previous message is now open.
The specified queue is being closed.
The queue specified in the preceding message is now closed.
The specified queue manager connection is closing.
The queue manager connection in the preceding message is now closed.
This message indicates that the queue manager is being opened for inquire processing.
This message indicates that a queue manager inquire is in progress.
This message indicates that the inquire has completed.
This message indicates that the queue manager is closing.
This message indicates that an inquire is in progress to determine queue attributes for the specified queue.
This message indicates that the target queue manager has terminated or stopped.
This message indicates that the queue manager cleanup routines have completed processing.
The specified queue manager is at the command level indicated in the message.
This message names the dynamic reply-to-queue opened to receive command responses.
This message signals the start of a WebSphere MQ request.
This message indicates that the request has completed.
This is the total external and internal elapsed CPU time used by the command. External time measures time attributable to the queue manager or channel initiator address spaces.
This is the total external and internal CPU time used by the command. External time measures time attributable to the queue manager or channel initiator address spaces.
This messages indicates how many, and the type of, WebSphere MQ API requests that were required to complete the command.
An internal request to obtain the target queue manager's ALET failed. This may occur when the queue manager is in the process of shutting down or abnormally terminating and a data collection request is in progress.
The WebSphere MQ cross memory data collection interface for the target queue manager is initialized.
This message indicates that the target queue manager is stopping or terminating and that normal command processing cannot continue.
This message indicates that the target queue manager is at a version of WebSphere MQ that is not supported.
This message indicates that DB2 statistics are not available. If the target queue manager was not started as part of a data sharing group, no DB2 data will be available. In addition, the queue manager must be recording SMF 115 records ( DB2 subtype ). See the WebSphere MQ System Setup guide, section Using System Management Facility for more information.
This message indicates that the command entered is not supported for the target queue manager WebSphere MQ version.
This message indicates that the channel initiator has been stopped or recycled while a command is in progress.
This message indicates that the current command cannot continue because the channel initiator is not active.
This message indicates that CSQUTIL completed with a return code of 0. Issue the MQMSGLOG command for more details.
This message indicates CSQUTIL completed with a return code of 4. Issue the MQMSGLOG command for more details.
This message indicates that CSQUTIL completed with a return code greater than or equal to 8. Issue the MQMSGLOG command for more details.
This message indicates that the IMPORT or EXPORT command must be specified to complete the message transfer. IMPORT will copy messages to the target queue from the source data set. EXPORT will copy messages to the target data set from the source queue.
Informational only.
The targeted Qmgr was not found.
The targeted Qmgr is stopping.
The targeted Queue was not found.
The targeted Queue is not a local queue.
The targeted dsname is not cataloged.
A LOCATE request failed for the targeted dsname.
The volume required to locate the targeted dsname is not mounted.
The targeted dsname does not reside on the volume specified.
A OBTAIN request failed for the targeted dsname on the volume specified.
A OBTAIN request failed for the targeted dsname on the volume specified.
The targeted dsname requires DSORG=PS.
TThe targeted dsname requires DSORG=VBS.
The targeted dsname is a partitioned data set.
The targeted dsname is a partitioned data set.
The MQEDIT command can only be invoked as a line command from the MQBROWSE display.
An error occurred while process the WebSphere MQ MQI command. Issue the MQMSGLOG command to see the return and reason codes associated with the failure.
The current or updated message has been saved and replaces the original message on the target queue.
The edit session has been canceled. This action causes the original message to be restored to the target queue in its original unmodified state.
This message is issued when a user attempts to edit a message while another edit session is in progress.
This message is issued when an error has occurred while attempting to save the target message. For example, the GET failed for the target message and a SAVE subcommand is inadvertently issued.
This message is issued when the Qmgr is stopped or terminates while an MQEDIT session is in progress. It indicates the target message will be restored to the target queue in its original unmodified state. No further processing can take place on the edit session, because the target qmgr has terminated. Enter PF3 or the CANCEL subcommand to terminate the edit session.
Informational only.
This message is issued when the Qmgr is stopped or terminates while an MQEDIT session is in progress. It indicates the target message has been restored to the target queue in its original unmodified state. No further processing can take place on the edit session, because the target qmgr has terminated. Enter PF3 or the CANCEL subcommand to terminate the edit session.
This message indicates that there is no connection to the target Qmgr. Issue the MQCONN <qmgr> command to establish a connection.
This message indicates that the command entered is not valid when a message editing session is in progress. The command may cause the session target Qmgr connection to be lost.
This message indicates that the target message has been restored into the target queue in its original unmodified state.
This message indicates that invalid hex input was entered during an MQEDIT session. The range of valid hex characters is 0-9 and A-F.
This message indicates that non-displayable characters were found in the message header, data, or context. These characters are converted to a displayable character specified by the NONDISPLAY character setting.
When the CONFIRM option is in effect, this message indicates you are trying to exit the edit session, but the message was modified. Issue the SAVE command to save the changes or repeat the command to exit. Repeating the command cancels the changes.
This message indicates the character <char> cannot be entered as an input character because it is the same character used to represent non-displayable characters on the display. To enter this character as input, either change the NONDISPLAY setting using the SET NONDISPLAY <char> command or use the OPTION HEX subcommand to edit the message in hex mode.
The command you entered requires that the product server address space be active and it is not active.
Historical request monitoring is not active for the specified queue manager.
The requested data could not be displayed. No active queue manager could be found.
The requested data could not be displayed. No monitored queue manager could be found.
A request was made to select or drill into the selected linetype. Additional information is not available.
A request was made to read a WebSphere MQ message, however the message size exceeds the maximum allowed.
No historical request monitoring data is available for any queue manager. Only current interval data may be available. After the current interval completes then history data will be available. If the current interval completes and still no history data is available contact CA Technical Support.
The command failed because an unexpected keyword was found. Correct the command syntax and reissue the command.
A request was made to define a new object, but an object of the same name already exists.
A command was issued as a result of the requested action. See the MQMSGLOG for result details.
The command failed because the data set specified is not cataloged.
The queue manager has been started with a parameter module that was built with macros from a release that is not supported. To see the queue manager parameters, rebuild the parameter module using macros supplied with the release of the queue manager that is running.
A line command was issued for an object that does not allow it based on the condition specified.
An "instance" channel stop command was issued, but there is no instance of the channel running. Only channels with a connection name can be stopped using one of the stop instance line commands.
The number of messages that were successfully moved from one local queue to another.
An external line command, <cmd>, was defined to invoke REXX exec <execname>, but the line command was not defined in exec and was rejected.
IMS based line commands like <cmd> are not designed to be run against IMS control regions.
The line command requested cannot be issued against a row representing the specified connection type.
The value specified for the MQI request trace <option> is invalid. For a list of valid keywords, review the help for the command.
The define command failed because the TSTRING keyword has a missing parameter.
The specified command cannot be issued against cluster queue manager <qmgr> because it is on a remote system.
An attempt to allocate or open the WebSphere MQ API load library failed. Ensure that API-LOAD-LIBRARY in the MQSERIES parmlib member specifies the correct <MQHLQ>.SCSQAUTH data set name.
Check that the API-LOAD-LIBRARY setting in the MQSERIES parmlib member specifies the correct library name for the MQ API. If it has a value of NONE, the modules will not get loaded.
The channel name specified cannot contain a mask character.
A function was performed against one or more local queue managers <qmgrs> and one or more objects <objs>. The message indicates the number of requests that succeeded <success> and failed <failure>.
This message is only displayed for requests to the local system.
Either masking characters were specified in the parm and they are not allowed or an incorrect use of masking characters was used. Check with the command help for the proper use of masking characters.
A command was issued that requires a current target queue manager, but none were found. If your MQTGTDEF profile variable is set to to NOAUTO, the command could not automatically switch to an active queue manager. Use the MQSERIES command to switch to an active queue manager or switch your MQTGTDEF profile variable to a setting that allows auto switching.
|
Copyright © 2013 CA.
All rights reserved.
|
|