Defining VTAM requirements (CAS)

ACF/VTAM definitions are required, if you are not using the cross-systems coupling facility (XCF) for CAS-to-CAS communication links, to identify each CAS used by CICSPlex® SM. This involves creating VTAM® application definitions and, optionally, cross-domain resource management definitions.

If you are also setting up a CMAS, see Defining VTAM requirements (CMAS) for more information about the steps for defining the VTAM requirements for a CMAS.

To create VTAM application definitions and cross-domain resource management definitions for a CAS, you must perform the following steps:

  1. Optionally, create a mode table entry.
  2. Create a VTAM application definition for each CAS you will be using.
  3. Define each CAS as a cross-domain resource.
  4. Add the application and cross-domain resource definitions to the VTAM configuration list.
  5. Activate the definitions.

Depending on your VTAM conventions, you may need to modify the procedures described in this section. Specifically:

After you have the CAS running and can access CICSPlex SM, you can define VTAM to CICSPlex SM. (See Setting the CAS system communication information.)

Step 1: (Optional) Creating a mode table

If you use Network Control Programs (NCPs), you may need to create a mode table with the default entry shown in Figure 49 in order to control the VTAM RUSIZES (request unit size) parameter. If you do not create a default entry, VTAM could select a number that is too small, thus resulting in considerable system overhead.

To create a default mode table entry:

  1. Define a mode table containing the following entry:
    Figure 49. Sample mode table entry
             TITLE 'modename - MODE Table - Entries'
    modename MODETAB ,
             MODEENT LOGMODE=entryname,                                   X
                   FMPROF=X'13',                                          X
                   TSPROF=X'07',                                          X
                   PRIPROT=X'B0',                                         X
                   SECPROT=X'B0',                                         X
                   COMPROT=X'50B1',                                       X
                   SSNDPAC=X'00',                                         X
                   SRCVPAC=X'00',                                         X
                   RUSIZES=X'F8F8',                                       X
                   PSNDPAC=X'00',                                         X
                   PSERVIC=X'060200000000000000002300',                   X
                   ENCR=X'00'
             MODEEND ,
             END ,

    where:

    modename
    Is a mode table name that you supply.
    entryname
    Is a name for an entry that you supply.
    For a copy of this mode table entry, see the member EYUSMPMT in CICSTS31.CPSM.SEYUSAMP.
  2. Assemble the mode table source and link-edit it into SYS1.VTAMLIB on all systems for which cross-system communication is enabled. As you do so, keep the following in mind:

    The JCL you use to assemble and link-edit should look like that shown in Figure 50. (The member EYUJCLMT in CICSTS31.CPSM.SEYUSAMP contains a copy of this JCL.)

    Figure 50. JCL to assemble a mode table entry
    //*----------------------------------------------------------------------
    //*
    //* Sample JCL - Assemble and Link Mode Table Entry
    //*
    //* The following needs to be provided:
    //*------------------------------------
    //*   ASM.SYSIN    - Input member containing the mode table source.
    //*   LINK.SYSLMOD - Output member name in SYS1.VTAMLIB
    //*
    //*---------------------------------------------------------------------
    //ASM     EXEC PGM=ASMA90,
    //            PARM='OBJECT,NODECK'
    //SYSLIB   DD  DISP=SHR,DSN=SYS1.SISTMAC1
    //         DD  DISP=SHR,DSN=SYS1.MACLIB
    //SYSUT1   DD  DSN=&&SYSUT1,
    //            UNIT=VIO,SPACE=(1700,(600,100))
    //SYSTERM  DD  SYSOUT=*
    //SYSPRINT DD  SYSOUT=*
    //SYSLIN   DD  DISP=(MOD,PASS),
    //            DSN=&&OBJSET,
    //            UNIT=VIO,SPACE=(80,(200,50))
    //SYSIN    DD  DISP=SHR,DSN=data_set_name(member_name)
    //*
    //LINK    EXEC PGM=IEWL,
    //            PARM=(XREF,LET,LIST,NCAL,REUS),
    //            COND=(8,LT,ASM)
    //SYSLIN   DD  DISP=(OLD,DELETE),DSN=&&OBJSET
    //         DD  DDNAME=SYSIN
    //SYSLMOD  DD  DISP=SHR,DSN=SYS1.VTAMLIB(member_name)
    //SYSUT1   DD  DSN=&&SYSUT1,
    //            UNIT=VIO,SPACE=(1024,(50,20))
    //SYSPRINT DD  SYSOUT=*
    //*

