Enhanced remote controller support

Enhanced remote controller support enables you to load, activate, and dump NCP using a switched SDLC link, including a token-ring connection and an X.25 switched virtual circuit (SVC). However, the token-ring and X.25 SVC switched connections require an NCP to be operational in the communication controller or available on the controller disk.

Following is a sample switched major node for enhanced remote controller support:

NCPSW111 VBUILD TYPE=SWNET                SWITCHED MAJOR NODEE
*
P5001T4  PU    ADDR=C1,                   PU TYPE 4 STATION ADDRESS
               MAXDATA=4096,              MAXIMUM DATA TRANSFER
               NETID=USIBMCSS,            NETWORK IDENTIFIER
               SUBAREA=112,               SUBAREA NUMBER
               IDNUM=11201,               UNIQUE IDNUM
               PUTYPE=4,                  PU TYPE 4
               ⋮
               TGN=8,                     TRANSMISSION GROUP NUMBER
*
         PATH  DIALNO=1234567,            TELEPHONE DIAL NUMBER
               GID=2,                     GROUP IDENTIFIER
               PID=2,                     PATH IDENTIFIER
               REDIAL=4,                  RETRY DIAL 4 TIMES
               ⋮
               GRPNM=G6INN                GROUP NAME IN NCP

To use enhanced remote controller support:

Define the switched physical connection by coding the NCP LINE and PU definition statements with the DIAL operand specified as YES.
Define the corresponding logical definition to VTAM® by coding a PU definition statement for a type 4 PU in a switched major node.
Because a subarea physical unit can have multiple connections, code a connection identifier (IDNUM) to distinguish the multiple PU definition statements that can apply to a subarea physical unit. The value of the IDNUM operand on the PU definition statement must match the value of the IDNUM operand on the SWMMT definition statement for the remote communication controller; when the IDNUM operand is concatenated with the subarea number for the NCP, it must be unique within the network. Therefore, you can use the same IDNUM to represent connection endpoints in different subareas. If IDNUM is duplicated within the network, a connection can be established with the wrong subarea, which may result in a connection failure or other errors later in the process. IDBLK is not used by VTAM and is set to a value of X'FFF' in the station identifier that is used for the XID exchange during the dial procedure.
Code a PATH definition statement so that VTAM performs a dial-out operation on the switched link and contacts the remote device (PUTYPE=4). The PATH definition statement also specifies the group name (GRPNM) of the group of switched lines in the NCP over which the connection can be made.
Make sure the value of the NETID operand on the PU definition statement in the switched or model major node matches the NETID operand on the SWMMT definition statement for the corresponding switched line in the remote communication controller.
Note: The IDNUM and NETID operands are maintained within the NCP load module so an NCP generation is required to change these values.
For security reasons, you might want to code a password on the PU definition statement using the PRTCT operand. If the check fails, the connection fails.
Note: In a single-domain network where a single VTAM and NCP control both link stations, VTAM does not support call security verification. (That is, if you code either the MONLINK=YES or MONLINK=CONT operand for the switched line in the link-attached NCP, VTAM does not support call security verification.)