Initialization procedure and general services messages (CSQY...)

CSQY000I

IBM WebSphere MQ for z/OSversion

Explanation:

This message is issued when the queue manager starts, and shows the release level.

CSQY001I

QUEUE MANAGER STARTING, USING PARAMETER MODULE parm-name

Explanation:

The START QMGR command is accepted. System parameter values will be taken from the module parm-name. This message is issued to the z/OS console at which the START command was issued. Message CSQY022I is sent when the queue manager startup process has completed.

System Action:

Queue manager startup processing begins.

CSQY002I

QUEUE MANAGER STOPPING

Explanation:

The STOP QMGR command is accepted. Message CSQ9022I is issued when the queue manager shutdown process has completed. The message is issued either to the originator of the STOP QMGR command, or to the z/OS console from which the START QMGR command was received.

System Action:

Queue manager shutdown is initiated.

CSQY003I

QUEUE MANAGER IS ALREADY ACTIVE

Explanation:

The START QMGR command has not been accepted, because the queue manager is active. Message CSQ9023E is issued after this message.

CSQY004I

QUEUE MANAGER IS ALREADY STOPPING

Explanation:

The STOP QMGR command has not been accepted either because the queue manager shutdown is in progress for the specified option (QUIESCE or FORCE), or because the QUIESCE option was specified after a FORCE option had been accepted previously. Message CSQ9023E is issued after this message.

System Action:

Queue manager shutdown continues.

CSQY005E

QUEUE MANAGER STARTUP TERMINATED, INVALID START COMMAND

Explanation:

The queue manager can be started only by a START QMGR command.

System Action:

Queue manager startup is terminated.

Operator Response:

Start the queue manager using the START QMGR command, and reenter the rejected command.

CSQY006E

csect-name INVALID AMODE OR RMODE ATTRIBUTE FOUND FOR LOAD MODULE module-name

Explanation:

The queue manager initialization procedures found that a module had an invalid AMODE or RMODE attribute when it was loaded. module-name is the name of the load module with an invalid addressing or residency mode.

System Action:

Queue manager startup terminates abnormally.

Operator Response:

Notify the system programmer of the problem.

System Programmer Response:

Verify that all installation and maintenance activities against WebSphere MQ have been done correctly. If you are unable to correct the problem, contact your IBM support center.

CSQY008I

QUEUE MANAGER SHUTDOWN REQUEST NOT ACCEPTED

Explanation:

The STOP QMGR command has not been accepted because startup has not completed to the point where shutdown can occur. Message CSQ9023E is issued after this message.

System Action:

Queue manager startup continues, and the STOP QMGR command is ignored.

Operator Response:

Reissue the STOP QMGR command after startup has completed.

CSQY009I

verb-name pkw-name COMMAND ACCEPTED FROM USER(userid), STOP MODE(mode)

Explanation:

This message is issued to record who issued the command to stop WebSphere MQ, and what type of stop it was. verb-name might include the command prefix (CPF). This depends on how the command was entered.

CSQY010E

csect-name LOAD MODULE module name IS NOT AT THE CORRECT RELEASE LEVEL

Explanation:

The named load module is not at the correct level for the version of the queue manager that was being used.

System Action:

If detected by the queue manager, startup terminates abnormally with reason code X'00E80161'. If detected by the channel initiator (module-name is CSQXJST), it does not start.

Operator Response:

Notify the system programmer.

System Programmer Response:

Verify that the correct WebSphere MQ program libraries are being used (for the queue manager or channel initiator as appropriate) and that all installation and maintenance activities against WebSphere MQ have been done correctly. If the early processing program is incorrect (module-name is CSQ3EPX), refresh it by issuing the REFRESH QMGR TYPE(EARLY) command.

If you are unable to correct the problem, contact your IBM support center.

CSQY011E

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 queue manager does not start.

System Programmer Response:

Reissue the z/OS command SETSSI ADD with the correct CPF parameter. 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.

CSQY012E

csect-name COMMAND PREFIX REGISTRATION FAILED. INVALID CHARACTER(S) IN QUEUE MANAGER NAME

Explanation:

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

System Action:

The queue manager does not start.

System Programmer Response:

CSQY013E

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 queue manager does not start.

System Programmer Response:

CSQY014E

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 queue manager does not start.

System Programmer Response:

CSQY015E

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 queue manager does not start.

System Programmer Response:

CSQY016E

csect-name SYSTEM ERROR DURING COMMAND PREFIX REGISTRATION

Explanation:

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

System Action:

The queue manager does not start.

