home *** CD-ROM | disk | FTP | other *** search
-
- +-------------------------------------------------------------+
- |II07093 |
- | |
- | COMMUNICATIONS MANAGER/2 INFORMATION APAR |
- | |
- | INSTALLING OS2, COMMUNICATIONS MANAGER/2 |
- | LAPS, AND NOVELL ON THE SAME WORKSTATION |
- | |
- |LAST UPDATE: 07/08/93 BY: RHB |
- | |
- +-------------------------------------------------------------+
- |
- |1. 07/08/93 REFERENCE PUBLICATIONS.
- | 1. ASKQ document G010367 / Flash 2129
- | 2. OS/2 and Communications Manager/2
- | installation documentation.
- | 3. NOVELL NETWARE INSTALLATION DOCUMENTATION
- | 4. LAPS FROM INSTALLED ES1, NTS2, TCP/IP, OR LS (V2+)
- | 5. IBM Personal Systems Technical Solutions, April 1992
- |
- |
- | IBM OS2 EE 1.3 (CSD 5050+) or Version 2.X base code,
- | Communication Manager 2, LAPS from either ES (previously
- | installed), NTS/2, or Lan Services (Version 2 or 3) and
- | Novell NetWare Version 3.1X are assumed. There may be
- | some variation to this overview otherwise.
- |
- |2. 07/03/93 INSTALLING OVERVIEW.
- |
- | This information is offered as a high-level overview
- | to assist in installing Novell Netware
- | requester and Communiations Manager/2
- | to coexist in the same machine. Consult the appropriate
- | publications for each product for complete information. It
- | is recommended to do the planning tasks (fill out the
- | worksheets, etc..) suggested by the individual products
- | prior to their installation.
- |
- | A. Install OS/2 (base operating system). Make
- | sure OS/2 is operable with no unresolved errors.
- |
- | B. The communication adapters (SDLC, 3270, LAN, etc...)
- | should be physically installed in the workstation
- | being configured.
- | A version of LAPS, (LAN Adapter and Protocol Support)
- | is used to install LAN adapter card interfaces. LAPS
- | can be installed by one of the following methods:
- |
- | -If Extended Services was installed prior to the
- | installation of Communications Manager/2, then the
- | installation of Communications Manager/2 will remove
- | the Communications Manager portion of ES1.
- | Communication Manager/2 will keep the LAPS
- | portion of Extended Services which can be used to
- | install the adapter cards used by your LAN.
- |
- | -If NTS/2, IBM Network Transport Services/2 (NTS/2) is
- | used then programming interfaces (NetBIOS, IEEE
- | 802.2 and Network Driver Interface) are provided that
- | can be used to install these adapter cards.
- |
- | -If Lan Services Version 2 or Version 3 is available
- | then a version of LAPS that can be used by
- | Communications Manager/2 is shipped with the LAN
- | Server product (one way to execute is to enter LAPS
- | at a command line).
- |
- | C. Install Communications Manager/2. The CSD level should
- | be WR06050 (apply Communications Manager/2 ServicePack
- | if needed). Communications Manager should be configured
- | to support the required communications, and the final
- | VERIFY must be completed with no unresolved errors.
- |
- | D. CONFIG.SYS and PROTOCOL.INI should now be saved to a
- | secure place (preferably not on the boot drive). These
- | can be used if needed to return to this level of
- | installation. Copy CONFIG.SYS to CNFIGNTV.SYS and
- | PROTOCOL.INI to PROTONTV.INI (Native CONFIG.SYS and
- | PROTOCOL.INI) for future reference.
- |
- | E. There are two Lan Support modules commonly used for
- | this configuration (LANSUPP (IBM) or ODINSUPP
- | (NOVELL)). The planning tasks done earlier should help
- | to decide which one is right for you. The OS/2 Lan
- | Requester code (if used) should be installed now. The
- | Novell Requester code should be installed last. IBM
- | Flash 2129 (Document ID G010367) shows the recommended
- | appearance of the CONFIG.SYS, PROTOCOL.INI, and the
- | NET.CFG for both Lan Support Modules. PROTOCOL.INI
- | and NET.CFG must include the LAA address if used.
- | ("ERROR GETTING CONNECTION ID error 880F, NWD0115" will
- | be seen at startup if LAA is not consistant)
- |
- | The NTS/2 product includes an additional protocol,
- | ODI2NDI. This protocol has been tested with LANSUPP.
- | ODI2NDI Protocol should be installed after the
- | successful installation of the NetWare requester.
- |
- | The NTS/2 product includes an additional protocol,
- | ODI2NDI. This protocol has been tested with LANSUPP.
- | ODI2NDI Protocol should be installed after the
- | successful installation of the NetWare requester.
- |
- | When the changes are complete, shut down the
- | workstation and reboot (a "cold" boot to reset the
- | adapter is recommended).
- |
- | F. The installation is now complete. Copies of the current
- | CONFIG.SYS, PROTOCOL.INI, and NET.CFG need to be saved
- | after the the reboot to be used for future reference.
- | Copy CONFIG.SYS to CNFIGREF.SYS, PROTOCOL.INI to
- | PRTCLREF.INI, and NET.CFG to NETREF.CFG.
- |
- |3. 07/08/93 IMPORTANT NOTE.
- |
- | Changes made in the Communications Manager/2 configuration
- | will cause a "VERIFY". This VERIFY results in the
- | PROTOCOL.INI (defined for coexistence between ES/1 and
- | NetWare) being modified.
- |
- | The reference copy of the PROTOCOL.INI (named
- | PRTCLREF.INI) should be compared with the PROTOCOL.INI
- | that was changed by the VERIFY. Note the updates made by
- | VERIFY, copy PRTCLREF.INI to PROTOCOL.INI (overwriting
- | PROTOCOL.INI made by VERIFY) then add the updates noted to
- | PROTOCOL.INI. Make sure the CONFIG.SYS and NET.CFG look
- | like the reference copies. A reboot is recommended,
- | although an exit from Communications Manager/2
- | and a restart may be all that is
- | necessary. Insure that the workstation functions as
- | desired. New reference copies should be made. Copy
- | PROTOCOL.INI to PROTCLREF.INI, CONFIG.SYS to CNFIGREF.SYS,
- | and NET.CFG to NETREF.CFG.
- +-------------------------------------------------------------+
- |KEYWORDS: CMINFO 562121301 R100 566933602 R130 562125400 CM |
- |CM2 CM/2 COEXISTENCE NOVELL NETWARE REQUESTER CM2INFO |
- | 0964137 |
- | |
- | |
- | |
- +-------------------------------------------------------------+
-
-