Table 2. Values Required to Configure APPC/MVS
This worksheet consists of two parts:

1. Symbols that must be matched with the workstation (the partner platform) are under the heading NETWORK VALUES.
2. Symbols local to MVS are under the heading LOCAL VALUES.

Symbol | How to determine the value for this symbol | Fill in your value here
--- | --- | ---
NETWORK VALUES
LUNAME | This symbol is for the APPC/MVS LU of the MVS system you are configuring. See "Define the APPC/MVS LU in VTAM" and the bibliography for additional information on creating this LU. For MVS/ESA 4.2, use the base APPC/LU. See MVS/ESA Planning: APPC Management. This value should be consistent with PARTNERLU as defined at all participating workstations. See Table 1 for more information about PARTNERLU at the workstation. |
NETNAME | This symbol is for the network name. For systems with VTAM already configured, this value is found in the VTAMLST start options (ATCSTRxx) member. The option name is NETID. This value should be consistent with PARTNERNET, as defined at all participating workstations within this network. See Table 1 for more information about PARTNERNET at the workstation. |
PARTNERLU | This symbol is for an associated workstation LU name. There should be a unique LU name for each participating workstation. This value should be consistent with the definition of LUNAME at the associated workstation. See Table 1 for more information about LUNAME at the workstation. |
IDBLK | This symbol defines the first three hexadecimal digits of the NODEID for each participating workstation. Its value is normally 05D for a workstation. This value is defined in VTAM and its value must match the value defined in NODEID at the workstation. See Table 1 for more information about NODEID at the workstation. |
IDNUM | This symbol defines the last five hexadecimal digits of the NODEID for each participating workstation. A unique IDNUM is defined in VTAM for each workstation. The last five hexadecimal digits of NODEID defined at the corresponding workstation must match IDNUM. See Table 1 for more information about NODEID at the workstation. |
LOCALCP | This symbol is for VTAM's System Services Control Point (SSCP) name. It is the value of SSCPNAME in the VTAM start options. This value should be consistent with PARTNERCP, as defined at all participating workstations. |
LOCAL VALUES
NCPLANADDR | This symbol is for the local LAN address coded in NCP on a LINE macro using the LOCADD parameter. For our example, the workstation is configured through the 3745, but not through a different APPN network node. Therefore, this value should be consistent with LANADDRESS, as defined at all participating workstations on this token-ring. See Table 1 for more information about LANADDRESS at the workstation. |
MODETAB | Name of a logon mode table in VTAM that contains the APPC mode entries. |
MODE | Name of the logon mode table entry within the table that is defined by MODETAB and used by VisualAge COBOL. Its recommended value should be #INTER. This value must match the value of MODE at the workstation. See Table 1 for more information about MODE at the workstation. | #INTER
SIFILE | This symbol is for the VSAM data set where the CPI-C side information profile will be permanently located. This value is normally SYS1.APPCSI. | SYS1.APPCSI
SYMDEST | This is the symbol for the value representing a CPI-C side information symbolic destination name. Each participating workstation will have a unique SYMDEST value which points to an entry in a VSAM data set. This entry identifies the corresponding workstation and is used by APPC/MVS during initialization of a Remote Debug session. The value of SYMDEST points to the following information for a workstation: The value of REMOTETP (COBVSDT) The value of PARTNERLU (the workstation LU name) The value of MODE (#INTER) |
TPFILE | This symbol is for the VSAM data set where the TP profiles will be permanently located. This value is normally SYS1.APPCTP. | SYS1.APPCTP
VOL | This is the name of a volume on which VSAM data sets for APPC/MVS are created. |
JES | The actual JES subsystem type (JES2 or JES3) should be substituted for this. |