System Programmer Response:

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

CSQY017E

csect-name INCORRECT STORAGE PROTECT KEY

Explanation:

The queue manager initialization procedures found that the storage protect key was not 7. The most likely causes are that the program properties table (PPT) entry for CSQYASCP has not been specified correctly, or that the WebSphere MQ program libraries or other libraries in the WebSphere MQ STEPLIB are not APF authorized.

System Action:

Queue manager startup terminates abnormally with reason code X'00E80162'.

Operator Response:

Notify the system programmer.

System Programmer Response:

See the WebSphere MQ for z/OS System Setup Guide for information about specifying the PPT entry for CSQYASCP and about APF authorization for the WebSphere MQ program libraries.

CSQY018E

csect-name INCORRECT APF AUTHORIZATION

Explanation:

The queue manager initialization procedures found that they were not APF authorized. The most likely cause is that the WebSphere MQ program libraries are not APF authorized.

System Action:

Queue manager startup terminates abnormally with reason code X'00E80163'.

Operator Response:

Notify the system programmer.

System Programmer Response:

See the WebSphere MQ for z/OS System Setup Guide for information about APF authorization for the WebSphere MQ program libraries.

CSQY022I

QUEUE MANAGER INITIALIZATION COMPLETE

Explanation:

This message is issued when the initialization of the queue manager completes normally, and it is ready for use.

CSQY100I

csect-name SYSTEM parameters ...

Explanation:

The queue manager is being started with the system parameter values shown in the following messages.

System Action:

Queue manager startup processing continues.

CSQY101I, CSQY102I, CSQY103I, CSQY104I, CSQY105I, CSQY106I, CSQY107I, CSQY108I, CSQY109I

csect-name parms

Explanation:

This series of messages shows the system parameter values that the queue manager is using. (Some values are followed by their internal hexadecimal representation in parentheses.) See the CSQ6SYSP macro in the WebSphere MQ for z/OS System Setup Guide for information about the system parameters.

System Action:

Queue manager startup processing continues.

CSQY110I

csect-name LOG parameters ...

Explanation:

The queue manager is being started with the log parameter values shown in the following messages.

System Action:

Queue manager startup processing continues.

CSQY111I, CSQY112I, CSQY113I

csect-name parms

Explanation:

This series of messages shows the log parameter values that the queue manager is using. See the CSQ6LOGP macro in the WebSphere MQ for z/OS System Setup Guide for information about the log parameters.

System Action:

Queue manager startup processing continues.

CSQY120I

csect-name ARCHIVE parameters ...

Explanation:

The queue manager is being started with the archive parameter values shown in the following messages.

System Action:

Queue manager startup processing continues.

CSQY121I, CSQY122I, CSQY123I, CSQY124I

csect-name parms

Explanation:

This series of messages shows the archive parameter values that the queue manager is using. See the CSQ6ARVP macro in the WebSphere MQ for z/OS System Setup Guide for information about the archive parameters.

System Action:

Queue manager startup processing continues.

CSQY200E

csect-name ARM request-type for element arm-element type arm-element-type failed, rc=rc reason=reason

Explanation:

An ARM request (IXCARM REQUEST=request-type) for the specified element failed. rc is the return code and reason is the reason code (both in hexadecimal) from the call.

System Action:

None.

System Programmer Response:

See the z/OS MVS Programming Sysplex Services Reference manual for information about the return and reason codes from the IXCARM call. If you are unable to solve the problem, contact your IBM support center.

CSQY201I

csect-name ARM REGISTER for element arm-element type arm-element-type successful

Explanation:

The specified element was successfully registered with ARM.

System Action:

None.

CSQY202E

csect-name ARM registration failed

Explanation:

An attempt to register with ARM failed.

System Action:

Processing continues, but automatic restart is not available.

System Programmer Response:

See the preceding CSQY200E message for more information about the failure.

CSQY203E

csect-name ARM request-type for element arm-element type arm-element-type timed out, rc=rc reason=reason

Explanation:

An ARM request (IXCARM REQUEST=request-type) was issued but some predecessor element specified in the ARM policy did not issue an ARM READY request within its specified time interval.

System Action:

Processing continues.

System Programmer Response:

None required. However, if your program cannot run without the predecessor element, some installation-defined action might be necessary.

CSQY204I

csect-name ARM DEREGISTER for element arm-element type arm-element-type successful

Explanation:

The specified element was successfully deregistered from ARM.

System Action:

None.

CSQY205I

csect-name ARM element arm-element is not registered

Explanation:

