Defining VTAM resources

Start by defining the associated VTAM® resources.

Defining a local LU

Define a local LU in a member in the SYS1.VTAMLST concatenation on the system where you are installing Tivoli Workload Scheduler for z/OS. This example shows how a VTAM APPL statement might be defined:

Local LU definition
VBUILD TYPE=APPL
 IS4MEOP4 APPL ACBNAME=IS4MEOP4,                                       C
               APPC=YES,                                               C
               AUTOSES=5,                                              C
               DMINWNL=3,                                              C
               DMINWNR=6,                                              C
               DSESLIM=9,                                              C
               MODETAB=APPCMODE,                                       C
               SECACPT=CONV,                                           C
               SRBEXIT=YES,                                            C
               VERIFY=OPTIONAL,                                        C
               VPACING=2

The LU is called IS4MEOP4 and uses the logon-mode table APPCMODE.

Before you can establish a session with v, a partner LU must be defined. If a partner TP is run at a different node, ensure that an LU is defined at that node.

The controller subsystem currently have tasks utilizing APPC. The subsystem is defined as one LU node to APPC and VTAM.

Defining logon modes

The logon-mode table, which you specify in the LU APPL definition statement, must be in the SYS1.VTAMLIB concatenation. To enable LU 6.2 communication for z/OS, you need the VTAM logon-mode SNASVCMG. For applications, APPC also requires at least one logon-mode entry other than SNASVCMG. You can create a new logon-mode table or add logon modes to an existing table. The name of the logon-mode table that is used by the LU and the partner LU need not be the same, but both LUs must use the same logon-mode names. That is, the logon modes used by these LUs must appear in each table, and they must have the same names. This example of an uncompiled logon-mode table contains three logon modes:

Example logon-mode table
APPCMODE MODETAB
          EJECT
 *---------------------------------------------------------------------*
 * Logmode table entry for resources capable of acting as LU 6.2       *
 * devices required for LU management.                                 *
 *---------------------------------------------------------------------*
  SNASVCMG MODEENT                                                     C
               LOGMODE=SNASVCMG,                                       C
               FMPROF=X'13',                                           C
               TSPROF=X'07',                                           C
               PRIPROT=X'B0',                                          C
               SECPROT=X'B0',                                          C
               COMPROT=X'D0B1',                                        C
               RUSIZES=X'8585',                                        C
               ENCR=B'0000',                                           C
               PSERVIC=X'060200000000000000000300'
 *---------------------------------------------------------------------*
 * Logmode table entry for resources capable of acting as LU 6.2       *
 * devices for PC target.                                              *
 *---------------------------------------------------------------------*
  LU62SYS1 MODEENT                                                     C
               LOGMODE=LU62SYS1,                                       C
               RUSIZES=X'8989',                                        C
               SRCVPAC=X'00',                                          C
               SSNDPAC=X'01'
 *---------------------------------------------------------------------*
 * Logmode table entry for resources capable of acting as LU 6.2       *
 * devices for host target.                                            *
 *---------------------------------------------------------------------*
  APPCHOST MODEENT                                                     C
               LOGMODE=APPCHOST,                                       C
               RUSIZES=X'8F8F',                                        C
               SRCVPAC=X'00',                                          C
               SSNDPAC=X'01'
           MODEEND
           END

Defining cross-domain resources

If the Tivoli Workload Scheduler for z/OS TP and the partner TP are not running in the same VTAM domain, ensure that their respective LUs can communicate by defining cross-domain resources. In this example, LU name IS1MVS1 is used for the system where the controller is activated, and IS1MVS2 for the system that the partner TP is running on.

On the Tivoli Workload Scheduler for z/OS controlling system:

Partner LU cross-domain resources
VBUILD TYPE=CDRSC
  LUMVS2 CDRSC  CDRM=IS1MVS2

On the partner system:

&opc LU cross-domain resources
VBUILD TYPE=CDRSC
 LUOPC CDRSC  CDRM=IS1MVS1