Task 7: Create procedures for the channel initiator

 

You need to create a channel-initiator started task procedure for each WebSphere MQ subsystem that is going to use distributed queuing.

To do this:

  1. Copy the sample started task procedure thlqual.SCSQPROC(CSQ4CHIN) to your procedure library. Name the procedure xxxxCHIN, where xxxx is the name of your WebSphere MQ subsystem (for example, CSQ1CHIN would be the channel initiator started task procedure for queue manager CSQ1).

  2. Make a copy for each WebSphere MQ subsystem that you are going to use.

  3. Tailor the procedures to your requirements using the instructions in the sample procedure CSQ4CHIN. We can also use symbolic parameters in the JCL to allow the procedure to be modified when it is started. This is described with the start options in the WebSphere MQ for z/OS System Administration Guide.

    Concatenate the library containing your national language feature (thlqual.SCSQANLx where x is the letter for your language) before thlqual.SCSQAUTH in the STEPLIB DD statement.

    Concatenate the distributed queueing library thlqual.SCSQMVR1.

    Access to the LE runtime library SCEERUN is required; if it is not in your link list (SYS1.PARMLIB(LNKLSTkk)), concatenate it in the STEPLIB DD statement.

  4. Authorize the procedures to run under your external security manager.

We can add the exit library (CSQXLIB) to this procedure later if you want to use channel exits. You need to stop and restart your channel initiator to do this.

If you are using SSL, access to the system Secure Sockets Layer (SSL) runtime library SGSKLOAD is required. The library must be APF authorized.

If you are using TCP/IP, the channel initiator address space must be able to access the TCPIP.DATA data set that contains TCP/IP system parameters. The ways that the data set has to be set up depends on which TCP/IP product and interface you are using. They include:

Some of these affect your started-task procedure JCL. For more information, see the following: