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

CSQY000I: IBM MQ for z/OS® Vn release_type
Explanation: This message is issued when the queue manager starts, and shows the release level and release type.

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.

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.
System programmer response: Verify that all installation and maintenance activities against IBM MQ have been done correctly. If you are unable to correct the problem, contact your IBM support center.

CSQY007E: csect-name QUEUE MANAGER STARTUP TERMINATED, INVALID OPERATING SYSTEM LEVEL
Explanation: The queue manager initialization procedures found that the level of the operating system did not have the function required for correct queue manager operation.
System action: Queue manager startup terminates abnormally.
System programmer response: Verify that the prerequisite, or later, level of the operating system is installed. 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.

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

If detected by the AMS enablement module (DRQ0NABL), the queue manager only fails to start if SPLCAP=YES is specified in the system parameters. In this case message CSQY029E is issued.

System programmer response

Verify that the correct IBM MQ program libraries are being used (for the queue manager or channel initiator as appropriate) and that all installation and maintenance activities againstIBM 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. For information about the parameters, see Updating the subsystem name table.

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: Reissue the z/OS command SETSSI ADD with the correct CPF parameter. Correct the CPF parameter in the record of SYS1.PARMLIB member IEFSSNxx. For information about the parameters, see Updating the subsystem name table.

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: Reissue the z/OS command SETSSI ADD with the correct CPF parameter. Correct the CPF parameter in the record of SYS1.PARMLIB member IEFSSNxx. For information about the parameters, see Updating the subsystem name table.

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: Reissue the z/OS command SETSSI ADD with the correct CPF parameter. Correct the CPF parameter in the record of SYS1.PARMLIB member IEFSSNxx. For information about the parameters, see Updating the subsystem name table.

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: Reissue the z/OS command SETSSI ADD with the correct CPF parameter. Correct the CPF parameter in the record of SYS1.PARMLIB member IEFSSNxx. For information about the parameters, see Updating the subsystem name table.

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 IBM MQ program libraries or other libraries in the IBM MQ STEPLIB are not APF authorized.

System action

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

System programmer response

Check that all the libraries you include in the IBM MQ STEPLIB have been APF-authorized. Also, ensure that we use the actual library name and not the data set alias of the libraries in APF list.

For information about specifying the PPT entry for CSQYASCP and about APF authorization for the IBM MQ program libraries, see Updating the z/OS program properties table.

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 one or more of the data sets in the //STEPLIB concatenation is not APF authorized.

System action

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

System programmer response

Check all the libraries that you include in the IBM MQ STEPLIB are APF-authorized. Also, check that we do not use a data set alias of the libraries in the APF list, use the actual library name instead.

For information about APF authorization for the IBM MQ program libraries, see APF authorize the IBM MQ load libraries.

CSQY019E

csect-name QUEUE MANAGER STARTUP TERMINATED, INVALID PARAMETER MODULE LEVEL, REBUILD macro-name

Explanation

The queue manager initialization procedures found that the level of the parameter module (named in the preceding CSQY001I message) is not at the correct level for this version of the queue manager.

This can occur when starting a queue manager at a Continuous Delivery (CD) release of IBM MQ, if the system parameter (ZPARM) module has not been updated at a CD release with the value of OPMODE set to OPMODE=(NEWFUNC,90x), where x is the modification number.

System action

Queue manager startup terminates abnormally with reason code 00E80051.

System programmer response

Rebuild the parameter module ensuring that macro-name is recompiled with the same level of code that the queue manager is running with.

Ensure that OPMODE is set to OPMODE=(NEWFUNC,90x), where x is the modification number, for a CD release.

For more information about the macros used to build the parameter module see, Task 17: Tailor your system parameter module.

CSQY020E: csect-name CHANNEL INITIATOR STARTUP TERMINATED, INVALID START COMMAND
Explanation: The channel initiator can be started only by a START CHINIT command.
System action: Channel initiator startup is terminated.
System programmer response: Start the channel initiator using the START CHINIT command

