Channel initiator
Dynamic changing of parameters
Channel initiator parameters were originally implemented using assembler load modules, but have now been moved to be queue manager attributes. This means it is now possible to dynamically modify them using the ALTER QMGR command and view them using the DISPLAY QMGR command. A utility for migrating existing parameter load modules has also been provided.
To summarize:
- The ALTER QMGR command has been extended so that it now supports all the parameters previously supplied in the CSQ6CHIP macro.
- A migration facility is now provided in CSQUTIL for these parameters. This simplifies the migration process by allowing the load module to be migrated when the queue manager is not running, before the queue manager has been migrated to WebSphere MQ V6
- The PARM parameter has been removed from the START CHINIT command on z/OS.
- The DISPLAY QMGR command has been extended so that it now presents the values of these parameters.
For information about the commands, see WebSphere MQ Script (MQSC) Command Reference or WebSphere MQ Programmable Command Formats and Administration Interface.
For information about how the channel initiator is affected by this feature, see WebSphere MQ for z/OS System Setup Guide.
TCP/IP interface
Only one type of TCP/IP interface is now supported, which is that formerly specified by TCPTYPE=OESOCKET in the channel initiator parameters.
Multiple TCP/IP stacks
WebSphere MQ can now use more than one TCP/IP stack for both inbound as well as outbound communication. This provides greater flexibility when configuring WebSphere MQ on a system with than one network interface. If more than one network interface is involved, it is now possible to use more than one of them for your WebSphere MQ channels. This means it is no longer necessary to choose just one of these for all outbound channels, or install a second queue manager on the same system.
For more information see WebSphere MQ Intercommunications, and the WebSphere MQ Script (MQSC) Command Reference.