A STOP QMGR command requested ARM restart, but the queue manager was not registered for ARM.

System Action:

The queue manager stops normally, but will not be automatically restarted.

System Programmer Response:

Restart the queue manager manually.

CSQY210E

csect-name call-name call for name name-token failed, rc=rc

Explanation:

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

System Action:

If the failure occurs in the batch adapter (csect-name CSQBCON or CSQBDSC), the application call will fail with a reason code of MQRC_UNEXPECTED_ERROR. Otherwise (csect-name CSQYGRA1), processing continues, but the group connect facility will not be available.

System Programmer Response:

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.

CSQY211I

csect-name Unable to add entry to group connect name table (at table-addr)

Explanation:

During initialization for the group connect facility, a new entry could not be added to the name table for this queue manager. The most likely cause is that there is already the maximum of 32 queue managers active in the group.

System Action:

Processing continues, but this queue manager will not be available for group connection.

System Programmer Response:

Reduce the number of active queue managers and restart this queue manager. If this does not solve the problem, contact your IBM support center.

CSQY220I

Queue manager is using mm MB of local storage, nn MB are free

Explanation:

Displays the amount of virtual storage currently used and available in the extended private region. Both values are displayed in megabytes (1048576 bytes), and are approximations.

System Action:

Processing continues. Any special actions taken by MQ or that are required will be indicated by the CSQY221I and CSQY222E messages.

System Programmer Response:

No action is required at this time. However, a frequent occurrence of this message may be an indication that the system is operating beyond the optimum region for the current configuation.

CSQY221I

Queue manager is short of local storage

Explanation:

The queue manager is running short of virtual storage in the extended private region.

System Action:

Processing continues. Storage contraction processing is performed, which attempts to remove unused storage from internal subpools so that it can be reused in other subpools. This might be necessary after a temporary need for lots of storage; for example, more than the usual number of messages held on an indexed queue, or an unusually large unit of work being performed.

System Programmer Response:

No action is required at this time. However, a frequent occurrence of this message may be an indication that the system is operating beyond the optimum region for the current configuation.

CSQY222E

Queue manager is critically short of local storage - take action

Explanation:

The queue manager is running critically short of virtual storage in the extended private region. Action should be taken to relieve the situation, and to avoid the possible abnormal termination of the queue manager.

System Action:

Processing continues. Storage contraction processing has been performed, but the remaining unallocated virtual storage is less than a predetermined safe amount. If storage use continues to increase, the queue manager may terminate abnormally in an unpredictable way.

System Programmer Response:

Virtual storage is over-allocated for the current configuration. The following actions can reduce the virtual storage requirement:

Reduce buffer pool sizes with the ALTER BUFFPOOL command. Buffer pool statistics may be used to determine buffer pools which are over-allocated.
Reduce the number of messages held on private queues which are indexed.
Remove units of work which hold large numbers of locks. These are units of work which have put or got lots of messages, or large messages.
Reduce the number of concurrent connections to the queue manager. The DISPLAY CONN command can be used to determine connections which are consuming queue manager resources.

If the problem persists after taking actions described above, it may be an indication of an internal error whereby storage is not freed (a 'storage leak'). If you suspect this, then collect at least two system dumps of the queue manager, separated by an interval of time, and contact your IBM support center.

CSQY223I

Queue manager is no longer short of local storage

Explanation:

The queue manager is no longer short of virtual storage in the extended private region.

System Action:

Processing continues. Storage contraction processing has been performed, and the remaining unallocated virtual storage is more than a predetermined safe amount.

CSQY270E

csect-name UNRECOGNIZED MESSAGE NUMBER message-id

Explanation:

An unsuccessful attempt has been made to issue the message message-id. This message is issued only if the requested message could not be found in the MQ message directory.

Severity:

System Action:

Processing continues as though the requested message had been issued.

Operator Response:

Notify the system programmer.

System Programmer Response:

Use the message number (message-id) and look up the message in this book. If you are using a language other than US English, ensure that you have installed the language feature correctly and that you have the appropriate load library data set concatenations in your job. Apart from that possibility, this is an MQ system problem; see the WebSphere MQ for z/OS Problem Determination Guide.

Note:

Messages are also used to provide text for constructing panels and reports. If such a message cannot be found, message CSQY270E will appear on the panel or report, generally in truncated form.

CSQY271I

MESSAGE GENERATOR INITIALIZATION PARAMETERS NOT FOUND. DEFAULTS ASSUMED

Explanation:

