Subsystem support messages (CSQ3...)

An online routine was still supporting SSI calls (IEFSSREQ) even though the queue manager had nearly completed termination or was no longer executing. This occurs with csect-name CSQ3RS00 or CSQ3RS0X when the queue manager address space has reached end-of-memory and neither normal termination nor online error recovery routines have successfully completed termination of the queue manager. This occurs with csect-name CSQ3SSTM when this condition is discovered during online termination.

The connection is terminated. All IEFSSREQ requests are handled by the IBM® MQ early processing program until the queue manager is restarted. An SVC dump is requested.

There might be IBM MQ units of recovery (URs), related to an identified subsystem (connection-name), still in doubt after restart synchronization has taken place. (Indoubt URs are those for which commit has been voted by IBM MQ but which have not yet been acknowledged by connection-name.)

This message might appear if the connection-name subsystem has begun to do new work before having resolved all in-doubt URs. The connection-name subsystem is still in the process of resolving the in-doubt URs.

Resources held (locked) by these in-doubt URs are unavailable to any other work units until their status is resolved.

The system programmer or system administrator must determine the correct recovery action to resolve the in-doubt situations. This involves either ensure-commit or backout decisions for all in-doubt URs.

The DISPLAY THREAD command should be used to see the URs still in doubt. It will normally show that all in-doubt URs have now been resolved. If not, the RESOLVE INDOUBT command should be used to resolve the in-doubt URs and to release the resources they hold.

An internal error has occurred during initialization or termination.

The queue manager terminates.

Ensure that all maintenance has been applied to the IBM MQ program libraries, and then restart the queue manager.

An initialization sequence error has occurred.

The queue manager terminates.

Ensure that all maintenance has been applied to the IBM MQ program libraries, and then restart the queue manager.

A termination sequence error has occurred.

Termination continues.

Ensure that all maintenance has been applied to the IBM MQ program libraries.

One or more resource managers are still supporting application program calls through their program request handler, even though the queue manager had almost completed termination, or was no longer executing. This occurs when the queue manager address space has gone to end of memory and neither normal termination nor online error recovery routines have successfully completed termination.

The connection is terminated. All application program support requests are rejected with an indication that the queue manager is not active. An SVC dump is requested.

An internal error has occurred in RRS exit processing. The message contains error information that will be needed to resolve the problem.

Processing continues, but RRS coordination is no longer available to the queue manager. It will probably be necessary to restart the queue manager or RRS.

IBM MQ has participant responsibility for in-doubt threads. RRS, the commit coordinator, has informed the queue manager that it lost all knowledge of IBM MQ in-doubt threads. The in-doubt threads at this queue manager must be manually resolved with the RESOLVE INDOUBT command.

Processing continues.

A list of in-doubt threads where RRS is the coordinator can be displayed using the DISPLAY THREAD command for in-doubt type threads by specifying RRSBATCH as the connection name.

The decision to commit or back out the logical unit of work should be coordinated with any other participant RRS Recoverable Resource Managers. The existence of other participants might not be easy to determine. The information might be available in the RRS recovery log even though information has been lost.

At this queue manager, all in-doubt threads coordinated by RRS must be resolved with the RESOLVE INDOUBT command. Locked data remains unavailable until resolution. Threads that were already resolved with this command are discarded. Threads not yet resolved are discarded after resolution with the command.

The commit or back out decision provided using the RESOLVE INDOUBT command for a logical unit of work is propagated to all downstream participants, if any.

The queue manager has one or more in-doubt threads and is unable to connect to RRS to resolve these in-doubt units of recovery (URs).

Processing continues.

The queue manager is restarting with RRS where IBM MQ is a participant and RRS is the coordinator. RRS has a unit of recovery (UR) that the queue manager should be a participant in, but it has no knowledge of the RRS unit of recovery, with an ID of rrs-urid. RRS has recorded the IBM MQ URID as mq-urid.

Restart with RRS continues.

If the mq-urid appears to be a valid log RBA, use the log print utility (CSQ1LOGP) with the SUMMARY option and URID options using the mq-urid value. If this finds the UR, the disposition will indicate whether it was committed or backed out. If possible, use the RRS ISPF interface to commit or back out the RRS URID so that they match.

If you suspect an error in IBM MQ, collect the items listed in the Problem Determination section and contact your IBM support center.

The queue manager is restarting with RRS and RRS has lost some portion of its log.

Restart with RRS continues.

