Installing a TP that Responds to an Inbound Request

1. Start APPC

1. Create an LU in an APPCPMxx parmlib member with an LUADD statement. (See Adding a Local LU — LUADD Statement.)
   Figure 1. Example

   Jane decides to take all the defaults on her test run. She codes a parmlib member named APPCPM22 and only codes the LU name on the LUADD statement. Jane's APPCPM22 parmlib member looks something like this:

        LUADD
          ACBNAME(MVSLU)

2. Define a VSAM KSDS for TP profile information. (See Defining the VSAM Key Sequenced Data Sets (KSDS)
   Figure 2. Example

   Jane has no idea how large to make the TP profile file, so she uses the sample definition she found in SYS1.SAMPLIB(ATBTPVSM).

3. Specify the VSAM KSDS name in the APPCPMxx LUADD statement following the TPDATA keyword parameter. (See Adding a Local LU — LUADD Statement.)
   Figure 3. Example

   Because Jane used the sample VSAM definition, the name of her VSAM KSDS is SYS1.APPCTP. This is also the default name in the LUADD statement. Therefore, Jane does not need to add anything to her parmlib member APPCPM22.

4. Code a VTAM® APPL definition statement for the LU. (See Defining the Local LU to VTAM.)
   Figure 4. Example

   Jane uses the example APPL statement in SYS1.SAMPLIB member ATBAPPL, and changes both the APPL name and the name of the LU to MVSLU.

5. Depending on whether the APPC address space was started, do one of the following:
   • If the APPC address space was not yet started, issue the START command. (See Starting the APPC and ASCH Address Spaces.)
     Figure 5. Example

     From an operator's console, Jane issues the following START command:

        START APPC,SUB=MSTR,APPC=22

   • If the APPC address space was already started, issue the SET command. (See Dynamically Changing the APPC/MVS Environment.)
     Figure 6. Example

     From an operator's console, Jane issues the following SET command:

        SET APPC=22

2. Start ASCH

1. Create a class in an ASCHPMxx parmlib member with a CLASSADD statement. (See Defining a Class — CLASSADD Statement.)
   Figure 7. Example

   Jane's program is a multi-trans TP that she wants to run continuously in a class by itself. The expected response time goal for the TP is 1/2 second. Jane codes a parmlib member named ASCHPM11 and defines the class like this:

      CLASSADD
        CLASSNAME(DATA)
        MAX(3)
        MIN(1)
        RESPGOAL(.5)
        MSGLIMIT(1000)
   
      OPTIONS
        DEFAULT(DATA)
    

   Jane includes the OPTIONS statement with DATA as the default class.
2. Depending on whether the ASCH address space was started, do one of the following:
   • If the ASCH address space was not yet started, issue the START command. (See Starting the APPC and ASCH Address Spaces.)
     Figure 8. Example

     From an operator's console, Jane issues the following START command:

        START ASCH,SUB=MSTR,ASCH=11

   • If the ASCH address space was already started, issue the SET command. (See Dynamically Changing the APPC/MVS Environment.)
     Figure 9. Example

     From an operator's console, Jane issues the following SET command:

        SET ASCH=11

3. Configure the peer system

For details, see information about the peer system.

1. Create a local LU.
   Note: This local LU name is an MVS partner LU name.
   Figure 10. Example

   Jane uses Communication Manager to create an APPC LU profile for a local LU named PS2LU. She gives this LU name to her installation's VTAM programmer for use in the VTAM cross system configuration.

2. Define the MVS logon modes on the peer system.
   Figure 11. Example

   Logon modes are called transmission service modes in OS/2. Jane defines a transmission service mode for APPCPCLM, using the same name and the same parameter values for the OS/2 parameters as was used in the original VTAM definition.

3. Create a partner LU.
   Note: This partner LU name must match the MVS local LU name.
   Figure 12. Example

   Using the MVS local LU name MVSLU, Jane creates an APPC partner LU profile on the OS/2. She adds the name of the transmission service mode to the profile.

4. Create a TP profile

1. Define a TP profile entry. (See Creating a TP Profile.)
   Figure 13. Example

   Jane defines a TP profile entry that takes the defaults except for the parameters dealing with a multi-trans program. Her TP profile looks like this:

      TPNAME(TESTDATA)
      TPSCHED_DELIMITER(##)
        CLASS(DATA)
        TPSCHED_TYPE(MULTI_TRANS)
        GENERIC_ID(JANE)
        JCL_DELIMETER(XX)
    //TESTDATA JOB  'JANE',RWP,....
    //STEP     EXEC PGM=TESTDATA
    //INPUT    DD   DSN=DATABASE.DATA,....
    XX
    ##

2. Add the TP profile to the TP profile file. (See Using the APPC/MVS Administration Utility and Using the APPC/MVS Administration Dialog
   Figure 14. Example

   Jane chooses to use the APPC administration utility because the APPC administration dialog was not yet installed in TSO/E. She issues a TPADD based on the multi-trans example she found in SYS1.SAMPLIB member ATBUTIL.