Channel initiators

This might affect Task 7 in Customizing your queue managers.

 

Channel initiator parameters

The channel initiator parameters, which used to be specified in a channel initiator parameter module using CSQ6CHIP, are now queue manager attributes. To migrate your parameters, use the XPARM function of the WebSphere MQ utility program, CSQUTIL, which converts your parameter module into an ALTER QMGR MQSC command. The PARM parameter on START CHINIT is now obsolete. A warning message will be issued if this parameter is used, but the command will continue.

The minimum value of the TRAXTBL attribute has changed from 0 to 2 (2 MB). If your value of TRAXTBL is less than 2, CSQUTIL will change it to 2 during migration.

The initial value of the ADOPTMCA attribute has changed from NO to ALL. To retain the current behavior, use the ALTER QMGR command to change it to NO before starting the channel initiator.

For V5.3 users, there are new attributes RCVTIME, RCVTTYPE and RCVTMIN.

 

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.

Migration from IUCV to OESOCKET

MQ Steps

  1. Use the ALTER QMGR command to set the TCPNAME attribute to be the name of the OpenEdition stack for TCP/IP if this is not the same name as the TCP/IP address space.

Interlink Steps

  1. Ensure you are using Interlink V5.2 or greater.

  2. Create an OE segment for your channel initiator's user ID.

  3. Check your BPXPARMs to ensure that MAXSOCKET is set high enough (the Interlink documentation suggests MAXSOCKETS of 4096).

  4. It is no longer necessary to run an IUCV job.

  5. For specific details of configuration steps for UNIX System Services, check the Interlink documentation.

Migration from SNSTCPACCESS to OESOCKET

MQ Steps

  1. Change the channel initiator started task procedure (xxxxCHIN) to use hlq.SCSQMVR1 instead of hlq.SCSQMVR2.

  2. Use the ALTER QMGR command to set the TCPNAME attribute to be the name of the OpenEdition stack for TCP/IP.

Interlink Steps

  1. Ensure you are using Interlink V5.2 or greater.

  2. Create an OE segment for your channel initiator's user ID.

  3. Check your BPXPARMs to make ensure that MAXSOCKET is set high enough (the Interlink book suggests MAXSOCKETS of 4096).

  4. For specific details of configuration steps for UNIX System Services, check the Interlink documentation.

 

Enable or disable channel event messages

The queue manager attributes CHLEV, BRIDGEEV and SSLEV are introduced. These attributes enable you to control whether to generate channel events, IMS Bridge events and SSL events. By default, all these attributes are set to "ENABLED" to retain the behavior seen in previous releases. For more information about setting these attributes, see WebSphere MQ Script (MQSC) Command Reference.

 

Channel attributes

Heartbeat interval is now supported for server-connection channels. By default, existing such channels will have heartbeats set on with an interval of 300 seconds.

Although message retry is now supported for receiving channels, existing such channels will have message retry set to "no retry". However, if these channels are subsequently deleted and redefined they will have message retry set on.