OS/2 Communications Manager can be used to establish a connection between a workstation and the host.
Before attempting to set up OS/2 Communications Manager to support BIM-EDIT/XP, we recommend that you configure OS/2 Communications Manager to provide at least one 3270 emulator session. Consult documentation provided with Communications Manager to accomplish this. Once the emulator session is working, the process of enabling BIM-EDIT/XP communications, which is accomplished through LU 6.2 sessions, will be much smoother.
OS/2 Communications Manager maintains a network definition file in the CMLIB directory with name of the form "yourconfigname.NDF". In the System Directory are some sample .NDF files that can be used for comparison with your .NDF file.
The following items must be defined to OS/2 Communications Manager. The required dialogs can be reached through the "SNA features" profile.
Partner LU profiles. For each host BIM-EDIT system to which you wish to communicate, a partner LU profile must be defined.
The partner LU alias must match the name assigned to the host system in the Host System Definition Table (discussed above). If you are communicating with a single host BIM-EDIT system, the name "BIMEDIT" should probably be used.
The "Fully Qualified LU Name" is the name as known on the network. The first part of this name will be the network ID, as defined on the NETID parameter in the ATCSTR00 VTAM book on the host. The last part of this name will be the name of the application on the host system, as defined by the VTAM APPL statement. If you are communicating with a single host BIM-EDIT system, the last part of this name will probably be "BIMEDIT".
The partner LU must be defined as dependent.
The "Uninterpreted Name" should be same as the last part of the "Fully Qualified LU Name".
Local LU profiles. For each host BIM-EDIT system to which you wish to communicate, a set of three LU profiles must be defined.
Local LU profile #1. The LU alias must be of the form "EDXPssA", where ss is the host system ID (described above). For example, for host system ID "BI", the LU alias would be "EDXPBIA". The node name may be any name you wish except that the last character of the name must be an "A". The LU must be defined as a dependent LU and assigned an address. The node name and address must match the VTAM LU definition on the host BIM-EDIT system.
Local LU profile #2. The LU alias must be of the form "EDXPssB", where ss is the host system ID. The node name must be equal to the node name for LU profile #1, except that the last character is changed from an "A" to a "B". The LU must be defined as a dependent LU and assigned an address. The node name and address must match the VTAM LU definition on the host BIM-EDIT system.
Local LU profile #3. The LU alias must be of the form "EDXPssC", where ss is the host system ID. The node name must be equal to the node name for LU profile #1, except that the last character is changed from an "A" to a "C". The LU must be defined as a dependent LU and assigned an address. The node name and address must match the VTAM LU definition on the host BIM-EDIT system.
Mode name "EDITLU62". Defaults for other items should be acceptable.
In addition, the "Connection to a Host" dialog may need to be updated. To access the dialog:
Select the "SNA Connections" profile. Press "Configure".
The "Connections List" dialog appears. Select the link that will be used to establish communications with the host. There probably will be only one listed. Press "Change".
The "Adapter List" dialog appears. Press "Continue". The "Connection to a Host" dialog should appear.
Ensure that the "Partner network ID" and the "Partner node name" are set correctly. The "Partner network ID" should be set to the network ID, as defined on the NETID parameter in the ATCSTR00 VTAM book on the host. The "Partner node name" should be set to the control point name of the host computer, as defined on the SSCPNAME parameter in the ATCSTR00 book.
Also ensure that the APPN check box is NOT checked.