Establishing an LU 6.2 connection into a queue sharing group

There are two steps to establish an LU 6.2 connection. Defining yourself to the network and defining a connection to the partner.

1. 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 tell APPC where to locate the sideinfo.
      This line must be of the form:

      SIDEINFO
          DATASET(APPC.APPCSI)
      

   2. Add another line to SYS1.PARMLIB(APPCPMxx) to define the local LU name you intend to use for the IBM® MQ LU 6.2 group listener.
      The line you add must 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 is not 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, IBM MQ does not use this parameter, but it is required by the syntax of the LUADD command.

   3. 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 does not lose its knowledge of objects already defined to it in this member or another PARMLIB member.

   4. Add the new LU to a suitable VTAM major node definition. These are typically in SYS1.VTAMLST.
      The APPL definition will look like 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
      

   5. Activate the major node.
      You can do this activation with the command:

      V,NET,ACT,majornode
      

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

      The entries you add will look like this example:

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

   7. Alter the queue manager object to use the correct distributed queuing parameters using the following command.
      You must specify the local LU (9) assigned to your queue manager in the LUGROUP attribute of the queue manager.

      ALTER QMGR LUGROUP(MVSLU1)
      

2. Define a connection to a partner by adding an entry to the CPI-C side information data set.
   1. Add an entry to the CPI-C side information data set to define the connection.
      Sample JCL to do this definition is in thlqual.SCSQPROC(CSQ4SIDE).

      The entry you add looks like this:

           SIADD
                DESTNAME(M3)           13
                MODENAME(#INTER)       14
                TPNAME(MQSERIES)       15
                PARTNER_LU(WINNTLU)    16