Chapter 3: Establish the Communications Link

Fill out the worksheet before you proceed with this chapter. See Worksheet in Chapter 1: Plan the Gateway if you have not completed the worksheet.

Communications Link for the NLM Gateway

NetWare* for SAA provides the communications link between the LAN where the GroupWise* Gateway for OfficeVision/VM** resides and the mainframe host. Instructions for installing NetWare SAA are found in the NetWare for SAA Administrator’s Guide.

Configure NetWare for SAA
In this section you will configure NetWare for SAA for the first time. If you already run NetWare for SAA, the screens will display in a different order.

You configure NetWare for SAA using the CSCON.EXE utility which was placed in the SYS:SYSTEM\CSCON directory during the NetWare for SAA installation. To run the CSCON.EXE utility:

To start CSCON,

  1. At the DOS prompt, type CSCON .

  2. Choose the NetWare file server where NetWare for SAA resides.

  3. Choose Configure Communication Service.

  4. Choose NetWare for SAA.

From the menu, you perform the following tasks,

Configure the Network Adapter
Your NetWare file server can have one or more network adapters. The adapter used to connect to the mainframe host must be configured before it is recognized by NetWare for SAA.

To configure the LAN adapter,

  1. Choose Configure Data Link Adapters.

  2. Press Insert.

  3. Type the name assigned to the network adapter, (Worksheet item #12) {short description of image} press Enter.

  4. Choose Token Ring.

  5. Fill in the fields:

    Logical adapter name: Displays the name of the network adapter used to connect to the mainframe host. (Worksheet item #12)

    Logical adapter number: Enter a unique number that NetWare for SAA uses to identify the network adapter. The range is from 0 to 255, with 0 as the default. (Worksheet item #13)

    Adapter service status: This field should display In Service.

    Number of local service access points: Keep this field at the default value of 2.

    Terminate peer link if no active APPC session: This field does not apply to the gateway.

  6. Press Esc.

  7. Choose Yes to save your settings and display the Data Link Adapter Definitions list containing the definition you just saved.

  8. Press Esc to return to the Configure NetWare for SAA menu.

Create a PU Profile
NetWare for SAA uses the PU Profile to distinguish the GroupWise Gateway for OfficeVision/VM from other applications using NetWare for SAA. Each application must have its own PU profile.

To create a PU profile,

  1. Choose Configure for Host Connections.

  2. Choose Configure Host PU Profiles.

  3. Press Insert.

  4. Enter a profile name. You may want to use a name related to the gateway host connection.

  5. Press Enter.

    Modify only those fields explained in the following steps.

  6. Select Configure default LU attributes.

  7. Choose LU Category.

  8. Choose Dedicated to specify a category and return to the Configure Default LU Attributes form.

  9. Choose LU Type.

  10. Choose LUx (LU type 0, 1, 2, or 3) to specify a category and to return to the Configure Default LU Attributes form.

  11. The remaining fields retain their default values. Press Esc to return to the Configure PU Profile form.

  12. Choose Logical Adapter Name and press any key to display a list containing each defined adapter.

  13. Choose the name you assigned the network adapter, then press Enter to return to the Configure PU Profile form.

    Because the adapter definition was configured as a token ring connection, the Configure PU Profile form has fields for defining the token ring adapter.

  14. Choose Maximum Frame Size to Transmit Inbound.

  15. Choose 1033 to return to the Configure PU Profile form.

  16. Choose Node ID (Block ID/PU ID) and enter the ID block (Worksheet item #4) and ID num (Worksheet item #5) from the worksheet. In the worksheet example 05D is the ID block and 50009 is the ID num.

  17. Choose 802.2 Remote Node Address and enter the address of the mainframe host token ring adapter (Worksheet item #8).

    The remaining fields keep their default settings.

  18. Press Esc.

  19. Choose Yes to save the PU connection and display the following.

  20. Press Esc.

  21. Press Esc twice to return to the Configure NetWare for SAA menu.

You can now install and configure the GroupWise Gateway for OfficeVision/VM. To exit CSCON, press Esc twice, or to restrict the users who can access this profile, continue with Assigning Authorized Users (Optional).

Assigning Authorized Users (Optional)
You can authorize users to administer the PU profile of the gateway. If you do this, you must provide the user ID and password of the authorized user when you configure the gateway in the next chapter. At least one of the authorized users must be included when you configure the gateway in the next chapter.

If you have exited CSCON,

To assign authorized users,

  1. Choose Configure for Host Connections.

  2. Choose Configure Dedicated LUs.

  3. Choose the PU profile you created earlier.

  4. Press the Tab key.

  5. Press Insert.

  6. Select a user and press Enter to add that user to the Authorized Users list. Repeat steps 5 and 6 for each user you want to add.

  7. Press Esc until you exit CSCON.

Load NetWare for SAA
After you have loaded COMMEXEC.NLM and configured it by using CSCON.EXE, you can load NetWare for SAA by typing load nwsaa at the system console:

Communications Link for the OS/2 Gateway

The communications link requires both a physical connection and a logical connection. The physical connection is established through the adapter (token ring or SDLC) and the communication medium (direct wire or modem) connecting the gateway station to the mainframe host. The logical connection is established through the software, which must be installed on the gateway station and configured to work with your adapter and network protocol.

Set Up the LAN Adapter and Protocol Support (Token Ring Only)
If you are using a token ring configuration, you must install and configure the IBM** LAN Adapter and Protocol Support (LAPS). If you are not using a token ring configuration, proceed to Set Up the IBM Communications Manager/2 for SDLC later in this chapter.

To install LAPS,

  1. Insert the LAPS diskette into a disk drive. In this example, the A drive is used.

  2. Open an OS/2** window from your OS/2 desktop.

  3. Change to the drive where the LAPS diskette resides. In this example, the A drive is used.

  4. Type laps, then press Enter to display the LAN Adapter and Protocol Support banner window.

  5. Choose Install to display the Target Drive window.

  6. Enter the letter of the drive where the LAPS files are to reside in the Target drive field, then press Enter.

  7. Choose OK to start the installation. When all the files have been transferred, the Installation Complete window is displayed.

  8. Choose OK to return to the LAN Adapter and Protocol Support banner window.

  9. Choose Configure to display the Configuration window.

  10. Select Configure LAN transports {short description of image} choose Continue to display the Configure Workstation window.

  11. Fill in the fields:

    Network Adapters: Choose your network adapter, then choose Add. The possible types of network adapters are displayed in the Current Configuration list.

    HINT: Choose Edit if you must modify the adapter configuration to set the locally administered network adapter address and other parameters specified by your network administrator.


    Protocols: Choose IBM IEEE 802.2 {short description of image} choose Add. The protocol is displayed in the Current Configuration list.

    This selection is required for the GroupWise Gateway for OfficeVision/VM.

  12. Choose OK to return to the LAN Adapter and Protocol Support banner window.

  13. Choose Exit to display the CONFIG.SYS Updates window.

  14. Choose Continue to update your CONFIG.SYS file and to display the CONFIG.SYS Updated window.

  15. Choose OK to display the Exiting LAPS window.

  16. Choose Exit to return to the OS/2 window.

  17. Type exit to return to your desktop.

At this point, you have installed the LAPS. Proceed to Set Up the IBM Communications Manager/2 for Token Ring for information about how to install the IBM Communications Manager/2.

Set Up the IBM Communications Manager/2 for Token Ring
The logical connection between the LAN and the mainframe is established through the IBM Communications Manager/2 (Comm Manager). This section explains how to configure Comm Manager to work with the GroupWise Gateway for OfficeVision/VM. For detailed instructions about how to install Comm Manager, see the IBM Communications Manager/2 Reference manual.

The item numbers in parentheses refer to items on the Configuration Worksheet.

To install Comm Manager,

  1. Insert Diskette #1 into a disk drive. In this example, the A drive is used.

  2. Choose Drive A from your OS/2 desktop to display the Drive A - Icon View window.

  3. Choose CMSETUP.EXE to display the CMSETUP window.

  4. Choose OK to display the Communications Manager/2 Setup window. At this point, the program copies temporary files to your hard disk. These files are deleted when the installation is complete. When the files have been transferred, the Installation Notes window is displayed.

  5. Choose Continue to display the Target Drive Selection window. This window shows the partitions and the available disk space on your local drive.

    The Note section of this window informs you that the files have been copied to a subdirectory called CMLIB, which is not a user-defined directory.

  6. Choose OK to display the Communications Manager Setup window.

  7. Choose Setup to copy the files to your hard disk.

  8. Choose OK after you have inserted each diskette that is requested. When the files have been copied, the Open Configuration window appears.

  9. Fill in the fields:

    Configuration (Required): Choose this field to enter the name of the configuration file you are creating. Comm Manager saves the values you record in a configuration file, which it uses to establish your link to the mainframe. You can enter any name in this field, but you will want to use TOKEN if you are using a token ring configuration or SDLC if you are using an SDLC adapter. The name cannot exceed eight characters.

    Description (Optional): Choose this field to type a line of descriptive text to further define the configuration file.

    Directory: This list displays the target drive with the CMLIB directory.

    Directories (Optional): Use this field if you need to locate the CMLIB directory.

    Configurations (Optional): This field displays any configuration files you have created.

  10. Choose OK to display the OS/2 Communications Manager window.

  11. Choose Yes to create the configuration file and to display the second OS/2 Communications Manager window.

  12. Choose Yes to run your configuration file from your workstation and to display the Communications Manager Configuration Definition - TOKEN window. The name you assigned this configuration file appears in the title bar of the window.

  13. Choose your network topology from the Workstation Connection Type list box.

  14. Choose LUA APIs from the Feature or Application list box to display a diagram in the bottom portion of the window.

  15. Choose Configure to display the Communications Manager Profile List Sheet window.

    Comm Manager requires several fields on the following screens to have values assigned to them. Most of these fields do not apply to the the gateway, but they cannot be left blank or Comm Manager will not function properly.

  16. Select the first item on the profile list {short description of image} choose Configure to display the Token Ring or Other LAN Types SDLC Adapter Parameters window.

  17. Enter any value in the C&SM LAN ID field. This field is not relevant to the GroupWise Gateway for OfficeVision/VM, but it cannot be left blank or Comm Manager will not function properly. In the worksheet example, ANYID is used. All other fields in this window can maintain their default values.

  18. Choose OK to return to the Communications Manager Profile List Sheet window.

    A check mark is placed by each item on the list after it has been successfully configured.

  19. Select SNA Local Node Characteristics, then choose Configure to display the Local Node Characteristics window.

  20. Fill in the fields:

    Network ID: Enter any user-definable name. This field is not relevant to the GroupWise OfficeVision/VM Gateway, but it cannot be left blank or Comm Manager will not function properly.

    Local node name: Enter any user-definable name. This field is not relevant to the GroupWise Gateway for OfficeVision/VM, but it cannot be left blank or Comm Manager will not function properly.

    Node type: Select End node - no network node server.

    Your network node server address (hex): Leave this field blank.

    Local node ID (hex): Leave these fields at their default values.

  21. Choose OK to return to the Communications Manger Profile List Sheet window.

  22. Select SNA connections {short description of image} choose Configure to display the Connections List window.

  23. Choose To Host from the Partner Type Group box.

  24. Choose Create to display the Adapter List window.

    Make sure the correct adapter number is displayed in the Adapter number field. If you configure one adapter card with Comm Manger, the value of this field must be set to 0. If you configure multiple adapter cards with Comm Manager, the first card is assigned 0, and the second card is assigned 1.

  25. Select your network adapter from the Adapter Type list box {short description of image} choose Continue to display the Create a Connection to a Host window.

  26. Fill in the fields:

    Link name: Type any name in this field. This field is not relevant to the gateway.

    LAN destination address (hex): Type the token ring address of the mainframe host communication controller. (Worksheet item #8)

    This address must match your mainframe token ring address.

    Partner network ID: Leave this field blank.

    Partner node name: Leave this field blank.

    Local PU name: This field is dimmed and cannot be changed. It is not relevant to the gateway.

    Node ID (hex): Type the IDBLK and IDNUM from the major node definition. (Worksheet item #4 and Worksheet item #5)

    Use this host connection as your local point support: Leave this field unchanged.

    APPN support: Leave this field unchanged.

    Optional Comments: Type any comments that can help you to further identify this connection.

  27. Choose OK to display the Connections List window. The link name list, adapter type, and adapter number are displayed in the window.

  28. Choose Close to return to the Communications Manager Profile List Sheet window.

  29. Select SNA LUA APIs {short description of image} choose Configure to display the LUA APIs Parameter window.

  30. Fill in the fields:

    LU name: Type the link ID from the mainframe host. (Worksheet item #11) In the worksheet example, OVVMNJE1 is used.

    Host link name: This field is carried over from the Link name field you filled in when you configured the SNA connections. Leave this field unchanged.

    NAU address: Type the LU LOCADDR value from the VTAM** Definition Table. (Worksheet item #7) In the worksheet example, 02 is used.

    Optional comments: Enter any comments that can help you to further define the LUA API parameter.

  31. Choose Configure to save these values.

    When the screen reappears, the values you entered are blank. This is normal; it does not mean your entries have been lost.

  32. Choose Close to return to the Communications Manager Profile List Sheet window. At this point, each item on the list should be checked. If one is not, select it, then complete each window as explained above in step 28.

  33. Choose Close to return to the Communications Manager Configuration Definition-TOKEN window.

  34. Choose Close to display the OS/2 Communications Manager window, which informs you of the need for additional files.

  35. Choose Yes to display the Install window.

    All the fields in this screen can remain at their default values.

  36. Choose OK to display the Change CONFIG.SYS window.

  37. Select Change CONFIG.SYS to allow the Install program to install the required device drivers and search paths in your CONFIG.SYS file.

    or

    Select Do Not Change CONFIG.SYS if you want to manually add the required changes to your CONFIG.SYS file. The changes you need to make to your CONFIG.SYS file are stored in the \CMLIB\CONFIG.CM1 file.

  38. Choose OK for Comm Manager to load the necessary files for your specific configuration. The Insert Diskette window appears, prompting you to insert the proper diskettes.

    When the files have been copied, the Communications Manager Completion window is displayed.

  39. Choose Close to return to the Drive A - Icon View window.

You have now successfully installed Comm Manager. If you chose to update your CONFIG.SYS file, you must shut down your system and reboot your computer to start the program. If you did not update your CONFIG.SYS file, you must do so before Communications Manager can start. The changes you need to make to your CONFIG.SYS file are stored in the \CMLIB\CONFIG.CM1 file.

Set Up the IBM Communications Manager/2 for an SDLC Link
This section provides the steps for installing the IBM Communications Manager/2 (Comm Manager) when you are using an SDLC card to link to the mainframe. For more information about installing Comm Manager, see the IBM Communications Manager/2 Reference manual.

Before you install and setup Comm Manager, be aware of the following:

The item numbers in parentheses refer to items on the worksheet.

To install Comm Manager for an SDLC connection,

  1. Insert Disk 1 into a drive. For this example, drive A is used.

  2. Type a:cmsetup at an OS/2 window to display the IBM logo screen.

  3. Select OK to continue to display the Communications Manager/2 setup screen. At this point, the Install program copies temporary files to the hard drive. When the files have been copied, the Installation Notes screen is displayed.

  4. Choose Continue to display the Target Drive Selection screen.

  5. Select your target drive in the Drive window to create a directory called CMLIB and to display the Communication Manager Setup screen.

  6. Choose Setup to display the Communications Manager/2 Setup screen.

  7. Choose Setup to start the file transfer process. Insert the disks as requested on the screen. When this process is over, the Open Configuration screen is displayed.

  8. Fill in the fields:

    Configuration: Enter a name for the configuration file. The name cannot exceed eight characters.

    Description: Enter descriptive text that may further define the configuration file. This step is optional.

    Directory: This field displays the target drive with the CMLIB subdirectory.

  9. Choose OK to display the Configuration Confirmation screen.

  10. Choose Yes to create the configuration file and to display the OS/2 Communications Manager screen.

  11. Choose Yes to confirm that the C:\CMLIB\XXXXX configuration file will be used for this workstation and to display the Communications Manager Configuration Definition screen.

  12. Choose SDLC from the Workstation Connection Type window.

  13. Choose LUA APIs from the Feature or Application window. A graphic will be displayed at the bottom of the screen.

  14. Choose Configure to display the Communications Manager Profile List Sheet screen.

  15. Select DLC - SDLC from the list to display the SDLC DLC Adapter Parameters screen.

  16. Fill in the fields:

    Adapter: Enter the number of the SDLC adapter. The default is zero.

    Line type: Choose Switched or Non-switched, depending on your physical line type.

    Link station role: Choose Secondary.

    Free unused links: Disable this option.

  17. Fill in these fields for the Additional Parameters window:

    Link station role parameters: This field does not need to be modified.

    Modem parameters: The Line Mode field is half-duplex or full-duplex. You may need to change the NRZI option (Worksheet item #2), depending on your modem type. All other fields retain their default values.

    Window count parameters: Do not modify this field.

  18. Choose OK to return to the Communications Manager Profile List Sheet screen.

  19. Choose SNA Local Node Characteristics from the list to display the Local Node Characteristics screen.

  20. Choose Configure, then fill in the fields:

    Network ID: Enter any value. This field does not relate to the gateway, but Comm Manager will not run properly if it remains empty.

    Local node name: Enter any value. This field does not relate to the gateway, but Comm Manager will not run properly if it remains empty.

    Node type: Choose End node - no network node server.

    Local node ID: You can leave this field blank.

  21. Choose OK to return to the Communications Manager Profile List sheet.

  22. Choose SNA Connections from the list to display the Connections List screen.

  23. Choose Configure to display the connection list.

  24. Choose To Host from the Partner Type buttons.

  25. Choose Create to display the Adapter List screen.

  26. Choose your SDLC adapter type from the list.

  27. Choose Continue to display the Create a Connection to a Host screen.

  28. Fill in the fields:

    Link name: Enter any value. This field does not relate to the gateway, but Comm Manager will not run properly if it remains empty.

    Partner network ID: You can leave this field blank.

    Partner node name: You can leave this field blank.

    Local PU name: Accept the default value.

    Node ID (hex): Accept the default value. If your SDLC connection is using a major node definition, the IDBLK (Worksheet item #4) and IDNUM (Worksheet item #5) must be used.

  29. Choose OK to return to the Connections List screen. The Link Name field should display the type of adapter you selected.

  30. Choose Close to return to the Communications Manager Profile Lists Sheet screen.

  31. Choose SNA LUA APIs to display the LUA API Parameters screen.

  32. Choose Configure to display the LUA API's Parameters screen.

  33. Fill in the fields:

    LU name: Enter the Link ID (Worksheet item #11) from the mainframe host.

    Host link name: Use the default.

    NAU address: Enter the LU LOCADDR value (Worksheet item #7) from the VTAM Definition Table.

  34. Choose Configure; the entries disappear but are saved.

  35. Choose Close to return to the Communications Manager Profile Lists Sheet screen.

    The OS/2 Communications Manager screen is displayed. At this point, the Install program requests the remaining disks.

  36. Choose OK to display the Install screen.

Test the Communications Link
Before you install the gateway, verify your mainframe connection. To check the status of the connection,

  1. At a VM terminal, log on using the operator account.

  2. Choose Start Communications in the Communications Manager/2 - Icon View window.

  3. If the connection is good, the operator account displays a message that states the connection has been established.

  4. Close the Communications Manager/2 - Icon View window to return to the OS/2 window.

  5. Disconnect from the operator account.

Proceed to the next chapter, Chapter 4: Install the Gateway for instructions about how to install the GroupWise Gateway for OfficeVision/VM.

* Novell trademark. ** Third-party trademark. See Trademarks for more information.