CSQY021E: csect-name QUEUE MANAGER STARTUP TERMINATED, INSUFFICIENT MEMLIMIT
Explanation: The queue manager initialization procedures found that the configured MEMLIMIT is less than 512MB.
System action: Queue manager startup terminates abnormally.

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.

CSQY023A

SOME OBJECTS COULD NOT BE MIGRATED, MANUAL RESOLUTION REQUIRED. REPLY TO ACKNOWLEDGE AND CONTINUE STARTUP

Explanation

The queue manager has detected that it was previously running at an earlier version and forward migration has been performed. However, some objects could not be migrated because of locks held by in-doubt transactions. Message CSQI970E is also issued for each object that could not be migrated.

This message is not issued during subsequent restarts of the queue manager whilst it is running at the same version.

System action

Startup is suspended and the queue manager waits for the operator to reply with any single character.

System programmer response

Reply to acknowledge this message and allow queue manager startup to proceed.

Thereafter, additional action is required to complete forward migration of each identified object.

For more information see the description of message CSQI970E.

CSQY024I: IBM MQ AMS for z/OS is not installed, but the system parameter SPLCAP is set to YES
Severity: 8
Explanation: The system parameter SPLCAP is set to YES in the queue manager's ZPARM, however, Advanced Message Security has not been installed.
System action: Queue manager startup is terminated.
System programmer response: If Advanced Message Security is required, ensure it has been installed correctly and the queue manager's STEPLIB has been updated to include SDRQAUTH, otherwise update the queue manager's ZPARM to set the system parameter SPLCAP to NO.

CSQY025I: IBM MQ AMS for z/OS is installed.
Severity: 0
Explanation: This message indicates that Advanced Message Security is installed.
System action: Queue manager startup continues.
System programmer response: None.

CSQY027I: csect-name AMS STARTING
Severity: 0
Explanation: The Advanced Message Security (AMS) address space has been started because the system parameter SPLCAP is set to YES in the queue manager's ZPARM.
System action: Connections to the queue manager are permitted, but MQI calls that might require AMS function are suspended until AMS is available. Further messages are output when the AMS feature initializes.

CSQY028I: csect-name AMS HAS STARTED
Severity: 0
Explanation: Advanced Message Security (AMS) initialization has completed successfully.
System action: Applications waiting for AMS function are resumed.

CSQY029E: csect-name QUEUE MANAGER STARTUP TERMINATED, AMS INITIALIZATION FAILED
Severity: 12
Explanation: A severe error occurred during initialization of Advanced Message Security (AMS).
System action: The queue manager abnormally terminates with abend code 6C6 and reason 00F00003.
System programmer response: Investigate the problem reported by preceding messages in the job log for the AMS address space (xxxxAMSM). Resolve the problem, then restart the queue manager. If you are unable to resolve the error, contact your IBM support center.

CSQY030E: csect-name QUEUE MANAGER TERMINATING, AMS NOT AVAILABLE
Severity: 12
Explanation: The Advanced Message Security (AMS) address space has ended abnormally due to an unrecoverable error.
System action: The queue manager abnormally terminates with abend code 6C6 and reason 00F00003.
System programmer response: Investigate the problem reported by preceding messages in the job log for the AMS address space (xxxxAMSM). Resolve the problem, then restart the queue manager. If you are unable to resolve the error, contact your IBM support center.

CSQY031I: csect-name QUEUE MANAGER WAITING FOR AMS INITIALIZATION
Severity: 0
Explanation: The Advanced Message Security (AMS) address space has been started because the system parameter SPLCAP is set to YES in the queue manager's ZPARM. This message is periodically issued until AMS initialization completes.
System action: Processing continues. Connections to the queue manager are permitted, but MQI requests that might require AMS function are suspended until AMS is available.
System programmer response: Investigate the delay in initializing Advanced Message Security by reviewing the messages output in the job log for the AMS address space (xxxxAMSM).