IBM MQ might not be able to resolve in-doubt units of recovery successfully with RRS because of the loss of RRS log data.

During queue manager restart, the RRS function specified by call-name issued a return code rc indicating a failure.

Processing continues, but RRS functions will not be available. For example, connections using the RRS adapter will not be allowed, and queue-sharing group facilities will not work.

Investigate the RRS return code from the function specified and resolve the problem. Then restart the queue manager.

The queue manager has completed synchronization processing with RRS, and RRS functions are available.

None.

None.

The queue manager has terminated, and can be restarted when required.

The z/OS® command SETSSI ADD or the subsystem definition record in the IEFSSNxx member of SYS1.PARMLIB for the IBM MQ subsystem specified the early processing initialization parameter incorrectly. The name must be CSQ3EPX.

The failing subsystem name is provided in message IEF759I, which follows this message.

The IBM MQ subsystem with the indicated name is not available.

Correct the parameter fields in the record of SYS1.PARMLIB member IEFSSNxx. For information about the parameters, see Update SYS1.PARMLIB members.

The z/OS command SETSSI ADD or the subsystem definition record in the IEFSSNxx member of SYS1.PARMLIB for the IBM MQ subsystem specified the command prefix initialization parameter incorrectly.

The failing subsystem name is provided in message IEF759I, which follows this message.

The IBM MQ subsystem with the indicated name is not available.

Correct the parameter fields in the record of SYS1.PARMLIB member IEFSSNxx. For information about the parameters, see Update SYS1.PARMLIB members.

The queue manager has terminated. The actual z/OS termination of the queue manager address spaces might have completed earlier. This message is presented for every termination, normal or abnormal.

Subsystem initialization or early processing refreshing for the IBM MQ subsystem failed because the initialization program (CSQ3INI) could not locate the early processing program (CSQ3EPX).

For subsystem initialization, the program must be either in the linkpack area (LPA) or in a library which is in the link list. For early processing refreshing, the program must be in the LPA.

Subsystem initialization or early processing refreshing ends abnormally. IBM MQ subsystem ssnm is not available.

The command is not processed.

A command was received from a console that does not have the correct authority.

The command is not processed. This message is sent to the console that entered the command.

Verify that this console should be used for entering IBM MQ commands. If so, authorize it for IBM MQ commands by using z/OS services.

A command was received, but the path from z/OS consoles to the IBM MQ command processor is unavailable. It might still be possible to enter commands in other ways. You can also receive this message if the early code for the queue manager was being refreshed when the command was issued.

The command is not processed. This message is delivered to the console that entered the command.

The console command facility is available again the next time the queue manager is started.

If the command was rejected because the early code for the queue manager was being refreshed when you issued it, wait until message CSQ3110I is issued to indicate that the early code has successfully refreshed before you issue the command again.

IBM MQ was unable to obtain a subsystem affinity table index for the named subsystem. z/OS did not recognize the named subsystem name as a known subsystem. If this message is issued, a serious error has occurred in z/OS or IBM MQ.

In the message, nn is the return code from the IEFSSREQ z/OS service. ssnm is the name of the IBM MQ subsystem undergoing IPL-time initialization.

IBM MQ ends abnormally with completion code X'5C6' and reason code X'00F30104'. The IBM MQ subsystem with the indicated name is not available for this IPL of z/OS.

Try to perform an IPL of the z/OS system. If the problem persists, see Problem determination on z/OS for information about identifying and reporting the problem.

This message shows the level of the early processing program that is being used.

The level is of the form nnn-mmm and indicates the capability of the early code.

nnn is incremented for each new release of the product and mmm can be incremented from time to time when PTFs add maintenance to the early code.

The early code level used must have a capability level corresponding with the highest release of the product you intend to run on an LPAR. You can use the nnn value to confirm the level installed.

The z/OS command SETSSI ADD or the subsystem definition record in the IEFSSNxx member of SYS1.PARMLIB for the IBM MQ subsystem specified the CPF scope initialization parameter incorrectly.

The failing subsystem name is provided in message IEF759I, which follows this message.

The IBM MQ subsystem with the indicated name is not available.

Correct the parameter fields in the record of SYS1.PARMLIB member IEFSSNxx. For information about the parameters, see Update SYS1.PARMLIB members.

Command prefix registration failed because the command prefix (CPF) contains invalid characters.

The IBM MQ subsystem with the indicated name is not available.

