Subsystem support messages (CSQ3...)

 

CSQ3001E
csect-name - ABNORMAL DISCONNECT FROM SUBSYSTEM INTERFACE
Explanation:

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.

System Action:

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

Problem Determination:

Collect the following items, and contact your IBM support center:

  • System dump

  • Printout of SYS1.LOGREC

CSQ3002I
INDOUBT RECOVERY BY connection-name STILL IN PROGRESS
Explanation:

There might be 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 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.

System Action:

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

System Programmer Response:

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.

Problem Determination:

This error is probably caused by a cold start after an abnormal termination or by offline alterations of the logs of either MQ or the subsystem.

CSQ3004E
SSI DESCRIPTOR GET FAILURE, RC=rc REASON=reason
Explanation:

An internal error has occurred during initialization or termination.

System Action:

The queue manager terminates.

System Programmer Response:

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

Problem Determination:

If the problem persists, collect the following items, and contact your IBM support center:

  • Console log

  • System dump

CSQ3006E
'rmid' SSI FUNCTION WAS ALREADY ACTIVE WHEN ACTIVATE WAS ATTEMPTED
Explanation:

An initialization sequence error has occurred.

System Action:

The queue manager terminates.

System Programmer Response:

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

Problem Determination:

If the problem persists, collect the following items, and contact your IBM support center:

  • Console log

  • System dump

CSQ3007E
'rmid' SSI FUNCTION WAS ALREADY INACTIVE WHEN DEACTIVATE WAS ATTEMPTED
Explanation:

A termination sequence error has occurred.

System Action:

Termination continues.

System Programmer Response:

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

Problem Determination:

If the problem persists, collect the following items, and contact your IBM support center:

  • Console log

  • System dump

CSQ3008E
csect-name - ABNORMAL DISCONNECT FOR PROGRAM REQUEST HANDLER(S)
Explanation:

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.

System Action:

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.

System Programmer Response:

If the problem persists, collect the following items, and contact your IBM support center:

  • System dump

  • Printout of SYS1.LOGREC

CSQ3009E
error-info
Explanation:

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

System Action:

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.

Problem Determination:

Collect the following diagnostic items and contact your IBM support center:

  • A description of the actions that led to the message, or if applicable, a listing of the application program, or the input string to a utility program, being run at the time

  • The error information in the message

  • The queue manager job log

  • The queue manager active log data set

  • Any system dump output associated with the message

CSQ3011I
csect-name Coordinator RRS is cold-starting and has lost its log. In-doubt MQ threads need manual resolution
Explanation:

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

System Action:

Processing continues.

System Programmer Response:

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.

CSQ3013I
csect-name Queue manager was restarted on the wrong system so cannot connect to RRS. There are unresolved URs where MQ is a participant
Explanation:

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).

System Action:

Processing continues.

Operator Response:

Start the queue manager on the correct system.

CSQ3014I
csect-name In-doubt RRS URID=rrs-urid is unknown to MQ. URID recorded for MQ by RRS=mq-urid
Explanation:

The queue manager is restarting with RRS where 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, whose ID is rrs-urid. RRS has recorded the MQ URID as mq-urid.

System Action:

Restart with RRS continues.

System Programmer Response:

This message might indicate a problem in MQ or RRS, or it might be produced because of one of the following prior actions:

  • A conditional restart was performed that resulted in the loss of part or all of the MQ log. This conditional restart might have happened at any time in the past.

  • The RESOLVE INDOUBT command was used to resolve the MQ UR with ID mq-urid.

If one of these occurred, the message can be ignored. If neither occurred, there might be a problem in MQ or RRS.

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 MQ, collect the items listed in the Problem Determination section and contact your IBM support center.

Problem Determination:

Collect the following diagnostic items:

  • The queue manager job log

  • The queue manager active log data set

CSQ3016I
csect-name RRS has lost data from its log
Explanation:

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

System Action:

Restart with RRS continues.

System Programmer Response:

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

CSQ3017I
csect-name RRS function call-name failed, RC=rc
Explanation:

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

System Action:

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.

System Programmer Response:

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

CSQ3100I
csect-name - SUBSYSTEM ssnm READY FOR START COMMAND
Explanation:

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

Operator Response:

Issue the START QMGR command when desired.

CSQ3101E
csect-name - INVALID EARLY PROCESSING PARAMETER
Explanation:

The z/OS command SETSSI ADD or the subsystem definition record in the IEFSSNxx member of SYS1.PARMLIB for the 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.