CSQY032E: csect-name QUEUE MANAGER STARTUP TERMINATED, UNABLE TO START AMS
Severity: 12
Explanation: The queue manager attempted to start the Advanced Message Security (AMS) address space because the system parameter SPLCAP is set to YES in the queue manager's ZPARM. The AMS address space (xxxxAMSM) failed to start, which might be because another job with the same name is active, or there is an error in the started task JCL.
System action: The queue manager abnormally terminates with abend code 6C6 and reason 00F00003.
System programmer response: Investigate why the AMS address space could not be started. Resolve the problem by terminating an existing address space if one is active, or correct the started task JCL if required, then restart the queue manager.

CSQY033A: csect-name QUEUE MANAGER NOT AVAILABLE, AMS INITIALIZATION ERROR
Severity: 12
Explanation: A severe error occurred during initialization of Advanced Message Security (AMS).
System action: Queue manager startup is interrupted. The queue manager accepts commands, but MQI requests that might require AMS function fail with reason code 2063 (MQRC_SECURITY_ERROR).
System programmer response: Investigate the problem reported by preceding messages in the job log for the AMS address space (xxxxAMSM). Resolve the problem, then shutdown and restart the queue manager. If you are unable to resolve the error, contact your IBM support center.

CSQY034I: csect-name QUEUE MANAGER WAITING FOR AMS TO SHUTDOWN
Severity: 0
Explanation: The queue manager is stopping and has requested the Advanced Message Security (AMS) address space (xxxxAMSM) ends. This message is periodically issued until AMS shutdown completes.
System action: The queue manager continues to wait for the AMS address space to end.
System programmer response: If this message is repeatedly issued examine the job log for the AMS address space to determine why it has not ended. If the problem cannot be resolved terminate the address space to allow queue manager shutdown to continue.

CSQY035I: csect-name AMS HAS SHUTDOWN
Severity: 0
Explanation: The Advanced Message Security (AMS) address space (xxxxAMSM) has ended.
System action: Queue manager shutdown continues.

CSQY036I

QMGRPROD= prod-value, recording product usage for product-name, product ID product-id

Explanation

This message is issued when the queue manager starts if SMF 89 product usage records are to be recorded by the queue manager. product-name is the descriptive name of the product, and product-id is the product ID that is to be used in the SMF 89 data. For example:

QMGRPROD=MQ, recording product usage for IBM MQ for z/OS, product ID 5655-MQ9 - this indicates that usage data is to be collected for the IBM MQ for z/OS product.
QMGRPROD=ADVANCEDVUE, recording product usage for IBM MQ Advanced for z/OS, Value Unit Edition, product ID 5655-AV1 - this indicates that usage data is to be collected for the IBM MQ Advanced for z/OS, Value Unit Edition product.

See z/OS MVS Product Management for more information on product usage recording.

CSQY037I

Product usage data is not being recorded for product-name, product ID product-id

Explanation

This message is issued when the queue manager starts, if SMF 89 product usage data is not being recorded by the queue manager. This might be because SMF 89 collection is not activated for the system.

See z/OS MVS™ Product Management for more information on product usage recording.

CSQY038E

csect-name QUEUE MANAGER STARTUP TERMINATED, product is not valid for prod-keyword in prod-source

Explanation

The queue manager initialization procedures found a value product for prod-keyword in prod-source that is not valid.

prod-keyword can be 'QMGRPROD' or ‘AMSPROD', and prod-source can be 'START COMMAND', ‘JCL PARM' or ‘CSQ6USGP'.

The message can be issued more than once, if more than one value, that is not valid, is found.

System action

Queue manager startup terminates abnormally with reason code 00E80010.

System programmer response

Correct the value that is not valid:

If prod-source is 'START COMMAND', see START QMGR for further information.
If prod-source is 'JCL PARM', see Starting and stopping a queue manager for information on coding the JCL parameter for the queue manager JCL.
If prod-source is 'CSQ6USGP', see Use CSQ6USGP for information on configuring values using CSQ6USGP.

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, CSQY130I: 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.) For information about the system parameters for the CSQ6SYSP macro, see Use CSQ6SYSP.
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, CSQY114I: csect-name parms
Explanation: This series of messages shows the log parameter values that the queue manager is using. For information about the log parameters in the CSQ6LOGP macro, see Using CSQ6LOGP.
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. For information about the archive parameters in the CSQ6ARVP macro, see Using CSQ6ARVP.
System action: Queue manager startup processing continues.