Correct the CPF parameter in the record of SYS1.PARMLIB member IEFSSNxx. For information about the parameters, see Update SYS1.PARMLIB members.

Command prefix registration failed because the subsystem name used as the owner of the command prefix (CPF) contains invalid characters.

The IBM MQ subsystem with the indicated name is not available.

Correct the CPF parameter in the record of SYS1.PARMLIB member IEFSSNxx. For information about the parameters, see Update SYS1.PARMLIB members.

Command prefix registration failed because the command prefix (CPF) was already defined to z/OS.

The IBM MQ subsystem with the indicated name is not available.

Correct the CPF parameter in the record of SYS1.PARMLIB member IEFSSNxx. For information about the parameters, see Update SYS1.PARMLIB members.

Command prefix registration failed because the command prefix (CPF) is a subset of a CPF already defined to z/OS.

The IBM MQ subsystem with the indicated name is not available.

Correct the CPF parameter in the record of SYS1.PARMLIB member IEFSSNxx. For information about the parameters, see Update SYS1.PARMLIB members.

Command prefix registration failed because the command prefix (CPF) is a superset of a CPF already defined to z/OS.

The IBM MQ subsystem with the indicated name is not available.

Correct the CPF parameter in the record of SYS1.PARMLIB member IEFSSNxx. For information about the parameters, see Update SYS1.PARMLIB members.

A z/OS error occurred during command prefix (CPF) registration.

The MQ subsystem with the indicated name is not available.

Check the z/OS console for other messages relating to the problem.

During initialization for the group connect facility, a name token services call failed. rc is the return code (in hexadecimal) from the call.

Processing continues, but the group connect facility will not be available to CICS®.

See the MVS™ Authorized Assembler Services Reference manual for information about the return codes from the name token services call. If you are unable to solve the problem, take a stand-alone system dump and contact your IBM support center.

A CICS region with APPLID applid attempted to connect to a queue-sharing group. During processing of the request an IXCQUERY call failed with return code rc and reason code reason.

The XCF group for which the IXCQUERY request was performed is identified by group-name.

The request by CICS to connect to the queue-sharing group fails with the reason code MQRC_UNEXPECTED_ERROR.

See the z/OS MVS Sysplex Services Reference manual for an explanation of the IXCQUERY return and reason codes. If you are unable to solve the problem, contact your IBM support center.

Abnormal termination processing has been started for the agent with the values for the USER, CONNECTION-ID, THREAD-XREF, JOBNAME, ASID and TCB shown. These values are the last known set of identifiers for the terminating agent.

The abnormal termination might be the result of an error in the allied agent's address space or the result of the z/OS command CANCEL issued by the operator.

The value for the USER, the THREAD-XREF or both might be blank. The values for the USER, CONNECTION-ID, THREAD-XREF, JOBNAME and ASID are the last values established to IBM MQ for this connection and might represent the current activity of the agent. The TCB value is the address of the TCB that is terminating. Previous IBM MQ work by this agent might have completed successfully.

This message, CSQ3201E, is written to the z/OS console after the agent has been removed from the service task work queue at the time that termination processing begins.

The agent was previously queued to a service task for termination processing. This message indicates that the agent has been taken from the queue for processing. Any uncommitted changes will be backed out.

See the Problem Determination section of this message. The z/OS commands CANCEL and FORCE will have no effect. Do not cancel IBM MQ. If an extensive backout is in progress, the subsequent queue manager restart might take a very long time due to additional log activity.

jobname attempted to connect to IBM MQ using the MQCONN, or MQCONNX, API call.

There was insufficient common storage available to build the control blocks to represent the connection and to the connection attempt failed.

There might be a system wide ECSA shortage, or the storage available for creating new queue manager connections might be limited by the ACELIM system parameter.

This message can be seen for batch applications, including RRS applications; for example, Db2® stored procedures and WebSphere Application Server.

The MQCONN or MQCONNX API call, used by jobname returns MQCC_FAILED, together with reason code MQRC_Q_MGR_NOT_AVAILABLE 2059

Queue manager processing continues.

A nonzero return code has been returned to CSQ3AMI2 from the connect to subsystem interface (SSI) call. The variables in the message indicate which SSI call is involved and the actual return and reason codes associated with it.

The current task is ended abnormally with a system completion code of X'5C6' and a reason code of X'00F30580'. The queue manager terminates.

Restart the queue manager. Note the values contained in the message, and contact your IBM support center.