Step 2: Creating a VTAM application definition (CAS)

To establish a VTAM application definition for a CAS, either create a new member (major node) or access an existing member in the SYS1.VTAMLST library. To this member, add the following APPL statement:

          VBUILD TYPE=APPL
name      APPL ACBNAME=acbname,AUTH=(ACQ),                             x
               PARSESS=YES,MODETAB=mode_table

where:

name
Is a 1- to 8-character unique name.
acbname
Is the node name of this CAS. This name must be unique within the domain. If you omit this parameter, the name of the VTAM APPL statement is used.
mode_table
Is the name of the mode table that is to govern LU 6.2 conversations.

For example, to create a VTAM application definition for the CAS on SYSA, you might create a member named APPLCASA in the SYS1.VTAMLST library that contains the APPL statement:

          VBUILD TYPE=APPL
CASA      APPL ACBNAME=CASA,AUTH=(ACQ),                                x
               PARSESS=YES,MODETAB=AMODET

The same type of definition is needed for each CAS you will be using.

Step 3: Defining cross-domain resources (CAS)

You should define cross-domain resources (CDRSCs) when:

To establish a CDRSC definition, you must either create a new member or access an existing member in the SYS1.VTAMLST library. In the new or existing member, specify the following CDRSC statement for each CAS with which you want to communicate:

         VBUILD TYPE=CDRSC
name     CDRSC CDRM=cdrm

where:

name
Is the name you assigned to a CAS in Step 1.
cdrm
Is the name of the MVS™ image previously identified as the cross-domain resource manager (CDRM).

For example, to allow the CAS on SYSA to communicate with the CASs on SYSB and SYSC, you might create the member CDRCASA on the SYS1.VTAMLST library, which contains the CDRSC statements:

        VBUILD TYPE=CDRSC
CASB    CDRSC CDRM=VTAMB
CASC    CDRSC CDRM=VTAMC

where VTAMB and VTAMC are the cross-domain resource manager names assigned to SYSB and SYSC, respectively. The same types of definitions are also needed for the CASs on SYSB and SYSC. That is, for the CAS on SYSB, you might create a member named CDRCASB that contains:

        VBUILD TYPE=CDRSC
CASA    CDRSC CDRM=VTAMA
CASC    CDRSC CDRM=VTAMC

For additional information about cross-domain resources, see the VTAM Resource Definition Reference.

Step 4: Updating the configuration list (CAS)

If, in step 2 or 3, you created new members in the SYS1.VTAMLST library, you must update the VTAM configuration list for each MVS image. This causes the new members to be automatically activated when VTAM starts.

To do this, add the new member names to the end of the configuration list in the appropriate ATCCONxx member of the SYS1.VTAMLST library. To find the suffix of the ATCCONxx member, do the following:

To illustrate, the examples shown in steps 2 and 3 assume the creation of members named APPLCASA and CDRCASA. To add these members to the end of the configuration list in ATCCONxx, you would specify:

APPLCASA,                                                          x
CDRCASA
Note:
If you added the CAS and cross-domain definitions to existing members, ATCCONxx should already contain these member names.

Step 5: Activating the major nodes (CAS)

You can activate the definitions created in steps 1 and 2 by either restarting VTAM for each system, or manually activating the definitions.

To manually activate a major node, you can issue the following commands, where name identifies a major node created (or modified) in steps 2 and 3:

To ensure that the major node has been activated, issue the command:

   D NET,ID=name

For example, to activate the member APPLCASA and then ensure that it has been activated, you would issue the commands:

   VARY NET,INACT,ID=APPLCASA
   VARY NET,ACT,ID=APPLCASA
   D NET,ID=APPLCASA

To dynamically load a mode table that you have updated, issue the command:

   F NET,TABLE,OPTION=LOAD,NEWTAB=name

If you do not do this after updating and relinking a mode table with a new logmode entry, the entry is unavailable until you have stopped and restarted VTAM. Note that you do not need to issue this command when you create a mode table with a single logmode entry.

The preceding steps need to be performed for each CAS you may be using.

[[ Contents Previous Page | Next Page Index ]]