The message generator was unable to access the routing code initialization parameter defined by the CSQ6SYSP macro. Default values defined by that macro are assumed.

Severity:

System Action:

Queue manager initialization continues.

Operator Response:

Notify the system programmer.

System Programmer Response:

It might be necessary to change the CSQ6SYSP macro. See the WebSphere MQ for z/OS System Setup Guide for information about this macro.

CSQY290E

csect-name NO STORAGE AVAILABLE

Explanation:

There was insufficient storage available for a system routine. csect-name shows the system routine function:

CSQAXDPS, CSQVXDPS: User exits (other than channel)
CSQXARMY: Channel initiator automatic restart
CSQXDCTS, CSQXTRPG: Channel initiator trace
CSQXDMPS: Channel initiator system dump
CSQXLDXS: User channel exits
CSQ2GFRR, CSQ2MFRR: IMS bridge system dump

Severity:

System Action:

Processing continues, but the function provided by the system routine will be inhibited. For example, if the routine is CSQXLDXS, then user channel exits will not be available, and channels that use them will not start.

System Programmer Response:

If the problem occurs in the queue manager, increase the size of the its address space, or reduce the number of queues, messages, and threads being used.

If the problem occurs in the channel initiator, increase the size of the its address space, or reduce the number of dispatchers, adapter subtasks, SSL server subtasks, and active channels being used.

CSQY291E

csect-name SDUMPX FAILED, RC=0000ssrr, dump-identifier

Explanation:

The system dump routine was unable to issue a dump; the dump identifier was as shown in the message. rr is the return code and ss is the reason code (both in hexadecimal) from the z/OS SDUMPX service.

Severity:

System Action:

Processing continues.

System Programmer Response:

See the MVS Authorized Assembler Services Reference manual for information about the return code and reason code from the SDUMPX request.

CSQY330I

Queue manager has restricted functionality

Explanation:

The installation and customization options chosen for WebSphere MQ do not allow all functions to be used.

System Action:

Queue manager startup processing continues.

CSQY331E

parm value not allowed - restricted functionality

Explanation:

The value specified for the parm system parameter is not allowed because the installation and customization options chosen for WebSphere MQ do not allow all functions to be used.

System Action:

The queue manager does not start.

CSQY332I

IMS Bridge not available - restricted functionality

Explanation:

The MQ-IMS bridge cannot operate because the installation and customization options chosen for WebSphere MQ do not allow all functions to be used.

System Action:

The MQ-IMS bridge does not start.

CSQY333E

Command not allowed - restricted functionality

Explanation:

The command that was issued is not allowed because the installation and customization options chosen for WebSphere MQ do not allow all functions to be used.

System Action:

The command is ignored.

CSQY334E

csect-name keyword(value) not allowed - restricted functionality

Explanation:

The value specified for the keyword is not allowed because the installation and customization options chosen for WebSphere MQ do not allow all functions to be used.

System Action:

The command is ignored.

CSQY335E

csect-name Channel channel-name unusable - restricted functionality

Explanation:

The channel cannot be used because the installation and customization options chosen for WebSphere MQ do not allow all functions to be used.

System Action:

The requested operation fails.

CSQY340E

Queue manager has restricted functionality, but previously had full functionality. Unsupported objects will be deleted (losing messages), invalid attributes will be changed

Explanation:

The installation and customization options chosen for WebSphere MQ do not allow all functions to be used. However, the queue manager has run previously without any functional restriction, and so may have objects and attribute settings that are not allowed with the restricted functionality.

In order to continue, these objects must be deleted (which may mean messages are lost) and the attributes must be changed. The queue manager will do this automatically.

System Action:

Message CSQY341D is issued and the operator's reply is awaited.

System Programmer Response:

The operator has two options:

Allow the queue manager to delete the objects and change the attributes, by replying 'Y'.
Cancel the queue manager, by replying 'N'.

CSQY341D

Reply Y to continue or N to cancel

Explanation:

The installation and customization options chosen for WebSphere MQ have changed, as indicated in the preceding CSQY340E message.

System Action:

The queue manager waits for the operator's reply

System Programmer Response:

See message CSQY340E.

CSQY342I

Delete objects and changing attributes - restricted functionality

Explanation:

This message is sent if the operator answers 'Y' to message CSQY341D.

System Action:

The queue manager deletes the objects and changes the attributes that are not allowed with the restricted functionality.

CSQY343I

Queue manager terminating - restricted functionality not accepted

Explanation:

This message is sent if the operator answers 'N' to message CSQY341D.

System Action:

The queue manager does not start.