Step 2: Configure VTAM and SNALINK applications

If you are using NCP V7R3 or previous, NCPROUTE requires SNALINK type LU0 to run. To use SNALINK LU0, verify that you have configured the SNALINK LU0 interface, defined it to VTAM® with a VTAM APPL definition, and included the correct DEVICE and LINK statements in hlq.PROFILE.TCPIP. For NCP V7R4, or later, IP over CDLC can be used instead of SNALINK.

If you are using the Cross Domain Resource (CDRSC), verify that the cross-domain resource managers are configured in VTAM.

The following example shows an appropriate VTAM APPL definition:

***********************************************************************
*       SNALINK VTAM APPL DEFINITION                                  *
***********************************************************************
SNALKLU1 APPL AUTH=(ACQ,VPACE),ACBNAME=SNALKLU1,EAS=12,PARSESS=YES,   *
               SONSCIP=YES,VPACING=0,SRBEXIT=YES

Note: The application name (the ACBNAME value, SNALKLU1, in this example) must match the REMLU interface definition in the NCP clients generation program. See the example in Step 6: Configure the host-dependent NCP clients for more information.

The following example shows the corresponding DEVICE and LINK statements:

;
;  DEVICE AND LINK DEFINITIONS FOR SNALINK LU0
;
DEVICE SNA1LINK SNAIUCV SNALINK A04TOLU1 SNALPROC
LINK SNALINK SAMEHOST 1 SNA1LINK
;

Note: The LU name on the DEVICE statement (A04TOLU1 in this example) must match the LU name of the NCST interface definition in the NCP clients generation program. See the example in Step 6: Configure the host-dependent NCP clients for more information.

If you want the SNALINK device to start automatically, verify that you have a START statement for this device in hlq.PROFILE.TCPIP. For example, START SNA1LINK. Otherwise, you will have to start the device manually.