CSQY140I

csect-name USAGE parameters

Explanation

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

These values can be overridden by values provided in the queue manager JCL or on the START QMGR command. The resolved values are shown in message CSQY037I and CSQ0619I.

CSQY141I

csect-name No USAGE parameters provided

Explanation

No queue manager usage parameters are provided, and the defaults are assumed.

These values can be overridden by values provided in the queue manager JCL or on the START QMGR command. The resolved values are shown in message CSQY037I and CSQ0619I.

CSQY142I: csect-name parms
Explanation: This message shows the usage parameter values that the queue manager is using. For information about the usage parameters for the CSQ6USGP macro, see Use CSQ6USGP.

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

Go to the IBM Knowledge Center for z/OS MVS, and select the appropriate volume of 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.

CSQY212E: csect-name Unable to find the group attach table
Explanation: During initialization for the group connect facility, the group attach table could not be found. The most likely causes are that an error occurred during subsystem initialization, or that the subsystem was not initialized with the latest version of the IBM MQ early code.
System action: Processing continues, but the group connect facility will not be available to CICS®.
System programmer response: Ensure that the libraries with the latest version, release, or maintenance level of the IBM MQ early code are in the libraries used for the z/OS LPA, and refresh the early code for the queue manager using the IBM MQ command REFRESH QMGR TYPE(EARLY). See the Task 3: Update the z/OS link list and LPA.

CSQY220I

csect-name Queue manager storage usage : local storage : used mmMB, free nnMB : above bar : used aabb,free cc

Explanation

This message displays the amount of virtual storage currently used and available:

in the extended private region (local storage).
above the Bar (64 bit storage).
The amount of storage used is displayed in the most appropriate unit (MB / GB) according to the number of bytes, and are approximations. If the amount of storage available exceeds 10 GB, ' >10 GB' is displayed. In all other cases the amount of storage available is displayed in the most appropriate unit. For the amount of storage space available, the total is rounded down to a whole number in the appropriate unit (MB /GB). For example, if the value of 3 GB is displayed the amount of free storage is greater than or equal to 3 GB and less than 4 GB.

This message is logged at queue manager start and then either every hour if the usage does not change or when the memory usage changes (up or down) by more than 2%.

System action

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

System programmer response

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

CSQY221I: csect-name 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 a large amount of storage; for example, an unusually large unit of work being performed.
System programmer response: If only a few of these messages are output then 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 configuration and should be investigated.

CSQY222E

csect-name 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 might 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:

For buffer pools that have the LOCATION parameter set to BELOW, we can reduce buffer pool sizes with the ALTER BUFFPOOL command. Buffer pool statistics can be used to determine buffer pools which are over-allocated.
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 might be an indication of an internal error where 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: csect-name 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.

CSQY224I: csect-name Queue manager is short of local storage above the bar
Explanation: The queue manager is running short of virtual storage above the bar.
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.

CSQY225E: csect-name Queue manager is critically short of local storage above the bar - take action
Explanation: The queue manager is running critically short of virtual storage above the bar. 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 might terminate abnormally in an unpredictable way.

CSQY226I: csect-name Queue manager is no longer short of local storage above the bar
Explanation: The queue manager is no longer short of virtual storage above the bar.
System action: Processing continues. Storage contraction processing has been performed, and the remaining unallocated virtual storage is more than a predetermined safe amount.

CSQY227E: csect-name Unable to allocate storage above the bar using IARV64, RC=rc, reason=reason
Explanation: A request by the queue manager to allocate storage above the bar failed. rc is the return code and reason is the reason code (both in hexadecimal) from the z/OS IARV64 service.
System action: The queue manager will attempt to recover from the error. If recovery is not possible an application or queue manager abend, for example 5C6-00A30042, 5C6-00A31000 or 5C6-00E20045, will occur.

CSQY228E

ACE pool cannot be extended, ACELIM reached

Explanation

The internal storage pool used to manage control blocks representing new connections to the queue manager has reached the limit defined by the ACELIM system parameter.

