AMQ8000-AMQ8999 WebSphere MQ administration messages - Middleware News
-------------------------------
AMQ8001 WebSphere MQ queue manager created.
Explanation: WebSphere MQ queue manager &5 created.
User Response: None.
AMQ8002 WebSphere MQ queue manager '&5' deleted.
Explanation: WebSphere MQ queue manager '&5' deleted.
User Response: None.
AMQ8003 WebSphere MQ queue manager '&5' started.
Explanation: WebSphere MQ queue manager '&5' started.
User Response: None.
AMQ8004 WebSphere MQ queue manager '&5' ended.
Explanation: WebSphere MQ queue manager '&5' ended.
User Response: None.
AMQ8005 WebSphere MQ queue manager changed.
Explanation: WebSphere MQ queue manager &5 changed.
User Response: None.
AMQ8006 WebSphere MQ queue created.
Explanation: WebSphere MQ queue &5 created.
User Response: None.
AMQ8007 WebSphere MQ queue deleted.
Explanation: WebSphere MQ queue &5 deleted.
User Response: None.
AMQ8008 WebSphere MQ queue changed.
Explanation: WebSphere MQ queue &5 changed.
User Response: None.
AMQ8010 WebSphere MQ process created.
Explanation: WebSphere MQ process &5 created.
User Response: None.
AMQ8011 WebSphere MQ process deleted.
Explanation: WebSphere MQ process &5 deleted.
User Response: None.
AMQ8012 WebSphere MQ process changed.
Explanation: WebSphere MQ process &5 changed.
User Response: None.
AMQ8014 WebSphere MQ channel created.
Explanation: WebSphere MQ channel &5 created.
User Response: None.
AMQ8015 WebSphere MQ channel deleted.
Explanation: WebSphere MQ channel &5 deleted.
User Response: None.
AMQ8016 WebSphere MQ channel changed.
Explanation: WebSphere MQ channel &5 changed.
User Response: None.
AMQ8018 Start WebSphere MQ channel accepted.
Explanation: The channel &5 is being started. The start channel function has been initiated. This involves a series of operations across the network before the channel is actually started. The channel status displays "BINDING" for a short period while communication protocols are negotiated with the channel with whom communication is being initiated.
User Response: None.
AMQ8019 Stop WebSphere MQ channel accepted.
Explanation: The channel &5 has been requested to stop.
User Response: None.
AMQ8020 Ping WebSphere MQ channel complete.
Explanation: Ping channel &5 complete.
User Response: None.
AMQ8021 WebSphere MQ Listener program started.
Explanation: The channel listener program has been started.
User Response: None.
AMQ8022 WebSphere MQ queue cleared.
Explanation: All messages on queue &5 have been deleted.
User Response: None.
AMQ8023 WebSphere MQ channel reset.
Explanation: Channel &5 has been reset.
User Response: None.
AMQ8024 WebSphere MQ channel initiator started.
Explanation: The channel initiator for queue &5 has been started.
User Response: None.
AMQ8025 WebSphere MQ channel resolved.
Explanation: In doubt messages for WebSphere MQ channel &5 have been resolved.
User Response: None.
AMQ8026 End WebSphere MQ queue manager accepted.
Explanation: A controlled stop request has been initiated for queue manager &5.
User Response: None.
AMQ8027 WebSphere MQ command server started.
Explanation: The command server has been started.
User Response: None.
AMQ8028 WebSphere MQ command server ended.
Explanation: The command server has been stopped.
User Response: None.
AMQ8029 WebSphere MQ authority granted.
Explanation: Authority for object &5 granted.
User Response: None.
AMQ8030 WebSphere MQ authority revoked.
Explanation: Authority for object &5 revoked.
User Response: None.
AMQ8033 WebSphere MQ object recreated.
Explanation: MQ object &5 has been recreated from image.
User Response: None.
AMQ8034 WebSphere MQ object image recorded.
Explanation: Image of MQ object &5 has been recorded.
User Response: None.
AMQ8035 WebSphere MQ Command Server Status . . : Running
Explanation: None.
User Response: None.
AMQ8036 WebSphere MQ command server status . . : Stopping
Explanation: None.
User Response: None.
AMQ8037 WebSphere MQ command server status . . : Starting
Explanation: None.
User Response: None.
AMQ8038 WebSphere MQ command server status . . : Running with queue disabled
Explanation: None.
User Response: None.
AMQ8039 WebSphere MQ command server status . . : Stopped
Explanation: None.
User Response: None.
AMQ8040 WebSphere MQ command server ending.
Explanation: None.
User Response: None.
AMQ8041 The queue manager cannot be restarted or deleted because processes, that were previously connected, are still running.
Explanation: Processes, that were connected to the queue manager the last time it was running, are still active. The queue manager cannot be restarted.
User Response: Stop the processes and try to start the queue manager.
AMQ8042 Process &1 is still running.
Explanation:
User Response:
AMQ8043 Non runtime application attempted to connect to runtime only queue manager.
Explanation: A non runtime application attempted to connect to a queue manager on a node where support for non runtime applications has not been installed. The connect attempt will be rejected with a reason of MQRC_ENVIRONMENT_ERROR.
User Response: If the node is intended to support only runtime applications, investigate why a non runtime application has attempted to connect to the queue manager. If the node is intended to support non runtime only applications, investigate if the base option has been installed. The base option must be installed if non runtime applications are to run on this node.
AMQ8044 An error occurred while removing the queue manager from the Active Directory.
Explanation: The attempt to remove the queue manager from the Windows Active Directory failed. This may be because the appropriate entry could not be opened or modified, or the Service Control Point has already been removed.
User Response: Check that your account has the authority to delete objects from the Active Directory, and that the entry has not already been deleted.
AMQ8045 An error occurred while removing the queue manager from the Service Control Manager.
Explanation: The attempt to remove the queue manager from the Windows registry failed. This may be because the appropriate entry could not be opened or modified.
User Response: Check that the registry has sufficient space on your disk to grow and that your account has the authority to modify it.
AMQ8048 Default objects statistics : &1 created. &2 replaced. &3 failed.
Explanation: Information on the number of objects created or replaced successfully as well as any failures that occurred while creating the default objects.
User Response: None.
AMQ8049 Object &4. Unable to create or replace.
Explanation: While creating or replacing the default object &4 for WebSphere MQ queue manager &5 an error occurred. The error was due to improper authorization. The reason code is &1.
User Response: Check this log for more details of what the problem may be. Make sure there are sufficient resources such as disk space and storage. For damaged or corrupted objects, replace these from backup objects. If all else fails, delete the queue manager &5 using dltmqm and create it again using crtmqm.
AMQ8050 Creating or replacing default objects for &3.
Explanation:
User Response: None.
AMQ8051 For details of the failures that occurred, please check AMQERR01.LOG.
Explanation:
User Response: None.
AMQ8051 For details of the failures that occurred, please check MQERRLG1.
Explanation:
User Response: None.
AMQ8052 Completing setup.
Explanation:
User Response: None.
AMQ8053 Object &4. Unable to create or replace.
Explanation: While creating or replacing the default object &4 for WebSphere MQ queue manager &5 an error occurred. The error was due to a broken connection. The reason code is &1.
User Response: Check this log for more details of what the problem may be. Make sure there is sufficient resources such as disk space and storage. For damaged or corrupted objects, replace these from backup objects. If all else fails, delete the queue manager &5 using dltmqm and create it again using crtmqm.
AMQ8054 Object &4. Unable to create or replace.
Explanation: While creating or replacing the default object &4 for WebSphere MQ queue manager &5 an error occurred. The error was due to unavailable storage. The reason code is &1.
User Response: Check this log for more details of what the problem may be. Make sure there is sufficient resources such as disk space and storage. For damaged or corrupted objects, replace these from backup objects. If all else fails, delete the queue manager &5 using dltmqm and create it again using crtmqm.
AMQ8055 Object &4. Unable to create or replace.
Explanation: While creating or replacing the default object &4 for WebSphere MQ queue manager &5 an error occurred. The error was due to a damaged object. The reason code is &1.
User Response: Check this log for more details of what the problem may be. Make sure there is sufficient resources such as disk space and storage. For damaged or corrupted objects, replace these from backup objects. If all else fails, delete the queue manager &5 using dltmqm and create it again using crtmqm.
AMQ8056 Object &4. Unable to create or replace.
Explanation: While creating or replacing the default object &4 for WebSphere MQ queue manager &5 an error occurred. The error was due to a channel definition error. The error code is &1 (X'&2').
User Response: Check this log for more details of what the problem may be. Make sure there is sufficient resources such as disk space and storage. For damaged or corrupted objects, replace these from backup objects. If all else fails, delete the queue manager &5 using dltmqm and create it again using crtmqm.
AMQ8057 Object &4. Unable to create or replace.
Explanation: While creating or replacing the default object &4 for WebSphere MQ queue manager &5 an error occurred. The error was due to invalid records in the channel definition file. The error code is &1 (X'&2').
User Response: Check this log for more details of what the problem may be. Make sure there is sufficient resources such as disk space and storage. For damaged or corrupted objects, replace these from backup objects. If all else fails, delete the queue manager &5 using dltmqm and create it again using crtmqm.
AMQ8058 Object &4. Unable to create or replace.
Explanation: While creating or replacing the default object &4 for WebSphere MQ queue manager &5 an error occurred. The error was due to not finding the channel definition file. The error code is &1 (X'&2').
User Response: Check this log for more details of what the problem may be. Make sure there is sufficient resources such as disk space and storage. For damaged or corrupted objects, replace these from backup objects. If all else fails, delete the queue manager &5 using dltmqm and create it again using crtmqm.
AMQ8059 Object &4. Unable to create or replace.
Explanation: While creating or replacing the default object &4 for WebSphere MQ queue manager &5 an error occurred. The error was due to an unexpected error, error code &1 (X'&2').
User Response: Check this log for more details of what the problem may be. Make sure there is sufficient resources such as disk space and storage. For damaged or corrupted objects, replace these from backup objects. If all else fails, delete the queue manager &5 using dltmqm and create it again using crtmqm.
AMQ8061 Command '&4' is not valid.
Explanation: The command '&4' at line &1 in the WebSphere MQ service command file '&3' for queue manager '&5' is not valid for use in the service command file. The line is ignored.
User Response: Check the contents of the file and retry the operation.
AMQ8062 Unexpected return code, '&1', from command '&3'.
Explanation: An unexpected return code, '&1', was returned by command '&3'. This command was issued by the WebSphere MQ service for queue manager '&4'.
User Response: Verify that the command and parameters are correct.
AMQ8063 Not authorized to issue command '&3'.
Explanation: The current user '&5' is not authorized to issue the command '&3'. The command is ignored.
User Response: Add the user to the local 'mqm' security group and retry the operation.
AMQ8064 Not authorized to start trusted application.
Explanation: The user '&5' is not authorized to start the trusted application '&3'. The application has not started.
User Response: Add the user to the local 'mqm' security group and restart the application.
AMQ8065 Local group '&3' not found.
Explanation: The local group '&3' is unavailable. It is not possible to verify that the user is authorized. The function cannot continue.
User Response: Create the required local group and retry the operation.
AMQ8066 Local mqm group not found.
Explanation: The local mqm group is unavailable. It is not possible to verify that the user is authorized. The function cannot continue.
User Response: Create the local mqm group and retry the operation.
AMQ8067 WebSphere MQ channel auto-defined.
Explanation: Channel &5 auto-defined.
User Response: None.
AMQ8068 Setup completed.
Explanation:
User Response: None.
AMQ8069 ApplicationGroup for the crtmqm command does not contain the mqm userid.
Explanation: WebSphere MQ queue manager &5 not created. The ApplicationGroup specified for the crtmqm command must contain the mqm userid when the RestrictedMode option (-g) is specified.
User Response: None.
AMQ8070 ApplicationGroup for crtmqm command is not defined.
Explanation: WebSphere MQ queue manager &5 not created. RestrictedMode option (-g) specified, but the ApplicationGroup does not exist.
User Response: None.
AMQ8071 RestrictedMode option not supported on this platform.
Explanation: WebSphere MQ queue manager &5 not created. The RestrictedMode option was specified but is not supported on this platform.
User Response: None.
AMQ8072 Not authorized to administer channels.
Explanation: The command server for queue manager '&3' received an administration command for channels. The user '&5' is not authorized to administer WebSphere MQ channels. The command server has not processed the command.
User Response: Add the user to the local 'mqm' security group, and ensure that the security policy is set as required.
AMQ8073 Authorization failed because SID: (&3) could not be resolved.
Explanation: The Object Authority Manager was unable to resolve the specified SID into entity and domain information.
User Response: Ensure that the application provides a SID that is recognized on this system, that all necessary domain controllers are available, and that the security policy is set as you required.
AMQ8074 Authorization failed as the SID '&3' does not match the entity '&4'.
Explanation: The Object Authority Manager received inconsistent data - the supplied SID does not match that of the supplied entity information.
User Response: Ensure that the application is supplying valid entity and SID information.
AMQ8075 Authorization failed because the SID for entity '&3' cannot be obtained.
Explanation: The Object Authority Manager was unable to obtain a SID for the specified entity.
User Response: Ensure that the entity is valid, and that all necessary domain controllers are available.
AMQ8076 Authorization failed because no SID was supplied for entity '&3'.
Explanation: The Object Authority Manager was not supplied with SID information for the specified entity, and the security policy is set to 'NTSIDsRequired'.
User Response: Ensure that the application is supplying a valid SID, and that the security policy is set as you require.
AMQ8077 Entity '&3' has insufficient authority to access object '&4'.
Explanation: The specified entity is not authorized to access the required object. The following requested permissions are unauthorized: &5
User Response: Ensure that the correct level of authority has been set for this entity against the required object, or ensure that the entity is a member of a privileged group.
AMQ8078 Waiting for queue manager '&3' to end.
Explanation:
User Response: None.
AMQ8079 Access was denied when attempting to retrieve group membership information for user '&3'.
Explanation: WebSphere MQ, running with the authority of user '&4', was unable to retrieve group membership information for the specified user.
User Response: Ensure Active Directory access permissions allow user '&4' to read group memberships for user '&3'. To retrieve group membership information for a domain user, MQ must run with the authority of a domain user.
AMQ8101 Unexpected error (&1).
Explanation: An unexpected reason code with hexadecimal value &1 was received from the WebSphere MQ queue manager during command processing. (Note that hexadecimal values in the range X'07D1'-X'0BB7' correspond to MQI reason codes 2001-2999.) More information might be available in the log. If the reason code value indicates that the error was associated with a particular parameter, the parameter concerned is &4.
User Response: Correct the error and then try the command again.
AMQ8102 WebSphere MQ object name specified in &4 not valid.
Explanation: The object name &5 specified in &4 is not valid. The length of the name must not exceed 48 characters, or 20 characters if it is a channel name. The name should contain the following characters only: lowercase a-z, uppercase A-Z, numeric 0-9, period (.), forward slash (/), underscore (_) and percent sign (%).
User Response: Change the length of the parameter value or change the parameter value to contain a valid combination of characters, then try the command again.
AMQ8103 Insufficient storage available.
Explanation: There was insufficient storage available to perform the requested operation.
User Response: Free some storage and then try the command again.
AMQ8104 WebSphere MQ directory &3 not found.
Explanation: Directory &3 was not found. This directory is created when WebSphere MQ is installed successfully. Refer to the log for more information.
User Response: Verify that installation of WebSphere MQ was successful. Correct the error and then try the command again.
AMQ8105 Object error.
Explanation: An object error occurred. Refer to the log for more information.
User Response: Correct the error and then try the command again.
AMQ8106 WebSphere MQ queue manager being created.
Explanation: The queue manager is being created.
User Response: Wait for the creation process to complete and then try the command again.
AMQ8107 WebSphere MQ queue manager running.
Explanation: The queue manager is running.
User Response: None.
AMQ8108 WebSphere MQ queue manager '&3' ending.
Explanation: The queue manager '&3' is ending.
User Response: Wait for the queue manager to end and then try the command again.
AMQ8109 WebSphere MQ queue manager being deleted.
Explanation: The queue manager is being deleted.
User Response: Wait for the deletion process to complete.
AMQ8110 WebSphere MQ queue manager already exists.
Explanation: The queue manager &5 already exists.
User Response: None.
AMQ8117 WebSphere MQ queue manager deletion incomplete.
Explanation: Deletion of queue manager &5 was only partially successful. An object was not found, or could not be deleted. Refer to the log for more information.
User Response: Delete any remaining queue manager objects.
AMQ8118 WebSphere MQ queue manager does not exist.
Explanation: The queue manager &5 does not exist.
User Response: Create the message queue manager (crtmqm command) and then try the command again.
AMQ8135 Not authorized.
Explanation: You are not authorized to perform the requested operation for the WebSphere MQ object &5 specified in &3. Either you are not authorized to perform the requested operation, or you are not authorized to the specified MQ object. For a copy command, you may not be authorized to the specified source MQ object, or, for a create command, you may not be authorized to the system default MQ object of the specified type.
User Response: Obtain the necessary authority from your security officer or WebSphere MQ administrator. Then try the command again.
AMQ8137 WebSphere MQ queue manager already starting.
Explanation: The strmqm command was unsuccessful because the queue manager &5 is already starting.
User Response: Wait for the strmqm command to complete.
AMQ8138 The WebSphere MQ queue has an incorrect type.
Explanation: The operation is not valid with queue &5 because it is not a local queue.
User Response: Change the QNAME parameter to specify a queue of the correct type.
AMQ8139 Already connected.
Explanation: A connection to the WebSphere MQ queue manager already exists.
User Response: None.
AMQ8140 Resource timeout error.
Explanation: A timeout occurred in the communication between internal WebSphere MQ queue manager components. This is most likely to occur when the system is heavily loaded.
User Response: Wait until the system is less heavily loaded, then try the command again.
AMQ8141 WebSphere MQ queue manager starting.
Explanation: The queue manager &5 is starting.
User Response: Wait for the queue manager startup process to complete and then try the command again.
AMQ8142 WebSphere MQ queue manager stopped.
Explanation: The queue manager &5 is stopped.
User Response: Use the strmqm command to start the queue manager, and then try the command again.
AMQ8143 WebSphere MQ queue not empty.
Explanation: The queue &5 specified in &2 is not empty or contains uncommitted updates.
User Response: Commit or roll back any uncommitted updates. If the command is DELETE QLOCAL, use the CLEAR QLOCAL command to clear the messages from the queue. Then try the command again.
AMQ8144 Log not available.
Explanation: The WebSphere MQ logging resource is not available.
User Response: Use the dltmqm command to delete the queue manager and then the crtmqm command to create the queue manager. Then try the command again.
AMQ8145 Connection broken.
Explanation: The connection to the WebSphere MQ queue manager failed during command processing. This may be caused by an endmqm command being issued by another user, or by a queue manager error.
User Response: Use the strmqm command to start the message queue manager, wait until the message queue manager has started, and try the command again.
AMQ8146 WebSphere MQ queue manager not available.
Explanation: The queue manager is not available because it has been stopped or has not been created.
User Response: Use the crtmqm command to create the message queue manager, or the strmqm command to start the message queue manager as necessary. Then try the command again.
AMQ8147 WebSphere MQ object &3 not found.
Explanation: If the command entered was Change or Display, the object &3 specified does not exist. If the command entered was Copy, the source object does not exist. If the command entered was Create, the system default MQ object of the specified type does not exist.
User Response: Correct the object name and then try the command again or, if you are creating a new queue or process object, either specify all parameters explicitly or ensure that the system default object of the required type exists. The system default queue names are SYSTEM.DEFAULT.LOCAL.QUEUE, SYSTEM.DEFAULT.ALIAS.QUEUE and SYSTEM.DEFAULT.REMOTE.QUEUE. The system default process name is SYSTEM.DEFAULT.PROCESS.
AMQ8148 WebSphere MQ object in use.
Explanation: The object &5 specified in &3 is in use by an MQ application program.
User Response: Wait until the object is no longer in use and then try the command again. If the command is ALTER or CHANGE, specify FORCE to force the processing of the object regardless of any application program affected by the change. If the object is the dead-letter queue and the open input count is nonzero, it may be in use by an MQ channel. If the object is another queue object with a nonzero open output count, it may be in use by a MQ channel (of type RCVR or RQSTR). In either case, use the STOP CHANNEL and START CHANNEL commands to stop and restart the channel in order to solve the problem. To alter the queue USAGE the FORCE option must be used if the queue is not empty.
AMQ8149 WebSphere MQ object damaged.
Explanation: The object &5 specified in &4 is damaged.
User Response: The object contents are not valid. Issue the DISPLAY CHANNEL, DISPLAY QUEUE, or DISPLAY PROCESS command, as required, to determine the name of the damaged object. Issue the DEFINE command, for the appropriate object type, to replace the damaged object, then try the command again.
AMQ8150 WebSphere MQ object already exists.
Explanation: The object &5 specified for &3 could not be created because it already exists.
User Response: Check that the name is correct and try the command again specifying REPLACE, or delete the object. Then try the command again.
AMQ8151 WebSphere MQ object has different type.
Explanation: The type specified for object &5 is different from the type of the object being altered or defined.
User Response: Use the correct MQ command for the object type, and then try the command again.
AMQ8152 Source WebSphere MQ object has different type.
Explanation: The type of the source object is different from that specified.
User Response: Correct the name of the command, or source object name, and then try the command again, or try the command using the REPLACE option.
AMQ8153 Insufficient disk space for the specified queue.
Explanation: The command failed because there was insufficient disk space available for the specified queue.
User Response: Release some disk space and then try the command again.
AMQ8154 API exit load error.
Explanation: The WebSphere MQ queue manager was unable to load the API crossing exit.
User Response: Ensure that the API crossing exit program is valid, and that its name and directory are correctly specified. Correct any error and then try the command again.
AMQ8155 Connection limit exceeded.
Explanation: The queue manager connection limit has been exceeded.
User Response: The maximum limit on the number of WebSphere MQ application programs that may be connected to the queue manager has been exceeded. Try the command later.
AMQ8156 WebSphere MQ queue manager quiescing.
Explanation: The queue manager is quiescing.
User Response: The queue manager was stopping with -c specified for endmqm. Wait until the queue manager has been restarted and then try the command again.
AMQ8157 Security error.
Explanation: An error was reported by the security manager program.
User Response: Inform your systems administrator, wait until the problem has been corrected, and then try the command again.
AMQ8172 Already disconnected.
Explanation: The MQI reason code of 2018 was returned from the WebSphere MQ queue manager in response to an MQDISC request issued during command processing.
User Response: None.
AMQ8173 No processes to display.
Explanation: There are no matching processes defined on this system.
User Response: Using the DEFINE PROCESS command to create a process.
AMQ8174 No queues to display.
Explanation: There are no matching queues defined on this system.
User Response: Use the appropriate command to define a queue of the type that you require, that is, DEFINE QALIAS, DEFINE QLOCAL, DEFINE QMODEL, or DEFINE QREMOTE.
AMQ8185 Operating system object already exists.
Explanation: The WebSphere MQ object cannot be created because an object that is not known to MQ already exists in the MQ directory with the name that should be used for the new object. Refer to the log for previous messages.
User Response: Remove the non-MQ object from the MQ library, and try the command again.
AMQ8186 Image not available for WebSphere MQ object &5.
Explanation: The object &5 type &3 cannot be recreated because the image is not fully available in the logs that are currently online. Refer to earlier messages in the error log for information about the logs that need to be brought online for this object to be recreated.
User Response: Bring the relevant logs online, and try the command again.
AMQ8187 WebSphere MQ object &5 is currently open.
Explanation: The object &5, type &3, is currently in use, so the &1 command cannot be issued against it. If a generic list was presented to the command, the command is still issued against the other objects in the list.
User Response: Wait until the object is no longer in use, and try the command again.
AMQ8188 Insufficient authorization to WebSphere MQ object &5.
Explanation: You are not authorized to issue the &1 command against the object &5 type &3. If a generic list was presented to the command, the command is still issued against the other objects in the list.
User Response: Obtain sufficient authorization for the object, and retry the command.
AMQ8189 WebSphere MQ object &5 is damaged.
Explanation: The object &5 type &4 is damaged and the &3 command cannot be issued against it. If a generic list was presented to the command then the command is still issued against the other objects in the list.
User Response: Issue the appropriate DEFINE command for the object, specifying REPLACE, and then try the command again.
AMQ8190 &3 succeeded on &1 objects and failed on &2 objects.
Explanation: An operation performed on a generic list of objects was not completely successful.
User Response: Examine the log for details of the errors encountered, and take appropriate action.
AMQ8191 WebSphere MQ command server is starting.
Explanation: The command server is starting.
User Response: Wait for the strmqcsv command to complete and then try the operation again.
AMQ8192 WebSphere MQ command server already starting.
Explanation: The request to start the command server was unsuccessful because the command server is already starting.
User Response: Wait for the strmqcsv command to complete.
AMQ8193 WebSphere MQ command server is ending.
Explanation: The command server is ending.
User Response: Wait for the endmqcsv command to complete and then try the command again.
AMQ8194 WebSphere MQ command server already ending.
Explanation: The end command server request was unsuccessful because the command server is already ending.
User Response: Wait for the endmqcsv command to complete.
AMQ8195 WebSphere MQ command server already running.
Explanation: The strmqcsv command was unsuccessful because the command server is already running.
User Response: None.
AMQ8196 WebSphere MQ command server already stopped.
Explanation: The request to end the command server was unsuccessful because the command server is already stopped.
User Response: None.
AMQ8197 Deleted WebSphere MQ queue damaged.
Explanation: The deleted MQ queue &5 was damaged, and any messages it contained have been lost.
User Response: None.
-------------------------------
AMQ8001 WebSphere MQ queue manager created.
Explanation: WebSphere MQ queue manager &5 created.
User Response: None.
AMQ8002 WebSphere MQ queue manager '&5' deleted.
Explanation: WebSphere MQ queue manager '&5' deleted.
User Response: None.
AMQ8003 WebSphere MQ queue manager '&5' started.
Explanation: WebSphere MQ queue manager '&5' started.
User Response: None.
AMQ8004 WebSphere MQ queue manager '&5' ended.
Explanation: WebSphere MQ queue manager '&5' ended.
User Response: None.
AMQ8005 WebSphere MQ queue manager changed.
Explanation: WebSphere MQ queue manager &5 changed.
User Response: None.
AMQ8006 WebSphere MQ queue created.
Explanation: WebSphere MQ queue &5 created.
User Response: None.
AMQ8007 WebSphere MQ queue deleted.
Explanation: WebSphere MQ queue &5 deleted.
User Response: None.
AMQ8008 WebSphere MQ queue changed.
Explanation: WebSphere MQ queue &5 changed.
User Response: None.
AMQ8010 WebSphere MQ process created.
Explanation: WebSphere MQ process &5 created.
User Response: None.
AMQ8011 WebSphere MQ process deleted.
Explanation: WebSphere MQ process &5 deleted.
User Response: None.
AMQ8012 WebSphere MQ process changed.
Explanation: WebSphere MQ process &5 changed.
User Response: None.
AMQ8014 WebSphere MQ channel created.
Explanation: WebSphere MQ channel &5 created.
User Response: None.
AMQ8015 WebSphere MQ channel deleted.
Explanation: WebSphere MQ channel &5 deleted.
User Response: None.
AMQ8016 WebSphere MQ channel changed.
Explanation: WebSphere MQ channel &5 changed.
User Response: None.
AMQ8018 Start WebSphere MQ channel accepted.
Explanation: The channel &5 is being started. The start channel function has been initiated. This involves a series of operations across the network before the channel is actually started. The channel status displays "BINDING" for a short period while communication protocols are negotiated with the channel with whom communication is being initiated.
User Response: None.
AMQ8019 Stop WebSphere MQ channel accepted.
Explanation: The channel &5 has been requested to stop.
User Response: None.
AMQ8020 Ping WebSphere MQ channel complete.
Explanation: Ping channel &5 complete.
User Response: None.
AMQ8021 WebSphere MQ Listener program started.
Explanation: The channel listener program has been started.
User Response: None.
AMQ8022 WebSphere MQ queue cleared.
Explanation: All messages on queue &5 have been deleted.
User Response: None.
AMQ8023 WebSphere MQ channel reset.
Explanation: Channel &5 has been reset.
User Response: None.
AMQ8024 WebSphere MQ channel initiator started.
Explanation: The channel initiator for queue &5 has been started.
User Response: None.
AMQ8025 WebSphere MQ channel resolved.
Explanation: In doubt messages for WebSphere MQ channel &5 have been resolved.
User Response: None.
AMQ8026 End WebSphere MQ queue manager accepted.
Explanation: A controlled stop request has been initiated for queue manager &5.
User Response: None.
AMQ8027 WebSphere MQ command server started.
Explanation: The command server has been started.
User Response: None.
AMQ8028 WebSphere MQ command server ended.
Explanation: The command server has been stopped.
User Response: None.
AMQ8029 WebSphere MQ authority granted.
Explanation: Authority for object &5 granted.
User Response: None.
AMQ8030 WebSphere MQ authority revoked.
Explanation: Authority for object &5 revoked.
User Response: None.
AMQ8033 WebSphere MQ object recreated.
Explanation: MQ object &5 has been recreated from image.
User Response: None.
AMQ8034 WebSphere MQ object image recorded.
Explanation: Image of MQ object &5 has been recorded.
User Response: None.
AMQ8035 WebSphere MQ Command Server Status . . : Running
Explanation: None.
User Response: None.
AMQ8036 WebSphere MQ command server status . . : Stopping
Explanation: None.
User Response: None.
AMQ8037 WebSphere MQ command server status . . : Starting
Explanation: None.
User Response: None.
AMQ8038 WebSphere MQ command server status . . : Running with queue disabled
Explanation: None.
User Response: None.
AMQ8039 WebSphere MQ command server status . . : Stopped
Explanation: None.
User Response: None.
AMQ8040 WebSphere MQ command server ending.
Explanation: None.
User Response: None.
AMQ8041 The queue manager cannot be restarted or deleted because processes, that were previously connected, are still running.
Explanation: Processes, that were connected to the queue manager the last time it was running, are still active. The queue manager cannot be restarted.
User Response: Stop the processes and try to start the queue manager.
AMQ8042 Process &1 is still running.
Explanation:
User Response:
AMQ8043 Non runtime application attempted to connect to runtime only queue manager.
Explanation: A non runtime application attempted to connect to a queue manager on a node where support for non runtime applications has not been installed. The connect attempt will be rejected with a reason of MQRC_ENVIRONMENT_ERROR.
User Response: If the node is intended to support only runtime applications, investigate why a non runtime application has attempted to connect to the queue manager. If the node is intended to support non runtime only applications, investigate if the base option has been installed. The base option must be installed if non runtime applications are to run on this node.
AMQ8044 An error occurred while removing the queue manager from the Active Directory.
Explanation: The attempt to remove the queue manager from the Windows Active Directory failed. This may be because the appropriate entry could not be opened or modified, or the Service Control Point has already been removed.
User Response: Check that your account has the authority to delete objects from the Active Directory, and that the entry has not already been deleted.
AMQ8045 An error occurred while removing the queue manager from the Service Control Manager.
Explanation: The attempt to remove the queue manager from the Windows registry failed. This may be because the appropriate entry could not be opened or modified.
User Response: Check that the registry has sufficient space on your disk to grow and that your account has the authority to modify it.
AMQ8048 Default objects statistics : &1 created. &2 replaced. &3 failed.
Explanation: Information on the number of objects created or replaced successfully as well as any failures that occurred while creating the default objects.
User Response: None.
AMQ8049 Object &4. Unable to create or replace.
Explanation: While creating or replacing the default object &4 for WebSphere MQ queue manager &5 an error occurred. The error was due to improper authorization. The reason code is &1.
User Response: Check this log for more details of what the problem may be. Make sure there are sufficient resources such as disk space and storage. For damaged or corrupted objects, replace these from backup objects. If all else fails, delete the queue manager &5 using dltmqm and create it again using crtmqm.
AMQ8050 Creating or replacing default objects for &3.
Explanation:
User Response: None.
AMQ8051 For details of the failures that occurred, please check AMQERR01.LOG.
Explanation:
User Response: None.
AMQ8051 For details of the failures that occurred, please check MQERRLG1.
Explanation:
User Response: None.
AMQ8052 Completing setup.
Explanation:
User Response: None.
AMQ8053 Object &4. Unable to create or replace.
Explanation: While creating or replacing the default object &4 for WebSphere MQ queue manager &5 an error occurred. The error was due to a broken connection. The reason code is &1.
User Response: Check this log for more details of what the problem may be. Make sure there is sufficient resources such as disk space and storage. For damaged or corrupted objects, replace these from backup objects. If all else fails, delete the queue manager &5 using dltmqm and create it again using crtmqm.
AMQ8054 Object &4. Unable to create or replace.
Explanation: While creating or replacing the default object &4 for WebSphere MQ queue manager &5 an error occurred. The error was due to unavailable storage. The reason code is &1.
User Response: Check this log for more details of what the problem may be. Make sure there is sufficient resources such as disk space and storage. For damaged or corrupted objects, replace these from backup objects. If all else fails, delete the queue manager &5 using dltmqm and create it again using crtmqm.
AMQ8055 Object &4. Unable to create or replace.
Explanation: While creating or replacing the default object &4 for WebSphere MQ queue manager &5 an error occurred. The error was due to a damaged object. The reason code is &1.
User Response: Check this log for more details of what the problem may be. Make sure there is sufficient resources such as disk space and storage. For damaged or corrupted objects, replace these from backup objects. If all else fails, delete the queue manager &5 using dltmqm and create it again using crtmqm.
AMQ8056 Object &4. Unable to create or replace.
Explanation: While creating or replacing the default object &4 for WebSphere MQ queue manager &5 an error occurred. The error was due to a channel definition error. The error code is &1 (X'&2').
User Response: Check this log for more details of what the problem may be. Make sure there is sufficient resources such as disk space and storage. For damaged or corrupted objects, replace these from backup objects. If all else fails, delete the queue manager &5 using dltmqm and create it again using crtmqm.
AMQ8057 Object &4. Unable to create or replace.
Explanation: While creating or replacing the default object &4 for WebSphere MQ queue manager &5 an error occurred. The error was due to invalid records in the channel definition file. The error code is &1 (X'&2').
User Response: Check this log for more details of what the problem may be. Make sure there is sufficient resources such as disk space and storage. For damaged or corrupted objects, replace these from backup objects. If all else fails, delete the queue manager &5 using dltmqm and create it again using crtmqm.
AMQ8058 Object &4. Unable to create or replace.
Explanation: While creating or replacing the default object &4 for WebSphere MQ queue manager &5 an error occurred. The error was due to not finding the channel definition file. The error code is &1 (X'&2').
User Response: Check this log for more details of what the problem may be. Make sure there is sufficient resources such as disk space and storage. For damaged or corrupted objects, replace these from backup objects. If all else fails, delete the queue manager &5 using dltmqm and create it again using crtmqm.
AMQ8059 Object &4. Unable to create or replace.
Explanation: While creating or replacing the default object &4 for WebSphere MQ queue manager &5 an error occurred. The error was due to an unexpected error, error code &1 (X'&2').
User Response: Check this log for more details of what the problem may be. Make sure there is sufficient resources such as disk space and storage. For damaged or corrupted objects, replace these from backup objects. If all else fails, delete the queue manager &5 using dltmqm and create it again using crtmqm.
AMQ8061 Command '&4' is not valid.
Explanation: The command '&4' at line &1 in the WebSphere MQ service command file '&3' for queue manager '&5' is not valid for use in the service command file. The line is ignored.
User Response: Check the contents of the file and retry the operation.
AMQ8062 Unexpected return code, '&1', from command '&3'.
Explanation: An unexpected return code, '&1', was returned by command '&3'. This command was issued by the WebSphere MQ service for queue manager '&4'.
User Response: Verify that the command and parameters are correct.
AMQ8063 Not authorized to issue command '&3'.
Explanation: The current user '&5' is not authorized to issue the command '&3'. The command is ignored.
User Response: Add the user to the local 'mqm' security group and retry the operation.
AMQ8064 Not authorized to start trusted application.
Explanation: The user '&5' is not authorized to start the trusted application '&3'. The application has not started.
User Response: Add the user to the local 'mqm' security group and restart the application.
AMQ8065 Local group '&3' not found.
Explanation: The local group '&3' is unavailable. It is not possible to verify that the user is authorized. The function cannot continue.
User Response: Create the required local group and retry the operation.
AMQ8066 Local mqm group not found.
Explanation: The local mqm group is unavailable. It is not possible to verify that the user is authorized. The function cannot continue.
User Response: Create the local mqm group and retry the operation.
AMQ8067 WebSphere MQ channel auto-defined.
Explanation: Channel &5 auto-defined.
User Response: None.
AMQ8068 Setup completed.
Explanation:
User Response: None.
AMQ8069 ApplicationGroup for the crtmqm command does not contain the mqm userid.
Explanation: WebSphere MQ queue manager &5 not created. The ApplicationGroup specified for the crtmqm command must contain the mqm userid when the RestrictedMode option (-g) is specified.
User Response: None.
AMQ8070 ApplicationGroup for crtmqm command is not defined.
Explanation: WebSphere MQ queue manager &5 not created. RestrictedMode option (-g) specified, but the ApplicationGroup does not exist.
User Response: None.
AMQ8071 RestrictedMode option not supported on this platform.
Explanation: WebSphere MQ queue manager &5 not created. The RestrictedMode option was specified but is not supported on this platform.
User Response: None.
AMQ8072 Not authorized to administer channels.
Explanation: The command server for queue manager '&3' received an administration command for channels. The user '&5' is not authorized to administer WebSphere MQ channels. The command server has not processed the command.
User Response: Add the user to the local 'mqm' security group, and ensure that the security policy is set as required.
AMQ8073 Authorization failed because SID: (&3) could not be resolved.
Explanation: The Object Authority Manager was unable to resolve the specified SID into entity and domain information.
User Response: Ensure that the application provides a SID that is recognized on this system, that all necessary domain controllers are available, and that the security policy is set as you required.
AMQ8074 Authorization failed as the SID '&3' does not match the entity '&4'.
Explanation: The Object Authority Manager received inconsistent data - the supplied SID does not match that of the supplied entity information.
User Response: Ensure that the application is supplying valid entity and SID information.
AMQ8075 Authorization failed because the SID for entity '&3' cannot be obtained.
Explanation: The Object Authority Manager was unable to obtain a SID for the specified entity.
User Response: Ensure that the entity is valid, and that all necessary domain controllers are available.
AMQ8076 Authorization failed because no SID was supplied for entity '&3'.
Explanation: The Object Authority Manager was not supplied with SID information for the specified entity, and the security policy is set to 'NTSIDsRequired'.
User Response: Ensure that the application is supplying a valid SID, and that the security policy is set as you require.
AMQ8077 Entity '&3' has insufficient authority to access object '&4'.
Explanation: The specified entity is not authorized to access the required object. The following requested permissions are unauthorized: &5
User Response: Ensure that the correct level of authority has been set for this entity against the required object, or ensure that the entity is a member of a privileged group.
AMQ8078 Waiting for queue manager '&3' to end.
Explanation:
User Response: None.
AMQ8079 Access was denied when attempting to retrieve group membership information for user '&3'.
Explanation: WebSphere MQ, running with the authority of user '&4', was unable to retrieve group membership information for the specified user.
User Response: Ensure Active Directory access permissions allow user '&4' to read group memberships for user '&3'. To retrieve group membership information for a domain user, MQ must run with the authority of a domain user.
AMQ8101 Unexpected error (&1).
Explanation: An unexpected reason code with hexadecimal value &1 was received from the WebSphere MQ queue manager during command processing. (Note that hexadecimal values in the range X'07D1'-X'0BB7' correspond to MQI reason codes 2001-2999.) More information might be available in the log. If the reason code value indicates that the error was associated with a particular parameter, the parameter concerned is &4.
User Response: Correct the error and then try the command again.
AMQ8102 WebSphere MQ object name specified in &4 not valid.
Explanation: The object name &5 specified in &4 is not valid. The length of the name must not exceed 48 characters, or 20 characters if it is a channel name. The name should contain the following characters only: lowercase a-z, uppercase A-Z, numeric 0-9, period (.), forward slash (/), underscore (_) and percent sign (%).
User Response: Change the length of the parameter value or change the parameter value to contain a valid combination of characters, then try the command again.
AMQ8103 Insufficient storage available.
Explanation: There was insufficient storage available to perform the requested operation.
User Response: Free some storage and then try the command again.
AMQ8104 WebSphere MQ directory &3 not found.
Explanation: Directory &3 was not found. This directory is created when WebSphere MQ is installed successfully. Refer to the log for more information.
User Response: Verify that installation of WebSphere MQ was successful. Correct the error and then try the command again.
AMQ8105 Object error.
Explanation: An object error occurred. Refer to the log for more information.
User Response: Correct the error and then try the command again.
AMQ8106 WebSphere MQ queue manager being created.
Explanation: The queue manager is being created.
User Response: Wait for the creation process to complete and then try the command again.
AMQ8107 WebSphere MQ queue manager running.
Explanation: The queue manager is running.
User Response: None.
AMQ8108 WebSphere MQ queue manager '&3' ending.
Explanation: The queue manager '&3' is ending.
User Response: Wait for the queue manager to end and then try the command again.
AMQ8109 WebSphere MQ queue manager being deleted.
Explanation: The queue manager is being deleted.
User Response: Wait for the deletion process to complete.
AMQ8110 WebSphere MQ queue manager already exists.
Explanation: The queue manager &5 already exists.
User Response: None.
AMQ8117 WebSphere MQ queue manager deletion incomplete.
Explanation: Deletion of queue manager &5 was only partially successful. An object was not found, or could not be deleted. Refer to the log for more information.
User Response: Delete any remaining queue manager objects.
AMQ8118 WebSphere MQ queue manager does not exist.
Explanation: The queue manager &5 does not exist.
User Response: Create the message queue manager (crtmqm command) and then try the command again.
AMQ8135 Not authorized.
Explanation: You are not authorized to perform the requested operation for the WebSphere MQ object &5 specified in &3. Either you are not authorized to perform the requested operation, or you are not authorized to the specified MQ object. For a copy command, you may not be authorized to the specified source MQ object, or, for a create command, you may not be authorized to the system default MQ object of the specified type.
User Response: Obtain the necessary authority from your security officer or WebSphere MQ administrator. Then try the command again.
AMQ8137 WebSphere MQ queue manager already starting.
Explanation: The strmqm command was unsuccessful because the queue manager &5 is already starting.
User Response: Wait for the strmqm command to complete.
AMQ8138 The WebSphere MQ queue has an incorrect type.
Explanation: The operation is not valid with queue &5 because it is not a local queue.
User Response: Change the QNAME parameter to specify a queue of the correct type.
AMQ8139 Already connected.
Explanation: A connection to the WebSphere MQ queue manager already exists.
User Response: None.
AMQ8140 Resource timeout error.
Explanation: A timeout occurred in the communication between internal WebSphere MQ queue manager components. This is most likely to occur when the system is heavily loaded.
User Response: Wait until the system is less heavily loaded, then try the command again.
AMQ8141 WebSphere MQ queue manager starting.
Explanation: The queue manager &5 is starting.
User Response: Wait for the queue manager startup process to complete and then try the command again.
AMQ8142 WebSphere MQ queue manager stopped.
Explanation: The queue manager &5 is stopped.
User Response: Use the strmqm command to start the queue manager, and then try the command again.
AMQ8143 WebSphere MQ queue not empty.
Explanation: The queue &5 specified in &2 is not empty or contains uncommitted updates.
User Response: Commit or roll back any uncommitted updates. If the command is DELETE QLOCAL, use the CLEAR QLOCAL command to clear the messages from the queue. Then try the command again.
AMQ8144 Log not available.
Explanation: The WebSphere MQ logging resource is not available.
User Response: Use the dltmqm command to delete the queue manager and then the crtmqm command to create the queue manager. Then try the command again.
AMQ8145 Connection broken.
Explanation: The connection to the WebSphere MQ queue manager failed during command processing. This may be caused by an endmqm command being issued by another user, or by a queue manager error.
User Response: Use the strmqm command to start the message queue manager, wait until the message queue manager has started, and try the command again.
AMQ8146 WebSphere MQ queue manager not available.
Explanation: The queue manager is not available because it has been stopped or has not been created.
User Response: Use the crtmqm command to create the message queue manager, or the strmqm command to start the message queue manager as necessary. Then try the command again.
AMQ8147 WebSphere MQ object &3 not found.
Explanation: If the command entered was Change or Display, the object &3 specified does not exist. If the command entered was Copy, the source object does not exist. If the command entered was Create, the system default MQ object of the specified type does not exist.
User Response: Correct the object name and then try the command again or, if you are creating a new queue or process object, either specify all parameters explicitly or ensure that the system default object of the required type exists. The system default queue names are SYSTEM.DEFAULT.LOCAL.QUEUE, SYSTEM.DEFAULT.ALIAS.QUEUE and SYSTEM.DEFAULT.REMOTE.QUEUE. The system default process name is SYSTEM.DEFAULT.PROCESS.
AMQ8148 WebSphere MQ object in use.
Explanation: The object &5 specified in &3 is in use by an MQ application program.
User Response: Wait until the object is no longer in use and then try the command again. If the command is ALTER or CHANGE, specify FORCE to force the processing of the object regardless of any application program affected by the change. If the object is the dead-letter queue and the open input count is nonzero, it may be in use by an MQ channel. If the object is another queue object with a nonzero open output count, it may be in use by a MQ channel (of type RCVR or RQSTR). In either case, use the STOP CHANNEL and START CHANNEL commands to stop and restart the channel in order to solve the problem. To alter the queue USAGE the FORCE option must be used if the queue is not empty.
AMQ8149 WebSphere MQ object damaged.
Explanation: The object &5 specified in &4 is damaged.
User Response: The object contents are not valid. Issue the DISPLAY CHANNEL, DISPLAY QUEUE, or DISPLAY PROCESS command, as required, to determine the name of the damaged object. Issue the DEFINE command, for the appropriate object type, to replace the damaged object, then try the command again.
AMQ8150 WebSphere MQ object already exists.
Explanation: The object &5 specified for &3 could not be created because it already exists.
User Response: Check that the name is correct and try the command again specifying REPLACE, or delete the object. Then try the command again.
AMQ8151 WebSphere MQ object has different type.
Explanation: The type specified for object &5 is different from the type of the object being altered or defined.
User Response: Use the correct MQ command for the object type, and then try the command again.
AMQ8152 Source WebSphere MQ object has different type.
Explanation: The type of the source object is different from that specified.
User Response: Correct the name of the command, or source object name, and then try the command again, or try the command using the REPLACE option.
AMQ8153 Insufficient disk space for the specified queue.
Explanation: The command failed because there was insufficient disk space available for the specified queue.
User Response: Release some disk space and then try the command again.
AMQ8154 API exit load error.
Explanation: The WebSphere MQ queue manager was unable to load the API crossing exit.
User Response: Ensure that the API crossing exit program is valid, and that its name and directory are correctly specified. Correct any error and then try the command again.
AMQ8155 Connection limit exceeded.
Explanation: The queue manager connection limit has been exceeded.
User Response: The maximum limit on the number of WebSphere MQ application programs that may be connected to the queue manager has been exceeded. Try the command later.
AMQ8156 WebSphere MQ queue manager quiescing.
Explanation: The queue manager is quiescing.
User Response: The queue manager was stopping with -c specified for endmqm. Wait until the queue manager has been restarted and then try the command again.
AMQ8157 Security error.
Explanation: An error was reported by the security manager program.
User Response: Inform your systems administrator, wait until the problem has been corrected, and then try the command again.
AMQ8172 Already disconnected.
Explanation: The MQI reason code of 2018 was returned from the WebSphere MQ queue manager in response to an MQDISC request issued during command processing.
User Response: None.
AMQ8173 No processes to display.
Explanation: There are no matching processes defined on this system.
User Response: Using the DEFINE PROCESS command to create a process.
AMQ8174 No queues to display.
Explanation: There are no matching queues defined on this system.
User Response: Use the appropriate command to define a queue of the type that you require, that is, DEFINE QALIAS, DEFINE QLOCAL, DEFINE QMODEL, or DEFINE QREMOTE.
AMQ8185 Operating system object already exists.
Explanation: The WebSphere MQ object cannot be created because an object that is not known to MQ already exists in the MQ directory with the name that should be used for the new object. Refer to the log for previous messages.
User Response: Remove the non-MQ object from the MQ library, and try the command again.
AMQ8186 Image not available for WebSphere MQ object &5.
Explanation: The object &5 type &3 cannot be recreated because the image is not fully available in the logs that are currently online. Refer to earlier messages in the error log for information about the logs that need to be brought online for this object to be recreated.
User Response: Bring the relevant logs online, and try the command again.
AMQ8187 WebSphere MQ object &5 is currently open.
Explanation: The object &5, type &3, is currently in use, so the &1 command cannot be issued against it. If a generic list was presented to the command, the command is still issued against the other objects in the list.
User Response: Wait until the object is no longer in use, and try the command again.
AMQ8188 Insufficient authorization to WebSphere MQ object &5.
Explanation: You are not authorized to issue the &1 command against the object &5 type &3. If a generic list was presented to the command, the command is still issued against the other objects in the list.
User Response: Obtain sufficient authorization for the object, and retry the command.
AMQ8189 WebSphere MQ object &5 is damaged.
Explanation: The object &5 type &4 is damaged and the &3 command cannot be issued against it. If a generic list was presented to the command then the command is still issued against the other objects in the list.
User Response: Issue the appropriate DEFINE command for the object, specifying REPLACE, and then try the command again.
AMQ8190 &3 succeeded on &1 objects and failed on &2 objects.
Explanation: An operation performed on a generic list of objects was not completely successful.
User Response: Examine the log for details of the errors encountered, and take appropriate action.
AMQ8191 WebSphere MQ command server is starting.
Explanation: The command server is starting.
User Response: Wait for the strmqcsv command to complete and then try the operation again.
AMQ8192 WebSphere MQ command server already starting.
Explanation: The request to start the command server was unsuccessful because the command server is already starting.
User Response: Wait for the strmqcsv command to complete.
AMQ8193 WebSphere MQ command server is ending.
Explanation: The command server is ending.
User Response: Wait for the endmqcsv command to complete and then try the command again.
AMQ8194 WebSphere MQ command server already ending.
Explanation: The end command server request was unsuccessful because the command server is already ending.
User Response: Wait for the endmqcsv command to complete.
AMQ8195 WebSphere MQ command server already running.
Explanation: The strmqcsv command was unsuccessful because the command server is already running.
User Response: None.
AMQ8196 WebSphere MQ command server already stopped.
Explanation: The request to end the command server was unsuccessful because the command server is already stopped.
User Response: None.
AMQ8197 Deleted WebSphere MQ queue damaged.
Explanation: The deleted MQ queue &5 was damaged, and any messages it contained have been lost.
User Response: None.
Comments
Post a Comment