The process of enabling the workstation component of BIM-EDIT/XP to communicate with the host component of BIM-EDIT/XP (a.k.a. BIM-EDIT) via an LU 6.2 protocol involves:
Updating the BIM-EDIT/XP Host System Definition Table.
Updating the communications software running on the workstation and/or server and informing BIM-EDIT/XP of the communications software being used.
Updating the VTAM definition at the host or hosts.
Host System Definition Table
The host system definition table is built at startup by processing file DFNREMOT.CTL. BIM-EDIT/XP searches for this file first in the Specific User Directory (if user not "DEFAULT"), then in the Default User Directory, then in the Site Directory, and finally in the System Directory.
The file contains the following fields:
Host system ID. This is a two-character ID known only within BIM-EDIT/XP. The host system ID of the current host system will display on the information line.
Type. Usage currently undefined.
Host name. This is the partner LU alias (discussed below in the Communications Manager section). The partner LU alias is a name used to identify the host system BIM-EDIT application. If you are communicating with a single host BIM-EDIT system, the name "BIMEDIT" should probably be used.
Default user ID to be used when logging on to the host system. This field may be left blank.
Default password to be used when logging on to the host system. This field may be left blank.
Auto Connect. Specify "Yes" to automatically log on to the host system when BIM-EDIT is started. Specify "No" if automatic logon is not desired.
LU Alias. This field is normally used only where the communications software is server-based, as in the case of Microsoft SNA Server or OS/2 Communications Server. This is the first LU alias name (first of three) through which BIM-EDIT/XP communicates with a host system. The name should end in the character 'A'. BIM-EDIT/XP forms the second and third LU alias names by changing the last letter to 'B' and 'C', respectively. The three LU aliases must be defined to the server-based communications software and to VTAM on the host system.
LU Address. This field is used in conjunction with the LU alias field. It specifies the local LU address assigned to the LU alias name. LU address is a number between 001 and 255. This field is required only for Netware for SAA.
During installation a copy of DFNREMOT.CTL was placed in the Default User Directory. You can access the Default User Directory quickly through the menu structure by selecting "Options", then "Lib (Lc)C:\BimEdit\User\Default\*". Move the cursor down to the DFNREMOT.CTL line and press F12 to begin an Edit session.
The supplied table will provide access to the application "BIMEDIT" on host system "BI".
Workstation and/or Server Communications Software
The workstation and host components of BIM-EDIT/XP communicate with each other via an APPC protocol (a.k.a. LU 6.2). Workstation support for APPC is provided by software such as:
Attachmate Extra Personal Client
Select one of the above topics for configuration instructions. Other communication software should work with BIM-EDIT/XP provided it supports the standard APPC interface.
Inform BIM-EDIT/XP about the type of communications software running on the workstation and/or server. This is done by selecting "Options / Settings, System..." in the menu hierarchy. Select the "Host" page. In the "Communications Interface" box, select the communications software being used.
If the communications software being used is not listed, experiment with the existing entries. There is a very good chance that one of the existing entries will be compatible with the communications software.
VTAM Definition on Host
See BIM-EDIT System Reference Manual Chapter 9 Installation and Maintenance Item #10.
If the workstation is already set up to provide 3270 sessions, the physical unit (PU) will already have been defined. Otherwise, the PU will need to be defined. In general, the workstation appears to the host as a 3174 controller. Consult VTAM documentation for further information.
LUs must be defined to match the all Local LUs defined on the workstation. The DLOGMOD parameter, which references the mode entry, does not need to be specified since the EDITLU62 name is supplied by the workstation at session initiation. However, VTAM needs access to the EDITLU62 mode in whatever mode table it searches. The workstation provides only the NAME of the mode entry, not the actual mode entry. The name of the mode table to search is defined by the MODETAB parameter, and is usually specified at a higher level than the LU statement, often on the PU statement.
The following is an example of the VTAM definition for an SNA dial-up workstation.
JGPU PU ADDR=01,IDBLK=05D,IDNUM=11353,MAXDATA=256, X
MAXOUT=7,PACING=3,USSTAB=BIMUSSTR,MODETAB=ATCMODE
JG00BIA LU LOCADDR=5 6.2 LUs
JG00BIB LU LOCADDR=6 6.2 LUs
JG00BIC LU LOCADDR=7 6.2 LUs
JG01 LU LOCADDR=2,DLOGMOD=D4C32784 3270 LUs
JG02 LU LOCADDR=3,DLOGMOD=D4C32784 3270 LUs
JG03 LU LOCADDR=4,DLOGMOD=D4C32784 3270 LUs
The following is an example of the VTAM definition for a workstation connected via a token-ring LAN through a 3174 controller:
TRPU01 PU CUADDR=081, X
MODETAB=ATCMODE, BIND TABLE NAME X
USSTAB=BIMUSSTS, SNA LOCAL USSTAB AND MSG10 X
SECNET=YES, SPECIAL 3174/TOKEN RING PROCESSING X
MAXBFRU=8, X
PUTYPE=2
TR10BIA LU LOCADDR=5 6.2 LUs
TR10BIB LU LOCADDR=6 6.2 LUs
TR10BIC LU LOCADDR=7 6.2 LUs
TR11 LU LOCADDR=2,DLOGMOD=SNX32704,MODETAB=ATCMODE, X
USSTAB=BIMUSSTR 3270 LUs
TR12 LU LOCADDR=3,DLOGMOD=SNX32704,MODETAB=ATCMODE, X
USSTAB=BIMUSSTR 3270 LUs
TR13 LU LOCADDR=4,DLOGMOD=SNX32704,MODETAB=ATCMODE, X
USSTAB=BIMUSSTR 3270 LUs
In the above two examples, it is assumed that the mode "EDITLU62" has been added to the mode table "ATCMODE".