System Action:

The MQ subsystem with the indicated name is not available.

Operator Response:

If you are trying to add an MQ subsystem, reissue the z/OS command SETSSI ADD with the correct parameters. Otherwise, notify the system programmer.

System Programmer Response:

Correct the parameter fields in the record of SYS1.PARMLIB member IEFSSNxx. See the WebSphere MQ for z/OS System Setup Guide for information about the parameters.

CSQ3102E
csect-name - INVALID COMMAND PREFIX
Explanation:

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

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

System Action:

The MQ subsystem with the indicated name is not available.

Operator Response:

If you are trying to add an MQ subsystem, reissue the z/OS command SETSSI ADD with the correct parameters. Otherwise, notify the system programmer.

System Programmer Response:

Correct the parameter fields in the record of SYS1.PARMLIB member IEFSSNxx. See the WebSphere MQ for z/OS System Setup Guide for information about the

CSQ3104I
csect-name - TERMINATION COMPLETE
Explanation:

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.

CSQ3105E
csect-name - UNABLE TO LOAD EARLY PROCESSING PROGRAM 'CSQ3EPX'. ssnm IS NOT AVAILABLE
Explanation:

Subsystem initialization or early processing refreshing for the 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.

System Action:

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

Operator Response:

Use the z/OS command SETPROG LPA,ADD,... to load the CSQ3EPX program into the LPA. For subsystem initialization, reissue the z/OS command SETSSI ADD. For early processing refreshing, reissue the REFRESH QMGR TYPE(EARLY) command.

CSQ3106E
csect-name - QUEUE MANAGER STOPPED. COMMAND NOT PROCESSED - command-text
Explanation:

A command was received which cannot be processed due to one of the following:

  • The queue manager has not been started (this could be because the START QMGR command was not entered correctly)

  • The command was queued for processing while the queue manager was starting, but startup terminated with an error

  • The queue manager terminated before the command could be processed

System Action:

The command is not processed.

Operator Response:

Start the queue manager, then reenter the command.

CSQ3107E
csect-name - COMMAND REJECTED. REQUESTER NOT AUTHORIZED
Explanation:

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

System Action:

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

Operator Response:

Enter the command from another console that has the correct authority.

System Programmer Response:

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

Note:
If MQ security is not activated, this check is still performed. This authorization is the z/OS console authority, and is not related to the external security manager. The console that entered the MQ command must have the SYS, ALL, or MASTER console authority attribute.
CSQ3108E
csect-name - COMMAND REJECTED. COMMAND FACILITY PATH UNAVAILABLE
Explanation:

A command was received, but the path from z/OS consoles to the MQ command processor is unavailable. It might still be possible to enter commands in other ways.

System Action:

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

System Programmer Response:

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

CSQ3109E
csect-name - UNABLE TO OBTAIN SUBSYSTEM AFFINITY TABLE INDEX FOR SUBSYSTEM ssnm. IEFSSREQ RC=nn
Explanation:

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 MQ.

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

System Action:

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

Operator Response:

Notify the system programmer.

System Programmer Response:

Try to re-IPL. If the problem persists, see the WebSphere MQ for z/OS Problem Determination Guide for information about reporting the problem.

Problem Determination:

A record is written to SYS1.LOGREC. No SVC dump is taken. Return codes from IEFSSREQ are documented in the MVS Authorized Assembler Services Guide manual.

CSQ3110I
csect-name - SUBSYSTEM ssnm INITIALIZATION COMPLETE
Explanation:

Either:

  • MQ subsystem initialization is complete, following z/OS IPL processing or the z/OS command SETSSI ADD.

  • The MQ early processing program has been successfully refreshed, following a REFRESH QMGR TYPE(EARLY) command.

Operator Response:

Issue the START QMGR command when desired.

CSQ3111I
csect-name - EARLY PROCESSING PROGRAM IS version LEVEL n
Explanation:

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

CSQ3112E
csect-name - INVALID CPF SCOPE
Explanation:

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

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

System Action:

The MQ subsystem with the indicated name is not available.

Operator Response:

If you are trying to add an MQ subsystem, reissue the z/OS command SETSSI ADD with the correct parameters. Otherwise, notify the system programmer.

System Programmer Response:

Correct the parameter fields in the record of SYS1.PARMLIB member IEFSSNxx. See the WebSphere MQ for z/OS System Setup Guide for information about the parameters.

CSQ3113E
csect-name - COMMAND PREFIX REGISTRATION FAILED. INVALID CHARACTER(S) IN CPF
Explanation:

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

