Establishing an LU 6.2 connection into a queue-sharing group

To establish and LU 6.2 connection, there are two steps:

1. Define yourself to the network using generic resources.
2. Define a connection to the partner.

Defining yourself to the network using generic resources

This example describes how to use VTAM Generic Resources to have one connection name to connect to the queue-sharing group.

1. SYS1.PARMLIB(APPCPMxx) contains the start-up parameters for APPC. You must add a line to this file to define the local LU name you intend to use for the WebSphere MQ LU 6.2 group listener. The line you add should take the form

        LUADD ACBNAME(mvslu1)
              NOSCHED
              TPDATA(csq.appctp)
              GRNAME(mvsgr)
              
   

   Specify values for ACBNAME ((9)), TPDATA and GRNAME((10)).

   The NOSCHED parameter tells APPC that our new LU will not be using the LU 6.2 scheduler (ASCH), but has one of its own. TPDATA refers to the Transaction Program data set in which LU 6.2 stores information about transaction programs. Again, WebSphere MQ will not use this, but it is required by the syntax of the LUADD command.

2. Start the APPC subsystem with the command:

   START APPC,SUB=MSTR,APPC=xx
   

   where xx is the suffix of the PARMLIB member in which you added the LU in step 1.

   Note:

   If APPC is already running, it can be refreshed with the command:

   SET APPC=xx
   

   The effect of this is cumulative, that is, APPC will not lose its knowledge of objects already defined to it in this or another PARMLIB member.

3. Add the new LU to a suitable VTAM major node definition. These are typically in SYS1.VTAMLST. The APPL definition will look similar to the sample shown.

           MVSLU APPL  ACBNAME=MVSLU1,     (9)
                       APPXC=YES,
                       AUTOSES=0,
                       DDRAINL=NALLOW,
                       DLOGMOD=#INTER,    (6)
                       DMINWML=10,
                       DMINWNR=10,
                       DRESPL=NALLOW,
                       DSESLIM=60,
                       LMDENT=19,
                       MODETAB=MTCICS,
                       PARSESS=YES,
                       VERIFY=NONE,
                       SECACPT=ALREADYV,
                       SRBEXIT=YES
    
   

4. Activate the major node. This can be done with the command:

   V,NET,ACT,majornode
   

5. Add entries defining your LU and generic resource name to the CPI-C side information data set. Use the APPC utility program ATBSDFMU to do this. Sample JCL is in thlqual.SCSQPROC(CSQ4SIDE) (where thlqual is the target library high-level qualifier for WebSphere MQ data sets in your installation.)

   The entries you add will look like this:

        SIADD
             DESTNAME(G1)           (11)
             MODENAME(#INTER)
             TPNAME(MQSERIES
             PARTNER_LU(MVSLU1)     (9)
        SIADD
             DESTNAME(G2)           (12)
             MODENAME(#INTER)
             TPNAME(MQSERIES)
             PARTNER_LU(MVSGR)      (10) 
                     
   

6. Create the channel-initiator parameter module for your queue manager. Sample JCL to do this is in thlqual.SCSQPROC(CSQ4XPRM). You must specify the local LU ((9)) assigned to your queue manager in the LUGROUP= parameter of the CSQ6CHIP macro.

   Figure 88. Channel Initiator initialization parameters
   

   //SYSIN DD * CSQ6CHIP ADAPS=8, X ACTCHL=200, X ADOPTMCA=NO, X ADOPTCHK=ALL, X CURRCHL=200, X DISPS=5, X DNSGROUP=, X DNSWLM=NO, X LSTRTMR=60, X LUGROUP=MVSLU1 X LUNAME=MVSLU, X LU62ARM=, X LU62CHL=200, X OPORTMIN=0, X OPORTMAX=0, X TCPCHL=200, X TCPKEEP=NO, X TCPNAME=TCPIP, X TCPTYPE=OESOCKET, X TRAXSTR=YES, X TRAXTBL=2, X SERVICE=0 END /*

7. Modify the job to assemble and link-edit the tailored version of the initiator macro to produce a new load module.
8. Submit the job and verify that it completes successfully.
9. Put the new initialization-parameters module in an APF-authorized user library. Include this library in the STEPLIB concatenation for the channel initiator's started-task procedure, ensuring that it precedes the library thlqual.SCSQAUTH.

Defining a connection to a partner

Note:

This example is for a connection to an OS/2 system but the task is the same for other platforms.

Add an entry to the CPI-C side information data set to define the connection. Sample JCL to do this is in thlqual.SCSQPROC(CSQ4SIDE).

The entry you add will look like this:

     SIADD
          DESTNAME(M2)           (13)
          MODENAME(#INTER)       (14)
          TPNAME(MQSERIES)       (15)
          PARTNER_LU(OS2LU)      (16)

What next?

The connection is now established. You are ready to complete the configuration. Go to WebSphere MQ for z/OS shared channel configuration.