OSOTELIT - OS/2 WARP ENTERPRISE LAN INTEGRATION TEST RESULTS 07/27/95 ================================================================= OS/2 Warp Enterprise LAN Integration Test Results ================================================================= Please Read Entire Document for Full Explanation of Procedures ----------------------------------------------------------------- SYMPTOM This document contains the results from the IBM Enterprise LAN Integration Test (ELITE) organization in Research Triangle Park, NC. RESOLUTION NOTE: Make sure you have a backup of any file you intend to change. Author: Bob Spratt Composed: 11-09-94 09:04 AM Subject: Warp ELITE Report Category: ELITE IBM ENTERPRISE LAN INTEGRATION TEST RESEARCH TRIANGLE PARK, NC IBM OS/2 WARP VERSION 3 REPORT PURPOSE ------- The purpose of this document is to describe the integration testing results of the IBM Enterprise LAN Integration Test (ELITE) laboratory. The information contained in the report is intended to highlight cross product testing performed and draw attention to any specific cross product dependencies. It is intended as a supplement to the product information and publications. The report assumes familiarity with the products involved. TEST INFORMATION ---------------- OS/2 Warp Version 3.0 and OS/2 Warp Version 3.0 with WINOS2 are new versions of OS/2. At the time of this test OS/2 Warp Version 3.0 with WINOS2 was not available (Planned availability is First Quarter 1995 per Announcement Letter 294-667). This report covers the testing performed by the ELITE team on IBM OS/2 Warp Version 3. PRODUCT LEVELS TESTED: ---------------------- o IBM OS/2 Warp VERSION 3: The General Availability level was installed. - Version: 3.0 - Current CSD Level: XR03000 - Component ID: 562260100 TEST OBJECTIVES: o Verify CID installation of OS/2 Warp: - Using NetView Distribution Manager/2 o Verify support of OS/2 Warp with IBM products common to the Enterprise LAN environment. The products tested were: - NetView Distribution Manager/2 (NetView DM/2) 2.1 XR00000 - NetView DM/2 2.00.2 XR00005 (CSD: XR20334) Client - Communications Manager/2 (CM/2) 1.11 WR06150 (CSD: WR06150) - Network Transport Services/2 (NTS/2)-LAN Adapter and Protocol Support (LAPS) 2.20.2 WR07045 (CSD: WR07045) - Distributed Console Access Facility (DCAF) 1.21 UB09790 - DataBase2 for OS/2 (DB2 OS/2) 1.0.1 WR07015 - DataBase2 for OS/2 (DB2 OS/2) 1.20 WR07000 - Distributed Database Connection Services/2 (DDCS/2) 2.20 WR07000 - LAN NetView Management Utilities (LMU) 1.00 LM00200 - LAN Network Manager (LNM) 1.10 LM00004 (CSD: UR42384) - IBM OS/2 LAN Server (LS) 3.00.1 IP07040 - TCP/IP for OS/2 Base kit 2.0 (CSD: UN64092) - TCP/IP for OS/2 Network File System kit 2.0 (CSD: UN57064) - TCP/IP for OS/2 X-Windows System Client kit 2.0 (CSD: UN52842) - System Performance Monitor/2 (SPM/2) 2.00 WR06075 - LAN Station Manager (LSM) 1.01 MB02000 - LAN Distance (LD) 1.10 LD00000 OVERVIEW OF SCENARIOS TESTED: ----------------------------- Verify and exercise OS/2 Warp as a basic server and client using product functions such as host communications, data transfer, and client communications with different client machines. Test coverage included: o NetView DM/2 Installation, and Deinstallation functions, to the clients, as well as catalog functions such as builds and deletes on the server. o LMU Managing, Managed, and Administrator functions on server for the clients o Utilizing 3270 emulator sessions on the clients through CM/2 gateway functions on the server by concurrently sending and receiving files via clients. o Utilizing DCAF gateway, and controlling functions on the server, and the NetBIOS and APPC target functions on the clients. o Creating, Updating, Selecting, and Deleting Tables in the local and remote databases via DB2 OS/2 and DDCS/2. o Concurrently sending and receiving files via clients using LS. o Concurrently utilizing OS/2 file system, memory management, system processes and Desktop (WPS). o Utilize TCP/IP TELNET, FTP, and NFS support. o Utilize Gopher, NR2, FTPPM, TELNET support on Internet. o Monitor LAN using LNM, adding bridge definitions, naming adapters, viewing other side of bridges. o Utilize LD remote connection to access test LAN for 3270 gateway and LAN Requester Access TEST RESULTS: ------------- The following table lists the products tested and the level to which each supports OS/2 Warp. |----------------------------------------------------------------------| | Table 1 (Page 1 of 2). Product Support | |----------------------------------------------------------------------| | PRODUCT | | | | | REQUIREMENTS | VERSION | SUPPORTS | ADDITIONAL REQUIREMENTS | | DB2 OS/2 | 1.0.1 | Y | None | |------------------|---------|----------|------------------------------| | DB2 OS/2 | 1.2 | Y | APAR JR08226 | | CM/2 | 1.11 | Y | None | |------------------|---------|----------|------------------------------| | DCAF | 1.2 | Y | APAR IC08522 | |------------------|---------|----------|------------------------------| | DCAF | 1.1 | Y | APAR IC08511 | |------------------|---------|----------|------------------------------| | DDCS/2 | 2.0.1 | Y | None | |------------------|---------|----------|------------------------------| | DDCS/2 | 2.2 | Y | APAR JR08226 | |------------------|---------|----------|------------------------------| | LD | 1.1 | Y | None | |------------------|---------|----------|------------------------------| | LS | 3.00.1 | Y | None | |------------------|---------|----------|------------------------------| | LNM | 1.1 | Y | None | |------------------|---------|----------|------------------------------| | LMU | 1.0 | Y | None | |------------------|---------|----------|------------------------------| | LSM | 1.01 | Y | None | |------------------|---------|----------|------------------------------| | NetView DM/2, | 2.0, | Y | None | | Client | 2.1 | | | |------------------|---------|----------|------------------------------| | NetView DM/2, CC | 2.1 | Y | NetView DM/2 CSD XR20460, | | | | | DB2 OS/2 | | | | | | | Server | | | 1.2 APAR JR08263 or DB2 | | | | | OS/2 1.0.1 | | | | | | | | | | APAR JR08263 (note 1) | |------------------|---------|----------|------------------------------| | TCP/IP | 2.00 | Y | None | |------------------|---------|----------|------------------------------| | NTS/2 LAPS | 2.20.2 | Y | None | |------------------|---------|----------|------------------------------| | Internet | 2.0 | Y | None | | Connection | | | | | for OS/2 | | | | |------------------|---------|----------|------------------------------| | SPM/2 | 2.0 | Y | APARs IC07207 and IC07111 | |------------------|---------|----------|------------------------------| | | | LEGEND: | | Y = fully supported | | P = partially supported | | N = not supported | |----------------------------------------------------------------------| | | | NOTES: | | | | 1. NetView DM/2 Information APAR II08201 details NetView DM/2 | | support on OS/2 Warp. Please refer to that APAR for more | | information on NetView DM/2 running on IBM OS/2 Warp Version 3. | |----------------------------------------------------------------------| PROBLEMS SPECIFIC TO THE OS/2 WARP ENVIRONMENT The following is the list of problems that were encountered. The list is a by-product breakdown of the problems. 1. OS/2 WARP a. IBM OS/2 Warp Version 3 is not migratable from OS/2 2.0, 2.1 or 2.11. The only supported migration path for OS/2 Warp is from OS/2 for Windows. IBM OS/2 Warp Version 3 with WIN-OS/2 (planned availability in First Quarter 1995) will provide a migration path for existing OS/2 2.x customers. Refer to section "Hints/Samples for Distribution/Installation/ Migration with NetView DM/2" on page 12 for more informa- tion on installation options. RECOMMENDATION: Existing OS/2 2.x customers should consider waiting for the IBM OS/2 Warp Version 3 with WIN-OS/2 release. b. Although the minimum memory necessary to run OS/2 Warp is 4MB, the minimum memory necessary to CID install OS/2 Warp is 6MB. RECOMMENDATION: Install a minimum of 6MB on target machines for CID installation of OS/2 Warp. c. The BONUSPACK products delivered with OS/2 Warp are not CID enabled, with the exception of the Internet Connection. The ELITE team did successfully install the System Information Utility and FAXWORKS using NetView DM/2, but CID return codes and logging was not supported. d. OS/2 Warp does not support an AUTODETECT feature during CID installation for the various PCMCIA chip sets. The current method of installing PCMCIA support during a CID installation requires the administrator to build a response file with the "PCMCIAOptions" keyword equal to "1" and set the "PCMCIA" keyword equal to a value matching the target machine type. Refer to section "Hints/Samples for Distribution/Installation/Migration with NetView DM/2" on page 12 for additional information on CID installation options. The ELITE team tested these options using a ThinkPad 750C. Following a NetView DM/2 install of OS/2 Warp with the proper PCMCIA keywords, the PCMCIA support type installed was actually for a ThinkPad 510. No other PCMCIA capable workstations were tested by the ELITE team. RECOMMENDATION: For PCMCIA Modem and Fax support, the only difference between a ThinkPad 510 and a ThinkPad 750 is in the number of PCMCIA ports. The 510 only has one PCMCIA port while the 750 has two. The following change to the config.sys on the 750 will enable support of both PCMCIA ports. Change the device driver statement for PCMCIA Socket Services from: BASEDEV=IBM2SS01.SYS /s0=1 to: BASEDEV=IBM2SS01.SYS /s0=2 e. When running OS/2 Warp on client machines in our test environment while exercising various CM/2, LS, DB2 and OS/2 functions simultaneously, the workstations experienced a TRAP 000e after 16 to 48 hours. RECOMMENDATION: This problem is under investigation by OS/2 development. 2. CM/2 a. The following APARs are available for CM/2 in the OS/2 Warp environment. The CM/2 problems were opened by the CM/2 compatibility test team in RTP. o APAR JR08190 - FFST/2 causes SYS3175 when viewing message log o APAR JR08223 - TrapE in ACS3ECFG.DLL changing emulator font size o APAR JR08235 - Trap in IDLC performing CMSTOP ABNORMAL o APAR JR08240 - CID install of CM/2 traps using the debug kernel b. The ELITE team received random traps in EPWPSI32.DLL and REMMAIN.EXE during our CM/2 testing. RECOMMENDATION: The FFST/2 APAR JR08190 listed above is a complete refresh of FFST/2. When applied it also corrected the traps found in our testing. 3. DB2 a. The GA level of DB2 OS/2 1.2 will not install on a Warp workstation. RECOMMENDATION: For NVDM/2 installs, the fixes in APAR JR08226 must be used to update the DB2 OS/2 V1.2 code on the CC Server prior to attempting a remote installation. See section "Product Specific Hints and Tips" on page 10 for additional information on APAR JR08226. 4. DCAF a. DCAF target function traps in EQNPMGRE.DLL when the DCAF controlling workstation opens a session via either NETBIOS or APPC. RECOMMENDATION: Apply the following APARs; IC08522 for DCAF 1.2 and IC08511 for DCAF 1.1. 5. FFST/2 a. When installing DB2 and CM/2 on the same workstation at the levels in this test, there is a problem with conflicting FFST/2 levels. DB2 OS/2 1.2 is using 32-bit FFST/2 icons, but CM/2 V1.11 is still using 16-bit icons. When DB2 OS/2 1.2 is installed after CM/2 V1.11 the FFST/2 folder is deleted. When CM/2 V1.11 is installed after DB2 OS/2 1.2, both the 16-bit and 32-bit FFST/2 folders are left on the desktop, but both contain the 16-bit icons. This does not appear to cause any problems. A SYSLEVEL indicates only one FFST/2 and it is at CSD level WR00470, which is the one provided by CM/2. RECOMMENDATION: The missing FFST/2 folder can be recreated by using CMSETUP, Options, and then selecting Recreate folders or by using EPWINST, which creates it for you semi-automatically. This new folder is 16 bit. In the case of two FFST/2 folders, you can drag one of them to the shredder. 6. LNM a. A problem was intermittently encountered during diskette installation of the GA level of LNM 1.1. It is necessary to install the GA level prior to installing the most current PTF level. The problem encountered was that the prompt to insert diskette 2 can be issued before the system is actually finished with diskette 1. If diskette 1 is removed prematurely, this causes additional error messages that the wrong diskette is inserted in the drive and the installation will fail. RECOMMENDATION: The resolution is to leave diskette 1 in the machine until you receive the message "Database is now installed", and insert diskette 2 after that time, even if the prompt for diskette 2 is received earlier. 7. LNME a. LNME V1.0 (CSD UR40624) on OS/2 Warp seemed more sensi- tive to the placement of the LNME device driver statement in the CONFIG.SYS. If the statement "DEVICE = C:\LNME\EVYDD.SYS" was not last in the CONFIG.SYS, OS/2 would report during a reboot that this device driver could not be found. RECOMMENDATION: Moving this device driver to the end of CONFIG.SYS resolved the problem and LNME worked without problems. 8. LSM a. LAN Station Manager detects and reports the workstation operating system level as 2.3. RECOMMENDATION: The resolution to this problem is still under investigation. This is working as designed from an OS/2 Warp perspective. 9. NetView DM/2 a. NetView DM/2 2.0 Server is NOT supported on IBM OS/2 Warp Version 3. The NetView DM/2 2.0 clients are supported. b. The NetView DM/2 2.1 Server and Client are supported on IBM OS/2 Warp Version 3. NetView DM/2 2.1 Server requires the following: o NetView DM/2 2.1 CSD XR20460 - This CSD contains fixes for support of the CDM Dialogs and NVDMBDSK. The official CSD was not available at the time of this report. However, in the interim, for Internal IBM accounts, the fixes will also be available in a FIXWARP Package on the DM2TOOLS repository. Enter the following command to get this package: TOOLS SENDTO ROMEPPC TOOLS DM2TOOLS GET FIXWARP PACKAGE o DB2 OS/2 1.2 APAR JR08263 or DB2 OS/2 1.0.1 APAR JR08263 - This APAR fixes a transmission controller problem with NetView DM/2 2.1 running on OS/2 Warp Version 3.0 with DB2 OS/2 1.2 or DB2 OS/2 1.0.1. This problem applies to DB2 OS/2 non-standalone environments. See section "Product Specific Hints and Tips" on page 10 for additional information on APAR JR08263. RECOMMENDATION: Refer to NetView DM/2 information APAR II08201 for additional information on OS/2 Warp support. c. The NVDMBDSK.EXE utility on a NetView DM/2 2.1 CC Server (GA Level), used to create NetView DM/2 pristine diskettes, puts a "?" in the ADPTERNUM field of the IBMNVDM2.INI file. RECOMMENDATION: A fix is available in the NetView DM/2 CSD XR20460 referred to above. You can also manually edit the IBMNVDM2.INI file on the diskette and replace the "?" with the proper adapter number value. 10. SPM/2 a. SPM/2 Theseus function at the WR06075 CSD level does not work on OS/2 Warp. RECOMMENDATION: IBM Internal users can get the new Theseus level from OS2TOOLS. Customers can request the new Theseus level by requesting the fixes for SPM/2 APARs IC07207 and IC07111. PRODUCT SPECIFIC HINTS AND TIPS The following list contains hints and suggestions for configuring the different products used in this test: 1. OS/2 Warp When OS/2 performs a pristine install, the following line is placed in the CONFIG.SYS: THREADS=256 We have found that the value of 256 is too low, especially for a server class machine running several applications. We ran all of our scenarios with the value: THREADS=1024 2. DB2 OS/2 a. The database manager configuration default parameters were used with the exception of the following, which were changed on the server workstation. These parameters must be tuned for your specific server. These values were used on the OS/2 Warp server used by the ELITE team described in "Warp Server Environment" on page 34. o Maximum shared segments - sqlenseg = 8192 o Communication heap (segments) - comheapsz = 16 o Remote Data Services heap (segments) - rsheapsz = 15 o Maximum remote connections - numrc = 50 b. Packaging and Distribution of DB2 OS/2 APARs JR08226 and JR08172 Table 1 on page 3 lists APAR JR08226 as a prerequisite for DB2 OS/2 1.2 support on OS/2 Warp. When requesting this APAR, you will receive a package of install fixes. In particular it will also include APAR JR08172 which was also used in the ELITE lab to fix migration prob- lems from DB2 OS/2 1.0.1 to DB2 OS/2 1.2. A brief description of the two APARs is as follows: JR08172 SQLSYSTM/DB2SYSTM file not migrated after install. When installing DB2 OS/2 1.2 over a previous DB2 (before WR07025) the config values are not migrated. JR08226 Cannot install DB2 OS/2 1.2 on OS/2 Warp. Attempts to install DB2 OS/2 1.2 will end prematurely. c. Packaging and Distribution of DB2 OS/2 APAR JR08263 Between service/select pacs, all Engine fixes for DB2/2 v1.0 and v1.2 are sent to customers as a package called ENGINEI (or DDCSI for DDCS/2 v2.0 and v2.2). The fix for APAR JR08263 is included in this package. Since ENGINEI is a collection of all ENGINE fixes since the last CSD, the prerequisite for DB2 OS/2 1.0 is CSD/Syslevel WR07025. (WR07025 is a SelectPac and must be installed on top of ServicePac WR07015.) 3. LS It was discovered that the defaults set in the IBMLAN.INI for the LAN requester on a server machine are not sufficient to accommodate a heavy load. Therefore it was necessary to change the parameters under the requester section of the IBMLAN.INI as follows: charcount = 16 chartime = 250 charwait = 3600 keepconn = 600 keepsearch = 600 ; maxcmds = 16 *DEFAULT maxcmds = 160 maxerrorlog = 100 ; maxthreads = 10 *DEFAULT maxthreads = 45 ; maxwrkcache = 64 *DEFAULT maxwrkcache = 640 numalerts = 12 numcharbuf = 10 numservices = 16 ; numworkbuf = 15 *DEFAULT numworkbuf = 50 numdgrambuf = 14 othdomains = printbuftime = 90 sesstimeout = 600 sizcharbuf = 512 sizerror = 1024 sizworkbuf = 4096 NOTE: The values commented by *DEFAULT are the original setting which are modified by the following line. ----------------------------------------------------------------- HINTS/SAMPLES FOR DISTRIBUTION/INSTALLATION/MIGRATION WITH NETVIEW DM/2 This section describes helpful information for distributing and installing IBM OS/2 Warp Version 3 with NetView DM/2 and NetView DM. For information on installing OS/2 Warp and other products tested in the ELITE lab via NetView DM/2 please reference the "Quick Help for Installation of IBM Products via NetView DM/2." This document is available on MKTTOOLS and PCWIN as NVDM2HLP PACKAGE. If you cannot obtain this package via MKTTOOLS or PCWIN then please see section "Report Contact:" on page 35 for further assistance. INSTALLATION OF THE IMAGES ONTO THE CC SERVER Loading the Images on the CC Server from CDROM To load the images on the CC Server from a CDROM, run the following command: XCOPY source_path target_path /S Parameters: source_path - the path to the "root" of the OS/2 diskette images on the CDROM. For example, if the files from the OS/2 installation diskette #1 are in the directory G:\OS2DISKS\DISK_1 on the CDROM, then this parameter would be G:\OS2DISKS. target_path - the path to the target subdirectory to which the OS/2 diskette images are to be copied. Example: XCOPY G:\OS2V30 D:\CID\IMG\OS2\WARP30\GA /S NOTE: The /S parameter means to copy everything including the files and subdirectories residing within subdirectories of the source path. New Format for OS/2 Diskettes Most of the OS/2 Warp Version 3 installation diskettes use a high capacity diskette format called XDF to reduce the number of diskettes and time needed for OS/2 installation. Only the INSTALLATION diskette and Diskette #1 are NOT XDF format diskettes. Since these diskettes are not XDF format, you can modify, add, and delete files on these diskettes using standard commands (DIR, COPY, DISKCOPY, etc.). The remaining diskettes are in XDF format. If you are using an OS/2 Version 2 system for your code server, you MUST make some modifications to your system in order to read the OS/2 Warp Version 3 XDF format installation diskettes. To modify your OS/2 2.x system so that it can read the OS/2 Warp Version 3 XDF format installation diskettes, do the following: o ISA-bus Systems: 1. Rename IBM1FLPY.ADD to IBM1FLPY.OLD in the \OS2 directory. 2. Copy XDFLOPPY.FLT and IBM1FLPY.ADD from diskette #1 to the \OS2 directory. 3. Add the following line to your CONFIG.SYS file: BASEDEV=XDFLOPPY.FLT 4. Reboot o Micro Channel*-bus Systems: 1. Rename IBM2FLPY.ADD to IBM2FLPY.OLD in the \OS2 directory. 2. Copy XDFLOPPY.FLT and IBM2FLPY.ADD from diskette #1 to the \OS2 directory. 3. Add the following line to your CONFIG.SYS file BASEDEV=XDFLOPPY.FLT 4. Reboot NOTE: OS/2 1.x systems cannot be used to read the OS/2 Warp Version 3 XDF format installation diskettes. Installation of the Images from Diskettes using SEIMAGE Images are installed onto the CC Server using the SEIMAGE utility. Before SEIMAGE can be used, you must copy the OS/2 Warp 3.0 CID Utility programs onto the directory structure of your choice. The ELITE Team used the following target CID Utility directory: o D:\CID\EXE\OS2\WARP30\GA o From diskette 1, copy UNPACK.EXE into the OS/2 Warp 3.0 CID Utility directory. The ELITE Team used the following command to copy UNPACK.EXE: COPY A:\UNPACK.EXE D:\CID\EXE\OS2\WARP30\GA\*.* o Use the UNPACK.EXE to unpack the following OS/2 bundle files from diskette 7 into the CID Utility directory: - CID - REQUIRED The ELITE Team used the following command from the D:\EXE\OS2\WARP30\GA CID Utility Subdirectory to unpack the bundles: UNPACK D:\CID\IMG\OS2\WARP30\GA\DISK_7\CID D:\CID\EXE\OS2\ WARP30\GA UNPACK D:\CID\IMG\OS2\WARP30\GA\DISK_7\REQUIRED D:\CID\EXE\OS2\WARP30\GA o UNPACK of "CID" creates the following programs: - SEDISK.EXE - SEIMAGE.EXE - SEINST.EXE - SEMAINT.EXE o UNPACK of "REQUIRED" creates the following programs: - RSPINST.EXE - SAMPLE.RSP Now the CID Utility SEIMAGE.EXE must be run to copy OS/2 Warp 3.0 images. OS/2 Warp Version 3.0 provides support for Microsoft Windows 3.1. OS/2 Warp DOES NOT INSTALL WINDOWS 3.1. You need to have Windows 3.1 already installed on your machine in order for OS/2 Warp Version 3.0 to support it. In order to provide that support, OS/2 Warp Version 3.0 will need to utilize some of the files on the Windows 3.1 diskettes. Therefore, if you wish to have Windows 3.1 supported by OS/2 Warp Version 3.0, you will need to have the Windows 3.1 diskettes available when using SEIMAGE. Use the following syntax to copy the images to the CC Server: SEIMAGE /S:source_path /T:target_path where source_path = the source path of the images where target_path = the target path & directory where images will be copied o The target_path must already exist on your CC Server prior to running SEIMAGE. o The SEIMAGE utility will create new directories concatenated to the target_path you specified on the /T: parameter. o SEIMAGE will prompt the user for Windows 3.1 diskettes after the OS/2 product images are loaded. NOTE: THIS IS ONLY FOR SUPPORT OF WINDOWS 3.1 AND NOT TO INSTALL WINDOWS 3.1. The user responds Y or N. If the response is yes, then the user is asked to supply a subdirectory name. This subdirectory name will be appended to the target_path you specified with SEIMAGE. If the user does not type in a Windows subdirectory name to be appended to the the target subdirectory, then the Windows diskette images will be placed directly in the target subdirectory. Also, the user may load the diskette images for more than one set of Windows Diskettes. After a set of Windows diskettes is copied, the user will be prompted as to whether another set of Windows diskettes need to be copied. If the response is yes, then the user will be prompted again for a subdirectory name and the process starts over. o The ELITE team used the following SEIMAGE command syntax during the the test. SEIMAGE was executed from the directory \CID\EXE\OS2\WARP30\GA. SEIMAGE /S:A: /T:D:\CID\IMG\OS2\WARP30\GA /S:= the source path ( A drive ) /T:= the target path where images will be copied (D:\CID\IMG\OS2\WARP30\GA ) The following new subdirectories were concatenated to the target directory. The ELITE team also chose the Windows 3.1 support and supplied WIN31 as the subdirectory name. DISK_0 DISK_1 . . DISK_13 DISP_1 DISP_2 DISP_3 DISP_4 PMDD_1 PMDD_2 PMDD_3 WIN31 ( * Optional - created when prompted for Windows 3.1 support) DISK_W1 DISK_W2 DISK_W3 DISK_W4 DISK_W5 DISK_W6 *NOTE: THIS NEW FEATURE HAS BEEN PROVIDED TO ASSIST THE DOWNLOADING OF AUTHORIZED LICENSED COPIES OF MS WINDOWS FOR USE WITH OS/2 WARP. YOU SHOULD ONLY DOWNLOAD THE NUMBER OF COPIES OF WINDOWS FOR WHICH YOU ARE LICENSED. IN PROVIDING YOU THIS UTILITY IBM DOES NOT AUTHORIZE YOU TO MAKE ANY ADDITIONAL COPIES OF WINDOWS FOR WHICH YOU HAVE NOT BEEN AUTHORIZED TO MAKE BY THE MICROSOFT CORPORATION. PRISTINE-REMOTE INSTALLATION PROCEDURES NetView DM/2 Client It is necessary to create and boot the pristine (brand new) workstation from the pristine boot diskettes. This will allow the workstation to establish contact with the NetView DM/2 CC Server. The pristine boot diskettes contain a minimal OS/2 system, a minimal LAPS for LAN transport code which allows the connection to the Server, and a minimal NetView DM/2 agent to accept commands from the CC Server to install various products. In our test, we built the pristine diskettes with LAPS 2.0 at CSD WR07045 and NetView DM/2 2.1. We also tested with NetView DM/2 2.0 CSD XR020334 as well. o To create the two OS/2 Warp 3.0 pristine boot diskettes, the following steps should be executed from the NetView DM/2 2.1 Server. NOTE: We also tested with NetView DM/2 2.0, but we have only documented NetView DM/2 2.1 in these examples. 1. Insert a formatted diskette into the disk drive. 2. Apply the minimal OS/2 onto the diskettes by executing SEDISK which is located in the OS/2 CID Utility directory. SEDISK will apply the minimal OS/2 onto the first diskette and prompt you to insert the second diskette for completion. The following is the SEDISK syntax: os2_cid_utility_dir\SEDISK /S:os2_image_dir /T:target_dir where os2_cid_utility_dir = The drive and path of the OS/2 CID Utility directory on the NetView DM/2 CC Server os2_image_dir = The drive and path of the OS/2 images on the NetView DM/2 CC Server target_dir = The drive and path of target directory For example, the ELITE team used: SEDISK /S:D:\CID\IMG\OS2\WARP30\GA /T:A: 3. Keeping the second diskette in the disk drive, apply the minimal LAPS onto the second diskette by executing the THINLAPS utility. THINLAPS can be executed from the LAPS image directory on the NetView DM/2 CC Server. The following command syntax should be used: laps_image_directory\THINLAPS laps_image_directory target directory nif_file where laps_image_directory = The drive and path of the LAPS images on the NetView DM/2 CC Server target_directory = The drive and path of the target directory nif_file = the .NIF file you will use For example, the ELITE team used: THINLAPS D:\CID\IMG\NTS2\LAPS\WR07045 A: IBMTOK.NIF 4. Keeping the second diskette in the disk drive, apply the minimal NetView DM/2 agent using the NVDMBDSK utility. Execute NVDMBDSK from the BIN subdirectory within the NetView DM/2 product directory. NVDMBDSK is a presentation manager utility so, a window will be put up for you to fill in the required parameters. You should specify your Target Environment as OS/2 (rather than DOS) and it is recommended you leave the ? for the Client Name and Server Name, and change the Receive Timeout value from 15000 to -1. The "?" in this case means that the set of boot diskettes is suitable for use on ANY CC Client for installations, instead of being built with fixed Server Name and Client name. The ELITE team issued NVDMBDSK from the following directory: E:\IBMNVDM2\BIN o Boot the client workstation from the two diskettes. If when building the OS/2 pristine boot diskettes, you left the ? for the Client Name and the Server Name, you will be prompted to fill in these parameters. o You now have established connectivity to the NetView DM/2 CC server. To install OS/2, you must install the following 3 change files together as a COREQ group in the exact order as they appear below: 1. OS/2 pristine install profile - (OS230B.PRO) - Using program SEINST with PARM=/B:bootdrive /T:A:\ - Response file with FormatPartition=1 (Yes) or new Format parameters. (See "New Key Words for OS/2 Warp 3.0 Response Files" on page 21.) 2. LAPS pristine install profile - (LAP7045B.PRO) - Using program LAPS with PARM=/E:MAINT 3. NetView DM/2 pristine install profile - (NDM221BT.PRO) - Using program NVDMCLT - With PhaseEnd=Yes o After the successful completion, the workstation will be running with OS/2, LAPS and NetView DM/2 Client code. o Sample response files are located on the following diskettes: - OS/2 Warp 3.0 - "SAMPLE.RSP" is bundled in the "REQUIRED" file on OS/2 Warp 3.0 diskette 7. - LAPS - sample response files are provided in the SAMPLE directory on the NTS/2 Utility diskette. - NetView DM/2 2.1 did not ship any sample response files, but the only required parameters are "CLIENTNAME=" and SERVERNAME=" for a client. o See sections "Sample PROFILES used by ELITE test group." and "Sample PRISTINE RESPONSE FILES used by ELITE test group" on page 25 for the profiles and response files used during this test. SAMPLE PROFILES USED BY ELITE TEST GROUP. Below are the corresponding profiles presented in the same order that they must be installed as a COREQ group: o OS/2 Warp 3.0 o LAPS o NetView DM/2 Client After the remote installation of the above three products, there are two optional post install procedures for remote installation of Multimedia and SVGA. NOTE: For machines that will use identical Mulitmedia and SVGA support, these post install procedures can be added to the above COREQ group for future installs. Please refer to "OS/2 Warp 3.0 Post Installs for Multimedia and SVGA." on page 29 for the sample profiles and response files used for these two post installations. ----------------------------------------------------------------- TargetDir = C:\ Section Catalog Begin ObjectType=Software GlobalName=OS2.FORMAT.HPFS.ALLOPTIONS.REF.3.0.WARP Description="OS/2 3.0 WARP" End Section Install Begin Program = SB:\EXE\OS2\WARP30\GA\SEINST.EXE Parms = /B:C: /T:A:\ /R:$(ResponseFile) /S:$(SourceDir) /L1:$(LogFile1) ResponseFile = SB:\RSP\OS2\WARP30\GA\FHPFS.RSP SourceDir = SB:\IMG\OS2\WARP30\GA LogFile1 = SB:\LOG\OS2\WARP30\GA\$(WorkStatName).LOG End Figure 1. Sample OS/2 Pristine Install Profile (OS230B.PRO) ----------------------------------------------------------------- TargetDir = C:\ Section Catalog Begin ObjectType=Software GlobalName=LAPS.BOOT.PARM_MAINT.WKSTNAME.REF.1.0.WR07045 Description="LAPS Pristine Install" End Section Install Begin Program = SA:\IMG\NTS2\LAPS\WR07045\LAPS.EXE Parms = /E:MAINT /R:$(ResponseFile) /T:$(TargetDir) /TU:C:\ /S:$(SourceDir) /L1:$(LogFile1) SourceDir = SA:\IMG\NTS2\LAPS\WR07045 ResponseFile = SB:\RSP\NTS2\LAPS\WR07045\$(WorkStatName).RSP LogFile1 = SB:\LOG\NTS2\LAPS\WR07045\$(WorkStatName).LOG End Figure 2. Sample LAPS Pristine Install Profile (LAP7045B.PRO) ----------------------------------------------------------------- TargetDir = C:\IBMNVDM2 Section Catalog Begin ObjectType=Software GlobalName=NVDM2.CLIENT.BOOT.WKSTNAME.REF.2.1 Description="NVDM/2 client install for boot environment" End Section Install Begin Program = SA:\IMG\NVDM2\21\GA\NVDMCLT.EXE Parms = /B:C /R:$(ResponseFile) /T:$(TargetDir) /S:$(SourceDir) /L:$(LogFile1) PhaseEnd = Yes SourceDir = SA:\IMG\NVDM2\21\GA ResponseFile = SB:\RSP\NVDM2\21\GA\$(WorkStatName).RSP LogFile1 = SB:\LOG\NVDM2\21\GA\$(WorkStatName).LOG End Figure 3. Sample NetView DM/2 Pristine Install Profile (NDM221BT.PRO) ----------------------------------------------------------------- New Key Words for OS/2 Warp 3.0 Response Files There are new keywords within the response file. These keywords are documented within the sample response file. The sample response file is bundled in the "REQUIRED" file on OS/2 Warp 3.0 diskette 7 (DISK_7). See "Installation of the Images from Diskettes using SEIMAGE" on page 13 for the procedure to unpack the "REQUIRED" bundle. The following table describes the new keywords. NEW RESPONSE KEYWORD VALID PARMS DESCRIPTION ------------ ----------- ----------- FormatFAT Drive to format as Specifies which drive to FAT (Example: C) - format with FAT file see NOTE 1. system. This keyword cannot be used in conjunction with the BaseFileSystem or FormatPartition keywords. FormatHPFS Drive to format as Specifies which drive to HPFS (Example: C) format with HPFS file see NOTE 1 system. This keyword cannot be used in conjunction with the BaseFileSystem or FormalPartition keywords. MultimediaSupport 0 = Do NOT install Specifies whether or not multimedia support to install multimedia files during the 1 = Install installation. multimedia support (DEFAULT) - see NOTE 2 Windows Support 0 = Don't support Specifies whether or Windows 3.1 not to support Windows 3.1. THIS DOES NOT 1 = Don't support INSTALL WINDOWS 3.1, Windows 3.1 - see IT ONLY PROVIDES NOTE 3 SUPPORT IF YOU ALREADY HAVE WINDOWS 3.1 INSTALLED. WindowsInstallSource A string that Specifies the specifies the path subdirectory name relative to where the Windows the source path 3.1 diskettes reside. where the windows diskettes reside of the CID tree - see NOTE 4. ExistingWindowsPath A string that Specifies the path to an specifies the path existing Windows 3.1 to the existing system. Note: If Windows 3.1 system WindowsSupport selected (Example: C:\WINDOWS) and this value is NULL, install will search all partitions for existing Windows 3.1 system and the first valid Windows 3.1 system will be selected. If a Windows 3.1 system is not found, an error will be displayed and response file install will be aborted. AdditionalPrinters 0 = None Allows additional printers other than the default printer to be installed. Where m1, m2,etc. are port numbers as defined under "PrinterPort" keyword, and n1,n2, etc. are indices into PRDESC.LST as described in "DefaultPrinter" keyword. .m1:n1,m2:n2, . ------- NOTE 1) This parameter is not supported for multiple hard drives. However, during our testing, we were able to successfully install on a single hard drive that was partitioned into 3 logical drives (C, D, E). The parameters we used to accomplish this were FormatFAT=C:,D: andFormatHPFS=E: NOTE 2) This parameter only provides for installing the multi- media files. It does NOT create the multimedia ICON and it does NOT configure which multimedia options/applica- tions you desire. You need to run the MINSTALL program to configure multimedia support (see "Post Install Pro- cedure of Multimedia" on page 30). NOTE 3) This parameter only provides for installing the Windows 3.1 files required for the OS/2 support of Windows 3.1. It does NOT install Windows 3.1. Windows 3.1 must already exist on your target workstation in order for OS/2 Warp to support it. NOTE 4) This parameter value should match the subdirectory name you supplied when prompted for Windows support during the execution of SEIMAGE. For example, if you specified WindowsInstallSourcePath=\WIN31,and your CID image directory is \CID\IMG\OS2\WARP30\GA, then the entire path for the Windows files would be \CID\IMG\OS2\WARP30\GA\WIN31. See "Installation of the Images from Diskettes using SEIMAGE" on page 13. SPECIFYING WINDOWS 3.1 SUPPORT IN A OS/2 WARP VERSION 3.0 RESPONSE FILE In order to have OS/2 WARP Version 3.0 support an existing Windows 3.1 workstation, you need to be careful when building the response file. There are three response file keywords that are used together to specify Windows 3.1 support: o WindowsSupport= o ExistingWindowsPath= o WindowsInstallSourcePath= For example if we had the following configuration: o Target NetView DM/2 Client workstation: - Windows 3.1 installed on C drive in subdirectory WINDOWS. o NetView DM/2 Server - Source directory (SourceDir) specified in the OS/2 Warp profile where the images are located is D:\CID\IMG\OS2\WARP30\GA - Windows files are in D:\CID\IMG\OS2\WARP30\GA\WIN31. WIN31 was supplied as the subdirectory name during execution of SEIMAGE. Given the above configuration, the three response file keywords needed to have OS/2 Warp support of Windows 3.1 would be speci- fied as follows: RESPONSE FILE KEYWORD REASON ---------------------- ------ Windows Support=1 Provide OS/2 Warp support of the existing Windows 3.1 system. ExistingWindowsPath=C:\WIMDOWS The existing Windows 3.1 system is located on the target workstation on the C Drive in subdirectory Windows. WindowsInstallSourcePath=\WIN31 The Windows 3.1 diskettes that you supplies during the execution of SEIMAGE on the NetView DM/2 Server are located in the sub- directory WIN31. The \WIN value is concatenated to the source directory (SourceDir) specified in the OS/2 Warp Version 3.0 profile. So the files required for OS/2 Warp Version 3.0 to support Windows 3.1 are located in the NetView DM/2 Server directory, D:\CID\IMG\OS2\WARP30\GA\WIN31. ----------------------------------------------------------------- SAMPLE PRISTINE RESPONSE FILES USED BY ELITE TEST GROUP The following response files were used for the remote installa- tion of: o OS/2 WARP 3.0 o LAPS o NetView DM/2 Client Please see section "OS/2 Warp 3.0 Post Installs for Multimedia and SVGA." on page 29 for sample profiles and response files used for the two optional post install procedures for Multimedia and SVGA. The comments were edited out of the OS/2 Warp 3.0 response file for clarity. This response file was used for formatting the C drive as HPFS during the install. The following response file keywords are noted: RESPONSE FILE KEYWORD REASON --------------------- ------ BaseFileSystem=1 Indicates HPFS format (DEFAULT) CDROM=1 indicates AUTODETECT instead of the default(0) ExitOnError=1 Indicates exit with a return code instead of default (0) FormatPartition=1 Indicates format the partition instead of default (0) MultimediaSupport=0 Indicates no multimedia support instead of the default (1). If multimedia support is desired, see "Post Install Procedure of Multimedia" on page 30. ----------------------------------------------------------------- AdditionalPrinters=0 APM=1 AlternateAdapter=0 BaseFileSystem=1 CDROM=1 CountryCode=001 CountryKeyboard=US DefaultPrinter=0 DiagnosticAids=1 DisplayAdapter=0 Documentation=1 DOSSupport=1 WindowsSupport=0 *ExistingWindowsPath=C:\WINDOWS *WindowsInstallSourcePath=\WIN31\DISKETTES DPMI=1 ExitOnError=1 Fonts=1 * FormatFAT= * FormatHPFS= FormatPartition=1 * Include=include.rsp * IncludeAtEnd=atend.rsp * IncludeInLine=inline.rsp MigrateConfigFiles=1 *MigrateApplications= MoreBitmaps=1 Mouse=1 MousePort=0 OptionalFileSystem=1 OptionalSystemUtilities=1 OS2IniData=/AppName/KeyName/KeyValue/ PCMCIA=0 PCMCIAOptions=0 PrimaryCodePage=1 PrinterPort=1 ProcessEnvironment=1 ProgressIndication=1 RebootRequired=0 SCSI=1 SerialDeviceSupport=1 * SourcePath=D:\os2se20 TargetDrive=C: ToolsAndGames=1 * ConfigSysLine=REM This is a CONFIG.SYS remark line. * Copy=vga c:\ /n:ini.rc * EarlyUserExit=T c:\config.sys * ExtendedInstall=PROGRAM.EXE * SeedConfigSysLine=REM This is a remark line in the seed CONFIG.SYS. * UserExit=T.EXE C:\OS2\INSTALL\INSTALL.LOG *DDISrc = Z:\DDP *DDIDest = C:\ *DDIDDP = *.DDP MultimediaSupport=0 Figure 4. Sample OS/2 Warp 3.0 Pristine Install response file (FHPFS.RSP) ----------------------------------------------------------------- INST_SECTION = ( INSTALL=PRODUCT ) PROTOCOL = ( [PROT_MAN] DriverName = PROTMAN$ [IBMLXCFG] IBMTOK_nif = IBMTOK.nif LANDD_nif = LANDD.NIF NETBEUI_nif = NETBEUI.NIF [LANDD_nif] DriverName = LANDD$ Bindings = IBMTOK_nif NETADDRESS = "T40000C1DA053" ETHERAND_TYPE = "I" SYSTEM_KEY = 0x0 OPEN_OPTIONS = 0x2000 TRACE = 0x0 LINKS = 125 MAX_SAPS = 8 MAX_G_SAPS = 0 USERS = 10 TI_TICK_G1 = 255 T1_TICK_G1 = 15 T2_TICK_G1 = 3 TI_TICK_G2 = 255 T1_TICK_G2 = 25 T2_TICK_G2 = 10 IPACKETS = 250 UIPACKETS = 100 MAXTRANSMITS = 6 MINTRANSMITS = 2 TCBS = 64 GDTS = 30 ELEMENTS = 800 [NETBEUI_nif] DriverName = netbeui$ Bindings = IBMTOK_nif ETHERAND_TYPE = "I" USEADDRREV = "YES" OS2TRACEMASK = 0x0 SESSIONS = 188 NCBS = 240 NAMES = 50 SELECTORS = 30 USEMAXDATAGRAM = "NO" ADAPTRATE = 1000 WINDOWERRORS = 0 MAXDATARCV = 4168 TI = 30000 T1 = 500 T2 = 200 MAXIN = 1 MAXOUT = 1 NETBIOSTIMEOUT = 1000 NETBIOSRETRIES = 12 NAMECACHE = 0 PIGGYBACKACKS = 1 DATAGRAMPACKETS = 2 PACKETS = 350 LOOPPACKETS = 1 PIPELINE = 5 MAXTRANSMITS = 6 MINTRANSMITS = 2 DLCRETRIES = 5 [IBMTOK_nify] DriverName = IBMTOK$ ADAPTER = "PRIMARY" MAXTRANSMITS = 12 RECVBUFS = 2 RECVBUFSIZE = 256 XMITBUFS = 1 ) Figure 5. Sample LAPS response file (CIDA053.RSP) ----------------------------------------------------------------- SERVERNAME=CIDA097 CLIENTNAME=CIDA053 ATTACHTIMEOUT=-1 RECEIVETIMEOUT=-1 Figure 6. Sample NetView DM/2 Client response file (CIDA053.RSP) ----------------------------------------------------------------- OS/2 Warp 3.0 Post Installs for Multimedia and SVGA POST INSTALL PROCEDURE OF MULTIMEDIA There are two install processes associated with multimedia support. 1. You need to install the multimedia files onto the target workstation. 2. Then you must configure the multimedia support at the target workstation. The first step is accomplished by specifying MultimediaSupport=1 in the OS/2 Warp Version 3.0 response file. After the install completes for the first step, you need to go to the target workstation and execute the second step AT THE TARGET WORKSTATION. The second step is accomplished by running the MINSTALL program AT THE TARGET WORKSTATION. MINSTALL must be run from the MMTEMP subdirectory. MINSTALL presents a window to prompt you for the multimedia applications you desire. Following is the MINSTALL syntax: MINSTALL /M /C: /R: The following describes the MINSTALL parameters: /M This parameter is for telling MINSTALL.EXE to transfer files off of the MMTEMP directory and to the directory where the files need to be for multimedia IPL. This is required for CID. /C: This parameter is used when it is desired to Create a response file. This response file will be used for unattended multimedia installation of other machines using the /R parameter. /R: This parameter is used when you have already created a response file using the /C parameter. A response file should only be used with multimedia install if the machines hardware setup is the same as the hardware setup of the machine the response file was created on. Example of invoking MINSTALL while creating a response file: MINSTALL /M /C:MEDIA.RSP ----------------------------------------------------------------- For workstations that will have identical multimedia support you can configure the multimedia support remotely. To accomplish this, you will need to use the sample profile provided in this section and the response file generated from the MINSTALL procedure that was executed at the initial target workstation. The following is a sample profile used for the remote configuring of multimedia support. The response file referenced in the profile (MEDIA.RSP) was generated from the initial workstation by issuing the command "MINSTALL /M /C:MEDIA.RSP". When prompted for a multimedia application, we selected "Software Motion Video". We were then able to remotely configure another workstation via the following profile: ----------------------------------------------------------------- TargetDir = C:\ Section Catalog Begin ObjectType=Software GlobalName=OS2.MULTIMEDIA.MINSTALL.MOTION.VIDEO.REF.3.0.WARP Description="OS/2 3.0 Warp Multimedia install of Motion Video" End Section Install Begin Program = C:\MMTEMP\MINSTALL.EXE Parms = /M /R:$(ResponseFile) ResponseFile = SB:\RSP\OS2\WARP30\GA\MEDIA.RSP End Figure 7. Sample Multimedia Install Profile (OS230MM.PRO) ----------------------------------------------------------------- The following is a sample response file used for the remote configuring of multimedia support. This response file was generated at the initial workstation by issuing the command "MINSTALL /M /C:MEDIA.RSP" and selecting the multimedia application, "Software Motion Video". ----------------------------------------------------------------- /* Response file generated by MMPM/2 Install */ MMINSTSOURCE = "C:\\mmtemp" MMINSTTARGET = "C:" CHANGECONFIG = "Y" MMINSTGROUPS = ( GROUP.2 = "SoftwareMotion Video=NUM=1," GROUP.14 = " " GROUP.19 = " " GROUP.20 = " " ) Figure 8. Sample Multimedia Response File (MEDIA.RSP) ----------------------------------------------------------------- POST INSTALL PROCEDURE OF SVGA There are two install processes associated with SVGA. 1. You need to install OS/2 Warp Version 3 on the target workstation. 2. Then you must run a post install procedure AT THE TARGET WORKSTATION. After the install of OS/2 Warp Version 3 completes you need to go to the target workstation and execute the post install procedure AT THE TARGET WORKSTATION. This is accomplished by running the DSPINSTL program AT THE TARGET WORKSTATION. DSPINSTL must be run from the OS2\INSTALL subdirectory. DSPINSTL presents a window to prompt you for the SVGA support you desire. Following is the DSPINSTL syntax: DSPINSTL /PD:dsc_file /S:source_path /T:target_drive /RES:resolution /U The following describes the DSPINSTL parameters: /PD:dsc_file - The fully qualified .DSC file name. /S:source_path - The fully qualified path to the OS/2 images. /T:target_drive - The target drive or bootdrive. /RES:resolution - The resolution to come up in after reboot. /U - Indicates unattended installation. NOTES: 1. If a resolution was passed in that is not supported in the .PMI file then an error will occur. 2. If a resolution was passed in that is in the .PMI and not supported by the driver, then driver should default to low resolution. For multiple workstations that will have the same SVGA support you can configure the SVGA support remotely. To accomplish this, you will need to use the sample profile provided in this section. There is no response file required. The following is a sample profile used for the remote configuring of SVGA support. ----------------------------------------------------------------- TargetDir = C:\ Section Catalog Begin ObjectType=Software GlobalName=OS2.SVGA.DSPINSTL.REF.3.0.WARP Description="OS/2 3.0 Warp SVGA Install" End Section Install Begin Program = C:\OS2\INSTALL\DSPINSTL.EXE Parms = /PD:C:\OS2\INSTALL\PSXGA32.DSC /S:$(SourceDir) /T:C: /RES:1024x768x256 /U SourceDir = SB:\IMG\OS2\WARP30\GA End Figure 9. Sample SVGA Install Profile (OS30SVGA.PRO) ----------------------------------------------------------------- NOTE: A list of the dsc_file (.DSC files) is described in the README.CID file on Installation diskette (DISK_0). To check the results of the installation, you need to view the DSPINSTL.LOG file in subdirectory OS2\INSTALL on the target workstation. MIGRATION-REMOTE INSTALLATION PROCEDURES NOTE: OS/2 Warp Version 3 is the replacement for OS/2 for Windows. OS/2 Warp Version 3 with WIN-OS/2 is the replacement for OS/2 Version 2.1. At the time of this report, OS/2 Warp VERSION 3.0 for WIN-OS/2 was not available (planned availability is First Quarter 1995 per Announce Letter 294-667), so migration from OS/2 Version 2.1 or OS/2 Version 2.11 was not supported. There is migration support for migrating from OS/2 for Windows to OS/2 Warp Version 3.0, however, we did not test that migration. TEST ENVIRONMENT: LAN Environment o 16MB Token Ring LAN, 8228, 8230,8250, 3745 with NCP V7R1 o 3 segments, Local Token-Ring Bridge Program 1.0 directly controlled, and 8229 Token Ring-Ethernet bridge, numerous other bridged segments and events monitored Host Environment o VTAM V4R1 o NetView V2R3 o MVS/ESA 4.2.2 o NetView DM V1R5 o NPM V2R2 Warp Server Environment o SOFTWARE: - NetView DM/2 2.1 XR00000 - CM/2 1.11 WR06150 - NTS/2 - LAPS 2.20.2 WR07045 (CSD: WR07045) - DCAF 1.21 UB09790 - DB2 OS/2 1.0.1 WR07015 - DB2 OS/2 1.20 WR07000 - DDCS/2 2.10 WR07016 - DDCS/2 2.20 WR07000 - First Failure Support Technology/2 V1.2 WR00485 - User Profile Management 3.00.1 WR07040 - LMU 1.00 LM00200 - LNM 1.10 LM00004 (CSD: UR42384) - LS 3.00.1 IP07040 - TCP/IP for OS/2 Base kit 2.0 (CSD: UN64092) - TCP/IP for OS/2 Network File System kit 2.0 (CSD: UN57064) - SPM/2 2.00 WR06075 - LSM 1.01 MB02000 - LD 1.10 LD00000 o HARDWARE: - Server ----> 8595-0KF - Hard drive ----> 400MB SCSI - RAM ----> 24 meg. - Display ----> 8518-001 - TR cards (2) -- ----> AUTO LANStreamer MC32 Adapter -- ----> 16/4 Adapter/A - BUS ----> MCA Warp Client Environment o SOFTWARE: - OS/2 Warp (90% of clients) - OS/2 2.1 WR06200 (10% of clients) - NetView DM/2 2.00.2 XR00005 (CSD: XR20334) - NetView DM/2 2.1 XR00000 - CM/2 1.11 WR06150 - NTS/2 LAPS 2.20.2 WR07045 (CSD: WR07045) - DCAF 1.20 UB09790 - DB2 OS/2 1.2 WR07000 - First Failure Support Technology/2 V1.2 WR00478 - User Profile Management 3.00.1 WR07040 - LMU 1.00 LM00201 - LS 3.00.1 IP07040 - TCP/IP for OS/2 Base kit 2.0 UN64092 - TCP/IP for OS/2 Network File System kit 2.0 UN57064 - Internet Connection for OS/2 2.0 - SPM/2 2.00 WR06075 - LSM 1.01 MB02000 - LD 1.10 LD00000 o HARDWARE: - IBM 8556-24X PS/2 - IBM 8580-081 PS/2 - IBM 9556-QBA PS/2 - IBM 9545-706 ThinkPad 750C - IBM 9557-1BA PS/2 - IBM 9576-KUA PS/2 - IBM 9577-KUA PS/2 - IBM 9590-KLA PS/2 - IBM 6382-F51 PS/ValuePoint - IBM 6384-W53 PS/ValuePoint REPORT CONTACT: Questions or comments about this report or about integration testing can be sent: o via VNET to ELITE at RALVM12, o via Internet to elite@vnet.ibm.com o via IBMMAIL to USIB5K9S at IBMMAIL. Please reference this document (ELITE029) in your note. NOTICES The information contained in this document is distributed AS IS. The use of this information or the implementation of any of these techniques is a customer responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. Customers attempting to adapt these techniques to their own environments do so at their own risk. IBM will accept no liability for consequences resulting from the use of this information. This report is to be used solely for the purpose of installing and supporting the product(s) discussed. This material must not be used for other purposes without the written consent of IBM. In addition, this material must not be redistributed outside your company. The following terms are trademarks of the International Business Machines Corporation in the United States and/or other countries. Those trademarks followed by an asterisk (*) are registered trademarks of the International Business Machines Corporation. o DATABASE 2 o DB2* o FFST o FFST/2 o IBM* o Operating System/2* o OS/2* o PS/2* o ThinkPad* o ValuePoint o WIN-OS/2 The following terms are trademarks or registered trademarks of Microsoft Corporation: o Windows ----------------------------------------------------------------- IBM disclaims all warranties, whether express 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 (c) 1994, 1995 IBM Corporation. Any trademarks and product or brand names referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.