System Action:

The MQ subsystem with the indicated name is not available.

Operator Response:

If you are trying to add an MQ subsystem, reissue the z/OS command SETSSI ADD with a correct CPF parameter. Otherwise, notify the system programmer.

System Programmer Response:

Correct the CPF parameter in the record of SYS1.PARMLIB member IEFSSNxx. See the WebSphere MQ for z/OS System Setup Guide for information about the parameters.

CSQ3114E
csect-name - COMMAND PREFIX REGISTRATION FAILED. INVALID CHARACTER(S) IN SUBSYSTEM NAME
Explanation:

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

System Action:

The MQ subsystem with the indicated name is not available.

Operator Response:

If you are trying to add an MQ subsystem, reissue the z/OS command SETSSI ADD with a correct CPF parameter. Otherwise, notify the system programmer.

System Programmer Response:

Correct the CPF parameter in the record of SYS1.PARMLIB member IEFSSNxx. See the WebSphere MQ for z/OS System Setup Guide for information about the parameters.

CSQ3115E
csect-name - COMMAND PREFIX REGISTRATION FAILED. CPF ALREADY DEFINED
Explanation:

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

System Action:

The MQ subsystem with the indicated name is not available.

Operator Response:

If you are trying to add an MQ subsystem, reissue the z/OS command SETSSI ADD with a correct CPF parameter. Otherwise, notify the system programmer.

System Programmer Response:

Correct the CPF parameter in the record of SYS1.PARMLIB member IEFSSNxx. See the WebSphere MQ for z/OS System Setup Guide for information about the parameters.

CSQ3116E
csect-name - COMMAND PREFIX REGISTRATION FAILED. CPF IS A SUBSET OF A CPF ALREADY DEFINED
Explanation:

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

System Action:

The MQ subsystem with the indicated name is not available.

Operator Response:

If you are trying to add an MQ subsystem, reissue the z/OS command SETSSI ADD with a correct CPF parameter. Otherwise, notify the system programmer.

System Programmer Response:

Correct the CPF parameter in the record of SYS1.PARMLIB member IEFSSNxx. See the WebSphere MQ for z/OS System Setup Guide for information about the parameters.

CSQ3117E
csect-name - COMMAND PREFIX REGISTRATION FAILED. CPF IS A SUPERSET OF A CPF ALREADY DEFINED
Explanation:

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

System Action:

The MQ subsystem with the indicated name is not available.

Operator Response:

If you are trying to add an MQ subsystem, reissue the z/OS command SETSSI ADD with a correct CPF parameter. Otherwise, notify the system programmer.

System Programmer Response:

Correct the CPF parameter in the record of SYS1.PARMLIB member IEFSSNxx. See the WebSphere MQ for z/OS System Setup Guide for information about the parameters.

CSQ3118E
csect-name - SYSTEM ERROR DURING COMMAND PREFIX REGISTRATION
Explanation:

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

System Action:

The MQ subsystem with the indicated name is not available.

System Programmer Response:

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

CSQ3201E
ABNORMAL EOT IN PROGRESS FOR USER=user CONNECTION-ID=conn-id THREAD-XREF=thread-xref
Explanation:

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

The abnormal termination could 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 and/or THREAD-XREF might be blank. The values for the USER, CONNECTION-ID, and THREAD-XREF are the last values established to MQ for this connection and might or might not represent the current activity of the agent. Previous 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.

System Action:

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.

Operator Response:

Notify your system programmer.

System Programmer Response:

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

Problem Determination:

We can detect a deferred termination condition for a task by examining several indicators. Some or all of the following might be present:

  • The allied address space might be swapped out and appear to be in a never-ending WAIT condition.

  • The z/OS commands CANCEL and FORCE appear to have no effect.

  • The allied task holds a z/OS-shared ENQ on resource SYSZCSQ3.ERLYOLRH.erly-block-address.

  • During abnormal termination of the agent associated with the task in error, the task's connection will appear on the MQ DISPLAY THREAD output with a QD status, prior to this message being written, or with a D status after this message is written and until the thread is resolved. See message CSQV402I for the definitions of these status codes.

  • IMS transactions running in regions connected to MQ may receive this message for non-MQ transactions.

CSQ3580E
CONNECTION FOR 'ssi-call' GAVE RC=rc, REASON=reason
Explanation:

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.

System Action:

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.

Operator Response:

Notify the system programmer.

System Programmer Response:

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