Commands

 

PCF

PCF commands, identified by a message format of MQFMT_ADMIN, are now supported.

MQSC commands put to the system command input queue with a message format of MQFMT_ADMIN were accepted in previous versions. In V6, such messages will be treated as PCF commands, and so will be rejected.

Applications currently using PCF will need changing to use PCF on z/OS, to use the necessary extended command formats and handle the extended response formats. See WebSphere MQ Programmable Command Formats and Administration Interface for details.

 

Security profiles

The MQSC command DISPLAY DQM has been renamed DISPLAY CHINIT, although the old command still works as a synonym. If you have a security profile for the old command, you should rename it.

There are several new MQSC commands, and several commands now allowed outside the queue manager initialization data sets, for which you should add security profiles:

Most MQSC commands now have PCF equivalents. These generally use the same security profiles but there are some which need new profiles, for example Change Queue. For further information see Profiles for command security.

If you are using the WebSphere MQ V6.0 Explorer, we need appropriate security profiles for the queues SYSTEM.MQEXPLORER.REPLY.MODEL and AMQ.EXPLORER.*. For further information see Profiles used to control access to WebSphere MQ resources.

 

Channel Initiator

Channel initiator commands (other than START CHINIT) are no longer allowed in the queue manager initialization input data set CSQINP2. They should be moved to the channel initiator initialization input data set CSQINPX. Output from these commands is written to the output data set CSQOUTX. For more details, see Task 13: Customize the initialization input data sets.

The START TRACE, DISPLAY TRACE, ALTER TRACE, and STOP TRACE commands have been changed to handle channel initiator traces better. For information about WebSphere MQ commands, see the WebSphere MQ Script (MQSC) Command Reference manual.