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

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

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.

Queue manager shutdown is initiated.

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

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.

Queue manager shutdown continues.

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

Queue manager startup is terminated.

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.

Queue manager startup terminates abnormally.

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.

The queue manager initialization procedures found that the level of the operating system did not have the function required for correct queue manager operation.

Queue manager startup terminates abnormally.

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.

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.

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

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.

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

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.

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.

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

The queue manager does not start.

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.

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

The queue manager does not start.

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.

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

The queue manager does not start.

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.

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

The queue manager does not start.

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.

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

The queue manager does not start.

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.

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

The queue manager does not start.

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

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.

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

Check that all the libraries you include in the IBM MQ STEPLIB have been APF-authorized. Also, ensure that you 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.

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.

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

Check all the libraries that you include in the IBM MQ STEPLIB are APF-authorized. Also, check that you 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.

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.

Queue manager startup terminates abnormally with reason code 00E80051.

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.

The channel initiator can be started only by a START CHINIT command.

Channel initiator startup is terminated.

Start the channel initiator using the START CHINIT command

The queue manager initialization procedures found that the configured MEMLIMIT is less than 512MB.

Queue manager startup terminates abnormally.

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

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.

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

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.

The system parameter SPLCAP is set to YES in the queue manager's ZPARM, however, Advanced Message Security has not been installed.

Queue manager startup is terminated.

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.

This message indicates that Advanced Message Security is installed.

Queue manager startup continues.

None.

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.

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.

Advanced Message Security (AMS) initialization has completed successfully.

Applications waiting for AMS function are resumed.

A severe error occurred during initialization of Advanced Message Security (AMS).

The queue manager abnormally terminates with abend code 6C6 and reason 00F00003.

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.

The Advanced Message Security (AMS) address space has ended abnormally due to an unrecoverable error.

The queue manager abnormally terminates with abend code 6C6 and reason 00F00003.

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.

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.

Processing continues. Connections to the queue manager are permitted, but MQI requests that might require AMS function are suspended until AMS is available.

Investigate the delay in initializing Advanced Message Security by reviewing the messages output in the job log for the AMS address space (xxxxAMSM).

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.

The queue manager abnormally terminates with abend code 6C6 and reason 00F00003.

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.

A severe error occurred during initialization of Advanced Message Security (AMS).

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

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.

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.

The queue manager continues to wait for the AMS address space to end.

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.

The Advanced Message Security (AMS) address space (xxxxAMSM) has ended.

Queue manager shutdown continues.

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

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.

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.

Queue manager startup terminates abnormally with reason code 00E80010.

• 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 Using CSQ6USGP for information on configuring values using CSQ6USGP.

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

Queue manager startup processing continues.

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 Using CSQ6SYSP.

Queue manager startup processing continues.

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

Queue manager startup processing continues.

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.

Queue manager startup processing continues.

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

Queue manager startup processing continues.

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.

Queue manager startup processing continues.

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.

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.

This message shows the usage parameter values that the queue manager is using. For information about the usage parameters for the CSQ6USGP macro, see Using CSQ6USGP.

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.

None.

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.

The specified element was successfully registered with ARM.

None.

An attempt to register with ARM failed.

Processing continues, but automatic restart is not available.

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

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.

Processing continues.

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

The specified element was successfully deregistered from ARM.

None.

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

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

Restart the queue manager manually.

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

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.

If you are unable to solve the problem, take a stand-alone system dump and contact your IBM support center.

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.

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

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

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.

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

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.

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

The message is also generated if the ALTER BUFFPOOL command makes a change to the value either for LOCATION, or BUFFERS.

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

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.

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

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.

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.

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.

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.

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.

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

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

The queue manager is running short of virtual storage above the bar.

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.

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.

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.

The queue manager is no longer short of virtual storage above the bar.

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

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.

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.

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.

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

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.

csect-name UNRECOGNIZED MESSAGE NUMBER message-id

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.

Processing continues as though the requested message had been issued.

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 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 might be an MQ system problem; see Troubleshooting and support.

MESSAGE GENERATOR INITIALIZATION PARAMETERS NOT FOUND. DEFAULTS ASSUMED

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.

Queue manager initialization continues.

It might be necessary to change the CSQ6SYSP macro. For information about the system parameters for the CSQ6SYSP macro, see Using CSQ6SYSP.

csect-name NO STORAGE AVAILABLE

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.

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.

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

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.

Processing continues.

Select the appropriate volume of the z/OS 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.

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

Queue manager startup processing continues.

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.

The queue manager does not start.

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.

The MQ-IMS bridge does not start.

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.

The command is ignored.

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.

The command is ignored.

Check for message CSQ5037I, resolve the problem, and restart this queue manager. To access IBM MQ 8.0 capabilities, ensure that you have OPMODE=(NEWFUNC,800), or OPMODE=(NEWFUNC,900) specified in the CSQ6SYSP macro.

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

The requested operation fails.

The keyword 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 further information.

The command is ignored.

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.

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 further information.

The command is ignored.

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.

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

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

The queue manager waits for the operator's reply

See message CSQY340E.

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

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

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

The queue manager does not start.

8

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.

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

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.