NetWare for SAA can be used to establish a connection between a workstation and the host.
The Netware for SAA API support is presumed to be installed at the workstaton. If support has been installed, directory NWSAAAPI will exist, probably on the C drive.
The NetWare for SAA API directory, NWSAAAPI, must be accessible to BIM-EDIT/XP. The operating system PATH statement (in AUTOEXEC.BAT) must be updated to provide access to the NWSAAAPI directory, whether the directory exists on the NetWare server or on the workstation.
Configure the Netware for SAA server using the 'Netware Comm Services Config' program, CSCON, or the Windows-based graphical equivalent. Perform the following steps:
Define three local APPC dependent LUs for each BIM-EDIT/XP host component to which you will connect. Specify the following attributes for each local LU:
LU name may be any name you wish except that the last character of the name must be an "A" for the first LU, "B" for the second LU, and "C" for the third LU. The LU name must match the host VTAM LU statement.
Note that the LU name must match the VTAM LU name and not the dedicated LU name as defined on the Netware for SAA server. Note also that the LU name on the SAA Server must match the VTAM LU name.
LU (or NAU) address must match the address specified on the host VTAM LU statement.
From the BIM-EDIT/XP command line on each workstation:
Set the MCBPUNAM variable to the physical unit name for the Netware for SAA server. This corresponds to the VTAM PU statement. For example, if the physical unit name is R1241PU, enter the following:
=> set mcbpunam,R1241PU
Set the MCBNETNM variable to the VTAM network name.
If needed, set the MCBDLCNM to the data link name. This entry is initialized to ITRN, which is suitable for most LAN connections.