OS/2 Professional

home *** CD-ROM | disk | FTP | other *** search

/ OS/2 Professional / OS2PRO194.ISO / os2 / patches / nts2 / readme.nts < prev next >

Wrap

Text File | 1993-09-13 | 23.5 KB | 726 lines

NTS/2* README (09/93) --------------------- This README file contains information pertaining to the installation, configuration, and operation of NTS/2. It provides compatibility information and other useful tips for the use of NTS/2 functions. The information was collected during the final comprehensive system and compatibility testing phases. It was not finalized before the publications were printed and we want to share this information with you. Also, should you encounter problems with installation or customization of the features of this product, please refer to the section on conferencing tools later in this README for information on how to get help. The following topics are covered in this README: o LAN Server 2.0 upgrade to LAN Server 3.0 o Conferencing Tool for NTS/2 o Tracenames parameter for tracing Netbios o ODI2NDI obtains universal address automatically o LAPS ICON on the desktop o Emulator Configuration for 802.2 VDD o DOS Settings - PC3270* for DOS emulator o DOS Settings - PC3270 for Windows emulator o DOS Settings - Attachmate's Extra! Extended** for DOS o DOS Settings - Attachmate's Extra! Extended** for Windows o DOS Settings - PC Support/400* o DOS Settings - Wall Data's Rumba/400** emulator o DOS Settings - Wall Data's Rumba/3270** emulator o DOS Settings - TCP/IP* for DOS o Application Considerations - TCP/IP* for DOS o Installing Additional Network Drivers Via LAPS o Installing IBM Extended Services V1.0 Remote Data Services o Trademarks and Service Marks Please refer to the following topics in the OS/2* README for general information regarding configuration and restrictions of DOS and Windows applications running under OS/2 supervision: o Application considerations, o Performance of Windows Applications, and o Windows** Version 3.0 Programs Support IBM LAN Server 2.0 upgrade to IBM LAN Server 3.0 -------------------------------------------------- IBM LAN Server 2.0 users upgrading to IBM LAN Server 3.0 need to run NTS/2's LAPS configuration utility to install the proper netbios.os2 file. Failure to perform the following steps can result in unstable LAN Server 3.0 operations. The following steps should be performed: 1. Select the LAPS Icon or invoke LAPS from the \IBMCOM sub-directory. 2. Select Configure from the LAPS logo window and Configure LAN transports. 3. No changes are necessary, however re-configuration may take place at this time. After finishing, select OK. 4. At the LAPS logo window, select Exit. 5. After making the drive selection select Continue... from the CONFIG.SYS Updates window. 6. The system must be shut down and restarted. CONFERENCING TOOL FOR NTS/2 --------------------------- The OS2LAN CFORUM is available to present issues, questions, and problems encountered during the installation, customization and use of NTS/2. The OS2LAN CFORUM is a conferencing tool on the OS/2 Bulletin Board System. To obtain information about the OS/2 Bulletin Board System call 1-800-547-1283 and ask for the welcome package. TRACENAME PARAMETER FOR TRACING NETBIOS --------------------------------------- The TRACENAMES parameter is used to limit tracing activity to the interaction between specified machines. Prior to the offering of this parameter, tracing at the transport level picked up all frame activity on the line, causing the trace buffer to quickly fill with irrelevant frame records. This parameter is ideal for isolating a problem between a server and requester on a large network. Tracing is limited by selecting Netbios names on remote machines using the TRACENAMES parameter. Names may be specified as either a 16 byte ACSII or 32 byte Hex value. Up to 4 names can be selected in either format. The wild card character "*" can be used in the ASCII format for ease of use, or to increase the number of remote names traced if machines have similar names. All names must reside on the same line as the TRACENAMES parameter. Incorrect length or non-valid hex numbers will cause an error and Netbeui will not load. The recommended setting is 0x07FF. NDIS activity will not be filtered if the NDIS bits are activated in OS2TRACEMASK. TRACENAMES works in conjunction with the OS2TRACEMASK parameter and the TRACEOFF parameter already available for Netbeui in NTS/2 version 1.0 and Lan Server 3.0. The OS2TRACEMASK must be set to the necessary non-zero values to activate any Netbios traces. The TRACENAMES parameter must be inserted into the PROTOCOL.INI file using an editor, and is not yet a part of the LAPS config and install tool. TRACENAMES must be placed only in the NETBEUI_nif section. The following example shows the general location and format of the parameter. PROTOCOL.INI [NETBEUI_nif] DriverName = netbeui$ Bindings = IBMTOK_nif ... ... DLCRETRIES = 5 OS2TRACEMASK = 0x07FF TRACENAMES = "req1 " "req2 " "req3 " Other valid TRACENAMES formats are: TRACENAMES = "72617131202020202020202020202000" "req2 *" TRACENAMES = "req*************" "72617131202020202020202020202020" Tracing Specifics. Activity relevant to the remote Netbios name will be traced. This includes NCBs issued with that remote name, as well as all session activity related to that remote name. All statuses from the lower layers are reported whether related to the remote station or not. Frame activity between the remote and local machines is tracked by LSN number after the session is established with the remote machine. A maximum of 12 active sessions will be tracked. Some NCBs are not associated with a remote name or LSN, and are not traced. Add Name Add Group Name Delete Name Cancel LAN Status Session Status Receive Broadcast Datagram Send Broadcast Datagram NCB.Reset is traced even though it is not related to sessions or specific names. Datagrams and other UI frames are traced if they contain a remote name specified in TRACENAMES. Receive.Any type commands will be traced on completion if they report a session event related to a specified remote machine. ODI2NDI OBTAINS UNIVERSAL ADDRESS AUTOMATICALLY ----------------------------------------------- For ODI2NDI.OS2(v1.0), configuration of the NETADDRESS parameter was required, even if the user wanted to use the Network adapter's universally administered address. This requirement is necessary because ODI2NDI must provide the NETADDRESS to the ODI protocol (IPX) before ODI2NDI can obtain the adapter's netaddress via the NDIS interface. ODI2NDI.OS2(v1.1) has been modified so that it will attempt to obtain the Network adapter's universal address automatically when the NETADDRESS parameter has not been configured for ODI2NDI.OS2. To take advantage of this enhancement, some manual modification of CONFIG.SYS is required. First, configure ODI2NDI for a Network adapter MAC using the LAPS configuration utility as usual. Next, manually perform the following updates to CONFIG.SYS: 1) Locate the Network adapter's MAC device driver statement in CONFIG.SYS. For example, for IBM Token Ring Network Adapters, the MAC device driver statement is: DEVICE=C:\IBMCOM\MACS\IBMTOK.OS2 2) Position the the MAC device driver statement after the PROTMAN.OS2 device driver statement, but before the ODI2NDI.OS2 device driver statement in CONFIG.SYS. An example CONFIG.SYS fragment follows: : : DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM : : DEVICE=C:\IBMCOM\MACS\IBMTOK.OS2 : : REM --- NetWare Requester statements BEGIN --- DEVICE=C:\NETWARE\LSL.SYS RUN=C:\NETWARE\DDAEMON.EXE device = C:\ibmcom\protocol\odi2ndi.os2 : : 3) Save the modified CONFIG.SYS. You must restart your computer for the change to take effect. The manual updates to CONFIG.SYS only need to be done the first time the ODI2NDI protocol is configured for a Network Adapter MAC. Modifying ODI2NDI or MAC parameters does not require that the manual updates to CONFIG.SYS be done again. NOTE: This enhancement will NOT work with ALL Network adapters. If the enhancement does not work with your Network adapter, message LT80227 will be displayed when you start your computer. This message will also be logged in the LANTRAN.LOG file located in the IBMCOM subdirectory. If message LT80227 occurs, use the LAPS configuration utility to configure the NETADDRESS for ODI2NDI.OS2. The ODI2NDI.OS2 device driver will automatically obtain the adapter's permanent address from the MAC if the NETADDRESS parameter is not configured in the ODI2NDI section of the PROTOCOL.INI file. It was an requirement that the user configure an network address when configuring ODI2NDI (IBM NetWare requester support) device driver. LAPS ICON ON THE DESKTOP ------------------------ After installing and configuring NTS/2's LAN Adapter and Protocol Support (LAPS) on a OS/2 2.x system, a LAPS ICON is placed in the System Setup container. When doubled clicked, it brings up the LAPS installation/configuration utility. EMULATOR CONFIGURATION FOR 802.2 VDD ------------------------------------ To make your emulator easier to use, we recommend creating an icon on your OS/2 desktop for your emulator. In the discussions below relating to emulator settings, D:\EMULPATH refers to the drive and path of where your emulator program is installed. CFGFILE refers to the name of your emulator configuration file. The path and configuration file name of your particular emulator will be different from the examples below. Notes concerning Windows Emulators ---------------------------------- Note 1 - If a Windows emulator will not successfully start while another Windows emulator is running it may be necessary to start the emulators in reverse order. Note 2 - If a Windows emulator will not successfully start while another Windows emulator is running it may be necessary to toggle (Ctrl-Esc) back and forth to the OS/2 desktop or it may be necessary to minimize the running emulator session before starting the second emulator. Note 3 - It is not possible to run two WinOS2 sessions while using XGA video mode. Refer to the OS/2 README for additional information on restrictions using WinOS2 and XGA. DOS Settings - PC3270* for DOS emulator -------------------------------------- 1. On the Program panel, set the following parameters: Path/Filename = D:\EMULPATH\CFGFILE.BAT Parameters = blank Working Directory = D:\EMULPATH 2. On the Session panel, select DOS Full Screen. 3. Before attempting to run PC3270 for DOS, you must edit your CFGFILE.BAT file, and add COMMAND.COM as the last line in the file. This must be done every time you change your emulator configuration. Failure to add COMMAND.COM to your .BAT file will cause PC3270 to exit when it attempts to return control to DOS. DOS Settings - PC3270 for Windows emulator ------------------------------------------ PC3270 for Windows can run either as a regular Windows program (inside a Win-OS/2* session), or it can run 'seamlessly.' Seamless means the PC3270 windows appear on top of the OS/2 desktop directly, instead of appearing inside a Win-OS/2 command prompt. To run PC3270 as a Win-OS/2 application: 1. Create a file called CFGFILE.BAT. This file should look like this: @ECHO OFF COPY D:\EMULPATH\CFGFILE.CNF D:\EMULPATH\$$TEMP$$.BAT > NUL CALL D:\EMULPATH\$$TEMP$$.BAT ERASE D:\EMULPATH\$$TEMP$$.BAT CALL D:\EMULPATH\SOMEFILE %1 %2 %3 %4 %5 %6 %7 %8 %9 2. Create another file called SOMEFILE.BAT (this file is referenced in CFGFILE.BAT: @ECHO OFF C:\OS2\MDOS\WINOS2\WINOS2 D:\EMULPATH\PCSPDOS.EXE -END 3. On the Program panel, set the following parameters: Path/Filename = D:\EMULPATH\CFGFILE.BAT Parameters = blank Working Directory = D:\EMULPATH 4. On the Session panel, select DOS Full Screen. To run PC3270 Seamlessly: 1. Create a file called CFGFILE.BAT. This file should look like this: @ECHO OFF COPY D:\EMULPATH\CFGFILE.CNF D:\EMULPATH\$$TEMP$$.BAT > NUL CALL D:\EMULPATH\$$TEMP$$.BAT WINOS2.COM PCS3270.EXE 2. On the Program panel, set the following parameters: Path/Filename = D:\EMULPATH\PC3270W.EXE Parameters = blank Working Directory = D:\EMULPATH 3. On the Session panel, select Win-OS/2 window, click on Separate Session, then click on Win-OS/2 Settings. 4. On the Win-OS/2 Settings panel, add the following to the end of the DOS_SHELL statement: /C D:\EMULPATH\CFGFILE.BAT Note - If you start PC3270 for Windows, and get a message saying there is invalid TSR information, then edit the CFGFILE.CNF file and change the line 'REM TSR=N' to 'REM TSR=Y.' DOS Settings - Attachmate's Extra! Extended** for DOS ----------------------------------------------------- 1. On the Program panel, set the following parameters: Path/Filename = D:\EMULPATH\CFGFILE.BAT Parameters = blank Working Directory = D:\EMULPATH 2. On the Session panel, select DOS Full Screen. 3. Before attempting to run Extra! for DOS, you must edit your CFGFILE.BAT file, and add COMMAND.COM as the last line in the file. This must be done every time you change your emulator configuration. Failure to add COMMAND.COM to your .BAT file will cause Extra! to exit when it attempts to return control to DOS. Note - It may be necessary to run the VDM configuration utility, LTSVCFG, with the P=x parameter where x is a nonzero value indicating the number of half seconds the deadman timer will wait before expiring. This will be necessary if the emulator looks like it is hung. Typically this value should be set to 2 if needed. DOS Settings - Attachmate's Extra! Extended** for Windows --------------------------------------------------------- 1. Create a file called EXTRA.BAT. This file should look like this: @ECHO OFF C:\OS2\MDOS\WINOS2\WINOS2 2. On the Program panel, set the following parameters: Path/Filename = D:\EMULPATH\EXTRA.BAT Parameters = blank Working Directory = D:\EMULPATH 3. On the Session panel, select DOS Full Screen. Note 1 - The Extra! for Windows installation program normally modifies the AUTOEXEC.BAT file to add its directory to the PATH statement, and to add a DLCINTFC statement if Lan support is used. This information is also needed when running under OS/2. We suggest you keep this information in your AUTOEXEC.BAT file, exactly as Extra! for Windows placed it. Alternatively, you can add the DLCINTFC statement to your EXTRA.BAT file instead of adding it to AUTOEXEC.BAT. DOS Settings - PC Support/400* ------------------------------ PC Support will not run correctly in DOS Emulation mode. To run PC Support, you must start a version of DOS (such as DOS 5.0, etc.) that will run PC Support. Please refer to the Master Help Index of OS/2 for information on how to start a specific version of DOS. Search for 'Starting DOS.' When you create a diskette or diskimage for a specific version of DOS, you must insure the CONFIG.SYS file for that DOS version loads the following device drivers: DEVICE=C:\IBMCOM\PROTOCOL\LANVMEM.SYS DEVICE=D:\EMULPATH\EIMPCS.SYS DEVICE=D:\EMULPATH\ECYDDX.SYS In addition, you may want to create an AUTOEXEC.BAT file for your specific DOS version that automatically starts PC Support. To do this, invoke STARTPCS.BAT from your AUTOEXEC.BAT file. 1. On the Program panel, set the following parameters: Path/Filename = * Parameters = blank Working Directory = D:\EMULPATH 2. On the Session panel, select DOS Full Screen, then click on DOS Settings. 3. On the DOS Settings panel, set the following parameters: DOS_STARTUP_DRIVE = A:\ KBD_CONTROL_BYPASS = ALT_ESC In this example, DOS_STARTUP_DRIVE is set to A:\ with the assumption you are loading the specific DOS version from diskette. If you load the specific DOS version from a diskette image file on your hard drive, update the DOS_STARTUP_DRIVE accordingly. Note 1 - The PC Support installation program may update the CONFIG.SYS file and add two device drivers 'EIMPCS.SYS' and 'ECYDDX.SYS.' If these statements are in your CONFIG.SYS, remove them. Under OS/2, these statements will instead be loaded from your bootable DOS diskette. Note 2 - Each Virtual DOS Machine (VDM) will need a separate APPC controller on the AS/400. The controllers can be exactly the same except for the LAN destination service access point (LAN DSAP: 08). A line in the CONFIG.PCS needs to contain a matching TRSS entry (TRSS 08). Note 3 - It is necessary to run the VDM configuration utility, LTSVCFG, with the P=x parameter where x is a nonzero value indicating the number of half seconds the deadman timer will wait before expiring. Typically this value should be set to 1 for using a single VDM and increased to 4 if additional VM Boot sessions are active. When additional VM Boot sessions are active it is recommended to decrease the MAXWAIT parameter in CONFIG.SYS to 1 second. Note 4 - When running more than 2 sessions in a stress environment it may be necessary to obtain the OS/2 2.0 Service Pak. Note 5 - For valuable information required for operating PC Support/400 in a VDM, please reference IBM publication GG24-3856 entitled "Using DOS PC Support/400 in OS/2 2.0 Virtual DOS Machines". DOS Settings - Wall Data's Rumba/400** emulator ----------------------------------------------- 1. Create a file called RUMBA.BAT. This file should look like this: @ECHO OFF D:\PCS\STARTRTR D:\PCS\CONFIG.PCS C:\OS2\MDOS\WINOS2\WINOS2 In this example, D:\PCS is the directory where PC Support is installed. Rumba/400 requires PC Support in order to run. 2. On the Program panel, set the following parameters: Path/Filename = D:\EMULPATH\RUMBA.BAT Parameters = blank Working Directory = D:\EMULPATH 3. On the Session panel, select DOS Full Screen. DOS Settings - Wall Data's Rumba/3270** emulator ------------------------------------------------ 1. Create a file called RUMBA.BAT. This file should look like this: @ECHO OFF D:\EMULPATH\WDTOKTSR.EXE /R=16 /T=8 C:\OS2\MDOS\WINOS2\WINOS2 The WDTOKTSR.EXE file is required by Rumba in order to use Lan support. Refer to the Rumba program documentation for more information about command line parameters. We have found the above parameters work in most cases. 2. On the Program panel, set the following parameters: Path/Filename = D:\EMULPATH\RUMBA.BAT Parameters = blank Working Directory = D:\EMULPATH 3. On the Session panel, select DOS Full Screen. DOS SETTINGS - TCP/IP* for DOS ------------------------------ Before you can use TCP/IP under OS/2 2.0, you must set up certain DOS settings. To create an icon and initialize the DOS settings, follow these steps: 1. On the Program panel, set the following parameters: o Path/Filename = * o Parameters = Blank o Working Directory = C:\TCPDOS (Assuming TCP/IP was installed on C:\TCPDOS) 2. On the DOS Settings panel, click on 'Session' and set the following parameters: o DOS_DEVICE = C:\TCPDOS\BIN\NETDEV.SYS (Assuming TCP/IP was installed on C:\TCPDOS) APPLICATION CONSIDERATIONS - TCP/IP* for DOS -------------------------------------------- To run TCP/IP over the VDD, it is first necessary to run LTSVCFG.COM with the parameter D=1. This is necessary because TCP/IP uses the direct station link of the 802.2 protocol. If running over adapter 0 then run LTSVCFG D=1, if running over adapter 1 then LTSVCFG / D=1, or if running over adapter 2 then LTSVCFG / / D=1. A slash is used to signify the adapter number. LTSVCFG can be included in the AUTOEXEC.BAT file so it will be executed automatically when you double click on the TCP/IP icon, or it can be run manually from the DOS command prompt. Regardless, LTSVCFG with the D=1 parameter must be run before executing TCPSTART.BAT. When running TCP/IP's file transfer application FTPD and FTP it is necessary to clear the APPEND environment variable on both the server and client machines. This can be done by commenting out the LOADHIGH APPEND C:\OS2;C:\OS2\SYSTEM statement in the AUTOEXEC.BAT file, or by entering APPEND=* at the DOS command prompt. This is necessary because if the files being transferred appear in the APPEND path of the destination machine, the APPEND path will override the specified destination path. INSTALLING ADDITIONAL NETWORK DRIVERS VIA LAPS ---------------------------------------------- There are two ways to install additional network drivers using LAPS in the unattended mode. The first is described at the end of Chapter 3 in the LAN Adapter and Protocol Support Configuration Guide. In this method, files are added to the LAPS diskette image on the code server either in packed or unpacked format. This method is recommended when additional driver requirements are known prior to LAPS installation. Please note that this method may only be used when INSTALL=PRODUCT in the LAPS response file. To install additional drivers via response files after LAPS installation, you must specify INSTALL=ADDITIONAL in the LAPS response file. In this case, all the required network driver files must be stored in a single subdirectory. The /S: parameter of the LAPS invocation must specify the location of that subdirectory. Additionally, the drive on which LAPS is installed must be specified by either the /T: invocation parameter or the TARGET= keyword in the response file. INSTALLING IBM EXTENDED SERVICES V1.0 REMOTE DATA SERVICES ---------------------------------------------------------- The Remote Data Services feature of IBM Extended Services Version 1.0 should be installed using the Basic Configuration and Installation Option from the Extended Services Installation Options menu. This will ensure that the all Extended Services internal data structures are setup to recognize the presence of NTS/2. TRADEMARKS AND SERVICE MARKS ---------------------------- Terms denoted by a single asterisk in this file (*) are trademarks of the IBM Corporation in the United States and/or other countries. These terms include: IBM NTS/2 (acronym for Network Transport Services for OS/2 OS/2 PC SUPPORT PC3270 TCP/IP (acronym for IBM Transmission Control Protocol/ Internet Protocol) WIN-OS/2 Terms denoted by a double asterisk in this file (**) are trademarks of other companies. Other trademarks appearing in this file are owned by their respective companies. Rumba/400 and Rumba/3270 are trademarks of Wall Data Corporation Extra! Extended is a trademark of Attachemate Corporation Windows is a trademark of Microsoft Corporation. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESSED OR IMPLIED, INCLUDING WITHOUT LIMITATION, WARRANTIES OF FITNESS AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY RELATED PATENTS OR COPYRIGHTS. Copyright IBM Corporation, 1992, all rights reserved.