See Reading a message for an explanation of how to interpret these messages.
40 : Stop Error
The directory under which queue managers are to be created is not valid. It may not exist, or there may be a problem with authorization.
The location is specified in the machine-wide ini file. Correct the file and submit the request again.
40 : Stop Error
The directory under which the queue managers are to be created is not valid. It may not exist, or there may be a problem with authorization.
The location is specified in the configuration data. Correct the configuration data and submit the request again.
40 : Stop Error
An internal error occurred while trying to create or delete a queue manager file. It is likely that the error was caused by a disk having insufficient space, or by problems with authorization to the underlying filesystem.
Identify the file that caused the error, using problem determination techniques. For example check if there are any FFST files, which may identify the queue manager file causing the error. This error may also be caused if users have created, renamed or deleted that file. Correct the error in the filesystem and submit the request again.
40 : Stop Error
An internal error occurred while trying to create or delete a queue manager file.
In the case of a failure to delete a file a common reason for this error is that a non MQ process, such as the windows explorer or a virus checker, is accessing the file. In the case where the object that cannot be deleted is a directory then a non MQ process may be accessing a file within the directory or one of its subdirectories.
It is also possible that the error was caused by a disk having insufficient space, or by problems with authorization to the underlying filesystem.
Identify the file that caused the error, using problem determination techniques. For example check if there are any FFST files, which may identify the queue manager file causing the error. This error may also be caused if users have created, renamed or deleted that file. Correct the error in the filesystem and submit the request again.
40 : Stop Error
You tried to perform an action that requires the queue manager stopped, however, it is currently running. You probably tried to delete or start a queue manager that is currently running.
If the queue manager should be stopped, stop the queue manager and submit the failed command again.
20 : Error
The <insert_4> stanza starting on line <insert_1> of configuration file <insert_3> is missing the required <insert_5> attribute.
Check the contents of the file and retry the operation.
20 : Error
The <insert_4> stanza in the configuration data is missing the required <insert_5> attribute.
Check the contents of the configuration data and retry the operation.
40 : Stop Error
You tried to create a queue manager that already exists.
If you specified the wrong queue manager name, correct the name and submit the request again.
40 : Stop Error
You tried to perform an action against a queue manager that does not exist. You may have specified the wrong queue manager name.
If you specified the wrong name, correct it and submit the command again. If the queue manager should exist, create it, and then submit the command again.
40 : Stop Error
While deleting the queue manager, an error occurred deleting a file or directory. The queue manager may not have been completely deleted.
Follow problem determination procedures to identify the file or directory and to complete deletion of the queue manager.
40 : Stop Error
You specified a value for the trigger interval that is not valid. The value must be not less than zero and not greater than 999 999 999.
Correct the value and resubmit the request.
40 : Stop Error
You specified a name for the dead-letter queue that is not valid.
Correct the name and resubmit the request.
40 : Stop Error
You specified a name for the default transmission queue that is not valid.
Correct the name and submit the command again.
40 : Stop Error
You specified a value for the maximum number of open object handles to be allowed that is not valid. The value must be not less than zero and not greater than 999 999 999.
Correct the value and submit the command again.
40 : Stop Error
You specified a value for the maximum number of uncommitted messages to be allowed that is not valid. The value must be not less than 1 and not greater than 999 999 999.
Correct the value and submit the command again.
40 : Stop Error
The queue manager was unable to use the log. This could be due to a log file being missing or damaged, or the log path to the queue manager being inaccessible.
Ensure that the LogPath attribute in the queue manager configuration file is correct. If a log file is missing or otherwise unusable, restore a backup copy of the file, or the entire queue manager.
20 : Error
An attempt has been made to perform an operation on a queue manager. Resources required to perform the operation are not available.
40 : Stop Error
During creation of the queue manager an error occurred while trying to create a file or directory.
Identify why the queue manager files cannot be created. It is probable that there is insufficient space on the specified disk, or that there is a problem with access control. Correct the problem and submit the command again.
10 : Warning
The queue manager tried to resolve all internally coordinated transactions which are in-doubt. In-doubt transactions still remain after the queue manager has attempted to deliver the outcome of these transactions to the resource managers concerned. Transactions remain in-doubt when the queue manager cannot deliver the outcome of the transaction to each of the participating resource managers. For example, a resource manager may not be available at this time.
Use the DSPMQTRN command to display the remaining in-doubt transactions.
10 : Warning
The queue manager tried to resolve all internally coordinated transactions which are in-doubt. In-doubt transactions still remain after the queue manager has attempted to deliver the outcome of these transactions to the resource managers concerned. Transactions remain in-doubt when the queue manager cannot deliver the outcome of the transaction to each of the participating resource managers. For example, a resource manager may not be available at this time.
Use the Work with Transactions (WRKMQMTRN) command to display the remaining in-doubt transactions.
40 : Stop Error
While deleting the queue manager, an error occurred deleting a file or directory. The queue manager may not have been completely deleted.
Follow problem determination procedures to identify the file or directory and to complete deletion of the queue manager.
20 : Error
The identification number of the resource manager you supplied was not recognized.
Ensure that you entered a valid resource manager identification number. Use the DSPMQTRN command to display a list of resource managers and their identification numbers.
20 : Error
The resource manager, the identification number of which you supplied, was in an invalid state.
Ensure that you entered the correct resource manager identification number. Use the DSPMQTRN command to display a list of resource managers and their identification numbers. A resource manager is in an invalid state, if it is still available to resolve the transaction, use the -a optional flag to resolve this and all other internally coordinated in-doubt transactions.
20 : Error
You supplied arguments to a command that it could not interpret. It is probable that you specified a flag not accepted by the command, or that you included extra flags.
Correct the command and submit it again. Additional information on the arguments causing the error may be found in the error logs for the queue, or queue manager, referenced in the command.
40 : Stop Error
The descriptive text you supplied to the crtmqm command was in error.
Correct the descriptive text argument and submit the command again.
40 : Stop Error
You specified the name of a principal or group which does not exist.
Correct the name and resubmit the request.
20 : Error
The argument <insert_3> was supplied to the command <insert_4> which could not be interpreted. This argument is either not accepted by the command, or an extra flag has been included.
Correct the command and submit it again.
40 : Stop Error
You have requested an action that requires the queue manager running, however, the queue manager is not currently running.
Start the required queue manager and submit the command again.
0 : Information
You have requested that the queue manager end when there is no more work for it. In the meantime, it will refuse new applications that attempt to start, although it allows those already running to complete their work.
None.
40 : Stop Error
You issued a command that requires the queue manager running, however, it is currently in the process of stopping. The command cannot be run.
None
40 : Stop Error
A Define Object operation was performed, but the name selected for the object is already in use by an object that is unknown to WebSphere MQ. The object name selected by MQ was <insert_3>, in directory <insert_4>, of object type <insert_5>.
Remove the conflicting object from the MQ system, then try the operation again.
20 : Error
The media image for object <insert_3>, type <insert_4>, is not available for media recovery. A log file containing part of the media image cannot be accessed.
A previous message indicates which log file could not be accessed. Restore a copy of the log file and all subsequent log files from backup. If this is not possible, you must delete the object instead.
20 : Error
The media image for object <insert_3>, type <insert_4>, is not available for media recovery. A log file containing part of the media image cannot be accessed.
A previous message indicates which log file could not be accessed. Restore a copy of the log file and all subsequent log files from backup. If this is not possible, you must delete the object instead.
20 : Error
Media recovery is not possible on a queue manager using a circular log. Damaged objects must be deleted on such a queue manager.
None.
40 : Stop Error
An internal error occurred during the processing of a command.
Follow problem determination procedures to identify the cause of the error.
40 : Stop Error
Either the specified queue manager name does not conform to the rules required by WebSphere MQ or the queue manager does not exist. The rules for naming MQ objects are detailed in the WebSphere MQ Command Reference.
Correct the name and submit the command again.
0 : Information
The prepared transaction has been committed.
None.
0 : Information
The prepared transaction has been backed out.
None.
20 : Error
The number of the transaction you supplied was not recognized as belonging to an in-doubt transaction.
Ensure that you entered a valid transaction number. It is possible that the transaction number you entered corresponds to a transaction which was committed or backed out before you issued the command to resolve it.
0 : Information
This message is used to report the number of an in-doubt transaction.
None.
20 : Error
An error has occurred when reading the MQS.INI file or a queue manager QM.INI file.
If you have been changing the INI file content check and correct the change. If you have not changed the INI file, use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
20 : Error
An error has occurred when reading the configuration data.
If you have changed the configuration data, check and correct the change. If you have not changed the configuration data, use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
20 : Error
An error has occurred locking the MQS.INI file or a queue manager QM.INI file.
If you have been changing the INI file permissions check and correct the change. If you have not changed the INI file, use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
20 : Error
An error has occurred locking the configuration data.
If you have changed the configuration data permissions, check and correct the change. If you have not changed the configuration data, use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
20 : Error
An expected stanza is missing from the MQS.INI file or a queue manager QM.INI file or the stanza contains errors.
If you have been changing the INI file content check and correct the change.
20 : Error
An expected stanza is missing from the configuration data or the stanza contains errors.
If you have changed the configuration data, check and correct the change.
20 : Error
Access to the MQS.INI file or a queue manager QM.INI file is denied.
If you have been changing the INI file permissions check and correct the change.
20 : Error
Access to the configuration data is denied.
If you have changed the configuration data permissions, check and correct the change.
20 : Error
The MQS.INI file or a queue manager QM.INI file is missing.
If you have been changing the INI file recover the previous file and retry the operation.
20 : Error
The configuration data for WebSphere MQ is missing.
If you have changed the configuration data, recover the previous configuration data and retry the operation.
40 : Stop Error
The supplied log path could not be used by the queue manager. Possible reasons for this include the path not existing, the queue manager not being able to write to the path, or the path residing on a remote device.
Ensure that the log path exists and that the queue manager has authority to read and write to it. If the queue manager already exists, ensure that the LogPath attribute in the queue manager's configuration file matches the intended log path.
The auxiliary storage pool identifier supplied does not exist on the system and could not be used by the queue manager to create a journal receiver.
Specify *SYSTEM, or the identifier of an existing auxiliary storage pool and try the request again. You can use WRKDSKSTS to check the assignment of disk units to auxiliary storage pools.
40 : Stop Error
The operation cannot be completed due to shortage of disk space.
Either make more disk space available, or reduce the disk requirements of the command you issued.
10 : Warning
There are no prepared transactions to be resolved.
None.
40 : Stop Error
A syntax error has been found in one of the files containing authorization information for the queue manager.
Correct the contents of the incorrect authorization file by editing it.
40 : Stop Error
The queue manager was defined to be the default queue manager for the machine when it was created. However, although the queue manager has been created, an error occurred trying to make it the default. There may not be a default queue manager defined for the machine at present.
There is probably a problem with the machine-wide ini file. Verify the existence of the file, its access permissions, and its contents. If its backup file exists, reconcile the contents of the two files and then delete the backup. Finally, either update the machine-wide ini file by hand to specify the desired default queue manager, or delete and recreate the queue manager.
40 : Stop Error
The queue manager was defined to be the default queue manager for the machine when it was created. However, although the queue manager has been created, an error occurred trying to make it the default. There may not be a default queue manager defined for the machine at present.
There is probably a problem with the configuration data. Update the configuration data to specify the desired default queue manager, or delete and recreate the queue manager.
40 : Stop Error
An invalid QM.INI file stanza was found. Refer to the error log for more information.
Correct the error and then retry the operation.
40 : Stop Error
A stanza that is not valid was found. Refer to the error log for more information.
Correct the error and retry the operation.
40 : Stop Error
Either the number of log files or the size of the log files was outside the accepted values.
Make sure that the log parameters you enter lie within the valid range.
10 : Warning
Line <insert_1> of the configuration file <insert_3> contained a stanza called <insert_3>. This stanza is not recognized.
Check the contents of the file and retry the operation.
10 : Warning
Line <insert_1> of the configuration file <insert_3> contained a stanza key <insert_4>. This stanza is not recognized.
Check the contents of the file and retry the operation.
10 : Warning
Key <insert_3> contained a stanza called <insert_4>. This stanza is not recognized.
Check the contents of the configuration data and retry the operation.
10 : Warning
Line <insert_1> of the configuration file <insert_3> contained an attribute called <insert_4> that is not valid. This attribute is not recognized in this context.
Check the contents of the file and retry the operation.
10 : Warning
Key <insert_3> in the configuration data contained an attribute called <insert_4> that is not valid. This attribute is not recognized in this context.
Check the contents of the configuration data and retry the operation.
10 : Warning
Line <insert_1> of the configuration file <insert_3> contained value <insert_5> that is not valid for the attribute <insert_4>.
Check the contents of the file and retry the operation.
10 : Warning
Key <insert_3> in the configuration data contained value <insert_5> that is not valid for the attribute <insert_4>.
Check the contents of the configuration data and retry the operation.
40 : Stop Error
You tried to issue a command for the queue manager. You are not authorized to perform the command.
Contact your system administrator to perform the command for you. Alternatively, request authority to perform the command from your system administrator.
40 : Stop Error
You entered an object type of *ALL or *MQM and an object name that contains generic characters, this is an invalid combination.
Correct the command and submit it again.
10 : Warning
No objects were processed, either because no objects matched the criteria given, or because the objects found did not require processing.
None.
0 : Information
The object <insert_3>, type <insert_4> was recreated from its media image.
None.
10 : Warning
Object <insert_3>, type <insert_4> cannot be recreated since it is not damaged.
None
20 : Error
The command failed due to a resource problem. Possible causes include the log being full or the command running out of memory.
Look at the previous messages to diagnose the problem. Rectify the problem and retry the operation.
20 : Error
The object <insert_3>, type <insert_4> was damaged. The object must be deleted or, if the queue manager supports media recovery, recreated from its media image.
Delete the object or recreate it from its media image.
20 : Error
Object <insert_3>, type <insert_4> cannot be found.
None.
0 : Information
The media image for object <insert_3>, type <insert_4>, defined in Queue Manager <insert_5>, has been recorded.
None.
20 : Error
Object <insert_3>, type <insert_4> is a temporary object. Media recovery operations are not permitted on temporary objects.
None.
20 : Error
Object <insert_3>, type <insert_4> is in use. Either an application has it open or, if it is a local queue, there are uncommitted messages on it.
Ensure that the object is not opened by any applications, and that there are no uncommitted messages on the object, if it is a local queue. Then, retry the operation.
20 : Error
Another media recovery operation is already in progress. Only one media recovery operation is permitted at a time.
Wait for the existing media recovery operation to complete and retry the operation.
40 : Stop Error
The CCSID to be used by the QMGR is not valid for the iSeries platform. The CCSID encoding must be a valid EBCDIC value.
Check that the CCSID that you have entered is a valid EBCDIC value.
40 : Stop Error
The CCSID to be used by the QMGR is not valid, because:
1) It is a DBCS CCSID.
2) The CCSID encoding is not ASCII or ASCII related. EBCDIC or UCS2 encodings are not valid on this machine.
3) The CCSID encoding is unknown.
Check the CCSID is valid for the machine on which you are working.
40 : Stop Error
Modification of authorizations for a queue manager can be performed only from that queue manager. You must not specify an object name.
Correct the command and submit it again.
40 : Stop Error
The command needs the name of an object, but you did not specify one.
Correct the command and submit it again.
40 : Stop Error
The command needs the type of the object, but you did not specify one.
Correct the command and submit it again.
40 : Stop Error
Either the type of object you specified was not valid, or you specified multiple object types on a command which supports only one.
Correct the command and submit it again.
40 : Stop Error
The command needs one or more entity names, but you did not specify any. Entities can be principals or groups.
Correct the command and submit it again.
40 : Stop Error
The command sets the authorizations on WebSphere MQ objects. However you did not specify which authorizations are to be set.
Correct the command and submit it again.
40 : Stop Error
The authorization specification you provided to the command contained one or more items that could not be interpreted.
Correct the command and submit it again.
40 : Stop Error
The command can accept only one principal or group name. You specified more than one.
Correct the command and submit it again.
0 : Information
Informational message. The list of authorizations follows.
None.
0 : Information
This message reports the state of a resource manager with respect to an in-doubt transaction.
None.
0 : Information
This message reports the state of a resource manager with respect to an in-doubt transaction.
None.
0 : Information
This message reports the state of a resource manager with respect to an in-doubt transaction.
None.
0 : Information
This message reports the identification number and name of a resource manager.
None.
0 : Information
All, if there were any, of the internally coordinated transactions which were in-doubt, have now been resolved. This message reports successful completion of the RSVMQTRN command when the -a option is used.
None.
0 : Information
All, if there were any, of the internally coordinated transactions which were in-doubt, have now been resolved.
None.
0 : Information
A decision for an internally coordinated transaction which was in-doubt, has now been delivered on behalf of the unavailable resource manager. This message reports successful completion of the RSVMQTRN command when the -r option is used.
None.
0 : Information
The media image for the syncfile has been recorded.
None.
0 : Information
This message reports the state of a resource manager with respect to an in-doubt transaction.
None.
0 : Information
This message is used to report the number of an in-doubt transaction which has encountered an error with one or more resource managers.
Refer to the queue manager error log for more information about which resource managers are in error. Ensure that the resource managers that were in error, are working correctly, restart the queue manager. If the problem persists, use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
20 : Error
The required flag, -rn, was omitted from the command crtmqm
Add the flag and associated database name and submit it again.
20 : Error
The required flag, -rp, was omitted from the command crtmqm
Add the flag and associated database password and submit it again.
20 : Error
The required flag, -rt, was omitted from the command crtmqm
Add the flag and associated database type and submit it again
20 : Error
The argument supplied with the flag -rt, is greater than 8 characters long
Reduce the length of the database type argument and submit it again
20 : Error
The MSD shared library was either not located or failed to load correctly.
Ensure that the database type is specified correctly when creating a queue manager since this is used to form the name of the shared library to be loaded. Further information on the failure may be found in the FFST logs. Also, ensure that ensure that the MSD shared library is installed correctly.
20 : Error
This copy of WebSphere MQ was licensed to be used in trial mode for a limited period only. This period has expired.
Install a Production license for this copy of WebSphere MQ.
20 : Error
This copy of WebSphere MQ was licensed for a limited period only. This period has now expired.
Install a Production license for this copy of WebSphere MQ.
10 : Warning
When the Trial Period License Agreement is displayed, the user must accept it before this copy of WebSphere MQ can be used.
Submit the command again and accept the agreement.
0 : Information
This copy of WebSphere MQ is licensed for a limited period only.
None.
10 : Warning
This copy of WebSphere MQ is licensed for a limited period only.
Install a Production license for this copy of WebSphere MQ.
0 : Information
This copy of WebSphere MQ is licensed for a limited period only.
None.
0 : Information
A Production license has been installed for this copy of WebSphere MQ.
None.
0 : Information
One or more messages have been displayed. They will disappear when the user presses the Enter key.
Press the Enter key when the messages are no longer required.
20 : Error
The installation of WebSphere MQ is invalid since no Production, Beta, or Trial Period license has been installed.
Check that the installation steps described in the Quick Beginnings book have been followed, and if the problem persists contact your IBM service representative.
0 : Information
This copy of WebSphere MQ is licensed for a limited period only and the trial period has been started previously.
None.
0 : Information
A Production license has been installed for this copy of WebSphere MQ. A beta or trial period cannot be started.
None.
0 : Information
This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only.
None.
0 : Information
This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only.
None.
0 : Information
This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only.
None.
0 : Information
This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only.
None.
0 : Information
This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only.
None.
0 : Information
This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only.
None.
0 : Information
This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only.
None.
0 : Information
This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only.
None.
0 : Information
This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only.
None.
0 : Information
This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only.
None.
0 : Information
This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only.
None.
0 : Information
The Trial Period License Agreement has been displayed to the user and the user should now accept or reject the Agreement.
Reply 'yes' or 'no' and press 'Enter'.
0 : Information
Part of the Trial Period License Agreement has been displayed to the user. The user should press the Enter key to indicate that they are ready for the next part of the Agreement to be displayed.
Press the Enter key when ready for the next part of the Agreement to be displayed.
0 : Information
This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only.
None.
0 : Information
This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only.
None.
0 : Information
This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only.
None.
0 : Information
This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only.
None.
0 : Information
This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only.
None.
0 : Information
This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only.
None.
0 : Information
This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only.
None.
0 : Information
This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only.
None.
0 : Information
This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only.
None.
20 : Error
A Production, Beta or Trial Period license could not be installed for this copy of WebSphere MQ. This is because the 'nodelock' file in the 'qmgrs/@SYSTEM' directory could not be created or updated.
Check the ownership and permissions of the 'qmgrs/@SYSTEM' directory.
20 : Error
The production license for this copy of WebSphere MQ has an expiry date. This date has been passed.
Contact your IBM support center.
20 : Error
The program requires that the file <insert_3> is present, available and is a valid license file.
Check that the installation steps described in the Quick Beginnings book have been followed, and if the problem persists contact your IBM service representative.
0 : Information
A Production license has previously been installed for this copy of WebSphere MQ.
None.
20 : Error
The license <insert_3> has been installed but it is not a valid production license for this copy of WebSphere MQ.
Submit the SETMQPRD command again specifying the name of a valid production license.
20 : Error
The license <insert_3> has been installed but it is not a valid trial period license for this copy of WebSphere MQ.
Check that the correct version of the file is available.
10 : Warning
A FASTPATH application has ended in a way which did not allow the queue manager to clean up the resources owned by that application. Any resources held by the application can only be released by stopping and restarting the queue manager.
Investigate why the application ended unexpectedly. Avoid ending FASTPATH applications in a way which prevents WebSphere MQ from releasing resources held by the application.
0 : Information
0 : Information
0 : Information
0 : Information
The job's PID is <insert_2> the CCSID is <insert_1>. The job name is <insert_4>.
None
0 : Information
WebSphere MQ has been waiting <insert_1> seconds to start job <insert_3> for Queue Manager: <insert_5>
Check that the job queue that is associated with job description <insert_4> is not held, and that the subsystem that is associated with the job queue is active.
20 : Error
This copy of WebSphere MQ was licensed to be used for Beta testing for a limited period only. This period has expired.
Install a Production license for this copy of WebSphere MQ.
20 : Error
This copy of WebSphere MQ was licensed for a limited period only. This period has now expired.
Install a Production license for this copy of WebSphere MQ.
10 : Warning
When the IBM International License Agreement for Early Release of Programs is displayed, the user must accept it before this copy of WebSphere MQ can be used.
Submit the command again and accept the agreement.
0 : Information
This copy of WebSphere MQ is licensed for a limited period only.
None.
10 : Warning
This copy of WebSphere MQ is licensed for a limited period only.
Install a Production license for this copy of WebSphere MQ.
20 : Error
The Resolve option is not valid for external transactions. The Commit and Backout options are not valid for internal transactions.
Select a different option for this transaction.
0 : Information
This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only.
None.
0 : Information
This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only.
None.
0 : Information
This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only.
None.
0 : Information
This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only.
None.
0 : Information
This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only.
None.
0 : Information
This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only.
None.
0 : Information
This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only.
None.
0 : Information
This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only.
None.
0 : Information
This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only.
None.
0 : Information
This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only.
None.
0 : Information
This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only.
None.
0 : Information
This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only.
None.
0 : Information
This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only.
None.
0 : Information
This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only.
None.
0 : Information
This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only.
None.
0 : Information
This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only.
None.
0 : Information
This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only.
None.
0 : Information
This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only.
None.
0 : Information
This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only.
None.
0 : Information
This is part of the Early Release of Programs License Agreement (VZ125-5544-01 10/97 (MK002))which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only.
None.
0 : Information
This copy of WebSphere MQ is licensed for a limited period only.
None.
0 : Information
This copy of WebSphere MQ is licensed for a limited period only and the Beta test period has been started previously.
None.
0 : Information
The IBM International License Agreement for Early Release of Programs has been displayed to the user and the user should now accept or reject the Agreement.
Reply 'yes' or 'no' and press 'Enter'.
0 : Information
Part of the IBM International License Agreement for Early Release of Programs has been displayed to the user. The user should press the Enter key to indicate that they are ready for the next part of the Agreement to be displayed.
Press the Enter key when ready for the next part of the Agreement to be displayed.
20 : Error
The license <insert_3> has been installed but it is not a valid trial period license for this copy of WebSphere MQ.
Check that the correct version of the file is available.
0 : Information
None.
20 : Error
This copy of WebSphere MQ is a beta version and cannot be used with a production or trial license.
Uninstall the beta version of WebSphere MQ and install the production or trial version.
10 : Warning
The purchased processor allowance (<insert_1>) is less than the number of processors (<insert_2>) in this machine.
Ensure sufficient license units have been purchased and use the MQ setmqcap command to set the purchased processor allowance for this installation. Refer to the Quick Beginnings book for more information.
10 : Warning
The purchased processor allowance for this installation is zero.
Ensure sufficient license units have been purchased and use the MQ CHGMQMCAP command to set the purchased processor allowance for this installation. Refer to the Quick Beginnings book for more information.
0 : Information
The purchased processor allowance for this installation has been set to <insert_1> using the MQ setmqcap command.
None.
0 : Information
The purchased processor allowance for this installation has been set to <insert_1> using the MQ CHGMQMCAP command.
None.
0 : Information
The purchased processor allowance is currently set to <insert_1>
Ensure sufficient license units have been purchased and, if necessary, use the MQ setmqcap command to change the purchased processor allowance for this installation. Refer to the Quick Beginnings book for more information.
0 : Information
The purchased processor allowance is currently set to <insert_1>
Ensure sufficient license units have been purchased and, if necessary, use the MQ CHGMQMCAP command to change the purchased processor allowance for this installation. Refer to the Quick Beginnings book for more information.
0 : Information
The operating system reports that the number of processors in this machine is <insert_1>
None.
0 : Information
The purchased processor allowance for this installation has been set to -1, which allows any permitted processor configuration.
None.
10 : Warning
The purchased processor allowance for this installation has not been set.
Ensure sufficient license units have been purchased and use the MQ setmqcap command to set the purchased processor allowance for this installation. Refer to the Quick Beginnings book for more information.
10 : Warning
The purchased processor allowance for this installation has not been set.
Ensure sufficient license units have been purchased and use the MQ CHGMQMCAP command to set the purchased processor allowance for this installation. Refer to the Quick Beginnings book for more information.
0 : Information
Install has detected Intel Hyper=Threading support enabled for Logical Processors. The current Processor Mask is set to <insert_1>.
None.
0 : Information
Microsoft Windows system call SetProcessAffinityMask failed. If this problem persists contact your IBM service representative.
None.
40 : Stop Error
WebSphere MQ only supports group names up to 12 characters long. The operating system is attempting to return a group longer than this.
Reduce the group name to 12 characters or less.
40 : Stop Error
WebSphere MQ only supports user names up to 12 characters long. This operation is being attempted from a user name longer than this.
Reduce the user name to 12 characters or less.
10 : Warning
The queue manager attempted to put a PCF message to <insert_3> to start the channel <insert_4> to cluster queue manager <insert_5>. The put failed with reason <insert_1>. When the queue manager resolves a cluster queue to a remote cluster queue manager, the message is put to the SYSTEM.CLUS.TRANSMIT.QUEUE. If the channel to the remote cluster queue manager is not running, the queue manager attempts to start the channel by sending a PCF message to <insert_3>.
Resolve the problem with <insert_3> and if necessary start the channel manually.
10 : Warning
When the queue manager resolves a cluster queue to a remote cluster queue manager, the message is put to the SYSTEM.CLUS.TRANSMIT.QUEUE. If the channel to the remote cluster queue manager is not running, the queue manager attempts to start the channel by sending a PCF message to the SYSTEM.CHANNEL.INITQ
Resolve the problem with the SYSTEM.CHANNEL.INITQ and if necessary start the channels manually.
10 : Warning
The Cluster Workload exit module <insert_3> could not be loaded for reason <insert_4>.
Correct the problem with the Cluster Workload exit module <insert_3>
10 : Warning
The Queue Manager is configured to run the Cluster Workload Exit in SAFE mode. This means that the Cluster Workload Exit is run by a server process (amqzlw0). The Queue Manager has been waiting <insert_1> seconds for this server process to reply to a request to run the Cluster Workload Exit. It is possible that the exit is hung or is looping.
End the Queue Manager, resolve the problem with the Cluster Workload Exit and restart the Queue Manager
10 : Warning
The address of the Cluster exit function <insert_4> could not be found in module <insert_3> for reason <insert_1> <insert_5>.
Correct the problem with the Cluster exit function <insert_4> in the module <insert_3>
40 : Stop Error
The module <insert_4> for API Exit <insert_3> could not be loaded for reason <insert_5>.
Correct the problem with the API Exit module <insert_3>.
40 : Stop Error
The API Exit <insert_3> function <insert_4> could not be found in the module <insert_5>. The internal return code was <insert_1>.
Correct the problem with the API Exit <insert_3>.
40 : Stop Error
The API Exit <insert_3> function <insert_4> could not be found in the module <insert_5>. The internal return code was <insert_1>.
Correct the problem with the API Exit <insert_3>.
10 : Warning
The API Exit <insert_3> function <insert_4> in the module <insert_5> returned CompCode <insert_1> and ReasonCode <insert_2>.
Correct the problem with the API Exit <insert_3>
10 : Warning
The API Exit <insert_3> module <insert_4> function <insert_5> returned a response code <insert_1> that is not valid in the ExitResponse field of the API Exit parameters (MQAXP).
Investigate why the API Exit <insert_3> set a response code that is not valid.
0 : Information
0 : Information
0 : Information
0 : Information
0 : Information
0 : Information
0 : Information
No authority records match the specified parameters.
20 : Error
The profile name contains invalid characters, contains an invalid wildcard specification, or is of invalid length.
Correct the profile name and submit it again.
10 : Warning
MQ failed to successfully complete a network operation due to the specified error.
Ensure that your network is functioning correctly.
0 : Information
0 : Information
<insert_1> log records have been accessed so far on queue manager <insert_3> during the log replay phase in order to bring the queue manager back to a previously known state.
None.
0 : Information
The log replay phase of the queue manager restart process has been completed for queue manager <insert_3>.
None.
0 : Information
<insert_1> log records have been accessed so far on queue manager <insert_3> during the recovery phase of the transactions manager state.
None.
0 : Information
The state of transactions at the time the queue manager ended has been recovered for queue manager <insert_3>.
None.
0 : Information
<insert_1> transactions out of <insert_2> in-flight at the time queue manager <insert_3> ended have been resolved.
None.
0 : Information
<insert_1> messages from queue <insert_4> have been loaded on queue manager <insert_3>.
None.
40 : Stop Error
The library <insert_3> already exists.
Specify a library which does not already exist.
0 : Information
WebSphere MQ queue manager <insert_3> has been activated.
None.
10 : Warning
WebSphere MQ queue manager <insert_3> is not a backup queue manager and so cannot be activated. A possible reason might be that the queue manager is configured for circular logging.
Re-try the command without the '-a' option.
0 : Information
WebSphere MQ queue manager <insert_3> replay has completed.
None.
20 : Error
WebSphere MQ queue manager <insert_3> cannot be started for replay. A possible reason might be that the queue manager is configured for circular logging.
Re-try the command without the '-r' option.
20 : Error
WebSphere MQ queue manager <insert_3> cannot be started because it has previously been started for replay but has not been activated.
Activate the queue manager and try starting the queue manager again.
20 : Error
The command <insert_3> required at least one of the following arguments, none of which you supplied: <insert_4>.
Check the WebSphere MQ System Administration documentation for details on the usage of the command, correct the command and then retry.
10 : Warning
The attempt to put a trigger message on queue <insert_4> on queue manager <insert_5> failed with reason code <insert_1>. The message will be put on the dead-letter queue.
Ensure that the initiation queue is available, and operational.
10 : Warning
An undelivered message has not been put on the dead-letter queue <insert_4> on queue manager <insert_5>, because the queue is not a local queue. The message will be discarded.
Inform your system administrator.
10 : Warning
The attempt to put a message on the dead-letter queue <insert_4> on queue manager <insert_5> failed with reason code <insert_1>. The message will be discarded.
Ensure that the dead-letter queue is available and operational.
0 : Information
At least one of the conditions required for generating a trigger message was not satisfied, so a trigger message was not generated. If you were expecting a trigger message, consult the WebSphere MQ Application Programming Guide for a list of the conditions required. (Note that arranging for condition <insert_1> to be satisfied might not be sufficient because the conditions are checked in an arbitrary order, and checking stops when the first unsatisfied condition is discovered.)
If a trigger message is required, ensure that all the conditions for generating one are satisfied.
10 : Warning
The attempt to put a report message on queue <insert_4> on queue manager <insert_5> failed with reason code <insert_1>. The message will be put on the dead-letter queue.
Ensure that the reply-to queue is available and operational.
20 : Error
The attempt to put a messsage containing accounting data to the queue <insert_3> failed with reason code <insert_1>. The message data has been discarded.
This error message will be written only once for attempts to put a message to the queue as part of the same operation which fail for the same reason.
Ensure that the queue <insert_3> is available and operational.
20 : Error
The attempt to put a messsage containing statistics data to the queue <insert_3> failed with reason code <insert_1>. The message data has been discarded.
This error message will be written only once for attempts to put a message to the queue as part of the same operation which fail for the same reason.
Ensure that the queue <insert_3> is available and operational.
40 : Stop Error
A journal replay operation was attempted, but the operation required journal entries from journal receivers that are not currently present on the system.
Restore the required journal receivers from backup. Then try the operation again.
40 : Stop Error
WebSphere MQ encountered a problem reading one or more journal entries while performing a journal replay operation.
If you have previously created a journal receiver for a queue manager or are performing a cold restart of a queue manager, delete the QMQMCHKPT file from the queue manager subdirectory in /QIBM/UserData/mqm/qmgrs/ and attempt to restart the queue manager. If the problem persists, use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
40 : Stop Error
The WebSphere MQ commitment control exit program was called with incorrect parameters.
If the program was called by OS/400 as part of a commit or rollback, save the job log, and contact your IBM support center.
40 : Stop Error
The WebSphere MQ commitment control exit program failed due to an unexpected error.
Save the job log, and contact your IBM support center.
0 : Information
The oldest journal receiver in the receiver chain is <insert_3> in library <insert_4>.
None
0 : Information
This message is issued periodically by WebSphere MQ to help you identify which journal receivers can be removed from the system because they are no longer required for startup recovery.
None
0 : Information
A previously damaged object has been re-created, either automatically, or by explicit use of the Recreate Object (RCRMQMOBJ) command. The authorities that applied to this object have not been re-created.
Use the Grant Authority (GRTMQMAUT) command, as appropriate, to re-create the required authorities to this MQ object.
0 : Information
This message is issued periodically by WebSphere MQ to help you identify which journal receivers can be removed from the system because they are no longer required for media recovery.
None
20 : Error
This message is issued when an attempt to write a log record is rejected because the log is full. The queue manager will attempt to resolve the problem.
This situation may be encountered during a period of unusually high message traffic. However, if you persistently fill the log, you may have to consider enlarging the size of the log. You can either increase the number of log files by changing the values in the queue manager configuration file. You will then have to stop and restart the queue manager. Alternatively, if you need to make the log files themselves bigger, you will have to delete and recreate the queue manager.
0 : Information
This message is issued when a log was previously full, but an attempt to write a log record has now been accepted. The log full situation has been resolved.
None
20 : Error
An attempt to resolve a log full situation has failed. This is due to the presence of a long-running transaction.
Try to ensure that the duration of your transactions is not excessive. Commit or roll back any old transactions to release log space for further log records.
10 : Warning
The log for queue manager <insert_3> is too small to support the current data rate. This message is issued when the monitoring tasks maintaining the log cannot keep up with the current rate of data being written.
The number of primary log files configured should be increased to prevent possible log full situations.
0 : Information
The log file <insert_4> contains the oldest log record required to restart the queue manager. Log records older than this may be required for media recovery.
You can move log files older than <insert_4> to an archive medium to release space in the log directory. If you move any of the log files required to recreate objects from their media images, you will have to restore them to recreate the objects.
0 : Information
The log file <insert_4> contains the oldest log record required to recreate any of the objects from their media images. Any log files prior to this will not be accessed by media recovery operations.
You can move log files older than <insert_4> to an archive medium to release space in the log directory.
0 : Information
The log space for the queue manager is becoming full. One or more long-running transactions have been rolled back to release log space so that the queue manager can continue to process requests.
Try to ensure that the duration of your transactions is not excessive. Consider increasing the size of the log to allow transactions to last longer before the log starts to become full.
10 : Warning
Object <insert_3>, type <insert_4> has been marked as damaged. This indicates that the queue manager was either unable to access the object in the file system, or that some kind of inconsistency with the data in the object was detected.
If a damaged object is detected, the action performed depends on whether the queue manager supports media recovery and when the damage was detected. If the queue manager does not support media recovery, you must delete the object as no recovery is possible. If the queue manager does support media recovery and the damage is detected during the processing performed when the queue manager is being started, the queue manager will automatically initiate media recovery of the object. If the queue manager supports media recovery and the damage is detected once the queue manager has started, it may be recovered from a media image using the rcrmqmobj command or it may be deleted.
10 : Warning
Object <insert_3>, type <insert_4> has been marked as damaged. This indicates that the queue manager was either unable to access the object in the file system, or that some kind of inconsistency with the data in the object was detected.
If a damaged object is detected, the action performed depends on whether the queue manager supports media recovery and when the damage was detected. If the queue manager does not support media recovery, you must delete the object as no recovery is possible. If the queue manager does support media recovery and the damage is detected during the processing performed when the queue manager is being started, the queue manager will automatically initiate media recovery of the object. If the queue manager supports media recovery and the damage is detected once the queue manager has started, it may be recovered from a media image using the RCRMQMOBJ command or it may be deleted.
10 : Warning
The commitment control exit program was called during a commit or rollback operation. The queue manager was stopped while the program was registered. This might have resulted in the rolling back of some uncommitted message operations.
Inform your system administrator that uncommitted message operations might have been rolled back when the queue manager was stopped.
20 : Error
The attempt to put a logger event messsage to the queue <insert_3> failed with reason code <insert_2>. The message data has been discarded.
Ensure that the queue <insert_3> is available and operational. Current logger status information can be displayed with the DISPLAY QMSTATUS runmqsc command.
40 : Stop Error
Line <insert_1> of the configuration file <insert_3> contained a duplicate XA resource manager <insert_5>. This is not valid for attribute <insert_4>. Each XA resource manager must be given a unique name.
Check the contents of the file and retry the operation.
40 : Stop Error
Key <insert_3> in the configuration data contained a duplicate XA resource manager <insert_5>. This is not valid for attribute <insert_4>. Each XA resource manager must be given a unique name.
Check the contents of the configuration data and retry the operation.
40 : Stop Error
The WebSphere MQ commitment control exit program was called with incorrect parameters.
If the program was called by OS/400 as part of a commit or rollback, save the job log, and contact your IBM support center.
20 : Error
The XA switch file <insert_4> for resource manager <insert_3> indicates that an attempt has been made to configure another queue manager as an external resource manager. This is not allowed so the queue manager will terminate.
Remove the offending XAResourceManager stanza from the qm.ini configuration file and restart the queue manager.
20 : Error
The XA switch file <insert_4> for resource manager <insert_3> indicates that an attempt has been made to configure another queue manager as an external resource manager. This is not allowed, so the queue manager will terminate.
Remove the offending XAResourceManager stanza from the configuration data and restart the queue manager.
10 : Warning
The XA resource manager <insert_3> has indicated that it is not available, by returning XAER_RMERR on an xa_open request or XAER_RMFAIL when called for something else. Normally this indicates that the resource manager has been shut down. In this case the resource manager cannot participate in any new transactions. Any in-flight transactions in which it was involved will be backed out, and any transactions in which it is in-doubt will only be resolved when contact with the resource manager is re-established. A further message will be issued when the queue manager has been able to do this. If the problem occurred on an xa_open request, and the resource manager should be available, then there may be a configuration problem.
Try to establish the reason why the resource manager is unavailable. It may be that an invalid XAOpenString has been defined for the resource manager in the 'qm.ini' configuration file. If this is the case, stop and then restart the queue manager so that any change will be picked up. Alternatively, the queue manager may be reaching a resource constraint with this resource manager. For example, the resource manager may not be able to accommodate all of the queue manager processes being connected at one time, you may need to alter one of its tuning parameters.
10 : Warning
The XA resource manager <insert_3> has indicated that it is not available, by returning XAER_RMERR on an xa_open request or XAER_RMFAIL when called for <insert_4>. The queue manager is continuing without this resource manager. Normally this indicates that the resource manager has been shut down. In this case the resource manager cannot participate in any new transactions. Any in-flight transactions in which it was involved will be backed out, and any transactions in which it is in-doubt will only be resolved when contact with the resource manager is re-established. A further message will be issued when the queue manager has been able to do this. If the problem occurred on an xa_open request, and the resource manager should be available, then there may be a configuration problem.
Try to establish the reason why the resource manager is unavailable. It may be that an invalid XAOpenString has been defined for the resource manager in the 'qm.ini' configuration file. If this is the case, stop and then restart the queue manager so that any change will be picked up. Alternatively, the queue manager may be reaching a resource constraint with this resource manager. For example, the resource manager may not be able to accommodate all of the queue manager processes being connected at one time, you may need to alter one of its tuning parameters.
20 : Error
WebSphere MQ received an unexpected return code when calling XA resource manager <insert_3> at its <insert_4> entry point. This indicates an internal error, either within MQ or the resource manager.
Try to determine the source of the error. A trace of the failure could be used to look at the XA flows between MQ and the resource manager. MQ has allocated an RMId of <insert_2> to this resource manager. This will be useful when isolating the flows associated with the resource manager concerned. If the error occurs on an xa_commit or xa_rollback request, the queue manager will not attempt to redeliver the commit or rollback instruction for this transaction, until after the queue manager has been restarted. The transaction indoubt is identified by the following XID of X<insert_5>. If you think that the error lies within the queue manager, contact your IBM support center. Do not discard any information describing the problem until after the problem has been resolved.
20 : Error
WebSphere MQ received unexpected return code <insert_1> when calling XA resource manager <insert_3> at its <insert_4> entry point. This indicates an internal error, either within MQ or the resource manager.
Try to determine the source of the error. A trace of the failure could be used to look at the XA flows between MQ and the resource manager. MQ has allocated an RMId of <insert_2> to this resource manager. This will be useful when isolating the flows associated with the resource manager concerned. If the error occurs on an xa_commit or xa_rollback request, the queue manager will not attempt to redeliver the commit or rollback instruction for this transaction, until after the queue manager has been restarted. The transaction indoubt is identified by the following XID of X<insert_5>. If you think that the error lies within the queue manager, contact your IBM support center. Do not discard any information describing the problem until after the problem has been resolved.
20 : Error
WebSphere MQ was processing the commit operation for a transaction involving external resource managers. One or more of these resource managers failed to obey the commit request and instead rolled back their updates. The outcome of the transaction is now mixed and the resources owned by these resource managers may now be out of synchronization. MQ will issue further messages to indicate which resource managers failed to commit their updates.
The transaction with the mixed outcome is identified by the following XID of X<insert_3>. The messages which identify the failing resource managers will also contain this same XID. If the transaction has completed it won't be displayed by the dspmqtrn command and all other transaction participants will have committed their updates. If the transaction is displayed by the dspmqtrn command then there are some participants still in prepared state. In order to preserve data integrity you will need to perform recovery steps local to the failing resource managers.
20 : Error
WebSphere MQ was rolling back a transaction involving external resource managers. One or more of these resource managers failed to obey the rollback request and instead committed their updates. The outcome of the transaction is now mixed and the resources owned by these resource managers may now be out of synchronization. MQ will issue further messages to indicate which resource managers failed to roll back their updates.
The transaction with the mixed outcome is identified by the following XID of X<insert_3>. The messages which identify the failing resource managers will also contain this same XID. If the transaction has completed it won't be displayed by the dspmqtrn command and all other transaction participants will have rolled back their updates. If the transaction is displayed by the dspmqtrn command then there are some participants still in prepared state. In order to preserve data integrity you will need to perform recovery steps local to the failing resource managers.
20 : Error
This message is associated with an earlier AMQ7606 message reporting a mixed transaction outcome. It identifies one of the resource managers (<insert_4>) that failed to commit its updates. The transaction associated with this failure is identified by the following XID of X<insert_3>.
Use the return code <insert_1> returned by the resource manager to determine the effects of the failure. The return code indicates that the resource manager made a heuristic decision about the outcome of the transaction which disagrees with the commit decision of the queue manager. In order to preserve data integrity you will need to perform recovery steps local to this resource manager.
20 : Error
This message is associated with an earlier AMQ7607 message reporting a mixed transaction outcome. It identifies one of the resource managers (<insert_4>) that failed to rollback its updates. The transaction associated with this failure is identified by the following XID of X<insert_3>.
Use the return code <insert_1> returned by the resource manager to determine the effects of the failure. The return code indicates that the resource manager made a heuristic decision about the outcome of the transaction which disagrees with the rollback decision of the queue manager. In order to preserve data integrity you will need to perform recovery steps local to this resource manager.
20 : Error
Exception number <insert_1> occurred when calling resource manager switch <insert_3>.
Check the resource manager switch has not been corrupted.
20 : Error
An error has occurred loading XA switch file <insert_4>. If the error occurred during startup then the queue manager will terminate. At all other times the queue manager will continue without this resource manager meaning that it will no longer be able to participate in global transactions. The queue manager will also retry the load of the switch file at regular intervals so that the resource manager will be able to participate again should the load problem be resolved.
Look for a previous message outlining the reason for the load failure. Message AMQ6175 is issued if the load failed because of a system error. If this is the case then follow the guidance given in message AMQ6175 to resolve the problem. In the absence of prior messages or FFST information related to this problem check that the name of the switch load file is correct and that it is present in a directory from which it can be dynamically loaded by the queue manager. The easiest method of doing this is to define the switch load file as a fully-qualified name. Note that if the queue manager is still running it will need to be restarted in order that any changes made to its configuration data can be picked up.
10 : Warning
The queue manager has noticed that XA resource manager <insert_3> was removed from the qm.ini file of the queue manager. However, it was logged as being involved in <insert_1> transactions that are still in-doubt. The queue manager cannot resolve these transactions.The queue manager is continuing without this resource manager.
First check that the qm.ini configuration file of the queue manager concerned hasn't been mistakenly altered resulting in an 'XAResourceManager' stanza being removed, or the 'Name' of any the resource managers being changed. If the qm.ini file was changed by mistake then you will need to reinstate resource manager <insert_3> in the qm.ini file before stopping and then restarting the queue manager in order that the change will be picked up. If you have intentionally removed a resource manager from the qm.ini file, consider the integrity implications of your action since the resource manager concerned may be in an in-doubt state. If you are sure that is not the case then you can use the 'rsvmqtrn' command to deliver an outcome on behalf of the resource manager in order that the queue manager can forget about the transactions concerned. If you cannot be sure that such an action will not cause an integrity problem then you should consider re-instating the resource manager in the qm.ini file so that the queue manager can contact the resource manager and automatically resolve the transactions concerned next time the queue manager is restarted.
10 : Warning
The queue manager has recognized that XA resource manager <insert_3> was removed from the registry entry of the queue manager. However, it was logged as being involved in <insert_1> transactions that are still in-doubt. The queue manager cannot resolve these transactions.
Check that the configuration data entry of the queue manager concerned has not been altered by mistake, resulting in an 'XAResourceManager' stanza being removed, or the 'Name' of any the resource managers being changed.
If the configuration data entry was changed by mistake, you need to reinstate resource manager <insert_3> in the configuration data before stopping, and then restarting the queue manager to access the change.
If you have intentionally removed a resource manager from the configuration data, consider the integrity implications of your action because the resource manager concerned may be in an in-doubt state.
If you are sure that this is not the case, you can use the 'rsvmqtrn' command to instruct the resource manager to inform the queue manager that it can forget about the transactions concerned.
If using the 'rsvmqtrn' command could result in an integrity problem, you should consider reinstating the resource manager in the configuration data, so that the queue manager can contact the resource manager and automatically resolve the transactions concerned next time the queue manager is restarted.
20 : Error
An exception has been detected during a call to an XA resource manager. The queue manager will continue after assuming a return code of XAER_RMERR from the call.
An FFST should have been produced which documents the exception. Use this and any further FFSTs to try and determine the reason for the failure. A trace of the problem will be useful to identify the XA flows between the queue manager and the resource manager concerned. MQ has allocated an RMId of <insert_1> to this resource manager. Use this to isolate the flows concerned. First contact the supplier of the resource manager for problem resolution. If however you think that the problem lies within the queue manager then contact your IBM support center. Do not discard any information describing the problem until after it has been resolved.
0 : Information
WebSphere MQ has managed to regain contact with a resource manager that had become unavailable. Any in-doubt transactions involving this resource manager will be resolved. The resource manager will now be able to participate in new transactions.
None.
20 : Error
The queue manager has failed to initialize one or more of the XA resource managers defined in the qm.ini configuration file.
Correct the error and restart the queue manager.
20 : Error
The queue manager has failed to initialize one or more of the XA resource managers defined in the configuration data.
Correct the error and restart the queue manager.
0 : Information
You have started the DMPMQLOG command and it is processing your request.
None.
0 : Information
The DMPMQLOG command has finished processing your request and no errors were detected.
None.
20 : Error
You started the DMPMQLOG command specifying an invalid option value. The <insert_4> value for option <insert_3> is either missing or of an incorrect format.
Refer to the command syntax, and then try the command again.
20 : Error
You started the DMPMQLOG command specifying an invalid option of <insert_3>.
Refer to the command syntax and then try the command again.
0 : Information
None.
20 : Error
The DMPMQLOG command has used <insert_3> as the queue manager name and, if shown, <insert_4> as the directory path for <insert_3>. Either <insert_3> and/or <insert_4> is incorrect; if <insert_4> is not shown then it is <insert_3> which is incorrect.
Possible reasons for the error include:
that <insert_3> is not an existing queue manager name;
the entries for <insert_3> in the MQ system initialization (INI) file are incorrect;
<insert_4> is not a correct path for <insert_3>.
If you started the command specifying option -m (queue manager name option) with a value then this value will have been used as the queue manager name, otherwise the default queue manager name will have been used.
Check that <insert_3> is an existing queue manager name. Check your MQ system's initialization (INI) file to ensure that <insert_3> and its associated entries are correct. If <insert_4> is shown, check that it is a correct MQ system directory path for <insert_3>.
20 : Error
The DMPMQLOG command has used <insert_3> as the queue manager name and, if shown, <insert_4> as the directory path for <insert_3>. Either <insert_3> and/or <insert_4> is incorrect; if <insert_4> is not shown then it is <insert_3> which is incorrect.
Possible reasons for the error include:
that <insert_3> is not an existing queue manager name;
the entries for <insert_3> in the MQ system initialization (INI) file are incorrect;
<insert_4> is not a correct path for <insert_3>.
If you started the command specifying option -m (queue manager name option) with a value then this value will have been used as the queue manager name, otherwise the default queue manager name will have been used.
Check that <insert_3> is an existing queue manager name. Check your MQ system's initialization (INI) file to ensure that <insert_3> and its associated entries are correct. If <insert_4> is shown, check that it is a correct MQ system directory path for <insert_3>.
20 : Error
The DMPMQLOG command has used <insert_3> as the queue manager name and, if shown, <insert_4> as the directory path for <insert_3>. Either <insert_3> and/or <insert_4> is incorrect; if <insert_4> is not shown then it is <insert_3> which is incorrect.
Possible reasons for the error include:
that <insert_3> is not an existing queue manager name;
the entries for <insert_3> in the MQ configuration data are incorrect;
<insert_4> is not a correct path for <insert_3>.
If you started the command specifying option -m (queue manager name option) with a value then this value will have been used as the queue manager name, otherwise the default queue manager name will have been used.
Check that <insert_3> is an existing queue manager name. Check your MQ configuration data to ensure that <insert_3> and its associated entries are correct. If <insert_4> is shown, check that it is a correct MQ system directory path for <insert_3>.
20 : Error
The DMPMQLOG command has detected an error and the MQ recording routine has been called. Possible reasons for this include a damaged log file, a problem during initialization for the queue manager or an internal MQ failure.
Check that the queue manager being used by DMPMQLOG, as specified by you using the -m command option or defaulted, exists and is not currently running. If it does not exist, try the command again specifying an existing queue manager. If it is running, stop the queue manager and then try the command again. Otherwise, use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Note the completion code (CompCode) and then contact your IBM support center.
20 : Error
You started the DMPMQLOG command without specifying option -m (queue manager name option) and so your MQ default queue manager name has been used. However, this default name either could not be found or is invalid.
Check that the default queue manager name exists and is valid, and then try the command again.
20 : Error
You started the DMPMQLOG command specifying an invalid combination of the options -b (base LSN option), -s (start LSN option) and -n (extent number option). Only 1 or none of these options may be specified.
Refer to the command syntax and then try the command again.
20 : Error
You started the DMPMQLOG command specifying option -n (extent number option) but this is not valid when your MQ log is defined as circular.
Use a different option and then try the command again.
20 : Error
You started the DMPMQLOG command specifying option -m (queue manager name option) with a value that is more than <insert_1> characters.
Specify a shorter queue manager name and then try the command again.
20 : Error
You started the DMPMQLOG command specifying option -f (log file path option) with a value which is more than <insert_1> characters.
Specify a shorter log file path name and then try the command again.
20 : Error
The DMPMQLOG command has been unable to allocate some storage.
Free some storage and then try the command again.
0 : Information
The DMPMQLOG command has processed any log data and has now reached the end of the log.
None.
20 : Error
The DMPMQLOG command was unable to open file <insert_3> for reading.
Check that the file exists, can be opened for reading, and that you have authority to access it, and then try the command again.
0 : Information
The DMPMQLOG command has finished with your request but an error has been detected. The previous message issued by the command can be used to identify the error.
Refer to the previous message issued by the command.
20 : Error
The DMPMQLOG command has failed during its initialization and the MQ recording routine has been called. Possible reasons for this include that your queue manager is already running. The completion code can be used to identify the error.
Check that the queue manager being used by DMPMQLOG, as specified by you using the -m command option or defaulted, exists and is not currently running. If it is running, stop the queue manager and then try the command again. Otherwise, use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
0 : Information
You have started the DMPMQLOG command without specifying option -m (queue manager name option) and so a default value of <insert_3> is being used. This value is obtained from your default queue manager name.
None.
0 : Information
You have started the DMPMQLOG command without specifying option -m (queue manager name option) and so a default value of <insert_3> is being used. This value is obtained from your MQ default queue manager name.
None.
0 : Information
You have started the DMPMQLOG command without specifying option -b (base LSN option), option -s (start LSN option) or option -n (extent number option), and so a default value of <insert_3> is being used. This value is the Log Sequence Number (LSN) of the first record in the active part of the log, and will be used as the location from which to start dumping.
None.
0 : Information
You have started the DMPMQLOG command without specifying option -b (base LSN option), option -s (start LSN option) or option -n (extent number option), and so a default value of <insert_3> is being used. This value is the Log Sequence Number (LSN) of the first record in the active part of the log, and will be used as the location from which to start dumping.
None.
20 : Error
You have started the DMPMQLOG command specifying option -n (extent number option) with a value of <insert_1> but this value is greater than <insert_2>, which represents the extent currently being used.
When using option -n, specify its value as being less than or equal to the extent number currently being used.
0 : Information
During its normal processing, the DMPMQLOG command did not find any log records in this extent.
None.
20 : Error
The DMPMQLOG command is using the queue manager named <insert_3> but cannot find the manager's object catalogue file. This file should have been created at the time the queue manager was created.
Refer to the "System Management Guide" for a description of the location and name of the object catalogue file. Check that the file exists and is available for use by this command. If it does not exist then you will need to re-create the queue manager.
20 : Error
The DMPMQLOG command is using the queue manager named <insert_3> but cannot find the manager's object catalogue file. This file should have been created at the time the queue manager was created.
Refer to the "System Management Guide" for a description of the location and name of the object catalogue file. Check that the file exists and is available for use by this command. If it does not exist then you will need to re-create the queue manager.
20 : Error
The DMPMQLOG command has been started with an LSN but it cannot be found in the log.
Check for an existing LSN and then try the command again.
20 : Error
The DMPMQLOG command has been started with an extent number but it is beyond the end of the log.
Check for an existing extent number and then try the command again.
20 : Error
The DMPMQLOG command has been started specifying an LSN which is older than the log's base LSN. However, the specified LSN could not be found.
Check for an existing LSN and then try the command again.
20 : Error
You started the DMPMQLOG command specifying option -s (start LSN option) with a value which is less than the base LSN of a log which is defined as circular. LSN values less than the base LSN can only be specified when using a linear log.
When using option -s with a circular log, specify an option value which is equal or greater to the log's base LSN, and then try the command again.
0 : Information
You have started the MIGRATEMQM program.
None.
0 : Information
The MIGRATEMQM program has completed migration of your queue manager and no errors were detected.
None.
20 : Error
See the previously listed messages in the job log. Correct the errors and then restart the MIGRATEMQM program.
None.
20 : Error
See the previously listed messages in this job log, or in associated job logs. Correct the errors and then restart the MIGRATEMQM program.
None.
20 : Error
The MIGRATEMQM program attempted to locate the journal receivers to use for migration, but the operation required access to a journal or journal receiver that is not currently present on the system.
Restore the required journal or journal receiver from backup. Then restart the MIGRATEMQM program.
20 : Error
The MIGRATEMQM program was unable to retrieve a journal entry required for migration. The operation may have failed because a required journal receiver is not currently present on the system.
Restore the required journal receiver from backup. Then restart the MIGRATEMQM program.
20 : Error
The MIGRATEMQM program is unable to create a queue manager with the same name as used in the previous release because a queue manager of this name has already been created.
Delete the queue manager. Then restart the MIGRATEMQM program.
0 : Information
The queue manager "<insert_3>" is starting.
None.
0 : Information
WebSphere MQ objects are being recreated from their media images contained in the log.
None.
0 : Information
WebSphere MQ channels are being recreated from the previous channel definition file.
None.
20 : Error
An unexpected return code, <insert_1>, was returned by command <insert_3>.
See the previously listed messages in this job log, or in associated job logs.
20 : Error
The migration of channel definitions or channel synchronization data encountered an unexpected error.
See the previously listed messages in this job log, or in associated job logs.
40 : Stop Error
The file was successfully sent.
None.
40 : Stop Error
The file was successfully received.
None.
40 : Stop Error
Displays a list of complete files.
None.
40 : Stop Error
Displays a list of incomplete files.
None.
40 : Stop Error
Displays a list of other messages.
None.
40 : Stop Error
Nothing to list.
None.
40 : Stop Error
File deleted.
None.
40 : Stop Error
Nothing to delete.
None.
40 : Stop Error
Invalid arguments supplied.
One or more options were incorrectly specified when issuing the send or receive command. Check the options used and reissue the command.
40 : Stop Error
Queue manager not available.
Check that the queue manager exists and that the listener is running.
40 : Stop Error
Queue manager not available.
Check that the queue manager exists and that the listener is running.
40 : Stop Error
There is insufficient memory to perform the requested action.
1) Check the message size is not excessive
2) Close other applications and try the command again
40 : Stop Error
A queue name was not specified when issuing a send or receive command.
Reissue the command with the QueueName option.
40 : Stop Error
Cannot open queue <insert_3>
Check that the queue exists.
40 : Stop Error
Cannot open file <insert_3>
Check that the file exists, that it is in the correct location and has the appropriate file permissions.
40 : Stop Error
Cannot put to queue <insert_3>
1) Check the Queue Manager has sufficient log space for sending large messages
2) Check the queue does not have put inhibited
3) Check the queue is not full
4) Check the message size of the queue is greater than the message size
5) Check the user has sufficient authority to put messages on the queue
40 : Stop Error
No file name specified.
A file name was not specified when issuing a send command. Reissue the command with the FileName option.
40 : Stop Error
Message length is too small to send data.
Increase the message size and resend with a send command, using the -l MessageSize option to specify a larger message size.
40 : Stop Error
The file being sent has been changed before the complete file has been sent.
Check the file for integrity and reissue the send command.
40 : Stop Error
The list, get, delete or extract request has failed.
1) Check the queue does have get inhibited
2) Check the user has sufficient WMQ authority to get messages from the queue
40 : Stop Error
The get or extract request has failed.
1) Check that the file is not write-protected. In Windows Explorer, right-click the file name and select Properties. Check the user has sufficient authority to write to the destination file system.
2) Check the destination file system exists
3) Check the destination file system is not full
40 : Stop Error
CorrelId is invalid.
1) Check that a valid correlation ID has been specified when receiving a file with the -c option.
2) It must be 48 characters in length.
3) Use the -v option of the receive command to display the correlation ID.
40 : Stop Error
MsgId is invalid.
1) Check that a valid message ID has been specified when receiving an 'other' message with the -u option.
2) It must be 48 characters in length.
40 : Stop Error
There are no FTA files on the specified queue.
Check with the sender that the file was actually sent.
40 : Stop Error
Cannot delete the file because it's not unique.
None.
40 : Stop Error
Cannot replace an existing file.
Reissue the command with the -y option.
40 : Stop Error
Unable to load the WebSphere MQ library.
None.
40 : Stop Error
This application requires <insert_3>.
Check that <insert_3> is available and installed correctly.
40 : Stop Error
This application cannot start <insert_3>.
Check that <insert_3> is available and installed correctly.
0 : Information
None.
None.
0 : Information
None.
None.
0 : Information
None.
None.
0 : Information
None.
None.
0 : Information
None.
None.
0 : Information
None.
None.
0 : Information
An unsuccessful attempt was made to start the web administration server on port <insert_1>.
Check the product is installed correctly; the required registry keys and values are correct and the web server port is not already in use. If the problem persists contact your service representative.
0 : Information
WebSphere MQ web administration server running. Listening on port <insert_4>, root directory is <insert_5>.
No action is required.
0 : Information
WebSphere MQ web administration had the following internal run-time error: <insert_4>.
Check that: the product is installed correctly and that the required registry keys and values are correct. If the problem persists contact your service representative.
10 : Warning
The maximum number of concurrent web administration users has been reached (<insert_4>).
Use the 'Web Administration Server' properties page in the Microsoft Management Console to increase the value of the web administration 'MaxClients' parameter.
20 : Error
While trying to create class <insert_3> on <insert_4> error code <insert_1> was encountered. The associated error message generated by the operating system is: <insert_5>
Check the system documentation to determine the course of action required to rectify the problem.
0 : Information
The service was unable to start <insert_4>/<insert_3>. The error message reported was as follows: <insert_5>
Use WebSphere MQ Explorer to investigate why the service could not begin. If recovery for this service is active, MQ will attempt to recover.
10 : Warning
The WebSphere MQ service was unable to stop <insert_4>/<insert_3>. The error message reported was as follows: <insert_5>
Use WebSphere MQ Explorer to investigate why the service could not be stopped.
0 : Information
The WebSphere MQ service has detected that <insert_4>/<insert_3> has failed, and is attempting to restart it.
No Action Required.
0 : Information
The WebSphere MQ service has successfully recovered <insert_4>/<insert_3>.
No Action Required.
10 : Warning
The WebSphere MQ service has attempted to recover <insert_4>/<insert_3>, but all attempts have failed. There will be no more attempts to recover this service.
Use WebSphere MQ Explorer to investigate why the service failed and could not be restarted.
10 : Warning
An attempt to delete queue manager <insert_4> failed. WebSphere MQ returned error code <insert_1>: <insert_5>
Ensure that the queue manager name has been specified correctly, and try again.
10 : Warning
Queue manager <insert_4> could not be created. WebSphere MQ returned error <insert_1>: <insert_5>
Check the error and application event logs to investigate the reason for the the returned error and suggested responses to take to rectify the fault. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved.
20 : Error
The WebSphere MQ extensible counter dll was unable to open a mapped file used to collect queue performance data. Your system may be running short on virtual memory.
No action required. Performance statistics for MQ queues will not be displayed.
20 : Error
The WebSphere MQ extensible counter dll was unable to create a mutex required to synchronise collection of queue performance data
No action required. Performance statistics for MQ queues will not be displayed.
20 : Error
The WebSphere MQ extensible counter dll was unable to map the shared memory file required for collection of queue performance data.
No action required. Performance statistics for MQ queues will not be displayed.
20 : Error
The WebSphere MQ extensible counter dll was unable to obtain performance counter values from the "Performance" key for WebSphere MQ services. Status code is the return value from the Windows registry call RegOpenKeyEx.
No action required. Performance statistics for MQ queues will not be displayed.
20 : Error
The WebSphere MQ extensible counter dll was unable to obtain performance counter values from the "Performance\First Counter" key for WebSphere MQ services. Status code is the return value from the Windows registry call RegOpenKeyEx.
No action required. Performance statistics for MQ queues will not be displayed.
20 : Error
The WebSphere MQ extensible counter dll was unable to obtain performance counter values from the "Performance\First Help" key for WebSphere MQ services. Status code is the return value from the Windows registry call RegOpenKeyEx.
No action required. Performance statistics for MQ queues will not be displayed.
30 : Severe error
The data-conversion exit program, <insert_3>, failed to load. The internal function gave exception <insert_4>.
Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
30 : Severe error
Message data conversion has been requested for a WebSphere MQ message with a user-defined format, but the necessary data-conversion exit program, <insert_3>, cannot be found. The internal function gave exception <insert_4>.
Check that the necessary data-conversion exit <insert_3> exists.
30 : Severe error
Message data conversion was requested for a WebSphere MQ message with a user-defined format, but the necessary data conversion exit program, <insert_3>, was not found, or loaded. The <insert_4> function call gave a return code of <insert_1>.
Check that the necessary data conversion exit routine exists in one of the standard directories for dynamically loaded modules. If necessary, inspect the generated output to examine the message descriptor (MQMD structure) of the MQ message for the conversion which was requested. This may help you to determine where the message originated.
30 : Severe error
The data-conversion exit program, <insert_3>, ended with an unexpected exception <insert_4>. The message has not been converted.
Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
30 : Severe error
The data-conversion exit routine, <insert_3>, ended with an unexpected exception. The message has not been converted.
Correct the error in the data-conversion exit routine.
0 : Information
Display active directory CRL server details.
None.
0 : Information
No active directory CRL server definitions could be found.
None.
0 : Information
20 : Error
No domain controllers with Active Directories could be found on the domain that your computer is a member of.
Active Directory support for MQ client connections cannot be used without a default Active Directory available on your domain.
20 : Error
WebSphere MQ support libraries for Active Directory client connections could not be initialized.
Check that the Active Directory client pre-requisite software has been installed on your machine before attempting to use this feature.
20 : Error
WebSphere MQ has failed to create an IBM-MQClientConnections container as a child of your domain's system container in the Active Directory.
Ensure that you have permission to create sub-containers of the system container, and modify the otherWellKnownObjects property of the system container.
10 : Warning
The client connection table for this Queue Manager could not be migrated at this time.
Ensure that the client connection table exists and is not corrupted, and that you have authority to create new objects in the Active Directory on your domain.
0 : Information
The service connection point was successfully created for this client connection.
None.
20 : Error
The IBM-MQClientConnections Active Directory container could not be located in the Global Catalog.
Ensure that setmqscp has been used to create the container object and that you have permission to read the container and its child objects.
0 : Information
Display active directory channel details.
None.
20 : Error
There was a problem when attempting to delete the MQ Active Directory container. The container must be empty before it can be deleted from the directory.
None.
0 : Information
No active directory client channel definitions could be found.
None.
0 : Information
30 : Severe error
The MQDXP structure passed to the Internal Formats Conversion routine contains an incorrect eye-catcher field.
Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
30 : Severe error
Message data conversion cannot convert a message in Programmable Command Format (PCF) because the message is only <insert_1> bytes long and does not contain a PCF header. The message has either been truncated, or it contains data that is not valid.
Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor of the message to determine the source of the message and to see how data that is not valid became included in the message.
30 : Severe error
Message data conversion cannot convert a message because the integer encoding value of the message, <insert_1>, was not recognized.
Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor of the message to determine the source of the message and to see how data that is not valid became included in the message.
30 : Severe error
Message data conversion cannot convert a message in Programmable Command Format (PCF) because the PCF header structure contains an incorrect length field. Either the message has been truncated, or it contains data that is not valid.
Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor of the message to determine the source of the message and to see how data that is not valid became included in the message.
30 : Severe error
Message data conversion cannot convert a message because the Version field of the message contains an incorrect value.
Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor of the message to determine the source of the message and to see how data that is not valid became included in the message.
30 : Severe error
Message data conversion cannot convert a message in Programmable Command Format (PCF) because the parameter count field of the PCF header is incorrect.
Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor of the message to determine the source of the message and to see how data that is not valid became included in the message.
30 : Severe error
A Programmable Command Format (PCF) structure passed to the Internal Formats Converter contained an incorrect type field.
Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor of the message to determine the source of the message and to see how data that is not valid became included in the message.
30 : Severe error
A Programmable Command Format (PCF) structure passed to the Internal Formats Converter contained an incorrect length field.
Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor of the message to determine the source of the message and to see how data that is not valid became included in the message.
30 : Severe error
Message data conversion cannot convert a message in Programmable Command Format (PCF) because structure number <insert_1>, of Type value <insert_2>, within the message is incomplete. The message has either been truncated, or it contains data that is not valid.
Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor of the message to determine the source of the message and to see how data that is not valid became included in the message.
30 : Severe error
A Programmable Command Format (PCF) structure passed to the Internal Formats Converter contains an incorrect CCSID.
Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor of the message to determine the source of the message and to see how data that is not valid became included in the message.
30 : Severe error
Message data conversion cannot convert a message in Programmable Command Format (PCF) because one of the structures of the message contains an incorrect length field.
Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor of the message to determine the source of the message and to see how data that is not valid became included in the message.
30 : Severe error
Message data conversion cannot convert a message in Programmable Command Format (PCF) because a StringList structure of the message contains an incorrect count field.
Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor, the headers of the message, and the incorrect structure to determine the source of the message, and to see how data that is not valid became included in the message.
30 : Severe error
Message data conversion cannot convert a message in Programmable Command Format (PCF) because structure number <insert_1> of the message contains an incorrect string length value <insert_2>.
Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor, the headers of the message, and the incorrect structure to determine the source of the message and to see how data that is not valid became included in the message.
30 : Severe error
Message data conversion could not convert a message in Programmable Command Format (PCF) because structure <insert_1> of the message contained a CodedCharSetId field of MQCCSI_DEFAULT while the message itself had a CodedCharSetId of MQCCSI_EMBEDDED, or the Flags field of the MQEPH structure containing the PCF specified flag MQEPH_CCSID_EMBEDDED. These are incorrect combinations.
Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor, the headers of the message and the incorrect structure to determine the source of the message and to see how data that is not valid became included in the message.
30 : Severe error
Message data conversion could not convert a message because the Message Descriptor of the message contained an incorrect CodedCharSetId field.
Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor of the message to determine the source of the message and to see how data that is not valid became included in the message.
30 : Severe error
The output file already exists, but REPLACE has not been specified.
Specify REPLACE to over-write the existing file, or select a different output file name.
30 : Severe error
This error is detected when attempting data conversion. The valid range for the length is 4 (with no string data) to 32767. The message is returned unconverted with a reason code of MQRC_CONVERTED_STRING_TOO_BIG.
Check the content of the message before data conversion and correct the message format. When converting data using two or more bytes per character, remember that the number of bytes in each character can change during data conversion. This causes the message lengths to change.
0 : Information
None.
None.
0 : Information
The crtmqcvx command has parsed one structure.
None.
0 : Information
The crtmqcvx command has parsed <insert_1> structures.
None.
0 : Information
The field within the structure is of a type that is not recognized.
Correct the field and retry the command.
0 : Information
An array field of the structure has an incorrect dimension value.
Correct the field and retry the command.
20 : Error
The structure contains another field after a variable length field. A variable length field must be the last field of the structure.
Correct the structure and retry the command.
30 : Severe error
Field name <insert_3> is a field of type 'float'. Fields of type float are not supported by this command.
Either correct the structure to eliminate fields of type float, or write your own routine to support conversion of these fields.
30 : Severe error
Field name <insert_3> is a field of type 'double'. Fields of type double are not supported by this command.
Either correct the structure to eliminate fields of type double, or write your own routine to support conversion of these fields.
30 : Severe error
Field name <insert_3> is a 'pointer' field. Fields of type pointer are not supported by this command.
Either correct the structure to eliminate fields of type pointer, or write your own routine to support conversion of these fields.
30 : Severe error
Field name <insert_3> is a 'bit' field. Bit fields are not supported by this command.
Either correct the structure to eliminate bit fields, or write your own routine to support conversion of these fields.
30 : Severe error
This command requires that an input file is specified.
Specify the name of the input file and retry the command.
30 : Severe error
This command requires that an output file name is specified.
Specify the name of the output file and retry the command.
30 : Severe error
The option specified is not valid for this command.
Retry the command with a valid option.
30 : Severe error
The command was passed an incorrect number of arguments.
Retry the command, passing it the correct number of arguments.
30 : Severe error
You cannot open the file <insert_3>.
Check that you have the correct authorization to the file and retry the command.
30 : Severe error
This line of the input file contains a language syntax error.
Correct the syntax error and retry the command.
30 : Severe error
This message identifies where, in the input file, a previously reported error was detected.
Correct the error and retry the command.
40 : Stop Error
A listener object can not be specified with a port.
Specify either a listener object or a port number.
40 : Stop Error
A listener object can not be specified with an IP address.
Specify either a listener object or an IP address.
40 : Stop Error
A listener object can not be specified with an end option.
Specify either a listener object or an end option.
30 : Severe error
The message compression value *ANY is only valid for *RCVR, *RQSTR and *SVRCN channel types.
Specify a valid message compression list.
30 : Severe error
RPLYMSG(*YES) can not be specified without RTEINF(*YES).
If RPLYMSG(*YES) is specified then RTEINF(*YES) must also be specified.
30 : Severe error
RPLYMQM can not be specified without RPLYQ.
If RPLYMQM is specified then RPLYQ must also be specified.
30 : Severe error
The CRRLID parameter was specified with one or more of MSGPST, MSGPRTY, OPTION, RPLYQ, RPLYMQM, EXPIRY, EXPRPT, RTEINF RPLYMSG, DLVRMSG, FWDMSG, MAXACTS and DETAIL which are invalid with CRRLID.
Specify only those parameters which are valid with CRRLID.
30 : Severe error
DSPMSG(*NO) was specified with one or more of BROWSE, DSPINF and WAIT which are invalid with DSPMSG(*NO).
Specify only those parameters which are valid with DSPMSG(*NO).
30 : Severe error
DSPMSG(*NO) and RPLYMSG(*YES) can not be specified without RPLYQ.
If DSPMSG(*NO) and RPLYMSG(*YES) are specified than RPLYQ must also be specified.
30 : Severe error
DSPMSG(*NO) and OPTION not *NONE can not be specified without RPLYQ.
If DSPMSG(*NO) and OPTION not *NONE are specified than RPLYQ must also be specified.
40 : Stop Error
The NPMCLASS parameter may not be specified for a queue of type *ALS or *RMT.
Remove the NPMCLASS parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
40 : Stop Error
The MONQ parameter may not be specified for a queue of type *ALS or *RMT.
Remove the MONQ parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
40 : Stop Error
The STATQ parameter may not be specified for a queue of type *ALS or *RMT.
Remove the STATQ parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
40 : Stop Error
The ACCTQ parameter may not be specified for a queue of type *ALS or *RMT.
Remove the ACCTQ parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
0 : Information
All queue managers have been successfully quiesced.
None.
40 : Stop Error
The MQMNAME parameter may only be specified for TRCEARLY(*NO). TRCEARLY(*YES) applies to all queue managers.
If TRCEARLY(*YES) is required remove MQMNAME from the command.
40 : Stop Error
The MQMNAME parameter may only be specified for SET(*ON) or SET(*OFF). SET(*END) applies to all queue managers.
If SET(*END) is required remove MQMNAME from the command.
40 : Stop Error
The CLWLRANK parameter may not be specified for a queue of type *MDL.
Remove the CLWLRANK parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
40 : Stop Error
The CLWLPRTY parameter may not be specified for a queue of type *MDL.
Remove the CLWLPRTY parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
40 : Stop Error
A listener object can not be specified with a listener backlog.
Specify either a listener object or a listener backlog.
40 : Stop Error
The MONCHL parameter may not be specified with channel type *CLTCN.
Remove the MONCHL parameter from the command or, if the command is CRTMQMCHL, specify a different value for CHLTYPE. Then try the command again.
40 : Stop Error
The STATCHL parameter may not be specified with channel type *CLTCN.
Remove the STATCHL parameter from the command or, if the command is CRTMQMCHL, specify a different value for CHLTYPE. Then try the command again.
40 : Stop Error
The CLWLRANK parameter may only be specified with channel types *CLUSSDR or *CLUSRCVR.
Remove the CLWLRANK parameter from the command or, if the command is CRTMQMCHL, specify a different value for CHLTYPE. Then try the command again.
40 : Stop Error
The CLWLPRTY parameter may only be specified with channel types *CLUSSDR or *CLUSRCVR.
Remove the CLWLPRTY parameter from the command or, if the command is CRTMQMCHL, specify a different value for CHLTYPE. Then try the command again.
40 : Stop Error
The CLWLWGHT parameter may only be specified with channel types *CLUSSDR or *CLUSRCVR.
Remove the CLWLWGHT parameter from the command or, if the command is CRTMQMCHL, specify a different value for CHLTYPE. Then try the command again.
40 : Stop Error
The CLWLUSEQ parameter may only be specified for a queue of type *LCL.
Remove the CLWLUSEQ parameter from the command or, if the command is CRTMQMQ, specify a value of *LCL for QTYPE. Then try the command again.
40 : Stop Error
The MCAUSRID parameter may not be specified with channel type *CLTCN.
Remove the MCAUSRID parameter from the command or, if the command is CRTMQMCHL, specify a different value for CHLTYPE. Then try the command again.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
pro |