The following is a list of PCF reason codes, in numeric order, providing detailed information to help you understand them, including:
See Reason code cross reference for a list of PCF reason codes in alphabetic order.
Type not valid.
The MQCFH Type field value was not valid.
Specify a valid type.
Structure length not valid.
The MQCFH StrucLength field value was not valid.
Specify a valid structure length.
Structure version number is not valid.
The MQCFH Version field value was not valid.
Specify a valid structure version number.
Message sequence number not valid.
The MQCFH MsgSeqNumber field value was not valid.
Specify a valid message sequence number.
Control option not valid.
The MQCFH Control field value was not valid.
Specify a valid control option.
Parameter count not valid.
The MQCFH ParameterCount field value was not valid.
Specify a valid parameter count.
Command identifier not valid.
The MQCFH Command field value was not valid.
Specify a valid command identifier.
Command failed.
The command has failed.
Refer to the previous error messages for this command.
Structure length not valid.
The MQCFIN or MQCFIN64 StrucLength field value was not valid.
Specify a valid structure length.
Structure length not valid.
The MQCFST StrucLength field value was not valid. The value was not a multiple of four or was inconsistent with the MQCFST StringLength field value.
Specify a valid structure length.
String length not valid.
The MQCFST StringLength field value was not valid. The value was negative or greater than the maximum permitted length of the parameter specified in the Parameter field.
Specify a valid string length for the parameter.
Force value not valid.
The force value specified was not valid.
Specify a valid force value.
Structure type not valid.
The structure Type value was not valid.
Specify a valid structure type.
Parameter identifier is not valid.
The MQCFIN or MQCFIN64 Parameter field value was not valid.
Specify a valid parameter identifier.
Parameter identifier is not valid.
The MQCFST Parameter field value was not valid.
Specify a valid parameter identifier.
Message length not valid.
The message data length was inconsistent with the length implied by the parameters in the message, or a positional parameter was out of sequence.
Specify a valid message length, and check that positional parameters are in the correct sequence.
Duplicate parameter.
Two MQCFIN or MQCFIN64 or MQCFIL or MQCFIL64 structures, or any two of those types of structure, with the same parameter identifier were present.
Check for and remove duplicate parameters.
Duplicate parameter.
Two MQCFST structures, or an MQCFSL followed by an MQCFST structure, with the same parameter identifier were present.
Check for and remove duplicate parameters.
Parameter count too small.
The MQCFH ParameterCount field value was less than the minimum required for the command.
Specify a parameter count that is valid for the command.
Parameter count too big.
The MQCFH ParameterCount field value was more than the maximum for the command.
Specify a parameter count that is valid for the command.
Queue already exists in cell.
An attempt was made to define a queue with cell scope, or to change the scope of an existing queue from queue-manager scope to cell scope, but a queue with that name already existed in the cell.
Do one of the following:
Queue type not valid.
The QType value was not valid.
Specify a valid queue type.
Format not valid.
The MQMD Format field value was not MQFMT_ADMIN.
Specify the valid format.
Structure length not valid.
The MQCFSL StrucLength field value was not valid. The value was not a multiple of four or was inconsistent with the MQCFSL StringLength field value.
Specify a valid structure length.
Replace value not valid.
The Replace value was not valid.
Specify a valid replace value.
Duplicate parameter value.
In the MQCFIL or MQCFIL64 structure, there was a duplicate parameter value in the list.
Check for and remove duplicate parameter values.
Count of parameter values not valid.
The MQCFIL or MQCFIL64 Count field value was not valid. The value was negative or greater than the maximum permitted for the parameter specified in the Parameter field.
Specify a valid count for the parameter.
Structure length not valid.
The MQCFIL or MQCFIL64 StrucLength field value was not valid.
Specify a valid structure length.
Mode value not valid.
The Mode value was not valid.
Specify a valid mode value.
Former name for MQRCCF_MODE_VALUE_ERROR.
Message sequence number not valid.
The message sequence number parameter value was not valid.
Specify a valid message sequence number.
Data count not valid.
The Ping Channel DataCount value was not valid.
Specify a valid data count value.
Ping Channel command failed.
The Ping Channel command failed with a data compare error. The data offset that failed is returned in the message (with parameter identifier MQIACF_ERROR_OFFSET).
Consult your systems administrator.
Parameter identifier is not valid.
The MQCFSL Parameter field value was not valid.
Specify a valid parameter identifier.
Channel type not valid.
The ChannelType specified was not valid, or did not match the type of an existing channel being copied, changed or replaced, or the command and the specified disposition cannot be used with that type of channel.
Specify a valid channel name, type, or disposition.
Parameter sequence not valid.
The sequence of parameters is not valid for this command.
Specify the positional parameters in a valid sequence for the command.
Transmission protocol type not valid.
The TransportType value was not valid.
Specify a valid transmission protocol type.
Batch size not valid.
The batch size specified was not valid.
Specify a valid batch size value.
Disconnection interval not valid.
The disconnection interval specified was not valid.
Specify a valid disconnection interval.
Short retry count not valid.
The ShortRetryCount value was not valid.
Specify a valid short retry count value.
Short timer value not valid.
The ShortRetryInterval value was not valid.
Specify a valid short timer value.
Long retry count not valid.
The long retry count value specified was not valid.
Specify a valid long retry count value.
Long timer not valid.
The long timer (long retry wait interval) value specified was not valid.
Specify a valid long timer value.
Sequence wrap number not valid.
The SeqNumberWrap value was not valid.
Specify a valid sequence wrap number.
Maximum message length not valid.
The maximum message length value specified was not valid.
Specify a valid maximum message length.
Put authority value not valid.
The PutAuthority value was not valid.
Specify a valid authority value.
Purge value not valid.
The Purge value was not valid.
Specify a valid purge value.
Parameter identifier is not valid.
The MQCFIL or MQCFIL64 Parameter field value was not valid, or specifies a parameter that cannot be filtered, or that is also specified as a parameter to select a subset of objects.
Specify a valid parameter identifier.
Message truncated.
The command server received a message that is larger than its maximum valid message size.
Check the message contents are correct.
Coded character-set identifier error.
In a command message, one of the following occurred:
The error response message contains the correct value.
This reason can also occur if a ping cannot be performed because the coded character-set identifiers are not compatible. In this case the correct value is not returned.
Construct the command with the correct coded character-set identifier, and specify this in the message descriptor when sending the command. For ping, use a suitable coded character-set identifier.
Encoding error.
The Encoding field in the message descriptor of the command does not match that required for the platform at which the command is being processed.
Construct the command with the correct encoding, and specify this in the message descriptor when sending the command.
Data conversion value not valid.
The value specified for DataConversion is not valid.
Specify a valid value.
In-doubt value not valid.
The value specified for InDoubt is not valid.
Specify a valid value.
Escape type not valid.
The value specified for EscapeType is not valid.
Specify a valid value.
Channel table value not valid.
The ChannelTable specified was not valid, or was not appropriate for the channel type specified on an Inquire Channel or Inquire Channel Names command.
Specify a valid channel table value.
Message channel agent type not valid.
The MCAType value specified was not valid.
Specify a valid value.
Channel instance type not valid.
The ChannelInstanceType specified was not valid.
Specify a valid channel instance type.
Channel status not found.
For Inquire Channel Status, no channel status is available for the specified channel. This may indicate that the channel has not been used.
None, unless this is unexpected, in which case consult your systems administrator.
Duplicate parameter.
Two MQCFSL structures, or an MQCFST followed by an MQCFSL structure, with the same parameter identifier were present.
Check for and remove duplicate parameters.
Total string length error.
The total length of the strings (not including trailing blanks) in a MQCFSL structure exceeds the maximum allowable for the parameter.
Check that the structure has been specified correctly, and if so reduce the number of strings.
Count of parameter values not valid.
The MQCFSL Count field value was not valid. The value was negative or greater than the maximum permitted for the parameter specified in the Parameter field.
Specify a valid count for the parameter.
String length not valid.
The MQCFSL StringLength field value was not valid. The value was negative or greater than the maximum permitted length of the parameter specified in the Parameter field.
Specify a valid string length for the parameter.
Broker has been deleted.
When a broker is deleted using the dltmqbrk command, all broker queues created by the broker are deleted. Before this can be done the queues are emptied of all command messages; any that are found are placed on the dead-letter queue with this reason code.
Process the command messages that were placed on the dead-letter queue.
Stream name is not valid.
The stream name parameter is not valid. Stream names must obey the same naming rules as for WebSphere MQ queues.
Retry the command with a valid stream name parameter.
Topic name is invalid.
A command has been sent to the broker containing a topic name that is not valid. Note that wildcard topic names are not allowed for Register Publisher and Publish commands.
Retry the command with a valid topic name parameter. Up to 256 characters of the topic name in question are returned with the error response message. If the topic name contains a null character, this is assumed to terminate the string and is not considered to be part of it. A zero length topic name is not valid, as is one that contains an escape sequence that is not valid.
Subscriber or publisher is not registered.
A Deregister command has been issued to remove registrations for a topic, or topics, for which the publisher or subscriber is not registered. If multiple topics were specified on the command, it fails with a completion code of MQCC_WARNING if the publisher or subscriber was registered for some, but not all, of the topics specified. This error code is also returned to a subscriber issuing a Request Update command for a topic for which he does not have a subscription.
Investigate why the publisher or subscriber is not registered. In the case of a subscriber, the subscriptions might have expired, or been removed automatically by the broker if the subscriber is no longer authorized.
An invalid or unknown queue manager name has been supplied.
A queue manager name has been supplied as part of a publisher or subscriber identity. This might have been supplied as an explicit parameter or in the ReplyToQMgr field in the message descriptor of the command. Either the queue manager name is not valid, or in the case of a subscriber identity, the subscriber's queue could not be resolved because the remote queue manager is not known to the broker queue manager.
Retry the command with a valid queue manager name. If appropriate, the broker includes a further error reason code within the error response message. If one is supplied, follow the guidance for that reason code in WebSphere MQ Application Programming Reference to resolve the problem.
Stream name does not match the stream queue it was sent to.
A command has been sent to a stream queue that specified a different stream name parameter.
Retry the command either by sending it to the correct stream queue or by modifying the command so that the stream name parameter matches.
An invalid or unknown queue name has been supplied.
A queue name has been supplied as part of a publisher or subscriber identity. This might have been supplied as an explicit parameter or in the ReplyToQ field in the message descriptor of the command. Either the queue name is not valid, or in the case of a subscriber identity, the broker has failed to open the queue.
Retry the command with a valid queue name. If appropriate, the broker includes a further error reason code within the error response message. If one is supplied, follow the guidance for that reason code in WebSphere MQ Application Programming Reference to resolve the problem.
No retained message exists for the topic specified.
A Request Update command has been issued to request the retained message associated with the specified topic. No retained message exists for that topic.
If the topic or topics in question should have retained messages, the publishers of these topics might not be publishing with the correct publication options to cause their publications to be retained.
Publisher or subscriber identity already assigned to another user ID.
Each publisher and subscriber has a unique identity consisting of a queue manager name, a queue name, and optionally a correlation identifier. Associated with each identity is the user ID under which that publisher or subscriber first registered. A given identity can be assigned only to one user ID at a time. While the identity is registered with the broker all commands wanting to use it must specify the correct user ID. When a publisher or a subscriber no longer has any registrations with the broker the identity can be used by another user ID.
Either retry the command using a different identity or remove all registrations associated with the identity so that it can be used by a different user ID. The user ID to which the identity is currently assigned is returned within the error response message. A Deregister command could be issued to remove these registrations. If the user ID in question cannot be used to execute such a command, you need to have the necessary authority to open the SYSTEM.BROKER.CONTROL.QUEUE using the MQOO_ALTERNATE_USER_AUTHORITY option.
Command sent to wrong broker queue.
The command is a valid broker command but the queue it has been sent to is incorrect. Publish and Delete Publication commands need to be sent to the stream queue, all other commands need to be sent to the SYSTEM.BROKER.CONTROL.QUEUE.
Retry the command by sending it to the correct queue.
Correlation identifier used as part of an identity is all binary zeroes.
Each publisher and subscriber is identified by a queue manager name, a queue name, and optionally a correlation identifier. The correlation identifier is typically used to allow multiple subscribers to share the same subscriber queue. In this instance a publisher or subscriber has indicated within the Registration or Publication options supplied on the command that their identity does include a correlation identifier, but a valid identifier has not been supplied.
Retry the command ensuring that the correlation identifier supplied in the message descriptor of the command message is not all binary zeroes.
Subscriber has insufficient authority.
To receive publications a subscriber application needs both browse authority for the stream queue that it is subscribing to, and put authority for the queue that publications are to be sent to. Subscriptions are rejected if the subscriber does not have both authorities. In addition to having browse authority for the stream queue, a subscriber would also require altusr authority for the stream queue to subscribe to certain topics that the broker itself publishes information on. These topics start with the MQ/SA/ prefix.
Ensure that the subscriber has the necessary authorities and reissue the request. The problem might occur because the subscriber's user ID is not known to the broker. This can be identified if a further error reason code of MQRC_UNKNOWN_ENTITY is returned within the error response message.
Stream is not known by the broker or could not be created.
A command message has been put to the SYSTEM.BROKER.CONTROL.QUEUE for an unknown stream. This error code is also returned if dynamic stream creation is enabled and the broker failed to create a stream queue for the new stream using the SYSTEM.BROKER.MODEL.STREAM queue.
Retry the command for a stream that the broker supports. If the broker should support the stream, either define the stream queue manually, or correct the problem that prevented the broker from creating the stream queue itself.
Invalid registration options have been supplied.
The registration options provided on a command are not valid.
Retry the command with a valid combination of options.
Invalid publication options have been supplied.
The publication options provided on a Publish command are not valid.
Retry the command with a valid combination of options.
Command received from an unknown broker.
Within a multi-broker network, related brokers pass subscriptions and publications between each other as a series of command messages. One such command message has been received from a broker that is not, or is no longer, related to the detecting broker.
his situation can occur if the broker network is not quiesced while topology changes are made to the network. When removing a broker from the network ensure that the channels between the two related brokers in question are active.
Queue manager coded character set identifier error.
The coded character set value for the queue manager was not valid.
Specify a valid value.
Invalid delete options have been supplied.
The options provided with a Delete Publication command are not valid.
Retry the command with a valid combination of options.
ClusterName and ClusterNamelist attributes conflict.
The command was rejected because it would have resulted in the ClusterName attribute and the ClusterNamelist attribute both being nonblank. At least one of these attributes must be blank.
If the command specified one of these attributes only, you must also specify the other one, but with a value of blanks. If the command specified both attributes, ensure that one of them has a value of blanks.
RepositoryName and RepositoryNamelist attributes conflict.
Either:
Reissue the command with the correct values or on the correct queue manager.
Queue cannot be a cluster queue.
The command was rejected because it would have resulted in a cluster queue also being a transmission queue, which is not permitted, or because the queue in question cannot be a cluster queue.
Ensure that the command specifies either:
Action value not valid.
The value specified for Action is not valid. There is only one valid value.
Specify MQACT_FORCE_REMOVE as the value of the Action parameter.
Library for requested communications protocol could not be loaded.
The library needed for the requested communications protocol could not be loaded.
Install the library for the required communications protocol, or specify a communications protocol that has already been installed.
NetBIOS listener name not defined.
The NetBIOS listener name is not defined.
Add a local name to the configuration file and retry the operation.
The broker command failed to complete.
A broker command was issued but it failed to complete.
Diagnose the problem using the provided information and issue a corrected command.
Conflicting parameters.
The command was rejected because the parameter identified in the error response was in conflict with another parameter in the command.
Consult the description of the parameter identified to ascertain the nature of the conflict, and the correct command.
Path not valid.
The path specified was not valid.
Specify a valid path.
Syntax error found in parameter.
The parameter specified contained a syntax error.
Check the syntax for this parameter.
Password length error.
The password string length is rounded up by to the nearest eight bytes. This rounding causes the total length of the SSLCryptoHardware string to exceed its maximum.
Decrease the size of the password, or of earlier fields in the SSLCryptoHardware string.
Filter not valid.
Either:
Wrong user.
A publish/subscribe command message cannot be executed on behalf of the requesting user because the subscription that it would update is already owned by a different user. A subscription can be updated or deregistered only by the user that originally registered the subscription.
Ensure that applications that need to issue commands against existing subscriptions are running under the user identifier that originally registered the subscription. Alternatively, use different subscriptions for different users.
The subscription already exists.
A matching subscription already exists.
Either modify the new subscription properties to distinguish it from the existing subscription or deregister the existing subscription. Then reissue the command.
The subscription name parameter is in error.
Either the subscription name is of an invalid format or a matching subscription already exists with no subscription name.
Either correct the subscription name or remove it from the command and reissue the command.
The subscription identity parameter is in error.
Either the supplied value exceeds the maximum length allowed or the subscription identity is not currently a member of the subscription's identity set and a Join registration option was not specified.
Either correct the identity value or specify a Join registration option to add this identity to the identity set for this subscription.
The subscription is in use.
An attempt to modify or deregister a subscription was attempted by a member of the identity set when they were not the only member of this set.
Reissue the command when you are the only member of the identity set. To avoid the identity set check and force the modification or deregistration remove the subscription identity from the command message and reissue the command.
The subscription is locked.
The subscription is currently exclusively locked by another identity.
Wait for this identity to release the exclusive lock.
The identity already has an entry for this subscription.
A Join registration option was specified but the subscriber identity was already a member of the subscription's identity set.
None. The command completed, this reason code is a warning.
Object in use by another command.
A modification of an object was attempted while the object was being modified by another command.
Retry the command.
File not defined to CICS.
A file name parameter identifies a file that is not defined to CICS.
Provide a valid file name or create a CSD definition for the required file.
File not available to CICS.
A file name parameter identifies a file that is defined to CICS, but is not available.
Check that the CSD definition for the file is correct and enabled.
Disconnection retry count not valid.
The DiscRetryCount value was not valid.
Specify a valid count.
Allocation retry count not valid.
The AllocRetryCount value was not valid.
Specify a valid count.
Allocation slow retry timer value not valid.
The AllocRetrySlowTimer value was not valid.
Specify a valid timer value.
Allocation fast retry timer value not valid.
The AllocRetryFastTimer value was not valid.
Specify a valid value.
Port number value not valid.
The PortNumber value was not valid.
Specify a valid port number value.
Channel system is not active.
An attempt was made to start a channel while the channel system was inactive.
Activate the channel system before starting a channel.
Entity name required but missing.
A parameter specifying entity names must be supplied.
Specify the required parameter.
Profile name not valid.
A profile name is not valid. Profile names may include wildcard characters or may be given explicitly. If you give an explicit profile name, then the object identified by the profile name must exist. This error may also occur if you specify more than one double asterisk in a profile name.
Specify a valid name.
Authorization value not valid.
A value for the AuthorizationList or AuthorityRemove or AuthorityAdd parameter was not valid.
Specify a valid value.
Authorization value required but missing.
A parameter specifying authorization values must be supplied.
Specify the required parameter.
Object type value required but missing.
A parameter specifying the object type must be supplied.
Specify the required parameter.
Error in connection id parameter.
The ConnectionId specified was not valid.
Specify a valid connection id.
Log type not valid.
The log type value specified was not valid.
Specify a valid log type value.
Program not available.
A request to start or stop a service failed because the request to start the program failed. This could be because the program could not be found at the specified location, or that insufficient system resources are available currently to start it.
Check that the correct name is specified in the definition of the service, and that the program is in the appropriate libraries, before retrying the request.
Program not available.
A request to start or stop a service failed because the user does not have sufficient access authority to start the program at the specified location.
Correct the progam name and location, and the user's authority, before retrying the request.
No items found matching request criteria.
An Inquire command found no items that matched the specified name and satisfied any other criteria requested.
Security refresh or reverification not processed, security switch set OFF.
Either
The switch in question may be returned in the message (with parameter identifier MQIACF_SECURITY_SWITCH).
Security refresh did not take place.
A SAF RACROUTE REQUEST=STAT call to your external security manager (ESM) returned a non-zero return code. In consequence, the requested security refresh could not be done. The security item affected may be returned in the message (with parameter identifier MQIACF_SECURITY_ITEM).
Possible causes of this problem are:
For information about resolving the problem, see the explanations of messages CSQH003I and CSQH004I.
Incompatible parameters or parameter values.
The parameters or parameter values for a command are incompatible. One of the following occurred:
The parameters in question may be returned in the message (with parameter identifiers MQIACF_PARAMETER_ID).
Reissue the command with correct parameters and values.
Commands not allowed at present time.
The queue manager cannot accept commands at the present time, because it is restarting or terminating, or because the command server is not running.
Object is being deleted.
The object specified on a command is in the process of being deleted, so the command is ignored.
Storage class is active or queue is in use.
The command for a local queue involved a change to the StorageClass value, but there are messages on the queue, or other threads have the queue open.
Remove the messages from the queue, or wait until any other threads have closed the queue.
Incompatible object name and type.
The command used a reserved object name with an incorrect object type or subtype. The object is only allowed to be of a predetermined type, as listed in the explanation of message CSQM108I.
Local queue limit exceeded.
The command failed because no more local queues could be defined. There is an implementation limit of 524 287 for the total number of local queues that can exist. For shared queues, there is a limit of 512 queues in a single coupling facility structure.
Delete any existing queues that are no longer required.
Object is in use, but could be changed specifying Force as MQFC_YES.
The object specified is in use. This could be because it is open through the API, or for certain parameter changes, because there are messages currently on the queue. The requested changes can be made by specifying Force as MQFC_YES on a Change command.
Wait until the object is not in use. Alternatively specify Force as MQFC_YES for a change command.
Parameters are incompatible with disposition.
The parameters or parameter values for a command are incompatible with the disposition of an object. One of the following occurred:
The parameter and disposition in question may be returned in the message (with parameter identifiers MQIACF_PARAMETER_ID and MQIA_QSG_DISP).
Reissue the command with correct parameters and values.
Queue manager is not in a queue-sharing group.
The command or its parameters are not allowed when the queue manager is not in a queue-sharing group. The parameter in question may be returned in the message (with parameter identifier MQIACF_PARAMETER_ID).
Reissue the command correctly.
Parameter value cannot be changed.
The value for a parameter cannot be changed. The parameter in question may be returned in the message (with parameter identifier MQIACF_PARAMETER_ID).
To change the parameter, the object must be deleted and then created again with the new value.
Namelist is empty or wrong type.
A namelist used to specify a list of clusters has no names in it or does not have type MQNT_CLUSTER or MQNT_NONE.
Reissue the command specifying a namelist that is not empty and has a suitable type.
Channel initiator not active.
The command requires the channel initiator to be started.
Channel initiator cannot be started, or no suitable channel initiator is available.
One of the following:
Incompatible queue manager command levels.
Changing the CFLevel parameter of a CF structure, or deleting a CF structure, requires that all queue managers in the queue-sharing group have a command level of at least 530. Some of the queue managers have a lower level.
Queue attributes are incompatible.
The queues involved in a Move Queue command have different values for one or more of these attributes: DefinitionType, HardenGetBackout, Usage. Messages cannot be moved safely if these attributes differ.
Events not enabled.
The command required performance or configuration events to be enabled.
Use the Change Queue manager command to enable the events if required.
Queue-sharing group error.
While processing a command that used the CommandScope parameter, an error occurred while trying to send data to the coupling facility.
Notify your system programmer.
Error saving command reply information.
While processing a command that used the CommandScope parameter, or a command for the channel initiator, an error occurred while trying to save information about the command.
The most likely cause is insufficient storage. If the problem persists, you may need to restart the queue manager after making more storage available.
Restricted command or parameter value used.
The command, or the value specified for one of its parameters, is not allowed because the installation and customization options chosen do not allow all functions to be used. The parameter in question may be returned in the message (with parameter identifier MQIACF_PARAMETER_ID).
Required parameter not specified.
The command did not specify a parameter or parameter value that was required. It may be:
The parameter in question may be returned in the message (with parameter identifier MQIACF_PARAMETER_ID).
Reissue the command with correct parameters and values.
Parameter value invalid.
The value specified for a parameter was not acceptable. It may be:
The parameter in question may be returned in the message (with parameter identifier MQIACF_PARAMETER_ID).
Reissue the command with correct parameters and values.
Command exceeds allowable length.
The command is so large that its internal form has exceeded the maximum length allowed. The size of the internal form of the command is affected by both the length, and the complexity of the command.
Command issued incorrectly.
The command cannot be issued using command server. This is an internal error.
Notify your system programmer.
Address conflict for listener.
A listener was already active for a port and IP address combination that conflicted with the Port and IPAddress values specified by a Start Channel Listener or Stop Channel Listener command. The Port and IPAddress value combination specified must match a combination for which the listener is active. It cannot be a superset or a subset of that combination.
Reissue the command with correct values, if required.
Listener is started.
An attempt was made to start a listener, but it is already active for the requested TransportType, InboundDisposition, Port, and IPAddress values. The requested parameter values may be returned in the message, if applicable (with parameter identifiers MQIACH_XMIT_PROTOCOL_TYPE, MQIACH_INBOUND_DISP, MQIACH_PORT_NUMBER, MQCACH_IP_ADDRESS).
Listener is stopped.
An attempt was made to stop a listener, but it is not active or already stopping for the requested TransportType, InboundDisposition, Port, and IPAddress values. The requested parameter values may be returned in the message, if applicable (with parameter identifiers MQIACH_XMIT_PROTOCOL_TYPE, MQIACH_INBOUND_DISP, MQIACH_PORT_NUMBER, MQCACH_IP_ADDRESS).
Channel command failed.
A channel command failed because of an error in the channel definition, or at the remote end of the channel, or in the communications system. An error identifier value nnn may be returned in the message (with parameter identifier MQIACF_ERROR_ID).
For information about the error, see the explanation of the corresponding error message. Error nnn generally corresponds to message CSQXnnn, although there are some exceptions. The section Distributed queuing message codes in the WebSphere MQ for z/OS Messages and Codes book gives full details.
CF structure error.
A command could not be processed because of a coupling facility or CF structure error. It may be:
In the case of a Backup CF Structure or Recover CF Structure command, take action appropriate to the CF struture status reported.
In other cases, check for error messages on the console log that might relate to the problem. Check whether the coupling facility structure has failed and check that DB2 is available.
User identifier not found.
A user identifier specified in a Reverify Security command was not valid because there was no entry found for it in the internal control table. This could be because the identifier was entered incorrectly in the command, or because it was not in the table (for example, because it had timed-out). The user identifier in question may be returned in the message (with parameter identifier MQCACF_USER_IDENTIFIER).
Unexpected or severe error.
An unexpected or severe error or other failure occurred. A code associated with the error may be returned in the message (with parameter identifier MQIACF_ERROR_ID).
Notify your system programmer.
MQ is not connected to the XCF partner.
The command involving the IMS Bridge cannot be processed because MQ is not connected to the XCF partner. The group and member names of the XCF partner in question may be returned in the message (with parameter identifiers MQCA_XCF_GROUP_NAME and MQCA_XCF_MEMBER_NAME).
Parameter identifier is not valid.
The MQCFGR Parameter field value was not valid.
Specify a valid parameter identifier.
Structure length not valid.
The MQCFIF StrucLength field value was not valid.
Specify a valid structure length.
Parameter count not valid.
The MQCFIF Operator field value was not valid.
Specify a valid operator value.
Parameter identifier is not valid.
The MQCFIF Parameter field value was not valid, or specifies a parameter that cannot be filtered, or that is also specified as a parameter to select a subset of objects.
Specify a valid parameter identifier.
Filter value length not valid.
The MQCFSF FilterValueLength field value was not valid.
Specify a valid length.
Structure length not valid.
The MQCFSF StrucLength field value was not valid.
Specify a valid structure length.
Parameter count not valid.
The MQCFSF Operator field value was not valid.
Specify a valid operator value.
Parameter identifier is not valid.
The MQCFSF Parameter field value was not valid.
Specify a valid parameter identifier.
Too many filters.
The command contained more than the maximum permitted number of filter structures.
Specify the command correctly.
Listener is running.
An attempt was made to perform an operation on a listener, but it is currently active.
Stop the listener if required.
Listener status not found.
For Inquire Listener Status, no listener status is available for the specified listener. This may indicate that the listener has not been used.
None, unless this is unexpected, in which case consult your systems administrator.
Service is running.
An attempt was made to perform an operation on a service, but it is currently active.
Stop the service if required.
Service status not found.
For Inquire Service Status, no service status is available for the specified service. This may indicate that the service has not been used.
None, unless this is unexpected, in which case consult your systems administrator.
Service is stopped.
An attempt was made to stop a service, but it is not active or already stopping.
Duplicate parameter.
Two MQCFBS structures with the same parameter identifier were present.
Check for and remove duplicate parameters.
Structure length not valid.
The MQCFBS StrucLength field value was not valid.
Specify a valid structure length.
Parameter identifier is not valid.
The MQCFBS Parameter field value was not valid.
Specify a valid parameter identifier.
String length not valid.
The MQCFBS StringLength field value was not valid. The value was negative or greater than the maximum permitted length of the parameter specified in the Parameter field.
Specify a valid string length for the parameter.
Structure length not valid.
The MQCFGR StrucLength field value was not valid.
Specify a valid structure length.
Parameter count not valid.
The MQCFGR ParameterCount field value was not valid. The value was negative or greater than the maximum permitted for the parameter identifier specified in the Parameter field.
Specify a valid count for the parameter.
Connection not stopped.
The Stop Connection command could not be executed, so the connection was not stopped.
A Suspend or Resume Queue Manager command was issued, or a Refresh Security command, but such a command is currently in progress.
Wait until the current request completes, then reissue the command if necessary.
No start command.
The service cannot be started because no start command is specified in the service definition.
Correct the definition of the service.
No stop command.
The service cannot be stopped because no stop command is specified in the service definition.
Correct the definition of the service.
Structure length not valid.
The MQCFBF StrucLength field value was not valid.
Specify a valid structure length.
Parameter identifier is not valid.
The MQCFBF Parameter field value was not valid.
Specify a valid parameter identifier.
Filter value length not valid.
The MQCFBF FilterValueLength field value was not valid.
Specify a valid length.
Parameter count not valid.
The MQCFBF Operator field value was not valid.
Specify a valid operator value.
Listener still active.
An attempt mas made to stop a listener, but it failed and the listener is still active. For example, the the listener may still have active channels.
Wait for the active connections to the listener to complete before retrying the request.
Object already exists.
An attempt was made to create an object, but the object already existed and the Replace parameter was not specified as MQRP_YES.
Specify Replace as MQRP_YES, or use a different name for the object to be created.
Object has wrong type or disposition.
An object already exists with the same name but a different subtype or disposition from that specified by the command.
Ensure that the specified object is the same subtype and disposition.
New and existing objects have different subtype.
An attempt was made to create an object based on the definition of an existing object, but the new and existing objects had different subtypes.
Ensure that the new object has the same subtype as the one on which it is based.
Object is open.
An attempt was made to operate on an object that was in use.
Wait until the object is not in use, and then retry the operation. Alternatively specify Force as MQFC_YES for a change command.
Attribute value not valid or repeated.
One or more of the attribute values specified was not valid or was repeated. The error response message contains the failing attribute selectors (with parameter identifier MQIACF_PARAMETER_ID).
Specify the attribute values correctly.
Queue manager not known.
The queue manager specified was not known.
Specify the name of the queue manager to which the command is sent, or blank.
Action not valid for the queue of specified type.
An attempt was made to perform an action on a queue of the wrong type.
Specify a queue of the correct type.
Name not valid.
An object or other name name was specified using characters that were not valid.
Specify only valid characters for the name.
Allocation failed.
An attempt to allocate a conversation to a remote system failed. The error may be due to an entry in the channel definition that is not valid, or it might be that the listening program at the remote system is not running.
Ensure that the channel definition is correct, and start the listening program if necessary. If the error persists, consult your systems administrator.
Remote system not available.
An attempt to allocate a conversation to a remote system was unsuccessful. The error might be transitory, and the allocate might succeed later. This reason can occur if the listening program at the remote system is not running.
Ensure that the listening program is running, and retry the operation.
Configuration error.
There was a configuration error in the channel definition or communication subsystem, and allocation of a conversation was not possible. This might be caused by one of the following:
Identify the error and take appropriate action.
Connection refused.
The attempt to establish a connection to a remote system was rejected. The remote system might not be configured to allow a connection from this system.
Correct the error or restart the listener program.
Connection name not valid.
The connection name in the channel definition could not be resolved into a network address. Either the name server does not contain the entry, or the name server was not available.
Ensure that the connection name is correctly specified and that the name server is available.
Send failed.
An error occurred while sending data to a remote system. This might be caused by a communications failure.
Consult your systems administrator.
Received data error.
An error occurred while receiving data from a remote system. This might be caused by a communications failure.
Consult your systems administrator.
Receive failed.
The receive operation failed.
Correct the error and retry the operation.
Connection closed.
An error occurred while receiving data from a remote system. The connection to the remote system has unexpectedly terminated.
Contact your systems administrator.
Not enough storage available.
Insufficient storage is available.
Consult your systems administrator.
Communications manager not available.
The communications subsystem is not available.
Ensure that the communications subsystem has been started.
Listener not started.
The listener program could not be started. Either the communications subsystem has not been started, or the number of current channels using the communications subsystem is the maximum allowed, or there are too many jobs waiting in the queue.
Ensure the communications subsystem is started or retry the operation later. Increase the number of current channels allowed, if appropriate.
Bind failed.
The bind to a remote system during session negotiation has failed.
Consult your systems administrator.
Channel in-doubt.
The requested operation cannot complete because the channel is in doubt.
Examine the status of the channel, and either restart a channel to resolve the in-doubt state, or resolve the channel.
MQCONN call failed.
Check whether the queue manager is active.
MQOPEN call failed.
Check whether the queue manager is active, and the queues involved are correctly set up.
MQGET call failed.
Check whether the queue manager is active, and the queues involved are correctly set up, and enabled for MQGET.
MQPUT call failed.
Check whether the queue manager is active, and the queues involved are correctly set up, and not inhibited for puts.
Ping error.
A ping operation can only be issued for a sender or server channel. If the local channel is a receiver channel, you must issue the ping from a remote queue manager.
Reissue the ping request for a different channel of the correct type, or for a receiver channel from a different queue manager.
Channel in use.
An attempt was made to perform an operation on a channel, but the channel is currently active.
Stop the channel or wait for it to terminate.
Channel not found.
The channel specified does not exist.
Specify the name of a channel which exists.
Remote channel not known.
There is no definition of the referenced channel at the remote system.
Ensure that the local channel is correctly defined. If it is, add an appropriate channel definition at the remote system.
Remote queue manager not available.
The channel cannot be started because the remote queue manager is not available.
Start the remote queue manager.
Remote queue manager terminating.
The channel is ending because the remote queue manager is terminating.
Restart the remote queue manager.
MQINQ call failed.
Check whether the queue manager is active.
Queue is not a transmission queue.
The queue specified in the channel definition is not a transmission queue, or is in use.
Ensure that the queue is specified correctly in the channel definition, and that it is correctly defined to the queue manager.
Channel disabled.
An attempt was made to use a channel, but the channel was disabled (that is, stopped).
Start the channel.
User exit not available.
The channel was terminated because the user exit specified does not exist.
Ensure that the user exit is correctly specified and the program is available.
Commit failed.
An error was received when an attempt was made to commit a unit of work.
Consult your systems administrator.
Parameter not allowed for this channel type.
The parameter is not allowed for the type of channel being created, copied, or changed. Refer to the description of the parameter in error to determine the types of channel for which the parameter is valid
Remove the parameter.
Channel already exists.
An attempt was made to create a channel but the channel already existed and Replace was not specified as MQRP_YES.
Specify Replace as MQRP_YES or use a different name for the channel to be created.
Data too large.
The data to be sent exceeds the maximum that can be supported for the command.
Reduce the size of the data.
Channel name error.
The ChannelName parameter contained characters that are not allowed for channel names.
Specify a valid name.
Transmission queue name error.
The XmitQName parameter contains characters that are not allowed for queue names. This reason code also occurs if the parameter is not present when a sender or server channel is being created, and no default value is available.
Specify a valid name, or add the parameter.
Message channel agent name error.
The MCAName value contained characters that are not allowed for program names on the platform in question.
Specify a valid name.
Channel send exit name error.
The SendExit value contained characters that are not allowed for program names on the platform in question.
Specify a valid name.
Channel security exit name error.
The SecurityExit value contained characters that are not allowed for program names on the platform in question.
Specify a valid name.
Channel message exit name error.
The MsgExit value contained characters that are not allowed for program names on the platform in question.
Specify a valid name.
Channel receive exit name error.
The ReceiveExit value contained characters that are not allowed for program names on the platform in question.
Specify a valid name.
Transmission queue name not allowed for this channel type.
The XmitQName parameter is only allowed for sender or server channel types.
Remove the parameter.
Message channel agent name not allowed for this channel type.
The MCAName parameter is only allowed for sender, server or requester channel types.
Remove the parameter.
Disconnection interval not allowed for this channel type.
The DiscInterval parameter is only allowed for sender or server channel types.
Remove the parameter.
Short retry parameter not allowed for this channel type.
The ShortRetryCount parameter is only allowed for sender or server channel types.
Remove the parameter.
Short timer parameter not allowed for this channel type.
The ShortRetryInterval parameter is only allowed for sender or server channel types.
Remove the parameter.
Long retry parameter not allowed for this channel type.
The LongRetryCount parameter is only allowed for sender or server channel types.
Remove the parameter.
Long timer parameter not allowed for this channel type.
The LongRetryInterval parameter is only allowed for sender or server channel types.
Remove the parameter.
Put authority parameter not allowed for this channel type.
The PutAuthority parameter is only allowed for receiver or requester channel types.
Remove the parameter.
Connection name parameter required but missing.
The ConnectionName parameter is required for sender or requester channel types, but is not present.
Add the parameter.
Error in connection name parameter.
The ConnectionName parameter contains one or more blanks at the start of the name.
Specify a valid connection name.
MQSET call failed.
Check whether the queue manager is active.
Channel not active.
An attempt was made to stop a channel, but the channel was already stopped.
No action is required.
Channel terminated by security exit.
A channel security exit terminated the channel.
Check that the channel is attempting to connect to the correct queue manager, and if so that the security exit is specified correctly, and is working correctly, at both ends.
Dynamic queue scope error.
The Scope attribute of the queue is to be MQSCO_CELL, but this is not allowed for a dynamic queue.
Predefine the queue if it is to have cell scope.
Cell directory is not available.
The Scope attribute of the queue is to be MQSCO_CELL, but no name service supporting a cell directory has been configured.
Configure the queue manager with a suitable name service.
Message retry count not valid.
The MsgRetryCount value was not valid.
Specify a value in the range 0-999 999 999.
Message-retry count parameter not allowed for this channel type.
The MsgRetryCount parameter is allowed only for receiver and requester channels.
Remove the parameter.
Channel message-retry exit name error.
The MsgRetryExit value contained characters that are not allowed for program names on the platform in question.
Specify a valid name.
Message-retry exit parameter not allowed for this channel type.
The MsgRetryExit parameter is allowed only for receiver and requester channels.
Remove the parameter.
Message retry interval not valid.
The MsgRetryInterval value was not valid.
Specify a value in the range 0-999 999 999.
Message-retry interval parameter not allowed for this channel type.
The MsgRetryInterval parameter is allowed only for receiver and requester channels.
Remove the parameter.
Nonpersistent message speed not valid.
The NonPersistentMsgSpeed value was not valid.
Specify MQNPMS_NORMAL or MQNPMS_FAST.
Nonpersistent message speed parameter not allowed for this channel type.
The NonPersistentMsgSpeed parameter is allowed only for sender, receiver, server, requester, cluster sender, and cluster receiver channels.
Remove the parameter.
Heartbeat interval not valid.
The HeartbeatInterval value was not valid.
Specify a value in the range 0-999 999.
Heartbeat interval parameter not allowed for this channel type.
The HeartbeatInterval parameter is allowed only for receiver and requester channels.
Remove the parameter.
Channel automatic definition error.
The ChannelAutoDef value was not valid.
Specify MQCHAD_ENABLED or MQCHAD_DISABLED.
Channel automatic definition parameter not allowed for this channel type.
The ChannelAutoDef parameter is allowed only for receiver and server-connection channels.
Remove the parameter.
Channel automatic definition event error.
The ChannelAutoDefEvent value was not valid.
Specify MQEVR_ENABLED or MQEVR_DISABLED.
Channel automatic definition event parameter not allowed for this channel type.
The ChannelAutoDefEvent parameter is allowed only for receiver and server-connection channels.
Remove the parameter.
Channel automatic definition exit name error.
The ChannelAutoDefExit value contained characters that are not allowed for program names on the platform in question.
Specify a valid name.
Channel automatic definition exit parameter not allowed for this channel type.
The ChannelAutoDefExit parameter is allowed only for receiver and server-connection channels.
Remove the parameter.
Action suppressed by exit program.
An attempt was made to define a channel automatically, but this was inhibited by the channel automatic definition exit. The AuxErrorDataInt1 parameter contains the feedback code from the exit indicating why it inhibited the channel definition.
Examine the value of the AuxErrorDataInt1 parameter, and take any action that is appropriate.
Batch interval not valid.
The batch interval specified was not valid.
Specify a valid batch interval value.
Batch interval parameter not allowed for this channel type.
The BatchInterval parameter is allowed only for sender and server channels.
Remove the parameter.
Network priority value is not valid.
Specify a valid value.
Network priority parameter not allowed for this channel type.
The NetworkPriority parameter is allowed for sender and server channels only.
Remove the parameter.
Channel closed.
The channel was closed prematurely. This can occur because a user stopped the channel while it was running, or a channel exit decided to close the channel.
Determine the reason that the channel was closed prematurely. Restart the channel if required.
SSL cipher specification not valid.
The SSLCipherSpec specified is not valid.
Specify a valid cipher specification.
SSL peer name not valid.
The SSLPeerName specified is not valid.
Specify a valid peer name.
SSL client authentication not valid.
The SSLClientAuth specified is not valid.
Specify a valid client authentication.
Retained messages used on restricted stream.
An attempt has been made to use retained messages on a publish/subscribe stream defined to be restricted to JMS usage. JMS does not support the concept of retained messages and the request is rejected.
Either modify the application not to use retained messages, or modify the broker JmsStreamPrefix configuration parameter so that this stream is not treated as a JMS stream.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
csq05pcf2 |