System action

Queue manager processing continues. New connection requests might have failed, message CSQ3202E or CSM078E give further information about the affected jobs.

System programmer response

Review the configured ACELIM value. It might be useful to use a STATISTICS CLASS(2) trace to establish the normal size of the ACE pool.

See Address space storage for more information.

CSQY270E: csect-name UNRECOGNIZED MESSAGE NUMBER message-id
Severity: 8
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 IBM MQ message directory.
System action: Processing continues as though the requested message had been issued.
System programmer response: Use the message number (message-id) and look up the message in this product documentation. If you are using a language other than US English, ensure that we have installed the language feature correctly and that we have the appropriate load library data set concatenations in your job. Apart from that possibility, this might be an MQ system problem; see Troubleshooting and support.
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
Severity: 4
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.
System action: Queue manager initialization continues.
System programmer response: It might be necessary to change the CSQ6SYSP macro. For information about the system parameters for the CSQ6SYSP macro, see Use CSQ6SYSP.

CSQY290E

csect-name NO STORAGE AVAILABLE

Severity

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

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

Severity

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.

Usually the return code is 08. The most common reason codes for return code 08 are:

02: An SVC dump was suppressed because the capture phase of another SVC dump was in progress.
04: An SVC dump was suppressed by a SLIP NODUMP command.
0B: An SVC dump was suppressed by DAE.

System action

Processing continues.

System programmer response

Go to the IBM Knowledge Center for z/OS MVS, and select the appropriate volume of the MVS Authorized Assembler Services Reference manual for information about the return code and reason code from the SDUMPX request.

For reason code OB, that is, in the case of DAE suppression, see generating a suppressed dump.

To summarize, use IPCS option 3.5 , that is, Utilities -> DAE to set the T (TAKEDUMP) option for the dump symptom, or symptoms, you want to allow.

CSQY330I: Queue manager has restricted functionality
Explanation: The installation and customization options chosen for IBM 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 IBM 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 IBM MQ-IMS bridge cannot operate because the installation and customization options chosen for IBM 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 IBM MQ do not allow all functions to be used.

For example, the queue manager might have been migrated from a previous version, and is currently operating with OPMODE=COMPAT. The function requested is not available in compatibility mode. See OPMODE on z/OS for more information.

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 IBM MQ do not allow all functions to be used.
System action: The command is ignored.
System programmer response: Check for message CSQ5037I, resolve the problem, and restart this queue manager. To access IBM MQ Version 8.0 capabilities, ensure that we have OPMODE=(NEWFUNC,800), or OPMODE=(NEWFUNC,900) specified in the CSQ6SYSP macro.

CSQY335E: csect-name Channel channel-name unusable - restricted functionality
Explanation: The channel cannot be used because the installation and customization options chosen for IBM MQ do not allow all functions to be used.
System action: The requested operation fails.

CSQY336E

csect-name keyword not allowed - restricted functionality

Explanation

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

System action

The command is ignored.

CSQY337E

csect-name keyword value length not allowed - restricted functionality

Explanation

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

System action

The command is ignored.

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 IBM MQ do not allow all functions to be used. However, the queue manager has run previously without any functional restriction, and so might have objects and attribute settings that are not allowed with the restricted functionality.

In order to continue, these objects must be deleted (which might mean that messages are lost) and the attributes must be changed. The queue manager does 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 IBM 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.

CSQY344E

csect-name Loading of channel authentication rules failed, profile rule-name is restricted

Severity

Explanation

During initialization the queue manager was unable to load the channel authentication rules because profile rule-name uses function that is disabled by the queue manager mode of operation (OPMODE).

For example, the channel authentication profile has been defined with a host name but the queue manager mode of operation is OPMODE(COMPAT,800), so version 8 new functions are not available. Only the first profile found is reported so other restricted profiles might also exist.

System action

Queue manager initialization continues, but inbound channels are not permitted to start.

System programmer response

Ensure the queue manager mode of operation is correctly configured. If the configuration is correct, remove channel authentication profiles that use restricted function, then restart the queue manager.