═══ 1. Introduction ═══ IBM OS/2 LAN Server 3.0 ServicePak IP07060 IBM PTF IP07060 This ServicePak can be applied to: - IBM OS/2 LAN Server Version 3.0 - Entry, and IBM OS/2 LAN Server Version 3.0 - Advanced For use with OS/2 2.0 or higher. - IBM LAN Adapter and Protocol Support, Versions 2.11, 2.14, 2.20, 2.20.1 - 2.20.4 Fixes for LAPS, OS/2 LAN Requester, UPM, Fault Tolerance, DLR, and Remote IPL are also included in this package. This package also includes the LAN Support Program, version 1.38, as a separately installable package. Warning: 1 - After upgrading LS 3.0 with this package, the ENCLOSED LAN Support Program version 1.38 MUST be used instead of any previous copy of the LSP. Warning: 2 - This ServicePak has a new method of installation using Corrective Service Facility (CSF) Version 2-B. Although the installation instructions look similar to previous ServicePaks, there are significant differences. Please review the entire Installation section before proceeding. Service to Servers which use "Advanced Features" can be complex. Good Insurance! Have appropriate Bootable Standalone Service Diskettes. ═══ 1.1. Affected SYSLEVEL Files ═══ After installing this ServicePak for some or all of the components listed below, the CURRENT CSD level of the associated SYSLEVEL file(s) will indicate IPx7060 (where x indicates the country code.) SYSLEVEL.SRV IBM OS/2 LAN Server SYSLEVEL.REQ IBM OS/2 LAN Requester SYSLEVEL.MUG IBM OS/2 User Profile Management SYSLEVEL.UPE IBM OS/2 User Profile Management - Extended SYSLEVEL.DLR IBM DLR - DOS LAN Requester SYSLEVEL.TRP IBM OS/2 LAN Adapter and Protocol Support Note: IBM LAN Support Program version 1.38 is provided in this package. After installation, SYSLEVEL.LSP will indicate a current CSD level of URx7060 (where x indicates country code) and a current version of 1.38. ═══ 1.2. Trademarks ═══ The following are trademarks of IBM Corporation: o AT o Communication Manager (CM) o IBM o LAN SERVER for MacIntosh (LSM) o LAN Support Program (LSP) o Micro Channel o Operating System/2 o OS/2 o OS/2 Warp o PC LAN Program (PCLP) o Presentation Manager (PM) o Win-OS/2 o WorkFrame/2 o XGA The following are trademarks of other Corporations: o AmiPro (Lotus Development Corporation) o Freelance Graphics (Lotus Development Corporation) o Lotus 1-2-3 (Lotus Development Corporation) o Microsoft (Microsoft Corporation) o MSACCESS (Microsoft Corporation) o MSNET (Microsoft Corporation) o Pentium (Intel Corporation) o SuperCalc (Computer Associates International, Inc.) o Ungermann-Bass (Ungermann-Bass, Inc.) o Windows (Microsoft Corporation) o WordPerfect Office (WordPerfect Corporation) ═══ 2. Installation ═══ This ServicePak uses Corrective Service Facility (CSF) Version 2-B (provided on the tool diskette of this ServicePak) for installation. Complete instructions for the use of the updated SERVICE and FSERVICE commands are provided with the CSF Version 2-B README.INF file on the ServicePak Tool Diskette. Please read the CSF instructions for information on the use of CSF Version 2-B backup and restore capabilities. Note: - Archiving is not enabled for this ServicePak. Installing the ServicePak is essentially a three phase process: Phase 1 - Quiesce the Target System Stop all running applications so that LAN Server/Requester is not in use. Phase 2 - Install the ServicePak Use one of the following methods to replace system files with those provided on this ServicePak: Selective Install Redirected (CID) Install Phase 3 - Return the Serviced System to Normal Operation Perform a normal system boot. Also, Post Installation Procedures may be necessary to update Remote IPL images or DOS LAN Requester clients. Note: - If asked for permission to replace any files, respond Yes for RIPL .CNF files, hidden or system files, or any private fixes that are indicated as newer than the ServicePak files. ═══ 2.1. Selective Install ═══ This method will apply fixes to selected subsystems, partitions, and directories: The Corrective Service Facility will handle Locked Files automatically so boot diskettes are not required before applying service. 1. Insert ServicePak Tool diskette in the A drive. 2. At an OS/2 command prompt type "A:SERVICE" and press Enter. 3. Insert ServicePak diskette 1 when prompted. 4. Follow the prompts to the CSF SERVICEABLE PRODUCTS panel. Review the serviceable products selected on the panel and deselect any products that you do not want to service at this time. Then choose the SERVICE push button. 5. Enter (optional) backup path then choose the OK push button. 6. If the APPLICATION IN USE locked files panel is presented, choose CONTINUE. 7. Follow prompts to complete the process. 8. Remove the diskette from drive A:, then perform the system Shutdown procedure. 9. Reboot the system normally. If the system to be serviced is a multiboot system with LAN Advanced Server using IBM386FS on a drive other than the "C" drive, use the Special Situation Install method to complete the installation on each bootdrive. When problems such as insufficient disk space are encountered when performing the Selective Install, use the Special Situation Install method to perform service. ═══ 2.2. Redirected Installation (CID) Method ═══ This method is useful for those who are using the CID (Configuration, Installation, and Distribution) Services as provided by IBM NTS/2. The Selective Install method is recommended for Servers exploiting 386 HPFS function, Fault Tolerance, and/or Local Security. While setting up a CID server is beyond the scope of this document, we have provided a sample LAN CID Utility REXX Command file segment (IP_7060.CID) that may prove useful in setting up a CID server for this ServicePak. The sample IP_7060.CID assumes the following: o The ServicePak Tool diskette files are placed on the code server using "XCOPY A:\*.* /S" (or equivalent) in 'x:\img\csd\ls30\ip_7060' where 'x:' is the drive seen by the client. o The ServicePak files are placed on the code server using "XCOPY A:\*.* /S" (or equivalent) in 'x:\img\csd\ls30\ip_7060.' o The sample RESPONSE.FIL (or equivalent) is placed on the code server in x:\rsp\csd\ls30\ip_7060. o The following CID server directory structure contains the contents of the ServicePak and the tool diskette. img\csd\ls30\ip_7060 * Root directory of ServicePak diskette 1 img\csd\ls30\ip_7060 * ServicePak Tool diskette files img\csd\ls30\ip_7060\FIX * No files img\csd\ls30\ip_7060\FIX\REQ.1 * Requester Fixes img\csd\ls30\ip_7060\FIX\SRV.2 * Server Fixes img\csd\ls30\ip_7060\FIX\MUG.3 * User Profile Management Fixes img\csd\ls30\ip_7060\FIX\UPE.4 * Extended UPM Fixes img\csd\ls30\ip_7060\FIX\TRP.5 * LAN Adapter and Protocol Support Fixes img\csd\ls30\ip_7060\FIX\DLR.6 * DOS LAN Requester Fixes rsp\csd\ls30\ip_7060 * RESPONSE.FIL (from sample on ServicePak tool diskette) o A log directory exists at 'x:\log\csd\ls30\ip_7060' for the log files. ═══ 2.3. Bootable Standalone Service Diskettes ═══ Sometimes it becomes necessary to boot from diskette in order to perform certain operations on fixed-disk, like installing this ServicePak or running CHKDSK /f. All necessary files must be contained on diskette. Files from the fixed-disk should not be referenced in A:\CONFIG.SYS or A:STARTUP.CMD. Otherwise Locked Files can still exist on the fixed-disk. Should the need arise to boot from diskette for any reason, you may: o Use the Install diskette and Diskette #1 of OS/2 2.x or OS/2 3.x. Escape to A: o Create custom Bootable Standalone Service Diskettes from your licensed materials. The makeup of these is dependent on the system to be serviced. Instruction is available for: Requesters and Entry Version Servers. Advanced Version Servers. CAUTION: LAN Servers that utilize the Advanced features such as Local Security and Fault Tolerance must use custom Bootable Standalone Service Diskettes. Regular HPFS boot diskettes, such as the OS/2 Installation diskettes, CANNOT mirror changes to Fault Tolerance partitions or access files/directories which are controlled by local security. ═══ 2.3.1. Making OS/2 Bootable Diskettes ═══ 1. Make a copy of the OS/2 2.x or OS/2 3.x Installation Diskette and Diskette #1. Call them SA#1 and SA#2 respectively. 2. Delete SYSINST2.EXE from Diskette SA#2. 3. Delete BUNDLE from Diskette SA#2 (this will be on OS/2 versions 2.1 or greater). 4. Modify CONFIG.SYS on SA#2 as follows: buffers=50 memman=noswap protshell=a:\cmd.exe protectonly=yes libpath=a:\; ifs=hpfs.ifs /c:64 set path=a:\; set dpath=a:\; 5. Copy UHPFS.DLL from OS/2 Diskette #2 or C:\OS2\DLL to SA#2. ═══ 2.3.2. Making Advanced Server Bootable Diskettes ═══ MAKEDISK is an Advanced Server utility designed to make the necessary Bootable Standalone Service Diskettes used in periodic maintenance of 386 HPFS systems. 1. Make a copy of the OS/2 2.x or 3.x Installation Diskette and Diskette #1. Call them SA#1 and SA#2 respectively. 2. Delete SYSINST2.EXE from Diskette SA#2. 3. Delete BUNDLE from Diskette SA#2 (this will be on OS/2 versions 2.1 or greater). 4. With Boot Diskette SA#2 in drive a: or b: run MAKEDISK from an OS/2 prompt. Note: Syntax is MAKEDISK /BOOTDRIVE:d where d is the OS/2 boot drive. For additional Information see the Network Administrators Reference: Creating a 386 HPFS Boot Diskette, or LAN Server Utilities. 5. If using Fault Tolerance, add the Fault Tolerance files to the Bootable Diskette SA#2. 6. Verify that the 386 HPFS Bootable Standalone Service Diskettes work properly. o Shutdown the system. o Insert the Bootable Standalone Service Diskette SA#1 in the A drive. o Reboot the system (Ctrl+Alt+Del, or other method). o Determine if Local Security is working. o Determine if Fault Tolerance is working. ═══ 2.3.3. Adding Fault Tolerance to 386 HPFS Bootable Standalone Service Diskettes ═══ 386 HPFS Bootable Standalone Service diskettes require additional customizing in order to properly update files on partitions which are mirrored. The following steps may have to be done for each LAN Server with Fault Tolerance since the configuration information transferred in step 3 can be unique for each such system. 1. Copy the following four Fault Tolerance files from the first diskette of the LAN Server 3.0 ServicePak to your Bootable Standalone Service Diskette SA#2. 1) DISKFT.SYS 2) FTD.MSG 3) FTATTRIB.EXE 4) FTCOPY.CMD 2. Add the following line to the CONFIG.SYS on the Bootable Standalone Service Diskette SA#2. DEVICE=DISKFT.SYS 3. At an OS/2 command prompt, make the current drive A:, and have the 386 HPFS Bootable Standalone Service Diskette SA#2 in drive A. Type "FTCOPY" to copy the customized Fault Tolerance configuration information to the 386 HPFS Bootable Standalone Service Diskette SA#2. Warning: Test your 386 HPFS Bootable Standalone Service Diskette before you make any alterations to your system. This Diskette is the Master Key should your system ever fail to boot from its hard drive. ═══ 2.4. Special Situation Install ═══ This method will apply all fixes to all partitions and directories: FSERVICE is used for CID installation of this ServicePak, for multiboot systems with IBM386FS on a drive other than the 'C' drive, or when problems, such as insufficient memory for the locked file device driver or corrupted disk drives, are encountered using the Selective Install method. It does require booting from diskette to insure that there are no Locked Files during the install phase. Warning: - Ensure that all drives to be updated are clean by performing a CHKDSK /F on each drive before FSERVICE is invoked. There will be no opportunity to clean up the drives after FSERVICE is invoked. 1. Boot from the Bootable Standalone Service Diskettes. 2. Establish A: as the Current Directory. 3. Replace the Boot Diskette with the ServicePak Tool Diskette. 4. From the A: prompt, type "FSERVICE" and press Enter. Click here for additional steps needed for multi-boot systems. 5. At the panel titled "Installing this Service Pak" press Enter (Option 1). 6. Follow the prompts provided by the Corrective Service Facility. 7. Reboot the system normally. ═══ 2.4.1. Updating IBM386FS Directory on a Multiboot System ═══ A new parameter has been added to the FSERVICE command to enable servicing the IBM386FS directory when it resides on a bootdrive other than C:. Specify the bootdrive containing the IBM386FS directory to be serviced as the /b parameter on the FSERVICE command: FSERVICE /b:d (where d is the drive letter assigned to bootdrive) Note: There is NO colon after the bootdrive 'd'. Two methods are available for servicing the IBM386FS directories on multiple bootable drives: 1. Run FSERVICE iteratively. That is, run FSERVICE /b: for each bootable drive containing an IBM386FS directory. 2. Edit the RESPONSE.FIL (on the Tool diskette of this ServicePak) to add the following parameter set after the :SYSLEVEL label: :DIRLIST d1:\IBM386FS where d1 = a bootable drive requiring IBM386FS service, d2:\IBM386FS and d2 = another bootable drive requiring IBM386FS service. :ENDDIRLIST ═══ Locked Files ═══ Sometimes it is essential that programs own (become the master of) system resources such as Memory Blocks, Communication Ports, and Files. When a program stakes claim to a file, that file is said to be Locked; no other program is allowed to alter (replace or write to) it until the owning program explicitly removes the lock. .DLL Files can become Locked by residing in a directory that is included in the LIBPATH string of CONFIG.SYS. For example, NETAPI.DLL can be locked when \MUGLIB\DLL exists in the LIBPATH of CONFIG.SYS. ═══ Escape to A: from OS/2 Install Diskettes ═══ To obtain the A: prompt when using the OS/2 Product installation diskettes as Bootable Standalone Service Diskettes: o Boot the system with Install Diskette in drive A. o At the IBM Logo Screen - Insert Diskette #1, press Enter. o At the Welcome Screen - Press Esc to Exit. (F3 for OS/2 3.x) The A: prompt should appear. OS/2 Programs, including FSERVICE.EXE, can be run from here. ═══ Creating a 386 HPFS Boot Diskette Refer to ═══ Appendix H in: Operating System/2 Local Area Network Server Network Administrator Reference Volume1: Planning and Installation Version 3.0 ═══ LAN Server Utilities ═══ Refer to Appendix C, Miscellaneous Utilities MAKEDISK in: Operating System/2 Local Area Network Server Network Administrator Reference Volume3: Network Administrator Tasks Version 3.0 ═══ 3. Post Installation Procedures ═══ Servers used for Remote IPL or DOS Lan Requester Download Service need additional consideration. ═══ 3.1. Install LSP 1.38 Image ═══ LAN Support Program version 1.38 is required for Remote IPL Servers and for Servers using the DLR Download Service. Follow the steps below to install the LSP 1.38 image included in this package: 1. Open the LAN Services icon on the desktop and select the OS/2 LAN Services Installation/Configuration icon. 2. Follow the prompts, selecting the ADVANCED method of configuration on the BASIC OR ADVANCED INSTALLATION/CONFIGURATION panel. 3. Follow further prompts until the INSTALLATION AND CONFIGURATION panel is displayed. Select "CONFIGURE A COMPONENT" and press "OK". 4. On the CONFIGURE panel, highlight one of the following as appropriate for the target system and then select CONFIGURE: DOS Remote IPL OS/2 Remote IPL DOS LAN Requester Download Service 5. On the COPY PROGRAMS panel, highlight LAN Support Program then select COPY. Verify that "copy" is displayed in the Action column. Press OK. 6. When returned to the CONFIGURE panel, press OK. 7. When the INSTALLATION AND CONFIGURATION panel is redisplayed, highlight "Apply the changes" and press OK. 8. Follow the remaining prompts (inserting Requester diskette 3 if requested), and insert the LAN Support Program version 1.38 diskette included in this package when requested. 9. Allow the system to perform a backup, then follow panel instructions to shutdown and re-IPL the system. After successful installation of the LAN Support Program provided with this package, SYSLEVEL.LSP will indicate a current CSD level of URx7060 (where x indicates country code) and a current version of 1.38. Warning: After upgrading LS 3.0 with this package, the ENCLOSED LAN Support Program version 1.38 MUST be used instead of any previous copy of the LSP. Warning: If one of the IBM AUTO 16/4 TOKEN RING Adapter Cards is installed anywhere on the network being serviced, additional steps are required to keep LSP compatible with the Adapter card. ═══ 3.1.1. Additional Steps for AUTO 16/4 Token Ring Adapters ═══ IBMTOK.DOS and associated files installed with LSP 1.38 are not compatible with the IBM AUTO 16/4 Token Ring Adapter cards. These files must be replaced by the same named files delivered with the IBM AUTO 16/4 Token Ring Adapter Card. This replacement is done as follows: 1. Insert Disk 2 (labeled DEVICE DRIVER AND LSP CUSTOM) of the diskettes delivered with the IBM AUTO 16/4 Token Ring Adapter Card into drive A. 2. Copy the following files from diskette 2 into the IBMLAN\DOSLAN\LSP\DOS directory on the system just serviced, overlaying the same named files already there. o IBMTOK.DOS o IBMTOK.NIF o LT2.MSG For example: COPY a:\dos\ibmtok.dos d:\ibmlan\doslan\lsp\dos\ibmtok.dos or COPY a:\dos\*.* d:\ibmlan\doslan\lsp\dos where d is the drive that lan server is installed on ═══ 3.2. Updating Remote IPL Servers ═══ CAUTION: Before updating remote IPL servers, please review the appropriate SPECIAL RIPL CONSIDERATIONS section of this document for Operating System specific information: If the Server is intended to Remote IPL OS/2 2.00.1, OS/2 2.1, OS/2 For Windows, or OS/2 Warp V3 then the following steps are necessary after complete installation of this ServicePak and LAN Support Program (LSP) version 1.38: 1. If creating OS/2 For Windows Remote IPL clients, preliminary steps are required before using RIPLINST. 2. If OS/2 2.00.1, 2.1, or OS/2 FOR Windows have not been installed in the Remote IPL directory, use the appropriate version of the OS/2 utility RIPLINST.EXE to install the desired version of OS/2. OS/2 Warp V3 does not have to be installed in the Remote IPL directory prior to running RPLS7060.CMD. 3. If updating the OS/2 RIPL directories with an OS/2 2.0 or 2.1 ServicePak, special procedures must be followed before continuing to the next step. 4. Run RPLS7060.CMD to: o Create the Remote IPL directories and files used to RIPL OS/2 2.00.1 (DEFALT2A). o Create the Remote IPL directories and files used to RIPL OS/2 2.1 (DEFALT21). o Create the Remote IPL directories and files used to RIPL OS/2 Warp V3 (DEFALT30). o Update the DEFALT21.FIT file to reflect the server name. o Update the DEFALT30.FIT file to reflect the server name. o Update and copy the OS/2 2.1 WINOS2 *.INI and *.GRP files to the correct default directory. o Create the OS/2 2.1 RIPL configuration files (*.CNF). o Create the OS/2 Warp V3 RIPL configuration files (*.CNF). o Update existing RIPL configuration files to support DOS LAN Support Program V1.38. o Update RPL.MAP to add server records for the new *.CNF files. 5. Start the Server. 6. Logon with Administrator Authority. 7. Run GETRPL.EXE to: o Migrate RPL.MAP workstation and server records from previous levels of LAN Server into the RPL.MAP on the current Remote IPL Server. o Move DOS Remote IPL users from previous levels of LAN Server into a group called RPLGROUP and create an access control profile for RPLGROUP granting all privileges to the users in that group. o Ensure that new OS/2 and DOS Remote IPL users added with LAN Server 3.0 are added to the group. o Create the default OS2.INI, OS2INI.20, OS2SYS.INI and OS2SYINI.20, and REINSTAL.INI files. o Update RPL.MAP to enable only the OS/2 server records for versions of OS/2 that are installed in the Remote IPL directory. In addition, only server records for which the corresponding LAN adapter is installed in the server will be enabled. CAUTION: DO NOT run RPLSETD.CMD until the steps above have been completed. CAUTION: After installing IPx7045 (where x indicates country code) or IPx7060, do not use the 21RIPL.ZIP package that is available on CompuServe. ═══ 3.3. Upgrading DOS LAN Requesters (DLR) ═══ If there are DLR clients using the server, execute UPGRDLR.BAT to copy the DLR files located in \IBMLAN\DOSLAN\NET to DLR workstations. UPGRDLR.BAT must be made PUBLIC before it can be used by a DLR client. For detailed information see Network Administrators Reference Volume 1: Planning and Installation, "Upgrading DOS LAN Requester". ═══ 3.3.1. Make UPGRDLR.BAT Public ═══ o Define an alias for \IBMLAN\DOSLAN\NET. o Set up the Access Control Profile for the alias as Read (R) access. o Define UPGRDLR.BAT as a public DOS application using the Create DOS Application panel. o Using the Manage DOS Applications panel: - Make a working directory for UPGRDLR. - Select the User IDs (or All) that are to have access to UPGRDLR. ═══ 3.3.2. Upgrading the DLR Workstations ═══ o Type "Net Start" and press Enter. o Type "Initfsi" and press Enter. o Type "Net" and press Enter. o Log onto the Domain. o Select the upgrade application (UPGRDLR.BAT) from the Served Applications panel. o Manually reboot the workstation after all disk activity has stopped. CAUTION: - Any attempt to use the workstation before manually rebooting will result in load failures, protection faults, or other errors. ═══ 4. Existing Problems ═══ This section contains descriptions of existing problems and their workarounds. A ServicePak number in parenthesis following the title indicates that this problem has been reported in that previous ServicePak. ═══ 4.1. Not all DOS 6.X files are expanded for RIPL on LS 3.01 REFRESH and above. ═══ APAR IC07136 reports the following workaround for DOS 6.x files that are not expanded for RIPL: DOS support must be installed on the remote IPL server to EXPAND the DOS files. If the remote IPL server does not have DOS support, then the files may be EXPANDed on another system and then copied to the remote IPL server into the d:\IBMLAN\DOSLAN\DOS directory. If only some of the DOS files were EXPANDed on the remote IPL server, start a DOS full screen or windowed session. Change directory to the d:/IBMLAN/DOSLAN/DOS directory. Run the EXPAND6X.BAT file that was created by the LANINST program. If all files were EXPANDed except for the E.E_ file, start a DOS full screen or windowed session. Change directory to the D:/IBMLAN/DOSLAN/DOS directory and type the following command: EXPAND d:/IBMLAN/DOSLAN/DOS/E.E_ d:/IBMLAN/DOSLAN/DOS/E.EX ═══ 4.2. HANG IN UPGRDLR WHEN RUNNING UNDER WIN3.1. (IPx7045) ═══ DLR machine will hang when attempting to run UPGRDLR.BAT from Windows 3.1 on MS DOS 6.1 when Windows is started using the WIN command without the /s parameter. This problem can be avoided by adding the parameter CF=Y to the DEVICE= statement for DXMT0MOD in the CONFIG.SYS file. EXAMPLE: DEVICE=C:\LSP\DXMT0MOD.SYS O=N S=12 C=14 ST=12 CF=Y ═══ 4.3. SEGMENT LOAD FAILURE RUNNING UPGRDLR.BAT (IPx7045) ═══ When UPGRDLR.BAT is run on a DLR machine with Windows 3.1 the upgrade appears to run successfully but at it's conclusion the following message may be displayed: Application Error RUNLSAPP caused Segment Load Failure in module RUNLSAPP.EXE at 0001:1956 The DLR upgrade completes successfully. This error occurs when UPGRDLR.BAT attempts to re-boot. Press ENTER to acknowledge the message and close UPGRDLR.BAT. Then re-boot the machine manually. ═══ 4.4. DLR DOES NOT INSTALL ON MS DOS 6.0 OR HIGHER (IPx7045) ═══ DOS LAN Requester will not install on MS DOS 6.0 or higher. This ServicePak includes replacement install modules that will allow the installation of DLR on higher levels of DOS. After installing this ServicePak and making a backup copy of the DLR INSTALL diskette 1 from LS 3.0, create a new DLR install diskette 1 using one of the methods below. 1. If the IBMLAN\DOSLAN\DLRINST directory exists on the server: o Copy CIP_MAIN.EXE and ISADJ.IA from the \IBMLAN\DOSLAN\DLRINST directory to the appropriate directory on DLR INSTALL diskette 1, overwriting the original files. The files may be marked as READ ONLY. If the COPY fails, issue an ATTRIB command naming the file and using the -R parameter to turn off the READ ONLY attribute. ATTRIB A:\CIP_MAIN.EXE -R COPY d:\IBMLAN\DOSLAN\DLRINST\CIP_MAIN.EXE A:\CIP_MAIN.EXE where d: is the drive on which the updated LS 3.0 resides COPY d:\IBMLAN\DOSLAN\DLRINST\ISASDJ.IA A:\IADIR\ISADJ.IA where d: is the drive on which the updated LS 3.0 resides ATTRIB A:\CIP_MAIN.EXE +R 2. IF IBMLAN\DOSLAN\DLRINST directory does NOT exist on the server the required files can be unpacked from the ServicePak diskettes as follows: o Create a temporary directory, TEMPINST, on the hard disk. Change to the TEMPINST directory. o Copy DLR INSTALL diskette 1 and all it's subdirectories to the temporary directory. XCOPY A:\*.* x:\TEMPINST /s where x: is the drive where TEMPINST is located o Use the UNPACK2 command (located on the ServicePak Tool diskette) to unpack and copy CIP_MAIN.EXE from diskette 4 of IPx7060(where x indicates country code) ServicePak(\FIX\DLR.6 directory) to the temporary directory, overlaying the same named file from the original DLR INSTALL diskette. ATTRIB A:\CIP_MAIN.EXE -R UNPACK2 A:\FIX\DLR.6\CIP_MAIN.EX_ x:\TEMPINST\CIP_MAIN.EXE where x: is the drive where TEMPINST is located ATTRIB A:\CIP_MAIN.EXE +R o Use the UNPACK2 command (located on the ServicePak Tool diskette) to unpack and copy ISADJ.IA from diskette 5 of IPx7060 (where x indicates country code) ServicePak (\FIX\DLR.6 directory) to the temporary directory, overlaying the same named file from the original DLR INSTALL diskette. UNPACK2 A:\FIX\DLR.6\ISADJ.IA_ x:\TEMPINST\IADIR\ISADJ.IA where x: is the drive where TEMPINST is located o Copy the entire updated TEMPINST directory tree to diskette. This will be the new DLR INSTALL diskette 1. XCOPY x:\TEMPINST\*.* A:\ /s where x: is the drive where TEMPINST is located 3. Use the modified install diskette set to install DLR on machines with MS DOS 6.x. ═══ 4.5. RIPL PROBLEM WITH OS/2 2.1 SERVICE PAK XRx6200 (IPx7045) ═══ When XRx6200 is applied to the RIPL copy of OS/2 2.1, and the server is running OS/2 2.0 or OS/2 2.0 + a Service Pak, the XRx6200 Service Pak installation may fail with an error in XRx6200 PRODUCT.EXE. In this case, the SYSLEVEL.OS2 file does not get updated to the correct level. This causes problems with RIPL. If this situation is encountered, see the SPECIAL PROCEDURES FOR OS/2 2.1 SERVICE PAK section of this document for instructions on how to RIPL XRx6200. ═══ 4.6. REQUESTER DISKETTE 3 REQUESTED WHEN INSTALLING LSP 1.38 (IPx7045) ═══ When installing the LSP 1.38 using LAN INSTALLATION and CONFIGURATION panels, if FFST has a status of "older version" or "damaged", the user is prompted to insert Requester diskette 3 before being prompted for LSP diskette 1 as expected. In this case, the user should insert Requester diskette 3 as directed and proceed with the reinstallation of FFST. After the FFST installation completes, the user is then prompted for the LSP diskette and can continue with the installation of LSP 1.38 as described in the INSTALL LSP 1.38 IMAGE section of this document. ═══ 5. Remote IPL Information ═══ This section contains additional information for Remote IPL. ═══ 5.1. Remote IPL Restrictions ═══ o Concurrent Applications Memory constrained remote IPL workstations should not try to run too many applications concurrently. If too many applications are running concurrently, the performance may become very slow and the workstation may eventually lock up. If the workstation locks up, the only recovery may be to power off. This recovery could result in lost data. o Server Name/Workstation Name (DBCS only) When installing a server that will be used as an OS/2 Remoteboot server, the server name can only contain DBCS characters in the range X'81'-X'9F.' The same restriction also applies to remoteboot workstation names. This restriction does not apply to Remoteboot servers that only boot DOS workstations. ═══ 5.2. LAN Server Remote IPL Service Upgrade Summary ═══ The following changes/additions have been made to Remote IPL Service: o The full screen interface was updated to default the 'File Index Table to model' parameter as follows: Server record type Model FIT OS/2 2.0 DEFALT20.FIT OS/2 2.00.1 DEFALT20.FIT OS/2 2.1 DEFALT21.FIT OS/2 3.0 DEFALT30.FIT o Changes were also made to remove the 'Read' attribute on OS/2 2.1 client INI files before attempting to delete them. The client file, AUTOEXEC.20, is updated to reflect the boot drive id. o The GETRPL.EXE utility has been updated to be CID enabled. Several new command line options have been added. RPL.MAP wil be updated to enable only the OS/2 server records for versions of OS/2 that are installed in the Remote IPL directory. In addition, only server records for which the corresponding LAN adapter is installed in the server will be enabled. o The RPLSETD.CMD REXX procedure has been updated to support the following OS/2 RIPL client upgrades: Current Client Operating System New Client Operating System 1.3.2 No updates supported 2.0 2.0 + SP, 2.00.1, 2.1* or OS/2 for Windows, Warp V3 for Windows, Warp V3 with Windows 2.0 + SP 2.1* or OS/2 for Windows, Warp V3 for Windows, Warp V3 with Windows 2.00.1 2.1* or OS/2 for Windows, Warp V3 for Windows, Warp V3 with Windows 2.1* Warp V3 for Windows, Warp V3 with Windows The following option changes/additions have been made to RPLSETD.CMD: /D: No longer a required parameter. Additional SVGA options have been added. /O: If not specified, the operating system directory is determined for the client being updated. /B: New. Specifies the bus type of a client (MCA or ISA/EISA). /S: New. Specifies whether the SWAPPATH is on a local drive or the RIPL server. RPLSETD.CMD has been moved from the \IBMLAN\RPL directory to the \IBMLAN\NETPROG directory so that it can be located via the PATH statement and executed from any directory. The LANINST program requires that a copy of RPLSETD.CMD be located in \IBMLAN\RPL. For this reason, a dummy version of RPLSETD.CMD is installed in the \IBMLAN\RPL directory. This dummy version invokes the version in \IBMLAN\NETPROG. o Default 2.1 WIN-OS/2 INI files are provided that are preconfigured for VGA display support. XGA and 8514 support statements are also present but commented out. When the /D option is specified on RPLSETD.CMD, the client copy of the SYSTEM.INI file will be updated to reflect the display type specified. The /S option will also cause the client copy of the SYSTEM.INI file to be updated. ═══ 5.3. Valid OS/2 / Remote IPL Configurations ═══ The following table identifies valid OS/2 / Remote IPL configurations: ┌─────────┬───────────────────────────────────────────────────────────────────────┐ │ │ Operating System to be Remote IPLed │ │ │Server │ OS/2 WARP OS/2 WARP│ │Operating│ 2.0+ OS/2 For V3 FOR V3 With │ │System │1.3.2 2.0 Service Pak 2.00.1 2.1 Windows WINDOWS WINDOWS │ │─────────┼──────┬─────┬───────────────┬───────┬─────┬────────┬─────────┬─────────│ │1.3.2 │ No │ No │ No │ No │ No │ No │ No │ No │ │ │ │ │ │ │ │ │ │ │ │ 2.x │ No │ Yes │ Yes │ Yes │ Yes │ Yes │ Yes │ Yes │ │ │ │ │ │ │ │ │ │ │ │ 3.0 │ No │ Yes │ Yes │ Yes │ Yes │ Yes │ Yes │ Yes │ └─────────┴──────┴─────┴───────────────┴───────┴─────┴────────┴─────────┴─────────┘ Note: 1. OS/2 2.1 and OS/2 For Windows are mutually exclusive. Only one of them can be installed in the RIPL tree, not both. Note: 2. OS/2 Warp V3 for Windows and OS/2 Warp V3 with Windows are mutually exclusive. Only one of them can be installed in the RIPL tree, not both. ═══ 5.4. Special RIPL Considerations ═══ The following sections describe items that need special consideration when a Remote IPL is to be performed. ═══ 5.4.1. Special Procedures For OS/2 2.x Service Paks ═══ Service Paks for OS/2 2.0 and 2.1 do not update the RIPL directory tree correctly. After installing one of the OS/2 2.x Service Paks, the appropriate REXX procedure (described below) must be run to finish the update of the RIPL directory tree. o For OS/2 2.0 + Service Pak (XRx6055): RPLSPDDI.CMD Installs the OS/2 Service Pak files in the RIPL directory that were not installed by the OS/2 Service Pak. Do NOT use the version of RPLSPDDI.CMD and RPLSETD.CMD made available on diskette 2 of the OS/2 Service Pak. An updated version is provided with this package. o For OS/2 2.0 + Service Pak 2 (XRx6100): RPLSP2DI.CMD Installs the OS/2 Service Pak 2 files in the RIPL directory that were not installed by the OS/2 Service Pak 2. o For OS/2 2.1 + Service Pak (XRx6200): The procedure for updating the OS/2 2.1 RIPL directories with the 2.1 Service Pak varies depending on what version of OS/2 the server is running. - Procedure 1: The server is running OS/2 2.1: 1. Use SERVICE or FSERVICE to apply the OS/2 2.1 Service Pak to the base operating system only. Do not try to update the base operating system and the RIPL directories at the same time. 2. Use SERVICE or FSERVICE to apply the OS/2 2.1 Service Pak to the copy of OS/2 2.1 in the RIPL directory. 3. If the Service Pak installation fails with an error in XRx6200 PRODUCT.EXE, the SYSLEVEL.OS2 file does not get updated to the correct level. The following manual procedure can be used to update SYSLEVEL.OS2: -- Change to the appropriate RIPL directory by entering the command: CD d:\IBMLAN\RPL\OS2.21\OS2\INSTALL where d is the drive where the RIPL directory tree is located. -- Make a backup copy of SYSLEVEL.OS2 by entering the command: COPY SYSLEVEL.OS2 SYSLEVEL.BAK -- Update SYSLEVEL.OS2 using the OS/2 PATCH command: ATTRIB SYSLEVEL.OS2 -R PATCH SYSLEVEL.OS2 -- When prompted, enter an offset of 29. -- Verify the following pattern is displayed: 00 00 00 58 52 xx 32 30 31 30 .... where xx can be any hexadecimal digits. -- Overtype the first, seventh, eighth, and ninth pairs of numbers (indicated with '*') as follows: 01 00 00 58 52 xx 36 32 30 30 .... * * * * -- Press Enter. -- Reply 'N' to the prompt asking if additional updates will be made. -- Restore READ ONLY attribute of the SYSLEVEL.OS2 file. ATTRIB SYSLEVEL.OS2 +R -- This completes the application of XRx6200 to the copy of OS/2 2.1 in the RIPL directory. - Procedure 2: The server is running OS/2 2.0 or 2.0 + a Service Pak: 1. Apply the OS/2 2.1 Service Pak to the copy of OS/2 2.1 in the RIPL directory. 2. If the Service Pak installation fails with an error in the XRx6200 PRODUCT.EXE use the manual procedure described in step 3 above to patch the SYSLEVEL.OS2. The OS/2 2.1 Service Pak does not update the video device drivers in the RIPL directory tree correctly. A REXX procedure, RPLSP211.CMD, has been provided in IPx7045, and above, to correct this problem. RPLSP211.CMD will install the OS/2 2.1 Service Pak Display Support diskettes into the RIPL directory. The command syntax for RPLSP211.CMD can be displayed by entering the command: RPLSP211 /H ═══ 5.4.2. OS/2 2.00.1 (OS/2 Preinstall) ═══ If you have access to the OS/2 Preinstalled Restore Diskette Pack, it is recommended that you use the RIPLINST utility (located on diskette 7) to install the new version of OS/2 2.0 in the directory d:\IBMLAN\RPL\OS2.20a (d is the drive where IBMLAN\RPL was installed). If you have the prior version of OS/2 2.0 installed, this will leave the prior version installed in the d:\IBMLAN\RPL\OS2.20 directory. After using RPLSETD to complete the migration to the new display drivers, the OS2.20 directory tree can be deleted. The menu interface has been updated to automatically select the FITS\DEFALT2A.FIT entry when a 'NEW' client is created using an OS/2 2.00.1 server record ID. However, the master CONFIG.20 files are not automatically updated to OS/2 2.00.1 level so that back level versions of OS/2 can also be supported. RPLSETD must be used to update the client to the OS/2 2.00.1 level. There is no support for SVGA on OS/2 2.00.1 RIPL clients. ═══ 5.4.3. Creating New OS/2 2.1 Remote IPL Clients ═══ IBM LAN Server 3.0 has been updated to support the remote IPL of OS/2 2.1 RIPL clients. The menu interface has been updated to automatically select the FITS\DEFALT21.FIT entry when a 'NEW' client is created using an OS/2 2.1 server record ID. However, the master CONFIG.20 files are not automatically updated to OS/2 2.1 level so that back level versions of OS/2 can also be supported. RPLSETD must be used to update the CONFIG.20 file to the OS/2 2.1 level. A new Remote IPL client created using the defaults, will be configured to support the IBMVGA32 display drivers. If the client has an XGA or 8514 display attached, RPLSETD must be run against the client to reconfigure the client for the correct display type. There is no support for SVGA on OS/2 2.1 (CSD level XR02010) RIPL clients. There is limited support for SVGA on OS/2 2.11 (CSD level XR06200) RIPL clients. Warning: After installing IPx7045 (where x indicates country code) or IPx7060, do not use the 21RIPL.ZIP package that is available on CompuServe or several other BBS systems. ═══ 5.4.4. Creating New OS/2 For Windows Remote IPL Clients ═══ IBM LAN Server 3.0 has been updated to support the remote IPL of OS/2 For Windows RIPL clients. OS/2 For Windows and OS/2 2.1 both install into the \IBMLAN\RPL\OS2.21 directory in the RIPL tree. For this reason, you can install OS/2 For Windows or OS/2 2.1, but not both. The Windows 3.1 code must be installed in the directory \IBMLAN\RPL\OS2.21\WINDOWS prior to using RIPLINST to install OS/2 For Windows in the RIPL tree. Three possible methods for completing this step are given below (choose one): 1. If the Windows 3.1 code is already installed on the server, copy the installed d:\WINDOWS directory tree into the e:\IBMLAN\RPL\OS2.21\WINDOWS directory tree using the XCOPY command below. 2. If the Windows 3.1 code is not installed on the server, boot the server with DOS and install Microsoft Windows 3.1 to a FAT partition on the server. Reboot the server and allow it to boot the OS/2 operating system. Copy the Windows files from the FAT partition to the d:\IBMLAN\RPL\OS2.21\WINDOWS directory tree using the XCOPY command below. 3. Install the Windows 3.1 code on a DOS machine. Remote IPL OS/2 to that machine. Start the LAN Requester and NET USE the drive where \IBMLAN\RPL is installed. Copy the Windows files from the local hardfile to the server using the XCOPY command below. XCOPY e:\WINDOWS d:\IBMLAN\RPL\OS2.21\WINDOWS /S /E where e: is the partition where Windows is installed d: is the partition where OS/2 RIPL is installed To create OS/2 For Windows RIPL clients, use the OS/2 2.1 options for creating new Remote IPL clients. ═══ 5.4.5. Support For OS/2 32-bit Display Device Drivers ═══ Prior to IPx7045, the LAN Server 3.0 Remote IPL service supported, by default, the OS/2 2.0 16-bit VGA display device driver. If one of the following versions of OS/2 that support 32-bit display device drivers is installed in the Remote IPL directory structure, use RPLSETD to upgrade existing RIPL clients to use the new display device drivers: o OS/2 2.0 + Service Pak (XRx6055, where x indicates country code) o OS/2 2.0 + Service Pak 2 (XRx6100) o OS/2 2.00.1 o OS/2 2.1* or OS/2 For Windows If an attempt is made to remote IPL an existing client workstation prior to upgrading the client, the client will hang while trying to initialize the display. New Warp clients will default to the 32-bit VGA display device drivers. ═══ 5.4.6. Updating Master Workplace Shell OS2.INI Files ═══ Some users have a master customized OS2.INI file that is copied to the client directory each time the client is remote IPLed. This master file must also be updated to identify the type of display driver that the client workstation is using. Clients with different display types (i.e. VGA, XGA, 8514, SVGA) MUST use different master OS2.INI files. To update a master OS2.INI file, enter the following command: RPLRXUTL /D:DISPLAY_DRIVER /C:INI_FILENAME where: /D:DISPLAY_DRIVER is the same as for RPLSETD for all display types except SVGA and S3SVGA. For SVGA and S3SVGA, you must specify IBMVGA32 as the display driver. /C:INI_FILENAME is the drive, path, and filename of the master OS2.INI file to be updated. For example: RPLRXUTL /D:IBMVGA32 /C:E:\IBMLAN\RPL\MASTER\VGAOS2.INI The RPLRXUTL utility will not display any error information. It does return with a non-zero return code if an error occurs. If you need to verify error information, invoke RPLRXUTL from a CMD procedure (batch file or REXX) so that the return code can be tested. ═══ 5.4.7. Supporting Multiple Levels of the OS/2 Operating System ═══ It is possible to install and support multiple levels of the OS/2 2.x operating system on a RIPL server. This section documents the correct procedure to use to support such an environment. The basic procedure is as follows: 1. Run the OS/2 utility RIPLINST to install the OS/2 code in the RIPL directory tree. You must be careful to use the version of RIPLINST that matches the level of code to be installed. RIPLINST is located on diskette 7 of all OS/2 2.x installation diskettes. RIPLINST is unique for each version of OS/2. 2. After running RIPLINST, run the LAN Server utility, GETRPL. GETRPL uses information stored in the OS2SYS.INI file by RIPLINST so it is very important that GETRPL be run before using RIPLINST to install another version of OS/2. 3. Repeat steps 1 and 2 for each version of OS/2 that will be RIPLed. 4. Check the \IBMLAN\RPL\RPL.MAP file. Look for the OS/2 server records, they start with yyyyyyyyyyyy or ;yyyyyyyyyyyy and field two will contain a name like OS220*.CNF or OS221*.CNF. A semicolon (;) in column 1 indicates the record is disabled. Make sure that the appropriate records are enabled/disabled based on what OS/2 version(s) you installed. 5. Determine whether the special RIPL client, DEFALT20, should be updated by RPLSETD. This depends on what OS/2 versions are installed. OS/2 version 2.0 uses 16 bit display drivers. OS/2 versions 2.00.1, 2.0+Service Pak, and 2.1* use 32 bit display drivers for VGA and XGA support. However, there are slight differences in the XGA support between 2.00.1 and the newer operating system versions (OS/2 2.0 + a Service Pak or 2.1*.) If OS/2 2.0 is present, DEFALT20 must not be updated. It must remain as is to allow the creation of future 2.0 clients. If OS/2 2.0 is not present, then DEFALT20 could be updated with RPLSETD to support either 2.00.1 or 2.0 + a Service Pak or 2.1*. To update DEFALT20 to support 2.0 + a Service Pak, enter the command: RPLSETD /D:IBMVGA32 /C:DEFALT20 To update DEFALT20 to support 2.00.1, enter the command: RPLSETD /D:IBMVGA32 /C:DEFALT20 /N:OS2.20a The /N parameter indicates that the new default target operating system will be \IBMLAN\RPL\OS2.20a. The RIPLINST for OS/2 2.00.1 defaults to a target directory of \IBMLAN\RPL\OS2.20a. To update DEFALT20 to support 2.1, enter the command: RPLSETD /D:IBMVGA32 /C:DEFALT20 /N:OS2.21 The /N parameter indicates that the new default target operating system will be \IBMLAN\RPL\OS2.21. The RIPLINST for OS/2 2.1 defaults to a target directory of \IBMLAN\RPL\OS2.21. 6. Since the special RIPL client DEFALT20 must be associated with a specific OS/2 version, it is recommended that model clients be created for the other OS/2 versions installed in the RIPL tree. RPLSETD can be used to update the model client definitions to point to the correct operating system. Then these model clients can be used to create future clients for each operating system type. ═══ 5.4.8. Preserving the Ability to Remote IPL OS/2 1.3 Clients ═══ If you upgrade an existing OS/2 1.30.1/LAN Server 2.0 server that has OS/2 Remote IPL installed to OS/2 2.0/LAN Server 3.0, the ability to remote IPL OS/2 1.3 client workstations is not preserved. If you need to preserve the ability to remote IPL OS/2 1.3 client workstations, you must use the procedure described below when upgrading the server. Two REXX command procedures, RPLSAV13.CMD and RPLRES13.CMD, have been provided to assist you in saving and then restoring the ability to Remote IPL OS/2 1.3 client workstations. These procedures are located on the LAN Server 3.0 Productivity Aids diskette 1 in the file RPLUTIL.ZIP. The following procedure assumes that you are installing LAN Server 3.0 on top of an existing LAN Server 2.0. Warning: The procedure will preserve 23MB of OS/2 1.3 remote IPL data. Be sure that you have sufficient space on your hardfile for this data and LAN Server 3.0 before starting this procedure. 1. If you have OS/2 1.3 and LAN Server 2.0 Advanced installed and you want to upgrade to OS/2 2.0 and LAN Server 3.0, the 386HPFS access control lists must be removed prior to installing OS/2 2.0. Insert the SERVER 1 diskette of LS 3.0 and run PREPACL to remove the access control lists. To run PREPACL, enter the following command: A:PREPACL /P /B:C:\ACL.LST /D:C: where: P indicates remove access control lists B indicates save ACL's in a list with path and filename D indicates remove the access control lists on the C drive Type PREPACL to display the parameter list. If you have OS/2 on the C drive and LAN on the D drive, THIN386 can be run on the D drive to remove enough access control lists to install LAN Server 3.0 over LAN Server 2.0. PREPACL can be run on the C drive for OS/2. Install the remote IPL REXX procedures located on the Productivity Aids diskette 1. To install these REXX procedures, do the following: a. Change to the d:\IBMLAN\INSTALL directory. b. Enter the following command (all on one line): PKUNZIP2 -D A:\RPLUTIL.ZIP d:\IBMLAN\RPL RPLSAV13.CMD RPLRES13.CMD where d is the drive where IBMLAN is installed. 2. Prior to installing OS/2 2.0, execute the REXX procedure RPLSAV13.CMD to save the appropriate OS/2 1.3 Remote IPL directories and files. To run the procedure, enter the command: d:\IBMLAN\RPL\RPLSAV13.CMD RPLSAV13.CMD performs the following functions: o Renames RPL\MUGLIB to RPL\MUGLIB13. o Renames RPL\IBMCOM to RPL\IBMCOM13. o Renames RPL\IBMLAN to RPL\IBMLAN13. o Renames RPL\OS2 to RPL\OS213. o Copies RPL.MAP to RPL\RPL13\. o Copies RPL\OS2BB*.CNF to RPL\RPL13\. Everything is saved under the RPL directory. Any other application subdirectories that are unique to OS/2 1.3 must be manually saved. 3. Install OS/2 2.0. (Be sure to select "REXX" on the OS/2 Setup and Installation panel.) 4. Install NTS/2. 5. Shutdown. 6. Install LAN Server 3.0. 7. Shutdown. 8. Insert SERVER 1 diskette in drive A and run PREPACL. To run PREPACL, enter the following command: A:PREPACL /R /B:C:\ACL.LST where R restores the ACLs and B says from what list. 9. Run the REXX procedure RPLRES13.CMD to make the changes required to support the OS/2 1.3 code base saved in step 3. To run the procedure, enter the following command: d:\IBMLAN\RPL\RPLRES13.CMD RPLRES13.CMD performs the following functions: o Renames RPL\OS213 to RPL\OS2. o Copies the saved CONFIG.13 files (in IBMCOM13 directory) to RPL\IBMCOM. o If necessary, updates RPL.MAP to contain the OS/2 1.3 server records. o Copies the saved OS2BB*.CNF files back to the RPL directory and updates them to be compatible with LAN Support Program V1.38. o Updates all the OS/2 1.3 *.FIT files to refer to the renamed MUGLIB13, IBMCOM13, and IBMLAN13 directories. 10. Unpack RIPLINST from diskette 7 of OS/2 2.0 diskettes and run the RIPLINST utility. 11. Start the server and log on, then run GETRPL. When GETRPL prompts for the first OS/2 1.3 Install diskette, select the Cancel option. Selecting the Cancel option will result in a warning message when GETRPL completes, but the message can be ignored. 12. If there were any predefined DOS workstations, a new DOS image needs to be made in order for the workstations to be able to remoteboot. 13. OS/2 1.3 client workstations can now be defined and remote IPLed. Existing OS/2 1.3 client workstations can be remote IPLed. OS/2 2.0 client workstations can now be defined and remote IPLed. ═══ 5.4.9. Special Considerations for Remote IPL of Warp ═══ The following sections provide information needed to Remote IPL on an OS/2 Warp system. ═══ 5.4.9.1. XDF Diskette Support Requirement ═══ The OS/2 Warp V3 installation diskettes are delivered in XDF diskette format. The Remote IPL server must be upgraded to support the XDF diskette format before the OS/2 Warp V3 support can be installed on the server. OS/2 2.1 servers can be upgraded to support the XDF diskette format. DOUBLE CLICK HERE for instructions on how to upgrade an OS/2 2.1 server. OS/2 1.x and OS/2 2.0 systems below ServicePak XRx6100 cannot be upgraded to support the XDF diskette format. Remote IPL support for OS/2 Warp V3 can not be installed on such systems. ═══ 5.4.9.2. Installing XDF Support on Remote IPL Servers ═══ If an OS/2 2.1 or OS/2 2.0 + XR06100 system is used for the code server, modifications must be made to the system in order to read the OS/2 Warp Version 3 XDF format installation diskettes. OS/2 Warp Version 3 systems will read these diskettes without any modification. To modify the OS/2 2.1 or OS/2 2.0 + XR06100 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 OS/2 Warp Version 3 diskette #1 to the \OS2 directory. 3. Add the following line to your CONFIG.SYS file: BASEDEV=XDFLOPPY.FLT o Micro Channel*-bus Systems: 1. Rename IBM2FLPY.ADD to IBM2FLPY.OLD in the \OS2 directory. 2. Copy XDFLOPPY.FLT and IBM2FLPY.ADD from OS/2 Warp Version 3 diskette #1 to the \OS2 directory. 3. Add the following line to your CONFIG.SYS file: BASEDEV=XDFLOPPY.FLT Note: OS/2 1.x and OS/2 2.0 systems below XR06100 cannot be updated to read the OS/2 Warp Version 3 XDF format installation diskettes. ═══ 5.4.9.3. Migrating Existing RIPL Clients To OS/2 Warp V3 for Windows ═══ Existing RIPL clients that are defined as OS/2 2.x type RIPL clients can not be migrated to OS/2 Warp V3 for Windows. Such clients must be deleted and recreated to switch to OS/2 Warp V3 for Windows. ═══ 5.4.9.4. Migrating Existing RIPL Clients To OS/2 Warp V3 With Windows (FullPak) ═══ Existing RIPL clients that are defined as OS/2 2.x type RIPL clients can be migrated to OS/2 Warp V3 With Windows clients using the RPLSETD.CMD REXX procedure. To migrate to OS/2 Warp V3 With Windows, enter the following command for each client to be migrated: RPLSETD /C:clientname /N:OS2.30 or RPLSETD /C:clientname1,clientname2,clientname3 /N:OS2.30 When OS/2 2.x clients are migrated to OS/2 Warp V3 With Windows, the following special conditions occur: o Major restructuring of the Desktop will take place. The first time the RIPL client reboots, it will look like a first time boot and take longer than normal. See the "Special Considerations for Migrating Customized Desktops" section of this document for additional information on updating customized Desktops. o A 'Drive A' shadow is left on the Desktop. This object is no longer needed since a shadow of drive A is automatically placed in the LaunchPad. The old 'Drive A' shadow on the Desktop can be deleted manually. o For OS/2 2.0 clients, all of the client Win-OS/2 *.INI and *.GRP files must be replaced with the Warp version. The old files are renamed *.OLD and left in the client directory for reference. o OS/2 2.11 clients configured for SVGA support can not be directly migrated to OS/2 Warp V3 With Windows SVGA support. After migrating OS/2 2.11 clients configured for SVGA support, the video system is reset to VGA mode. When the system is restarted a message will be displayed telling the user to wait until the Desktop creation completes and then run the OS/2 Selective Install function to reinstall SVGA support. After reinstalling the SVGA support, the client must be shutdown and restarted. o After migrating OS/2 2.11 clients configured for S3SVGA support, when the system is restarted the RIPL client will come up in VGA mode and automatically recreate the SVGADATA.PMI file. The user is instructed to wait until the Desktop creation completes and then to shutdown and restart to pick up the new copy of the SVGADATA.PMI file. When the client is restarted, it will come up in SVGA mode. ═══ 5.4.9.5. Creating New OS/2 Warp Remote IPL Clients ═══ IBM LAN Server 3.0 has been updated to support the remote IPL of OS/2 Warp RIPL clients. The menu interface has been updated to automatically select the FITS\DEFALT30.FIT entry when a 'NEW' client is created using an OS/2 Warp server record ID. A new Remote IPL client, created using the defaults, will be configured to support the IBMVGA32 display drivers. If the client has an XGA, 8514, or SVGA display attached, RPLSETD must be run against the client to reconfigure the client for the correct display type. ═══ 5.4.9.6. Special Considerations for Migrating Customized Desktops ═══ When a RIPL client is migrated to OS/2 Warp V3 With Windows, the Desktop is restructured to be similar to the Desktop of a locally installed OS/2 Warp With Windows system. If the RIPL client Desktop has been customized to remove or modify the standard OS/2 folders and objects, these folders and objects will be recreated by the migration process. However, there is a way to prevent this from occurring. The following procedure should be used: 1. Create a dummy client. 2. Use the RPLSETD.CMD procedure to migrate the dummy client to Warp. The first time a client is migrated to Warp, a special file, \IBMLAN\RPL\OS2.30\OS2\RPMWWINI.RC, is created. This file is used by the migration process to add entries to the client's OS2.INI file such that when the client is restarted the Desktop is recreated in the Warp fashion. This file is not recreated each time a client is migrated. If the file already exists, the existing file is used. 3. Edit the file \IBMLAN\RPL\OS2.30\OS2\RPMWWINI.RC. Delete any of the "PM_InstallObject" entries that would result in unwanted objects being placed on the Desktop or in Desktop folders. 4. If you want to suppress the creation of the LaunchPad object, remove the appropriate entry from RPMWWINI.RC. Also update the \IBMLAN\RPL\MACHINES\DEFALT30\CONFIG.DEF file to remove the LAUNCHPAD option from the SET AUTOSTART line. ═══ 5.4.9.7. Creating the Default Desktop Folders on Warp clients ═══ Use the following procedure to create the default DOS Programs and Windows Programs folders on the Desktop of a RIPL client: 1. Open the System Setup Folder. 2. Select the Add Programs object. 3. Select the 'Search for and select progams to add' option. 4. Deselect any local drives (C: for example). Select the Remote IPL boot drive (default is Z:). 5. Select OK on the 'Select Programs' panel. ═══ 5.4.10. OS/2 SVGA Support For RIPL Clients ═══ Limited SVGA support is provided for OS/2 2.11 and OS/2 Warp RIPL clients. SVGA support can be configured for RIPL clients that are using the following video chip sets: o S3 801/805 o ET4000 o Cirrus Logic 54xx The SVGA support has the following prerequisites: 1. IBM LAN Server V3.0 plus ServicePak IPx7060 installed on the RIPL server. 2. OS/2 REXX support. 3. OS/2 2.11 Manufacturing Refresh, the OS/2 2.11 ServicePak, or OS/2 Warp. 4. RIPL clients must be using one of the video chip sets listed above. 5. IBM PS/ValuePoint machines used as RIPL client must be at BIOS level L6ET53A or later. ═══ 5.4.10.1. Installing OS/2 SVGA Support on the RIPL Server ═══ 1. For OS/2 2.x, ensure that the RIPL Server is at version 2.11. If not, install the OS/2 2.1 manufacturing refresh to the RIPL directory or update the existing RIPL copy of OS/2 2.1 with the OS/2 2.1 ServicePak (csd level XR06200). If you use the XR06200 ServicePak, you must run the REXX procedure RPLSP211.CMD to install the new OS/2 device drivers in the RIPL directory. At an OS/2 command prompt, enter the command: RPLSP211 To see the complete command syntax for RPLSP211, enter the command: RPLSP211 /H 2. Run the RPLSVGAI.CMD procedure for each OS/2 version (2.11 and/or Warp) that is installed in the Remote IPL directory tree. RPLSVGAI can determine from Display Driver diskette 1 which OS/2 version is being updated. If diskettes are used as the source, RPLSVGAI will prompt for the appropriate OS/2 Display Driver diskettes. The Warp Display Driver diskettes are in XDF diskette format. The RIPL server must be updated to support the XDF format before RPLSVGAI can be used to install the Warp SVGA support files. 3. Start the server and logon as an administrator. 4. Run GETRPL. Step 2 created several new subdirectories. GETRPL will create the access control profiles for these directories. If you are running an Advanced Server, you do not need to do this step. ═══ 5.4.10.2. Configuring a Remote IPL Server/Client for OS/2 SVGA Video Support ═══ Configuring a Remote IPL client for SVGA video support is a two step process. First, the RIPL client definition on the RIPL server must be updated. Second, the RIPL client must use the appropriate OS/2 install function to install the SVGA support. The following sections provide step by step instructions for these two functions. ═══ 5.4.10.2.1. Creating a RIPL Client Definition For OS/2 SVGA Support ═══ At the remote IPL server: 1. Create an OS/2 remote IPL client. 2. Use RPLSETD to reconfigure the client for SVGA support. For example, to configure a ISA bus machine called MACH01, use the following command: RPLSETD /C:MACH01 /D:SVGA /B:ISA For a description of the RPLSETD options, enter the command RPLSETD /H or double click here. When the /D:SVGA or S3SVGA option is specified, the RPLSETD utility does not configure the client for SVGA. It modifies the client definition so that the RIPL client can run the appropriate OS/2 install function. CAUTION: Warp SVGA support requires that each RIPL client have a unique copy of the MONITOR.DIF file. This file is approximately 330K in size. Insure that there is enough free space on the hardfile where \IBMLAN\RPLUSER is installed to allow each SVGA workstation to have a copy of this file in addition to the normal hardfile requirements for a RIPL client. Warning: Configuring a workstation for SVGA moves the workstations CONFIG.SYS file from the \RPL\MACHINES\client directory to the \RPLUSER\client directory. The workstation will have write access to this file and could potentially modify it in such a fashion that the workstation could no longer IPL remotely. ═══ 5.4.10.2.2. Installing OS/2 2.11 SVGA Support On The RIPL Client ═══ Perform the following steps on the remote IPL client: 1. Start the remote IPL client. 2. Open an OS/2 window session. 3. Enter the command: DSPINSTL This will start the OS/2 SVGA install program. The 'Display Driver Install' panel will be displayed. 4. Select Primary Display, and then select OK. The Primary Display Adapter Type window is displayed. The detected SVGA adapter is highlighted. 5. Select OK. The Monitor Configuration/Selection Utility window is displayed. 6. Select Install Using Defaults for Monitor Type and then select OK. The screen appears blank for a few seconds, and then, depending on the video chip set installed, either a Screen Resolution Selection window or the Source Directory window is displayed. 7. If the Screen Resolution Selection window is displayed, select the appropriate resolution and then select OK. 8. The Source Directory window is displayed. Change the default source to be d:\OS2\DISP where d: is the boot drive id. Select Install. The selected video support will be installed. Depending on the video adapter, you may be prompted for additional information such as the desired display resolution. A Display Driver Install information window is displayed indicating that shutdown is required before the changes become effective. 9. If non-S3 SVGA support was installed, shutdown the system and restart it. If during the install (step 6), you were not prompted to select a display resolution, continue with the following steps after the system restarts. For S3 SVGA support, continue with the following steps. 10. Open the System Setup folder. 11. Open the System object. The System Settings notebook is displayed. 12. Select the desired display resolution. 13. Shut down and restart the system to use the new display support. ═══ 5.4.10.2.3. Installing OS/2 Warp SVGA Support On the RIPL Client ═══ Perform the following steps on the remote IPL client: 1. Start the remote IPL client. 2. Open the System Setup folder. 3. Select the Selective Install object. 4. Select Primary Display, and then select OK. The Primary Display Adapter Type window is displayed. The detected SVGA adapter is highlighted. 5. Select OK. The Monitor Configuration/Selection Utility window is displayed. 6. Select Install Using Defaults for Monitor Type and then select OK. The screen appears blank for a few seconds, and then either a Screen Resolution Selection window or the Source Directory window is displayed. 7. If the Screen Resolution Selection window is displayed, select the appropriate resolution. 8. The Source Directory window is displayed. Ensure that the default source (d:\OS2\DISP where d: is the boot drive id) is highlighted. Select Install. The selected video support will be installed. Depending on the video adapter, you may be prompted for additional information such as the desired display resolution. For OS/2 Warp, a panel will be displayed requesting the Microsoft Windows 3.1 diskettes. Change the source field to be d:\OS2\DISP where d: is the boot drive id (default is Z:). Use this same source path for any additional Windows diskettes requested. A Display Driver Install information window is displayed indicating that shutdown is required before the changes become effective. 9. If non-S3 SVGA support was installed, shutdown the system and restart it. If you were not prompted to select a display resolution during the install (step 6), continue with the following steps after the system restarts. If S3 SVGA support was installed, continue with the following steps. 10. Open the System Setup folder. 11. Open the System object. The System Settings notebook is displayed. 12. Select the desired display resolution. 13. Depending on the video adapter installed, the Screen page may have a Page 2 that allows you to configure a specific display for your workstation. 14. Shut down and restart the system to use the new display support. ═══ 5.5. RIPL Utilities and REXX Procedures ═══ The following sections provide information relating to changes in utilities and REXX procedures that are used by Remote IPL. ═══ 5.5.1. OS/2 RIPLINST Utility ═══ Each version of OS/2 has a unique version of RIPLINST. Most versions of RIPLINST have a different default target installation directory. The various default target installation directories are: OS/2 Version Target directory OS/2 2.0 and Service Pak d:\IBMLAN\RPL\OS2.20 OS/2 2.00.1 d:\IBMLAN\RPL\OS2.20a OS/2 2.1* d:\IBMLAN\RPL\OS2.21 OS/2 WARP* d:\IBMLAN\RPL\OS2.30 where d: indicates the drive where IBMLAN\RPL is installed. This prevents an existing ..\OS2.xx directory tree from being overwritten automatically. To upgrade an existing ..\OS2.xx directory tree, the target installation directory must be updated before starting the installation process. The target directory must be on the same drive where OS/2 remote IPL support was installed (this can be different from where LAN Server was installed). The only part of the directory path that should be updated is the drive id. Do not change any of the remaining path information. After using RIPLINST to install OS/2 for remote IPL, run the updated version of the LAN Server utility, GETRPL.EXE. Note: The OS/2 Warp V3 RIPLINST utility requires XDF diskette format support. The RIPLINST utility used to install the OS/2 code for OS/2 LAN Server remote IPL is located (in packed format) on diskette 7 of the OS/2 Installation diskettes. Use one of the following procedures to install and run RIPLINST: If your server operating system is the same as the version of OS/2 being installed by RIPLINST, double click here. If your server operating system is NOT the same as the version of OS/2 being installed by RIPLINST, double click here. ═══ 5.5.1.1. Steps to Install RIPLINST When Server is Same Version as RIPLINST ═══ 1. Insert the OS/2 Install diskette 7 into drive A. 2. Install RIPLINST by typing: UNPACK A:\RIPLINST The RIPLINST files will be unpacked to the \OS2\INSTALL directory. 3. To start the RIPLINST program, go to an OS/2 window or full-screen session and type: RIPLINST 4. Press Enter to remove the title window. 5. The Change Source/Target window is displayed. For OS/2 2.x, the source path should be left as A:\. For OS/2 Warp V3 for Windows, the source path can be updated to point to a diskette image tree created by the OS/2 SEIMAGE utility. CD-ROM drives are not supported as a source path. For OS/2 Warp V3 with Windows, the source path can be updated to point to a diskette image tree created by the OS/2 SEIMAGE utility. CD-ROM drives are supported as a source path. If necessary, the target directory can be updated to change the drive ID of the target. Only the target drive ID should be changed; do not change the default directory paths. The OS/2 code must be installed on the same drive where the OS/2 remote IPL support was installed during LAN Server installation. 6. Select Install. 7. Insert diskettes as prompted. ═══ 5.5.1.2. Steps to Install RIPLINST on Different Version Server ═══ 1. Create a temporary subdirectory by typing: MD TEMPRIPL 2. Change to the temporary subdirectory by typing: CD TEMPRIPL 3. If the version of RIPLINST is OS/2 Warp, additional handling is required for XDF format diskettes. Double click here to perform those steps before continuing with the following step. 4. Insert OS/2 Install diskette 2 into drive A. 5. Copy UNPACK.EXE to the TEMPRIPL directory by typing: COPY A:UNPACK.EXE 6. Check OS/2 Install diskette 2 for the file UNPACK2.EXE. If it is present, copy UNPACK2.EXE to the TEMPRIPL directory by typing: COPY A:UNPACK2.EXE Note: UNPACK2.EXE may not be present. If it is not on diskette 2, you do not need it. 7. Insert OS/2 Install diskette 7 into drive A. 8. Install the RIPLINST files by typing: UNPACK A:\RIPLINST d:\TEMPRIPL where d is the drive ID where TEMPRIPL is located. 9. Start the RIPLINST program by typing: RIPLINST Note: Each version of RIPLINST must use the corresponding OS/2 version of UNPACK and UNPACK2 (if it exists). Failure to do so will result in one of the following error conditions: o RIPLINST will trap while copying the W0F0000.BIO file. o The system will lock up after displaying the copy window. You must reboot if this occurs. 10. Press Enter to clear the title window. 11. The Change Source/Target window is displayed. For OS/2 2.x, the source path should be left as A:\. For OS/2 Warp V3 for Windows, the source path can be updated to point to a diskette image tree created by the OS/2 SEIMAGE utility. CD-ROM drives are not supported as a source path. For OS/2 Warp V3 with Windows, the source path can be updated to point to a diskette image tree created by the OS/2 SEIMAGE utility. CD-ROM drives are supported as a source path. If necessary, the target directory can be udpated to change the drive id of the target. Only the target drive ID should be changed; do not change the default directory paths. The OS/2 code must be installed on the same drive where the OS/2 remote IPL support was installed during LAN Server installation. 12. Select Install. 13. Insert diskettes as prompted. ═══ 5.5.2. RPLSETD.CMD REXX Procedure ═══ The RPLSETD.CMD procedure provides the following functions: o Upgrades existing remote IPL clients to use the appropriate 16 or 32 bit device driver. RPLSETD will determine the version of the target OS/2 and automatically select the appropriate 16 or 32 bit device driver. o In some cases, changes the display type (32-bit VGA, XGA, or 8514) that a remote IPL client is using. The RPLSETD utility does not support converting from the new 32-bit drivers back to the old 16-bit display drivers. o Updates a remote IPL client to perform an IPL on a different version of OS/2. The OS/2 code must be installed in the remote IPL directory structure. The OS/2 version conversions in the following table are supported: ┌───────────────────────────────────────────────────────────────────────────────┐ │OS/2 Version Conversions │ ├─────────────────────────┬─────────────────────────────────────────────────────┤ │OLD VERSION │ NEW VERSION │ ├─────────────────────────┼─────────────────────────────────────────────────────┤ │ 2.0 │ 2.0+ServicePak 1/2, 2.1, 2.1+ServicePak, 2.11, │ │ │ Warp V3 for Windows, Warp V3 With Windows │ ├─────────────────────────┼─────────────────────────────────────────────────────┤ │ 2.00.1 │ 2.0+ServicePak 1/2, 2.1, 2.1+ServicePak, 2.11, │ │ │ Warp V3 for Windows, Warp V3 With Windows │ ├─────────────────────────┼─────────────────────────────────────────────────────┤ │ 2.0+ServicePak 1/2 │ 2.1, 2.1+ServicePak, 2.11, │ │ │ Warp V3 for Windows, Warp V3 With Windows │ ├─────────────────────────┼─────────────────────────────────────────────────────┤ │ 2.1 or 2.11 │ Warp V3 for Windows, Warp V3 With Windows │ ├─────────────────────────┴─────────────────────────────────────────────────────┤ │ NOTE: There is no support for converting any of the newer versions back to │ │ the original OS/2 2.0. After a client is converted to OS/2 2.1, RPLSETD │ │ cannot be used to convert back to 2.0 + ServicePak 1/2 or 2.00.1. │ └───────────────────────────────────────────────────────────────────────────────┘ o Updates a remote IPL client to change the bus type, as in MCA or ISA/EISA. o Updates a remote IPL client to specify whether the SWAPPATH and WIN-OS/2 paging file is on a local hard disk or on the remote IPL server. ═══ 5.5.2.1. Command Syntax For RPLSETD.CMD ═══ The command syntax for RPLSETD.CMD is as follows: >>──RPLSETD──┬─────┬──┬─────────────────┬──/C:client──> └─/H:─┘ └─/R:responsefile─┘ >──┬─/L:logfile─────────────────────────────────────────┬──>< ├─/S:─┬─L─┬──────────────────────────────────────────┤ │ └─S─┘ │ ├─/B:─┬─MCA──┬───────────────────────────────────────┤ │ ├─ISA──│ │ │ └─EISA─┘ │ ├─/D:displaydriver───────────────────────────────────┤ ├──┬──────────────────┬─/N:newos2dir/D:displaydriver─┤ │ └─/O:currentos2dir─┘ │ └─/I:────────────────────────────────────────────────┘ Parameters Use the following parameters with the RPLSETD utility: /C:client1, client2, client3... Equivalent to the CLIENT and CLIENTLIST response file keywords. Specifies the name of one or more OS/2 remote IPL client clients that are to be updated. If multiple client names are specified, each client name must be separated with a comma. Imbedded blanks are not allowed. The response file keywords CLIENT and CLIENTLIST are equivalent to each other. You can specify them as many times as necessary. This is a required parameter if the /R parameter is not specified. When /R is specified, at least one other parameter must also be specified. /H: Displays the syntax on the screen. If specified, it must be the first parameter. /R:responsefile Specifies the drive, path, and file name of a file that contains the command inputs in keyword form (keyword=value). Each keyword corresponds to one of the RPLSETD syntax parameters as indicated in this section. For more information about the response file, see Response File Format. Only one keyword can be specified per line in the response file. The /C (client or clientlist) parameter and at least one other parameter are required when using a response file. If the /R parameter is specified, all other parameters specified on the command line are ignored. /L:logfile Specifies the drive, path, and file name of a file to which all messages and errors are to be logged. If this parameter is specified, the only errors displayed on the screen are for a failure to open the log file or for required parameters missing from the response file. /O:currentos2dir Equivalent to the CURRENTOS2DIR response file keyword. Specifies the root directory under \IBMLAN\RPL for the current version of OS/2 that the client is using. This parameter is case-sensitive. Specify the /O parameter only when you want the client operating system type verified before updating to a new operating system type. If you do not specify /O, the current operation system being used by the remote IPL client is determined from the CLIENT.FIT file. If you do specify /O, you must also specify /N. /N:newos2dir Equivalent to the NEWOS2DIR response file keyword. Specifies the root directory under \IBMLAN\RPL or the version of OS/2 to which the client is to be switched. This parameter is case-sensitive. The default is OS2.21. Specify the /O and /N parameters only when you need to switch a client from one OS version to another OS version. When an existing remote IPL client is updated to OS/2 2.1, you must replace the client WIN-OS/2 *.INI and *.GRP files with the 2.1 versions of these files. The old files are renamed to *.IBK and *.GBK. When these old files are no longer needed for reference, delete them. /D:displaydriver Equivalent to the DISPLAYDRIVER response file keyword. Specifies the new display type for the client definition. The following display types are valid: VGA or IBMVGA32 VGA display driver XGA or IBMXGA32 XGA display driver 8514, IBM8514, or 8514_32 8514 display driver SVGA SVGA display driver for non-S3 chip sets (OS/2 2.11 and OS/2 Warp V3) S3SVGA SVGA display driver for S3 chip sets (OS/2 2.11 and OS/2 Warp V3) Note: 1-The SVGA support requires that OS/2 2.11 or OS/2 Warp support files be installed prior to using RPLSETD. For information about installing the SVGA support files, see the Installing OS/2 SVGA Support on the RIPL Server section of this document. Note: 2-The appropriate 16-bit or 32-bit display driver for each display type is determined based on the version of OS/2 being used by the client. This parameter is normally optional. However, it must be specified when an existing 2.0 or 2.00.1 remote IPL client is converted to 2.1 by specifying the /N parameter. When upgrading the display type of an existing remote IPL client (when it has booted at least one time and has a desktop) from VGA to XGA or 8514, you must delete and recreate the remote IPL client and then run RPLSETD. If you update the existing client to a higher resolution display type, many of the display sizing characteristics in OS2.INI do not get updated. As a result, some objects are in VGA resolution and some are in the higher resolution. If no desktop exists for the client, the desktop can be updated to change to a higher resolution. When the desktop is created during the first boot, the desktop reflects the display characteristics for which it is configured. /B: Equivalent to the BUSTYPE response file keyword. Specifies the type of I/O bus used by the remote IPL client machine. Valid types are: MCA Micro Channel* ISA AT* compatible EISA AT compatible /S: Equivalent to the SWAPTARGET response file keyword. Specifies the location where the SWAPPER.DAT file is to reside. The following values are valid: L The file is to reside on the local hard disk of the remote IPL client. S The file is to reside on the remote IPL server. /I: Displays a message indicating the current configuration (display type, bus type, and swap target) of the remote IPL clients specified by the /C parameter. When /I is specified, all other parameters except /C are ignored. REMARKS o Client definitions can be updated individually or in a group (grouped by common attributes such as display type, bus type, and operating system). o The client names DEFALT20 and DEFALT21 are reserved. Do not create a client using either of these names. Do not attempt to update the DEFALT20 or DEFALT21 clients with RPLSETD. o If a desktop exists, use the RPLSETD utility to change to the higher resolution display type. Then perform an IPL on the client and let it create a new Desktop (changing the old Desktop could result in unpredictable results). o The client name DEFALT20 is a special name used by OS/2 remote IPL support as a default when creating a new client (not modelling an existing client). If you are supporting prior versions of OS/2 (2.0, 2.00.1, or 2.0+Service Pak(s)) in the remote IPL directory tree, do not update DEFALT20 to support OS/2 2.1. Leave DEFALT20 at its current level to support the prior versions of OS/2. To support OS/2 2.00.1 or 2.1 remote IPL clients, do the following (example is for OS/2 2.1): 1. Create a new remote IPL client, for example, MODEL21, using the defaults. 2. Use RPLSETD to update MODEL21 to support OS/2 2.1. Then use MODEL21 as a model to create all future 2.1 clients. 3. You may need to create multiple 2.1 models, one for each LAN type you support. o The client names DEFALT2A and DEFALT21 and DEFALT30 are reserved. Do not create clients with these names. DEFALT2A and DEFALT21 are not a complete client definition like DEFALT20. They are used in conjunction with DEFALT20 to support OS/2 2.00.1 and 2.1 clients. Do not attempt to update the DEFALT2A and DEFALT21 clients with RPLSETD.CMD. If the only version of OS/2 that will be installed in the remote IPL directory is OS/2 2.00.1 or 2.1, update the client DEFALT20 to the appropriate level. Then all future default clients will automatically support the correct OS/2 version. DEFALT30 is a complete definition and can be updated like DEFALT20. Examples: o To update the DEFALT20 client to use the 32-bit VGA display driver and switch the operating system from OS2.20 to OS2.21, type: RPLSETD /C:DEFALT20 /D:IBMVGA32 /N:OS2.21 This will update the default files to support OS/2 2.1 and the new VGA display driver. These files are used when defining clients using the default configuration. Note: If you also plan to support previous versions of OS/2 (i.e. 2.0, 2.00.1, or 2.0 + a Service Pak), do not update the DEFALT20 client. o To update the MACH001 client to use the 32-bit XGA display driver and switch the operating system to OS2.21, type: RPLSETD /C:MACH001 /D:IBMXGA32 /N:OS2.21 o To update the MACH001 client to use the 32-bit XGA display driver, verify the current operating system is OS2.20a, and switch the operating system to OS2.21, type: RPLSETD /C:MACH001 /D:IBMXGA32 /O:OS2.20a /N:OS2.21 o To update the MACH001 client to specify a bus type of ISA and set the SWAPPATH/PagingFile to the RIPL server, type: RPLSETD /C:MACH001 /B:ISA /S:S o To update the MACH001 client to use the 32-bit VGA display driver, verify the current operating system is OS2.20, switch the operating system to OS2.21, specify a bus type of ISA, and set the SWAPPATH/PagingFile to the RIPL server, type: RPLSETD /C:MACH001 /D:IBMVGA32 /O:OS2.20 /N:OS2.21 /B:ISA /S:S o To update multiple clients, MACH001 and MACH002, to use the 32-bit VGA display driver and switch the operating system to OS2.21, type: RPLSETD /C:MACH001,MACH002 /D:IBMVGA32 /N:OS2.21 o To update a client, MACH001, to allow for SVGA support to be configured by OS/2, type: RPLSETD /C:MACH001 /D:SVGA o To update a client, MACH001, to allow for S3 SVGA support to be configured by OS/2, type: RPLSETD /C:MACH001 /D:S3SVGA ═══ 5.5.2.2. Using a RPLSETD Response File ═══ To use the response file option, do the following: 1. Create an ASCII file that contains the appropriate keyword values. The valid response file entries/keywords are: ; Comment line [GROUP] (this statement is optional for the first group and required for all subsequent groups) DISPLAYDRIVER= CLIENT= CLIENTLIST= CURRENTOS2DIR= NEWOS2DIR= BUSTYPE= SWAPTARGET= A ';'(semicolon) in column 1 indicates the line is a comment. Leading blanks are allowed on keyword statements. The keywords are defined in the RPLSETD syntax description. [GROUP] designates the start of a RIPL client or group of clients that share the same configuration characteristics. When the [GROUP] statement is encountered, the client machine(s) in the previous group are updated according to the specified keyword(s). Multiple [GROUP]s can appear in the response file. This allows a single response file to process a number of different configurations. The [GROUP] statement is optional for the first group in the response file but is required for all subsequent groups. CLIENT and CLIENTLIST are equivalent and multiple entries can be specified on either. Multiple CLIENT and CLIENTLIST keywords can be specified per group. Only one of each of the other keywords is allowed per group. 2. Type the following command: RPLSETD /R:d:\path\response_filename where d:\path\response_filename is the fully qualified file name of the response file. Example: [GROUP] (optional) ; Update existing clients to support the IBMXGA32 display ; driver, switch from OS2.20 to OS2.21, support the MCA bus, ; and put the swappath on a local hardfile. CLIENT=DEFALT20 CLIENT=MACH001,MACH002 CLIENTLIST=MACH003,MACH004 DISPLAYDRIVER=IBMXGA32 CURRENTOS2DIR=OS2.20 NEWOS2DIR=OS2.21 BUSTYPE=MCA SWAPTARGET=L [GROUP] (required) ; Update client for ISA bus and put the swappath on the RIPL ; server (no local hardfile). CLIENT=MACH005 BUSTYPE=ISA SWAPTARGET=S ═══ 5.5.3. GETRPL.EXE Utility ═══ Refer to the IBM OS/2 LAN Server Version 3.0 Administrator Reference Volume 3: Administrator Tasks for information on running GETRPL. GETRPL has been updated to be CID enabled. Two command line options have been added to support this. They are: /L:Logfile A fully qualified path name for a logfile to which all messages and errors are logged. If /L is specified, GETRPL runs in an invisible window (no dialog boxes). /O:OS2_2x_path The fully qualified path of the OS2.2x directory in the RIPL directory tree that is to be processed by GETRPL. For example: /O:\C:\IBMLAN\RPL\OS2.21 If /O is not specified, GETRPL will use the last 'target file' saved in OS2SYS.INI by the RIPLINST utility. If RIPLINST has never been run, GETRPL will default the value to C:\IBMLAN\RPL\OS2.20. Two additional command line options have been added. They are: /I Force the default OS/2 INI files to be recreated and copied to the appropriate \RPLUSER\DEFALTXX\OS2 directory. /NA Suppress the creation of the access control profiles. This is useful when multiple versions of OS/2 will be installed and GETRPL will be run after each RIPLINST. The creation of access control profiles can be suppressed until after the last OS/2 is installed. Note: RPL.MAP will be updated to enable only the OS/2 server records for versions of OS/2 that are installed in the Remote IPL directory. In addition, only server records for which the corresponding LAN adapter is installed in the server will be enabled. If you are bridging different network types together, i.e, Token-ring and Ethernet, it will be necessary to manually update RPL.MAP to enable the server records for the LAN adapters installed in the RIPL clients that are different from the adapters installed in the server. ═══ 5.5.4. RPLSVGAI.CMD REXX Procedure ═══ Before a RIPL client can be configured for SVGA support, additional OS/2 SVGA support files must be installed. A special utility, RPLSVGAI.CMD, is provided to install this support. The syntax for RPLSVGAI.CMD is: RPLSVGAI [/S:sourcepath] [/L:logfile] o where sourcepath specifies where to look for the SVGA support files. It can be one of the following: - A diskette drive, i.e., A:\ - The root directory of a Warp diskette image tree created by the OS/2 SEIMAGE.EXE utility, for example, C:\CID\OS2211 or C:\CID\OS2WARP. The default is A:\. o where logfile specifies a fully qualified filename to be used to log any error messages. RPLSVGAI must be run for each OS/2 version (2.11 and/or Warp) that is installed in the Remote IPL directory tree. RPLSVGAI can determine from Display Driver diskette 1 which OS/2 version is being updated. If diskettes are used as the source, RPLSVGAI will prompt for the appropriate OS/2 Display Driver diskettes. The Warp Display Driver diskettes are in XDF diskette format. The RIPL server must be updated to support the XDF format before RPLSVGAI can be used to install the Warp SVGA support files. ═══ 5.5.5. RPLADD.EXE Utility ═══ The RPLADD utility (part of Productivity Aids package) has been upgraded as follows: 1. The '-s' flag used to specify 'Simple' file format is no longer needed. RPLADD can now automatically sense if an input file is using the 'Simple' format or the 'Map' format. 2. All versions of OS/2 2.X and OS/2 Warp V3 are supported. 3. DEFALT20', 'DEFALT2A', 'DEFALT21', and 'DEFALT30' can now be used as a model for both input file formats. However, when DEFALT2A or DEFALT21 are used to create OS/2 2.00.1 or 2.1 clients, the RPLSETD utility must be run to complete their configuration before they can be remote IPLed. See the Creating New OS/2 2.1 Remote IPL Clients section of this document for information on when RPLSETD should be run. 4. A new 'ASSUME DEFAULT SOURCE TOKENRNG' directive allows either input file format to specify where 'CONFIG.20' should come from when DEFALT20 is the MODEL MACHINE. See the documentation in sample input file(s) SIMPLE.FIL and SAMPLE.MAP for additional information. 5. The device driver parameter fields (fields 7, 8, and 9) in the 'MAP' format are preserved. The parameters MUST use the '~' character to represent SPACES just as required by RPL.MAP itself. The 'commas' used to separate the 3 parameters should not be preceded or followed by spaces. ═══ 5.5.6. RPLDEL.EXE Utility ═══ The RPLDEL utility (part of Productivity Aids package) has been upgraded as follows: 1. The '-s' flag used to specify 'Simple' file format is no longer needed. RPLDEL can now automatically sense if an input file is using the 'Simple' format or the 'Map' format. 2. RPLDEL can now handle directory entries that are up to 254 characters in length. ═══ 6. LAPS 802.2 Virtual Device Driver - Emulator Considerations ═══ 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. Warning: The following problems may occur: o 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. o 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 minimize the running emulator session before starting the second emulator. o It is not possible to run two WIN-OS/2 sessions while using XGA video mode. Refer to the OS/2 README for additional information on restrictions using WIN-OS/2 and XGA. ═══ 6.1. PC/3270 for DOS emulator ═══ On the Program panel, set the following parameters: Path/Filename = d:\EmulPath\CFGFILE.BAT Parameters = blank Working Directory = d:\EmulPath o On the Session panel, select DOS Full Screen. o Before attempting to run PC3270 for DOS, edit your CFGFILE.BAT file adding 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. ═══ 6.2. 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: o 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 o 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 o On the Program panel, set the following parameters: Path/Filename = d:\EmulPath\CFGFILE.BAT Parameters = blank Working Directory = d:\EmulPath o On the Session panel, select DOS Full Screen. To run PC3270 Seamlessly: o 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 o On the Program panel, set the following parameters: Path/Filename = d:\EmulPath\PC3270W.EXE Parameters = blank Working Directory = d:\EmulPath o On the Session panel, select WIN-OS/2 window, click on Separate Session, then click on WIN-OS/2 Settings. o 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'. ═══ 6.3. Attachmate's Extra! Extended for DOS ═══ o On the Program panel, set the following parameters: Path/Filename = d:\EmulPath\CFGFILE.BAT Parameters = blank Working Directory = d:\EmulPath o On the Session panel, select DOS Full Screen. o 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. ═══ 6.4. Attachmate's Extra! Extended for Windows ═══ o Create a file called EXTRA.BAT. This file should look like this: @ECHO OFF C:\OS2\MDOS\WINOS2\WINOS2 o On the Program panel, set the following parameters: Path/Filename = d:\EmulPath\EXTRA.BAT Parameters = blank Working Directory = d:\EmulPath o On the Session panel, select DOS Full Screen. Note: 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. ═══ 6.5. 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. o On the Program panel, set the following parameters: Path/Filename = * Parameters = blank Working Directory = d:\EmulPath o On the Session panel, select DOS Full Screen, then click on DOS Settings. o 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. Warning: Some known problems: 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. 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). 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. When running more than 2 sessions in a stress environment it may be necessary to obtain OS/2 2.0 Service Pak (XRx6055). 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 V2 Virtual DOS Machines". ═══ 6.6. Wall Data's Rumba/400 emulator ═══ o 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. o On the Program panel, set the following parameters: Path/Filename = d:\EmulPath\RUMBA.BAT Parameters = blank Working Directory = d:\EmulPath o On the Session panel, select DOS Full Screen ═══ 6.7. Wall Data's Rumba/3270 emulator ═══ o 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 WDTOKTSR.EXE is required by Rumba/3270 in order to use Lan support. Refer to the Rumba program documentation for more information about command line parameters. The above parameters work in most cases. o On the Program panel, set the following parameters: Path/Filename = d:\EmulPath\RUMBA.BAT Parameters = blank Working Directory = d:\EmulPath o On the Session panel, select DOS Full Screen. ═══ 7. LAPS TCP/IP for DOS - Considerations ═══ 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: o On the Program panel, set the following parameters: Path/Filename = * Parameters = Blank Working Directory = C:\TCPDOS (Assuming TCP/IP was installed on C:\TCPDOS) o On the DOS Settings panel, click on 'Session' and set the following parameters: DOS_DEVICE = C:\TCPDOS\BIN\NETDEV.SYS (Assuming TCP/IP was installed on C:\TCPDOS) LTSVCFG.COM must be run with parameter D=1 before TCP/IP can run in a VDD. This is necessary because TCP/IP uses the direct station link of the 802.2 protocol. A slash is used to signify the adapter number. Adapter Number Command to Run Adapter 0 LTSVCFG D=1 Adapter 1 LTSVCFG / D=1 Adapter 2 LTSVCFG / / D=1 LTSVCFG can be included in the AUTOEXEC.BAT file to execute automatically. or run manually from a DOS command prompt. 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. ═══ 8. Things that Changed ═══ The following sections describe changes that have been made to the product's executables, publications, and messages/helps. ═══ 8.1. Publications ═══ The ServicePak includes a Publications Addendum which updates the LAN Server 3.0 publications. The following files are online information that can be viewed at an OS/2 command prompt: o Publications Readme o Application Programmer's Reference Readme These files are included in the same directory as the file you are currently reading. To view these files type: View RDMExxx.INF where xxx is either PUB or APR depending on which file you want to view. ═══ 8.2. Changes and Additions other than APARs ═══ This ServicePak contains several changes and enhancements that do not have APARs associated with them. They are described in the following sections. ═══ 8.2.1. New feature summary ═══ This section describes features that are included in this ServicePak. ═══ 8.2.1.1. Support for OS/2 Warp Version 3 ═══ The following features have been enhanced to add support for OS/2 Warp Version 3: 1. Remote IPL support - See the RIPL sections of this document for details. 2. SMB Trace tool - The SMB tool is a large presentation manager utility that can be used to capture various types of network traces. Especially important is its ability to capture IBM LAN Server Server Message Block (SMB) information. It also includes extensive formatting and filtering features for SMB trace data. It can be used for advanced problem determination. SMBTOOL.EXE is provided on ServicePak diskette 1 in RDRUTIL.ZIP. To unpack the trace tool into the desired directory, insert ServicePak diskette 1 into drive A: and issue the following command: PKUNZIP2 A:\RDRUTIL.ZIP \ Note: IF PKUNZIP2.EXE is not in a directory that is in the current path, copy the PKUNZIP2.EXE program from the \IBMCOM directory on the boot drive into a directory that is in the current path. The SMB utility takes no parameters and requires OS/2 2.1 or later. More information is available by selecting HELP from within the utility. ═══ 8.2.1.2. IBM DOS Version 7 Support ═══ A REXX procedure, RPLDOS7.CMD, is available on ServicePak diskette 1 to upgrade the DOS Remote IPL Service to use IBM PC DOS Version 7. System Requirements: 1. Since the IBM PC DOS 7 diskettes are compressed in XDF format, the remote IPL server must be configured with the required BASEDEV device drivers to support reading XDF formatted diskettes. 2. The server must already be configured for the DOS Remote IPL Service. No command line parameters are required for this procedure, however, there are two optional command line parameters: o /D:source_drive letter The default source diskette drive letter is A:. To select a different source diskette drive letter for the DOS diskettes, use the /D:x parameter. For example, to specify a source drive of B:, use the following command: RPLDOS7 /D:B o /N:number_DOS_diskettes The default number of 3.5 inch, 1.44MB IBM DOS diskettes is 5. To specify a different number of diskettes, use the /N:y parameter. For example, to specify a set of 7 DOS diskettes, use the following command: RPLDOS7 /N:7 ═══ 8.2.1.3. Additional Server Authentication (IP07045) ═══ Additional servers in a domain will now allow the domain controller to authenticate a user attempting to establish a session. This will only occur if the user's password does not match the copy at the additional server. The additional server's password is used for authentication. This will fix the situation where users are forced to change their passwords, and then do not get all of their logon assignments at additional servers because the passwords have not replicated. ═══ 8.2.1.4. DOS RIPL (IP07045) ═══ Support for three new DOS versions has been added to DOS RIPL. IBM DOS 6.1 IBM DOS 6.3 MS DOS 6.0 In order for the installation program (LANINST) to successfully install the required DOS files for each of the new supported versions, OS/2 DOS support must have been installed with the operating system on the server. If OS/2 DOS support is not installed on the server, the DOS files necessary for RIPL will have to be manually installed. First, run LANINST and select the version of DOS desired for RIPL. After the installation has completed, find a workstation with DOS support, insert the first DOS diskette, and enter the command A:\SETUP /A. The /A parameter specifies LAN Server Administrator Installation option. Follow the instructions to install the DOS files on the workstation. The DOS files will then need to be copied to the drive and subdirectory on the server workstation where the DOS RIPL support was installed using LANINST. DOS RIPL support is usually installed on d:\IBMLAN\DOSLAN\DOS. Remote IPL DOS images for above listed DOS versions may be created using the existing DOS 5.0 standard definition(.DEF) files. ═══ 8.2.1.5. FIXACC LOG (IP07045) ═══ FIXACC will now generate a log of all its actions. The log file is FIXACC.LOG. It will also log warning and error messages. The list of messages logged are: NET3606 Network error %1 occurred while adding group %2. NET3607 Network error %1 occurred while adding user %2. NET3608 Network error %1 occurred while adding access control for %2. NET3609 Restored user %1 NET3610 Restored group %1 NET3611 Restored access control list for %1 NET3612 Restored %1 permissions to access control list for %2 NET3613 Added %1 group(s) to user %2 ; Message 3614 is used to list users and their access rights as ; they are restored, ex: ; ; USERS RWED ; GUESTS R NET3614 %1 %2 NET3615 Restored Password for user %1 NET3616 Error %1 occurred while setting users and groups on access control list for %1 NET3617 WARNING: FIXACC may not be able to restore %1 of the users. NET3618 WARNING: FIXACC may not be able to restore all of the access control lists. NET3619 An error %1 occurred when FIXACC attempted to update the groups. ═══ 8.2.2. Additional Information ═══ This section contains additional changes to LAN Server 3.0 that are included in this ServicePak. ═══ 8.2.2.1. Successful return codes from NET commands ═══ Following application of the fix for APAR IC05944, (included in LS 3.00.1 and IP07045 as well as the individual APAR fix), successful return from NET commands was indicated with a return code of 255. This was incorrect; successful return codes of 0 have been reinstated with the fix for APAR IC06738 included in this ServicePak. This could affect applications which were modified to check for successful return codes of 255 from NET commands. ═══ 8.2.2.2. What's new in 386 HPFS ═══ 1. One module instead of two. With the arrival of OS/2 2.0, we were able to consolidate the 386 HPFS server into one file. The CONFIG.SYS file will reflect this change by removing the HPFS200.386 module from the IFS= line. A place holder, HPFS200.386, will be placed in the \IBM386FS directory. 2. 64KB Work Buffer pre-allocation. Until this release of LS 3.0, HPFS386 allocated 64KB work buffers from OS/2 on an as needed basis. These buffers must be fixed (ie, contiguous) RAM. As the booted system "ages", fragmentation of RAM increases, which will decrease the success rate of dynamic buffer allocation. When a buffer cannot be allocated, the following error message is logged in NET.ERR: "NET3186: The 386 HPFS server ran out of the following resource: NET3235: RAM for 64KB work buffer." Pre-allocating these buffers at system boot time, or even at server initialization time, avoids the dynamic allocation problem. To pre-allocate these work buffers at system boot time, you need to add the following switch to the 386 HPFS IFS= statement: /FSPREALLOC:nn where 2 <= nn <= 64 and represents the number of buffers to pre-allocate. You can do the same thing at server initialization time by adding the following switch to the IFS= line: /SVRPREALLOC:nn where 2 <= nn <= 64 and represents the number of buffers to pre-allocate at server initialization time. Work buffers that are allocated using the /SVRPREALLOC switches will be freed when the server is stopped. Those allocated via the /FSPREALLOC switch will not be freed. These switches are useful in environments such as RIPL servers. 3. Makedisk and Fault Tolerance A new switch was added to the Makedisk utility: /FT. This allows the Fault Tolerance information to be copied onto the diskette itself. 4. Pentium The 386 HPFS is now Pentium-aware and takes advantage of some of the processor's features when detected. ═══ 8.2.2.3. Change to the NetAlias APIs ═══ The ai2_server field is CNLEN+1 in the alias_info_2 structure. In LS 3.0 (GA and IP7001), this field was expected to be in UNC format: \\server. This is incorrect. In this service level, both the UNC and CN format are allowed, but the '\\' are thrown away if they are used. In future releases, the slashes will not be allowed. Application developers should be aware of this change. ═══ 8.2.2.4. DOS LAN Requester logging on in Window with expired password ═══ Previously, when a user logged on in Windows with an expired password, the NET2242 error was reported which says "The user's password has expired," but the user was not given an opportunity to change it at that time. Now the "Change Password" window is displayed after clearing the error, allowing the user to change his or her logon password without having to go through the Windows Control Panel. ═══ 8.2.2.5. OS/2 Requester Considerations ═══ A change has been made to the OS/2 Requester that improves the handling of printing to DOS based servers, such as IBM PC LAN Program, which are based on the original "core" SMB dialect. This does not affect printing to OS/2 based servers like IBM LAN Server 3.0. The OS/2 Requester now sends the user name of a print job submitter rather than the machine name of the print job submitter when printing to PC LAN Program servers. This change will allow those using separator pages on PCLP servers to identify more easily the user who submitted a print job. It is also consistent with the IBM DOS LAN Requester which sends the user name of the print job submitter when printing to PC LAN Program Servers. Two new IBMLAN.INI wrkheuristics have been added. 1. Wrkheuristic 34 is used to set the behavior of the OS/2 Requester when getting the date and time on files on a PCLP or equivalent server. Users of non-IBM PCLP compatible servers that only accept the original PC LAN Program or MSNET SMB dialect may also find this new heuristic useful. Servers using the MSNET dialect and PCLP Servers use different date and time formats yet use the same SMB dialect. The OS/2 Requester will determine which date and time format to try to use first when communicating with a PCLP or MSNET server based on the value of wrkheuristic 34. If the date appears unlikely, the OS/2 Requester will try the other date and time format. This heuristic is not important if you are using only OS2 LAN Server 3.0 or equivalent servers. Values: 0 Verify date and time with prefrence towards PCLP server format 1 Verify date and time with prefrence towards MSNET server format 2 Assume that the date is always correct. Do not attempt to validate the date and time. The default (if not present) is 0. 2. wrkheuristic 35 is a usability enhancement to workaround problems with DOS applications that cannot handle large partitions. Recently, many customers have bought network servers and configured them with partitions larger than 2 gigabytes (GB). This causes problems for some DOS applications that were written assuming smaller than 2GB disk partition sizes. When users connect to these large network drives and run applications that incorrectly check the available disk space or the free disk space, the application may report unusual disk sizes or no disk space available. This is typically not a problem with OS/2 applications. Most DOS applications do not have problems with large disks, but users of DOS applications with problems handling large drives, should consider setting this wrkheuristic. Values: 0 Always return actual disk size and disk space available on network drives to applications running in DOS Emulation or DOS booted under OS/2. 1 Return less than 2GB disk size and disk space available on network drives to applications running in DOS Emulation or DOS booted under OS/2. The default (if not present) is 0. The APAR number for the wrkheuristic workaround is IC06791. ═══ 8.2.2.6. Additional Information on Domain Alias Operation ═══ Client requests for the connection or resolution of aliases will not be satisfied until the server and all sub-services have fully started. For reliability reasons, backup servers will always attempt to resolve aliases by using the primary copy of the domain control database (DCDB). If the domain controller is unavailable, the alias operation will be satisfied by using the backup copy of the DCDB stored on the backup server. It is not necessary for the DCDB replicator service to be running when the domain controller is unavailable. ═══ 8.3. OS/2 LAN Server and LAN Requester ServicePak APARs ═══ This section describes APARs that have been corrected in the previous service offerings for LAN SERVER/REQUESTER, as well as the additions for this cumulative ServicePak. ═══ 8.3.1. IPx7001 ServicePak APARs ═══ The APAR numbers for problems that were corrected by IPx7001 ServicePak are listed numerically and by component. ═══ 8.3.1.1. LAN Server ═══ The following list describes APARs for the Server component that are fixed by IPx7001 ServicePak. o IC04302 Users receive SYS0008 (out of memory) messages when trying to perform operations (for example, DIR X:) on remote drives. The following message is also logged. NET3186E: The 386 HPFS Server ran out of the following resource: 64KB Work Buffers o IC04424 A trap 0 occurs in the Ring 3 server (NETSERVR.EXE) when the requester sends an SMB read command with the number of read bytes set to 0. o IC04430 A trap often occurs in the 386 HPFS server when using Microsoft Windows 3.1 clients with the server. o IC04431 The system traps because the Ring 3 server fails to release space that has been allocated for renaming or moving files with access control profiles. o IC04710 Requirement to improve performance in deleting subdirectories and in handling lock requests at the server. Some applications also receive ERROR_LOCK_VIOLATION error messages that end processing prematurely. o IC04769 The server receives an error return code when trying to open a shared COM port and does not set the device to error status. The result is that all incoming requests are queued up for the port. The device is left in an open condition when viewed with the NET DEVICE command and cannot be cleared or reset. o IC04943 A trap occurs in the 386 HPFS server after installing NVDM/2. o IC04973 If a DOS LAN Requester workstation performs a DIR command on an empty directory, no volume label information is returned. o IC04992 A trap 003 occurs when remote IPLing a client with an XGA display. o IC05010 HFS0102 messages display while running the CHKDSK command, especially on larger drives (for example, 1GB). o IC05058 A trap occurs in the 386 HPFS server when starting from either a boot partition or boot diskettes. This problem may occur on machines that previously ran with DBCS code pages using OS/2 1.2 or OS/2 1.3. o IC05073 A trap occurs in the 386 HPFS server when doing a hotfix on an already hot-fixed sector. This problem usually occurs when a drive fails (especially on a machine with an IBM 3515 disk subsystem). o IC05075 Excessive access-denied violations accumulate in the server statistics, causing alerts to be sent. The permission violations in the server statistics do not match the audit entries in the audit log. This may cause confusion for users who have auditing enabled and get alerts indicating permission violations but when the audit log is viewed, there are no audit entries. o IC05106 The 386 HPFS server returns a return code of 0 when doing a DosCopy and duplicate files are encountered. o IC05112 A trap occurs in the 386 HPFS server when TRACE code 154 is enabled and the server tries to break an Oplock on a file. Setting TRACE=ON or TRACE=ON 154 (when using SPM/2) could cause the problem. o IC05129 A trap occurs in the 386 HPFS server when trying to write to a file that has become extremely fragmented. This requires a file of at least 240KB in size, but happens more frequently with larger files. o IC05141 The last update time for a 386 HPFS file is being updated in a DosOpen DosRead, DosBufReset combination. o IC05182 A trap occurs in the 386 HPFS server (or in the OS/2 kernel) during paging when 386 HPFS is handling paging and the page file (SWAPPER.DAT) becomes fragmented. o IC05184 Include MAKEDISK updates that will handle out-of-disk-space errors when trying to build boot diskettes. This will also verify that UHPFS.DLL exists on the boot diskettes so that AUTOCHECK can be run. Note: When building boot diskettes for OS/2 2.1, delete A:BUNDLE from backup diskette 1 before running MAKEDISK. o IC05188 Possible deadlock condition occurs when multiple programs try to read uninitialized file data simultaneously from the same file. o IC05190 The 386 HPFS server returns an ERROR_FILE_NOT_FOUND message instead of an ERROR_ACCESS_DENIED message when trying to delete a directory using DosDelete. o IC05200 A trap occurs in the 386 HPFS server when trying to set attributes on a directory whose sector is not accessible because of disk read/write errors. o IC05240 A trap occurs in the 386 HPFS server when using the Replicator service to import to a 386 HPFS drive. o IC05256 The 386 HPFS server will not correctly release space when the page file (SWAPPER.DAT) size is decreased by OS/2. o IC05327 Improve performance for servers running LAN Server for Macintosh. o Additional fix without APAR: OS/2 LAN Server is unable to run with Ungermann-Bass NETBIOS transport code. o IC05662 HPFS386 does not cache small (512 to 1K byte) I/O requests. This causes a performance problem. ═══ 8.3.1.2. LAN Requester ═══ The following list describes APARs for the Requester component that were fixed by IPx7001 ServicePak. o IC04248 Applications using a remote named pipe hang. o IC04475 Programs cannot edit hidden files on a PCLP server. o IC04492 An XCOPY of multiple files with an extension of .CMD or .BAT fails. On the server, the NET ERROR log shows MAXSESSOPENS exhausted. o IC04532 Programs using the NETBIOSSUBMIT application interface may hang. o IC04600 The LAN Management Utilities/2 (LMU/2) product or other programs that use DOSMAKEMAILSLOT() may fail with return code 87. o IC04667 A NET3190 error displays the following message: MSG incomplete in redir NCB 0600 Another symptom is that data is damaged on the requester. These symptoms can appear when the requester accesses large files or programs from the server. o IC04697 A trap 0D screen displays with an unrecoverable system abend. o IC04698 A page fault (Trap 0E) occurs when shutting down or rebooting a remote IPL client. o IC04750 A trap 0D screen shows EIP=00000032. o IC04761 A 32-bit GREP program and other programs using the 32-bit DOSFINDFIRST() DOSCALL may hang. o IC04834 Programs running on a requester receive errors on file operations (copying files, reading files, writing files). If errors disappear when you set bits 9 and 23 to 0 in the WRKHEURISTICS parameter in IBMLAN.INI, you are likely to need this fix. o IC04865 A remote IPL client hangs or stops with trap 8. In the case of the hang, after the machine is rebooted, there should be some entry in the NET ERROR logs stating that some resource has been exhausted (for example, NUMWORKBUFS, MAXCMDS, or MAXTHREADS). o IC04963 A trap 0D occurs on the requester when the server uses a FAT file system. o IC05170 This is a workaround for a Microsoft Windows for Workgroup problem. A copy from the IBM OS/2 LAN Requester to a Windows for Workgroup machine can fail. The OS/2 requester was changed to avoid encountering this problem. This APAR also included a fix for updating the date and time of files stored on OS/2 LAN Servers that were modified by Lotus 1-2-3**. Another customer reported a different symptom. The 16-bit DOSSETPATHINFO() call for a remote file on a server running OS/2 2.0 or later could receive error code 87. o IC05275 A damaged NETBIOS table causes programs using NETBIOS to receive error 0x13. o IC05298 Logon is unsuccessful after a SPM/2 program is started, or after other programs which use remote path names are started. o Other fixes: - OS/2 LAN Requester is unable to run with Ungermann-Bass** NETBIOS transport code. ═══ 8.3.1.3. User Profile Management (UPM) ═══ The following list describes APARs for the UPM component that were fixed by IPx7001 ServicePak. o IC04427 Logon using the LAN-aware workplace shell returns a SYS0317 error when the OS/2 optional utilities are not installed. The code has been changed to return a SYS0002 error. o IC04904 Responding with a N to the Y/N prompt at logoff when there are open files or active drives on the network results in the logoff continuing instead of canceling. o IC05694 An application invoking USER or GROUP API's on a workstation without the Server service started, would be left in a "critical section". All other threads of a process besides the calling thread are "frozen". o JR06434 User Profile Management (UPMACCTS) may fail to start and will return a UPM0004C or UPM0010C error if the logon domain consists of Microsoft LAN Manager servers. o JR06710 User Profile Management (UPMACCTS) will fail with a UPM0062C reason code 2140 error when attempting to open group or user management. The failure occurs when the domain controller in the domain is LAN Server 1.3 or 1.3 with CSD5015. o JR06859 Initialization of UPM (upon first logon) may result in the display of a SYS0039 drive-not-ready error message when an access control profile has been put on a removable-media drive. ═══ 8.3.1.4. Fault Tolerance ═══ The following list describes APARs for the Fault Tolerance component that were fixed by IPx7001 ServicePak. o IC04815, IC04824, IC05414 Provide Fault Tolerance support for large disks having more than 1.2GB or more than 1024 cylinders. If a mirror partition has already been created, use FDISK to remove all partitions on the disk. Then use FTSETUP or FTREMOTE to remirror the drives. o IC05409 Support for hot-replaceable disks. When a failed disk is replaced without booting, this fix enables the Verify function to restore the data from the good partition to the replaced partition. o Defect 1652 A trap occurs when mirroring a drive with FTSETUP or FTREMOTE if the target disk containing the mirror partition has damaged sectors. o Modification to DISKFT.SYS This fix makes it possible to install the Service Pak on a mirrored drive. Refer to the installation instructions in this document for information on installing the Service Pak on a mirrored drive. ═══ 8.3.1.5. Remote IPL Support for OS/2 2.1 (APAR IC05198) ═══ See the RIPL section of this document for a composite of the RIPL enhancements from the 7001 ServicePak to the 7045 level. ═══ 8.3.2. IPx7005 SelectPak APARs ═══ This section lists the contents of the 7005 SelectPak of HPFS fixes. The APAR numbers for problems that were corrected by IPx7005 SelectPak are listed numerically. o IC05536 DOS programs running on DLR 3.0 workstations may return "file is in use" or other unexpected errors when accessing files on an HPFS386 server. Problems have been found using the WordPerfect Office and SuperCalc applications. o IC05759 Problems dealing with a "split cache". When a workstation has more than 16MB of physical memory and the cache cannot fit within the 16MB to the end of physical memory range, a split cache results. A split cache is the separation of the cache memory into two chunks that are managed together. Depending on the amount of memory and the cache size requested, the workstation may hang and eventually trap during OS/2 startup. In conditions involving disk errors, incorrect data may be written to the disk. o IC05760 The FNODE for the paging file (SWAPPER.DAT) was not being updated with the file size. During CHKDSK, this may result in lost or orphaned disk space which would require a second CHKDSK at level 2 or above to reclaim. o IC05857 Under extremely rare conditions, it is possible for a page frame within the page file to be overwritten, causing page faults or damaged data. o IC05858 Under conditions in which an HFS0108E (severe disk errors) occurs, the workstation may trap. o IC05864 A trap occurs in UnlockBuffer on a workstation that is doing both heavy local I/O and heavy paging. This only affects local I/O operations. o IC05865 A trap occurs in ClrBit when trying to free space in a bitmap. o IC05867 A deadlock condition may occur if I/O requests are failing because of disk errors. When transferring to a user's buffer during a Read or Write operation, the I/O operation may deadlock, causing the thread issuing the request to stop. This only affects local I/O operations. o IC06194 The Ring 3 server appears to hang after a set of PCLP requesters fail to establish sessions with the server. ═══ 8.3.3. IPx7040 Manufacturing Refresh (LS 3.00.1) APARs ═══ This section contains a list of APARs opened against LAN Server and LAN Requester. These problems have been fixed since the previous service offerings and are also included in the LS 3.00.1 manufacturing refresh. ═══ 8.3.3.1. LAN Server ═══ This section contains APARS that are fixed in the Server portion of the LS 3.0 ServicePak. o APAR IC04857 CHGSRVR UTILITY NOT WORKING CORRECTLY...CORRUPTS RPL.MAP FILE After using the CHGSRVR utility to change the name of a remote IPL server, remotely IPL'ed workstations encountered errors upon reboot. o APAR IC05252 (ICO6194) AUTOMATED UPDATE OF NET.ACC USING LAN SERVER API'S CAUSES LOOP IN API WHICH MAKES SERVER APPEAR TO HANG A server user is assigned an index number (UID) that identifies the session to that server. An infinite loop occurs when a server attempts to delete a user session when the server session value does not match the session value identified by the UID. o APAR IC05297 UNGERMANN-BASS NETBIOS SIDEBAND PROBLEM When attempting to run LAN Server 3.0 on top of the Ungermann-Bass NETBIOS stack, the server would hang at server startup time. o APAR IC05454 PROVIDE A VEHICLE TO PROVIDE THE UPS MODULES THAT ALLOW THE SDLC AND UPS CODE TO BE COMPATIBLE (REFER TO APAR IC03805) Improved UPS configurability. The UPS device driver will share interrupts with other drivers. The /PORT parameter may be replaced with the combination /IOADDR and /IRQ parameters on the device driver statement in CONFIG.SYS. o APAR IC05468 ERROR CODE 2 - FILE NOT FOUND RETURNED WHEN TRYING TO CREATE FILE ON 386 HPFS VOLUME FROM DOS REQUESTER Applications, such as SuperCalc V5 and WordPerfect Office, were receiving error code 2 - File Not Found when attempting to create files on a 386 HPFS volume. o APAR IC05535 ON BACKUP HPFS386 SERVERS DCDB REPLICATOR WILL NOT CREATE THE ACP FOR THE DCDB TREE Users do not get logon assignments if they are logged on by a Backup Domain Controller and the IBMLAN\DCDB tree is on an HPFS drive. o APAR IC05546 NET2222 DOING APPLY TO ALIAS DEFINED FOR ROOT Applying IP06030 to a root directory or a subdirectory path that ends with an "\" fails. The apply causes a NET2222 error message to be issued. o APAR IC05739 WIN-OS2 SETTINGS INCORRECT AFTER RIPL ON OS/2 2.1 The TAPS on WIN/OS2 SETTINGS showed WIN 3.0 when it should show WIN 3.1. o APAR IC05785 TRAP000D IN NETSERVR.EXE DURING WILDCARD SEARCHES A Trap 000D may occur during wildcard searches. o APAR IC05793 USING FSI TO PROCESS LOGON DETAILS, FILE ASSIGNMENTS, EVERY ALIAS ON THE SERVER IS LISTED In the LAN Server full-screen interface, when defining logon assignments for a normal user, the Manage Logon Drive Assignments panel displays the list of all the aliases defined in the Domain Control Database (DCDB). This list should contain only the aliases which the user has permission to access. This problem occurs only when the DCDB contains a large number of aliases. o APAR IC05796 LOCAL SECURITY AND OS/2 INI FILES When Local Security is installed, the OS/2 INI files (Environment variables %USER_INI%, %SYSTEM_INI%) are moved to \OS2\OS2INI and the variables updated in the CONFIG.SYS file. This allows the correct ACLs to be applied to the files. o APAR IC05872 APAR FOR NEW HPFS386 API (GETINFO?) Provide an Application Programming Interface to HPFS386 via HPFS386.DLL. o APAR IC05881 FILE COPY CHANGES DATE & TIME WITH 386HPFS AND EA'S (EXTENDED ATTRIBUTES) Copying a file that has extended attributes to an HPFS386 drive modifies the file's date and time. o APAR IC05915 CANNOT BOOT OS/2 & HPFS386 FROM ADDRESS LIMITED DISK ADAPTERS With 16-bit disk adapters, the /USEALLMEM switch on the HPFS386 IFS= line will cause the machine to reboot itself. Removing the /USEALLMEM switch will correct the problem. o APAR IC05935 I/O DEADLOCK ON CROSS-LOCKED BUFFER IN RDASYNC Server deadlocks under heavy local I/O in certain cases. o APAR IC05938 TRAP E IN HPFS386 (HPFS200:COE:IRA) WHEN I/O HEADERS CROSS 64K BOUNDRY In certain cases, I/O headers were being allocated across 64KB boundaries. This was causing HPFS386 to trap. o APAR IC05941 TRAP IN CACHEXFER ATTEMPTING TO RECEIVE DATA IN BSMALL NB Under certain conditions, a DosFindNotify call will cause the server to trap. o APAR IC05953 SERIALIZED LOGONS AT SERVER CAUSES INTERMITTENT DLR LOGON FAILURE WHILE ACL APPLY COMPLETES Server processing of logon requests from clients was serialized in several critical areas. The serialization was removed to improve the performance of concurrent user domain logons. o APAR IC05955 NO_IPE SHOULD NOT PROCEED ON DASD MOUNTED VOLUME HPFS386 traps when I/O is attempted to a DASD-mounted volume. o APAR IC05956 PAGE FAULT WHILE COPYING TO USER BUFFER CAUSES TRAP IN FS_READ Bug in OS/2 2.0 and 2.1 kernel was causing HPFS386 to trap on local read operation. o APAR IC06219 386 HPFS HANGS WHEN DLR RUNNING WORDPERFECT 5.1 DOES REVEAL CODES A DOS LAN Requester client running WordPerfect V5.1 would open a file, reveal codes, and attempt to edit the codes. During this operation, the 386 HPFS server would hang while trying to seek to a negative location. This was caused by receiving erroneous information because of a bug in the WordPerfect application. o APAR IC06402 DOMAIN HANGS WITH NET311 NAME CONFLICT DETECTED ON LAN SERVER 3 3.0 WHEN MULTIPLE ADAPTERS ARE IN SERVER HARDWARE CONFIGURATION Servers in domain all log NET3111 errors and then hang: NET3111: An unexpected NETBIOS error occurred. In servers on a domain, the error logs then fills with NET3111 errors until the network is inaccessible. This is most likely to happen when there are duplicate names in the network, although other repeated error conditions could also cause it. o APAR IC06476 NETLOGON ON ADDITIONAL SERVER REQUIRES TIME TO BE WITHIN TEN MINUTES OF DC LOGON IN ORDER TO SYNC If the time is outside of a ten minute window compared to the time of the Domain Controller, Netlogon on an Additional Server fails to sync. o APAR IC06477 OS/2 TRIES TO OPEN A PATH NAME AND GENERATES ACCESS DENIED. LS COUNTS THIS IN NET STATS AS A PERMISSION VIOLATION When OS/2 tries to open a path name (ie. subdirectory or /), an access denied SYS0005 LAN Server code counts this in Net Statistics as a permission violation. o APAR IC06491 WHEN A DIR COMMAND IS ISSUED AGAINST A >2GIG NETWORK DRIVE FROM A DLR WORKSTATION THE RESULTS ARE "O BYTES AVAILABLE" When the number of sectors per cluster exceeds 255, then DOS is passed a 0. This 0 causes multiplication by 0 which results in incorrect information ("0 BYTES AVAILABLE"). o APAR IC06620 USER FAILS TO GET LOGON ASSIGNMENTS AFTER PASSWORD CHANGE When a user is forced to change their password, they do not always get the logon assignments from the additional servers because the new password has not replicated. o APAR IC06709 NEW HPFS386 SWITCH TO ALLOW CHKDSK TO BE RUN MORE THAN ONCE AT AUTOCHECK TIME A new switch has been added to the 386 HPFS IFS line. The switch is /RUNCHKDSK:nnn where nnn is a decimal number, greater than 0. This is the number of times CHKDSK /F will run on those drives that are specified by the /Autocheck parameter. The default value for this parameter is 1. CHKDSK /F will be run once even if this parameter is syntactically incorrect or if it is not present on the 386 HPFS IFS line. Use this switch if you want to have CHKDSK /F run more than once. o APAR IC06754 DOS SEARCH HANDLES NOT RELEASED BY OS/2 LS 3.0 IF NFS DRIVE IS MOUNTED AND REDIRECTED For DOS Wildcard Searches, the search handles were not cleaned up by the CleanupSearchHandles routine. o APAR IC06784 UPS DOES NOT UPDATE THE ERROR LOG AFTER QUERYING THE COM PORT BY ISSUING THE MODE COM1 COMMAND, OR USING QUERYVPD UTILITY When the QUERYVPD utility is used to query the COM port, UPS stops logging errors in the error log. Also using the MODE COM1 command to query the port, the results are the same. A NET STOP UPS, then a NET START UPS is required to have the UPS send errors to the error log. When disconnecting the cable to the port, after issuing the query, it did not record any error messages. ═══ 8.3.3.2. LAN Requester ═══ This section contains APARS that are fixed in the Requester portion of the LS 3.0 ServicePak. o APAR IC04490 FIXACC MSG - NET.ACC FILE IS NOT CORRUPTED CONTINUE Y/N: IS MISLEADING. The FIXACC utility requires more descriptive messages to inform user that the NET.ACC file is corrupt. o APAR IC04725 NET2761 ISSUED WHEN COMMAND NET SESSION IS ENTERED ON OS/2 COMMAND PROMPT Typing NET SESSION at a requester gives the incorrect NET2761 error message. The correct error message NET2106 should be displayed. o APAR IC05085 NET8002 AND SYS0234 RECEIVED BY ANY ID ATTEMPTING TO DISPLAY THE ACCESS CONTROL PROFILE + ALIAS + USER LIST ON ANY SERVER OR REQUESTER A NET8002 error message is issued when the LAN Full Screen Interface is invoked and the following are selected; Definitions, Access control, Alias, and User list. o APAR IC05150 (ICO5298) REMOTE MONITORING OF A SERVER IS ALLOWED WITHOUT THE SERVER BEING LOGGED ON TO THE LAN. The SPM/2 User's Guide and Reference clearly states that a server or requester must be logged onto the network before it can be monitored remotely. This statement is incorrect, however a problem arises when performing the above. When SPM/2 is monitoring a remote server which is not logged on to the domain, and an attempt is made to logon after Graphing/Recording has started, an error message is generated "Logon attempt failed". o APAR IC05212 REQUESTER FSI FAILS TO OPEN WHEN LOGGING ON TO AN EXTERNAL DOMAIN WHEN THE SERVER CODE IS LOADED BUT NOT STARTED. The Requester Full Screen Interface fails to open when logged on to an external domain from a system with Lan Server 3.0 loaded but not started. The attempt to open the Full Screen Interface will try to start the server, causing it to fail with a NET3062 error message. o APAR IC05227 SPECIFYING LOGONVERIFICATION When peer services was selected for install in the response file and the keyword LOGONVERIFICATION was set to something other than local (the default), Logonverification was reset to local and the value in the response file was ignored. o APAR IC05355 THE NETFILEENUM2 LS 3.0 API DOESN'T RETURN THE CORRECT NUMBER OF FILES. IT SEEMS AS THOUGH THE FIRST OPEN FILE IS NOT RETURNED. The sample program "fileenum" does not display all the open files. The first open file displayed by the NET FILES command is not shown by the "fileenum" program. o APAR IC05386 THE USER STATISTICS ARE NOT BEING UPDATED WHEN LOGGING ON TO A 3.0 SERVER ( BOTH ADVANCED AND BASIC). The Last logon field of the NET USER command always displays "Never" instead of the date and time of the last logon. o APAR IC05467 MAKEDISK FAILS WITH HFS0320 ON OS/2 2.1 INSTALL DISKETTES When attempting to build a 386 HPFS bootable diskette using MAKEDISK, error HFS0320 would occur. MAKEDISK was not removing the BUNDLE file from the diskette before starting the copying process and would run out of available space on the diskette. o APAR IC05543 LS 3.0 REQUESTER FSI LOGON DETAILS PANEL "F1=HELP" BEEPS, NO HELP MENU/DIALOGUE IS DISPLAYED WITH MOUSE-PTR OR FUNCT-KEY. No help panel was available for in the full-screen interface for the logon details item. o APAR IC05545 SYS3175 IN NETAPI.DLL AND/OR NET9570 ON APPLYING ACP TO LARGE SUBDIRECTORY TREE ON 3515 OF MORE THAN 8GB A Trap D occurs when applying an access control profile to a huge directory structure on a disk array. o APAR IC05547 LAN SERVER 3.0 - APPLY ON HIDDEN DIRECTORIES GIVES INCORRECT RESULTS In the full-screen interface, the Apply operation on a directory path which contains hidden subdirectories does not work. The access control profile of the hidden subdirectories is not updated. o APAR IC05679 TRAP 00E WHILE RUNNING GENALERT SERVICE ON HPFS386 SERVER AND REQUESTER ATTEMPTS TO LOG AN NCB ERROR. A Trap 000E may occur when the Lan Requester attempts to log an error and the GENALERT service is started. o APAR IC05681 PRINTER ASSIGNMENT NOT DELETED - INTERMITTENT OS/2 2.0, LS 3.0 Attempting to delete a user's print logon assignments in the full-screen interface sometimes takes the user back to the FSI main panel and does not delete the logon assignments. o APAR IC05710 NET8002 ATTEMPTING TO DISPLAY THE NETNAMES ON A WINDOWS 3.1 FOR WORKGROUP SERVER THROUGH THE FSI (FULL SCREEN INTERFACE) When a user attempts to display the netnames of resources on a Windows for Workgroup server via the full-screen interface, an error panel is displayed (NET8002). o APAR IC05741 ACCESS CHECK CALLOUT NOT INVOKED FOR DIRECTORY CMDS ACCESS check callout not invoked for directory commands o APAR IC05835 FIXACC UTILITY SWAPPING ACCESS RIGHTS FOR USERS WITH SAME HASH TABLE VALUES After running FIXACC, some users lost access to HPFS386 resources. The access control list for HPFS386 resources would contain the wrong users. o APAR IC05845 ISSUING THE API NETWKSTA.GETINFO WILL NOT GET SERVER NAME UNTIL AFTER THE LOGON SCRIPT HAS RUN. If the API "NetWkStaGetInfo" is called while the logon script is running, the "logon_server" field returned is blank. The "logon_server" field should be filled in before the logon script is invoked. o APAR IC05873 OS2/2.1 MAKEDISK FAILS TO PROPERLY MAKE HPFS386 BOOT DISK MAKEDISK on OS/2 2.1 would fail because of insufficient disk space (OS/2 return code=112). o APAR IC05894 INCORRECT OUTPUT IN USER DEFINITION FILES Deleted alias definitions show up as logon assignments when the domain definition is printed. o APAR IC05903 \IBMLAN\NETSRC\H\NETERR.H DEFINITIONS NOT CONSISTENT WITH: "OS/2 LS 3.0 APPLICATION PROGRAMMERS REFERENCE". IBMLAN\NETSRC\H\NETERR.H error codes not consistent with the error codes listed in Appendix C of the "OS/2 LAN Server Applications Programmer's Reference v3.0". o APAR IC05907 SYS2070 ERROR ON SHUTDOWN WITH CM/2 AND OTHER PROGRAMS LOADED ACROSS THE NETWORK. Shutdown when running Communications Manager/2 and other programs remotely across the network causes a SYS2070 error to be issued. o APAR IC05914 RECEIVE ERROR PANEL CANNOT BE FOUND NET9822E WHEN ADDING A HOME DIRECTORY TO A NEW USER. When Requester attempts to create a home directory on the Server, the error panel is missing from the panel lib file. o APAR IC05931 BAD LOGON INFORMATION IS NOT TAKEN BY AUDIT=BADLOGON, NETLOGON, LOGON OR LOGON Logon failures caused by undefined user accounts are not audited. o APAR IC05944 LOGGED-ON USERS UNDER UTILITIES IN FULL SCREEN INTERFACE DOESN'T SHOW ALL OF THE DESCRIPTIONS AFTER 75 USERS ARE LOGGED ON The NET WHO command does not display comments for all users when 75 or more users are logged on. o APAR IC05966 NET3190 ERRORS WHEN BREAKING CONECTION If customer machine is being monitored by an SPM-enabled machine. NET3090 error "Active cnt going negative!" appears in the error log after logoff. o APAR IC05970 NET ACCESS CAUSES CDROM DRIVE NOT READY ERROR Hard-error popups should be disabled in NET.EXE. o APAR IC06063 REQUESTER GENERATES A TRAP 000D IN NETBEUI.OS2 DURING SHUTDOWN During OS/2 shutdown, the machine traps in the NETBEUI.OS2 device driver at label CLEANUPRCV_386+0B. This problem could also cause a hang or incorrect function of the Lan Transport code during shutdown. o APAR IC06075 A SYS0015 OR SYS01529 ERROR IS RECEIVED WHEN TRYING TO PRINT TO A SHARED PRINTER ON THE PEER SERVER OFF THE RIPL WORKSTATION When a user tries to print a job to a shared printer defined on a RIPL workstation, where the RIPL workstation is defined as a peer Server, an error SYS0015 or SYS01529 is received. The user can Net Use to a shared printer but he cannot print a file to it. o APAR IC06101 CANNOT DELETE USER ACCESS FOR PUBLIC APPLICATION VIA FSI STARTER. When a public application is deleted from user's application selector list by using the Starter pull-down menu of the Manage OS/2 Applications panel, the application is not deleted from the user's application selector list. o APAR IC06106 CHGSRVR.EXE AND CHKSTOR.EXE DO NOT GET INSTALLED WHEN MIGRATING o APAR IC06147 NET2229 HELP TEXT IMPROVEMENT SUGGESTS FIXACC/RESTACC The help text associated with error NET2229 required modification. The help text ACTION: section now suggests repeating the command and if it fails then the drive may be at fault. o APAR IC06182 SYS0039 MSG WHEN STARTING REQUESTER WITHOUT MEDIA IN CD-ROM DRIVE When customer created an ACL for a diskette drive or CD-ROM drive and then started the requester for the first time without a diskette or CD in the drive, it displayed a hard-error popup message indicating the drive was not ready. o APAR IC06222 SYS2070 MSG RECEIVED INTERMITTENTLY AT LOADING OF DLL Program failures (especially programs loaded from a share on the server), accompanied by SYS2070 messages. o APAR IC06241 NET8014 WHEN EXECUTING A PUBLIC APPLICATION - DOMAIN CONTROLLER DOWN AND BACKUP DOMAIN COTROLLER UP Public applications could not be executed when the domain controller was down even though all necessary resources and information was available from other servers. o APAR IC06243 NETUSEADD IN LS 3.0 VIRT LAN API DOES NOT USE OS/2 LANREQ PASSWORD After installing the fix for APAR IC04957 the problem described in the APAR disappeared. However when attempting to add a connection with ui1_password<>NULL an error ERROR_INVALID_PASSWORD (86), even though the password is correct. o APAR IC06251 NET2453 ON NET ALIAS COMMAND - DOMAIN CONTROLLER DOWN AND BACKUP DOMAIN COTROLLER UP The NET ALIAS and NET USE alias commands fail when the primary domain controller fails and the backup domain controller is running. o APAR IC06259 LSI00571 ERROR DURING INSTALL ON LAN WITH POST IP07001 LEVEL NETAPI.DLL LSI00571 error occurs during install on LAN with post IP07001 level NETAPI.DLL o APAR IC06263 DUPLICATE MNEMONICS - NOT CONSISTANT WITH CUA GUIDELINES Trap 0D in nff_reterrnomorefiles. o APAR IC06312 PREPACL COMMAND IS EXECUTED INCOMPLETELY WHEN TRYING TO RESTORE FILES ACESS CONTROLS PREPACL.EXE could only handle reading a file that was 64K or less. Large hardfiles can have more than 64K of access controls. o APAR IC06432 NET8018: OS/2 ERROR 3 OCCURRED WHILE LOADING C:\OS2\CMD.EXE The public application code was unable to find the COMSPEC environment variable to use CMD.EXE when the public application was a .CMD file. It would default the path to CMD.EXE as C:\OS2. o APAR IC06448 ERROR NETALIASADD RC 87 When the NetAliasAdd function is remoted, NULL pointers in the alias_info_2 buffer will cause an error 87 (ERROR_INVALID_PARAMETER) to be returned to the caller, even though the NULL pointers are valid. o APAR IC06492 NET STATISTICS SERVER RESETS "KILOBYTES SENT" AFTER 4 GIGABYTES The NET STATS SRV command will reset the "Kilobytes Sent" counter field to zero after approximately four Gigabytes of data are sent. o APAR IC06624 ERROR_INVALID_DATA ON DEVICELESS NETUSERSETLOGONASN When doing a NetUserSetlogonasn with deviceless assignments (ie. empty lal_device) NetUserSetlogonasn will return with an error ERROR_INVALID_DATA. o APAR IC06740 NETUSERGETAPPSEL GIVES UNDOCUMENTED RC 6273 The RC 6273 was an internal error code that meant "Application NetUserGetAppSel Definition not found". This code should not have passed back and was most likely unable to get the application because the application was deleted without the application being removed from the user's selector. A return code of zero and 0x40 for the apptype, which means "UNKNOWN", should have been returned. o APAR IC06791 APPLICATION SUCH AS WORD PERFECT RETURN 0 BYTES FREE ON PARTITION SIZES > 2 GB ON A LAN SERVER 3.0 FILE SERVER Workaround for DOS Applications that can not handle large partitions. o APAR IC06814 REQUESTER HANGS (ESPECIALLY RIPL) ON RAW READS/WRITES While reading, loading or writing to large files on the server Requester hangs, or programs running on a requester hang. This is most likely to occur on a RIPL requester. ═══ 8.3.3.3. User Profile Management(UPM) ═══ This section contains APARS that are fixed in the User Profile Management (UPM) portion of the LS 3.0 ServicePak. o APAR IC04572 (ICO4995) LOGOUT USING THE NETWORK FOLDER'S OBJECT MENU ITEM "LOGOUT" RESULTS IN A SYSTEM HANG A DESKTOP hang may occur when performing a Lan Server Logout function. o APAR IC04933 NO PUBLIC APPS FOLDER OR LOGO If a backup server responds to a logon request from an LS 3.0 requester and the backup server does not have the DCDB replicator service running, users may not get their logon assignments. o APAR IC05238 LOGON ASSIGNMENTS FAIL WHEN LOGON IS SERVICED BY BACKUP DOMAIN CONTROLLER LOGON assignments fail when logon is serviced by a backup domain controller o APAR IC05416 (ICO5355, ICO5832) NET FILES COMMAND REPORTS MORE OPEN FILES THEN FSI The number of files reported by the Net Files command are inconsistent to those reported by the Full Screen Interface Action Open command. A NET9151M error message may be issued as a result. o APAR IC05468 SEV1 CL93/08/13 R300 FILE NAME ERROR OVERWRITING SUPERCALC V5 FILE TO LAN SERVER WITH 386FS SuperCalc v5.0 and v5.5 existing files cannot be saved from a DLR 3.0 machine with DOS 5.0 to a 386FS drive. A new file can be created. These files can be created and updated to a LAN Server 3.0 Entry drive (ie, regular HPFS). o APAR IC05764 NET SHARE USES DOSQUERYFSATTCH WHICH FAILS DUE TO A BUFFER OVERFLOW, ALTHOUGH ALL NECCESSARY INFORMATION IS RETURNED An overflow condition may cause a Net Share to fail with a NET2117. All the required information is available to Lan and the command therefore should complete sucessfully. o APAR IC06137 CHANGE PROFILE FAILS WHEN TRYING TO LOGON WITH DB2/2 UPM AS AN ADMINISTRATOR When trying to logon as an Admistrator using DB2/2 UPM the UPM opens the profile for the admin id that is logged on instead of the user that was selected. This problem is not with the LAN Services UPM, just the UPM that shipped with DB2/2. o APAR IC06324 NET COPY - INCONSISTENT OPERATION ON NETWORK. Operation of the NET COPY is inconsistent: When NET COPYing a subdirectory from one drive to the same drive, the subdirectory contents and the contents of all subdirectories are copied. When NET COPYing to a drive on another Server, only the first level of the subdirectory contents are copied. o APAR IC06646 WHEN PERFORMING AUTOMATED LOGON, UPM ISSUES DOSSEMCLEAR AND RECEIVED A TRAP-D WITH VALUES OF CS=D02F AND EIP=000026B3 TRAP-D in UPM when calling DOSSEMCLEAR. ═══ 8.3.3.4. Fault Tolerance ═══ This section contains APARS that are fixed for the Fault Tolerance portion of the LS 3.0 ServicePak. o APAR IC05383 TRAP000E CAUSED BY NON-MICRO CHANNEL SCSI DRIVES TURNED OFF OR FAILING This fix allows the DISKFT code to logically shut down I/O to a drive located on a powered-down or non-working disk on a non-microchannel computer. o APAR IC05853 MIRROR REQUEST FAILS USING QUANTUM DRIVE This fix enables mirroring to fixed disks having different geometries, for example, disks having different number of sectors per track or tracks per cylinder. o APAR IC05854 FTMONIT TRAP WITH CD-ROM DRIVE This fix prevents FTMONIT from searching replaceable media when looking for fault tolerance configuration data. o APAR IC05855 WHEN THE C: DRIVE IS NOT THE BOOT DRIVE, IT CANNOT BE MIRRORED This fix enables mirroring for all boot drives, not just C:. ═══ 8.3.3.5. Remote IPL Support ═══ This section contains APARS that are fixed for the RIPL portion of the LS 3.0 ServicePak. o APAR IC04982 WIN-OS2 SETUP ICON MISSING IN RIPL SYSTEMS o APAR IC05306 GETTING RPU0007 WHEN RUNNING RPLADD. RPLADD fails if there is no RPL1= parameter in IBMLAN.INI. o APAR IC06072 CANNOT UPDATE RIPL DEFINITION DRIVE LETTER FOR LS 3.0 When a Desktop exists for a RIPL workstation, the boot drive id parameter should not be allowed to change. In some cases, the boot drive id parameter is being changed which causes the Desktop to disappear the next time the workstation boots up. o APAR IC06152 RIPL SERVICE GOES DOWN WITH A NET3257 When running with multiple LAN adapters on the same LAN segment, after booting a large number of RIPL workstations (the number depends on the amount of memory in the server) the Remoteboot service will eventually log a NET3257 error and then stop. o APAR IC06242 RIPL BOOT DRIVE FIELD ERROR When users located on a RIPL workstation attempt to update the OS/2 RIPL requester in the NET FSI, they are allowed to change the RIPL boot drive letter. However, if users continue to attempt to change the drive letter, they receive one of the following errors: 1. An error panel is displayed that states that the drive letter cannot be changed if the desktop exists. This error occurs even if the DESKTOP directory does not exist in the RPLUSER\MACHINE directory. 2. An error panel is displayed that states that the AUTOEXEC.20 file could not be found or opened. ═══ 8.3.4. IPx7045 ServicePak APARs since LS 3.00.1 Refresh ═══ This section describes APARs fixed since the LS 3.00.1 Manufacturing Refresh. ═══ 8.3.4.1. Remote IPL Support ═══ This section contains APARS that are fixed for the RIPL portion of the LS 3.0 IPx7045 ServicePak. o APAR IC07217 RIPL SUPPORT FOR OS/2 SERVICE PAK XRx6200 REXX procedure RPLSP211.CMD has been added to complete the installation of the OS/2 2.1 Service Pak XRx6200 to the RIPL copy of OS/2 2.1. o APAR IC07218 HANG DURING LSP NETBIND WHEN DOING RIPL USING NDIS PROTOCOLS AND DXMJ0MOD.SYS When a RIPL client is booted using NDIS protocols and the DXMJ0MOD.SYS, the client machine will hang after doing the LSP netbind. This occurs because LSP 1.35 requires the DXMJ0MOD.SYS buffer size be set to 17K instead of the 14K required by LSP 1.31. The RPLS7045.CMD provided for users of this ServicePak will create the *.cnf files with the updated buffer size. ═══ 8.3.5. IPx7060 APARs ═══ The following section describes APARs that are corrected with the IPx7060 ServicePak. APARs are described in numerical order by functional area. ═══ 8.3.5.1. LAN Server ═══ This section describes LAN Server APARS corrected for IPx7060. o APAR IC06806 NETUSERVALIDATE2 SOMETIMES RETURNS ERROR CODE 65 When logon as a USER and using NetUserValidate2 api to verify an id and password at a server, results vary by file system. When logged on to a FAT system the password is validated. If logged on to a HPFS system a 2458 error indicating a password mismatch is received. If logged on to a HPFS386 system an error 65, indicating network access denied, is received. o APAR IC07017 AUTOCHECK HANGS ON DRIVES GREATER THAN 2GB WITH HPFS386 Customer has 2 15GB 3514 RAID arrays attached to a LAN Server 3.0 Advanced system. /AUTOCHECK of a 2GB+ drive residing on the raid fails because the mini-FSD (OS2BOOT) returns an error to HPFS386 when the latter issues a DosRead. OS/2 base has provided a fix in the mini-FSD for a similar problem but for regular HPFS not HPFS386. See Base APAR PJ12353 if the system is using HPFS. o APAR IC07030 NETALIASADD DOES NOT CREATE EXTERNAL RESOURCES--FAILS WITH RC=13 NetAliasAdd fails with a rc=13 (ERROR_INVALID_DATA) when attempting to create an external resource using either ALIAS_EXTERNAL_DOS or ALIAS_EXTERNAL_OS2. It is neccessary to create a command file or batch file to use external resources, but the Application Programmers Reference does not specifically state at what point this should be done. o APAR IC07107 SERVER DISAPPEARS FROM THE RING, BUT STILL RUNNING, MANY DUPLICATE UNKOWN SESSIONS, SESS ESTABLISH BUT THEN DISCONTINUE The SERVER will effectively disappear from the ring. Everyone is bumped off, no one can establish a session, some apps may hang the requester's session. You can still get out on the ring from the SERVER machine, (i.e. NET USE to another server and transfer data, this worked once, but failed the second time). It seems that when this starts to occur, the error log gets: NET3195 An NCB error occurred: NET1. The NCB is the data. C1 06 xx xx xx xx The C1 comand, SCATTERRCV gets a return code 06, Incomplete NCB. At this point the server starts going downhill You may also get: NET5317 The local session table is full D7 11 xx xx xx xx NET3193 A virtual circuit error has occurred. 96 18 Another symptom is a NET SESS command will return many duplicate sessions with a status of UNKOWN. o APAR IC07129 NETSVINI ACCESS VIOLATION 00010883 SETTING AUDIT IN IBMLAN.INI POST7045 Invalid parameters in IBMLAN.INI file may cause a server to trap. TRAP DETAILS MESSAGE ID : SYS3175 access violation at 00010883 netsvini.exe 0001;0000883 For example, problem happens when specifying an option on the auditing= line that includes logon and a switch that logon also monitors (such as badnetlogon). o APAR IC07150 ON 386HPFS FILE SYSTEM, DOS APPLICATION (SCHEDULE.EXE) FILE IS DELETED AND RECREATED EVERYTIME APPLICATION IS EXECUTED While executing SCHEDULE.EXE (DOS app) in a 386HPFS environment NO STATUS FILE is indicated on the main menu of the application. This is correct because it has to create PROJECT.XXX files the first time. But on each reexecution of the program, the PROJECT.STA file gets deleted and recreated. This only happens in a 386HPFS file system. The application works fine in a FAT or HPFS file system. Customer stated that the application works fine from a redirected drive, but not locally. o APAR IC07220 WF/2 PROJECTS ARE WPS OBJECTS WHICH ACCESS INI FILES VIA PRF CALLS. INI FILE UPDATES FAIL ON HPFS386 DRIVES. Accessing the WorkFrame/2 underlying files through Prf calls across the network on HPFS386 file system, the file does not get updated. As a result, the date and time stamp does not change. Also a SYSTEM "S" attribute is added to the file, making the file hidden. SYSTEM attribute problem is an Operating System problem fixed with APAR PJ15267. This fix must be applied to complete the resolution of this problem. o APAR IC07224 NET3057 ON NET START SRV, AFTER STOPPING SERVER WHEN NO ONE COULD ACCESS SYSTEM OR LOGON. Domain controller seemed to stop functioning. No one could logon or access resources. The system itself was not hung and seemed fine. NET STOP NETLOGON followed by NET START NETLOGON did nothing. A NET STOP SRV followed by NET START SRV gave a NET3057 on the NET START of the server. o APAR IC07239 FREQUENT NET8215 ERRORS RECEIVED, POST 7045 Several net8215 errors received each day on the Backup Domain Controller during busy hours. Errors occur on files dcbd.p and dcdb.f and appear to be related to the amount of traffic on the DC. o APAR IC07254 USER GETS ERROR MSGS WHEN PERFORMING NET START RPL ON SRV THAT CONTAINS SRVIFS STATEMENT IN THE CONFIG.SYS FILE Start RIPL Services and after some modification in FSI on LS 3.0.1, the Server will receive NET2186 and NET3257 if CONFIG.SYS contains SRVIFS statements. o APAR IC07256 TRAP D USING A DOS E-MAIL APP A TRAP D CS:EIP=0017:00006755 using a DOS E mail app. The problem appears unexpectedly. Dump shows Netservr code in MOVETOCLOSE list (search processing). o APAR IC07287 SYS0318 BOOTING FROM 386HPFS BOOT DISK, POST 7045 Booting from HPFS386 Boot Diskette created using MAKEDISK results in the error "SYS0318: Message file C:\IBMLAN\NETPROG\HFS.MSG cannot be found." Also, the MAKEDISK utility refers to 2.0, rather than 2.1 as the source disk to create the bootable diskettes. o APAR IC07355 THIN386 CREATES CORRUPT CONFIG.SYS Using THIN386 according to procedure in Appendix F of the Network Administrator Reference Volume 1: Planning and Installation. THIN386 creates a CONFIG.SYS that has two problems: 1. The last four lines (number 71 thru 74) contain garbage characters. 2. The first line, the IFS statement, tries to load a file (HPFS386.IFS) that is not created by THIN386. o APAR IC07414 UPS FAILS TO RESUME SERVER SERVICE AFTER POWER RESTORED, POST 7045 After UPS power is lost and then restored, appropriate messages are received but users cannot logon; the server appears to still be paused. Issuing a NET CONTINUE restores the server service and the users can logon as usual. o APAR IC07433 TIME-STAMPS CHANGE FOR ALL FILES WITH ANTIVIRUS APP and 386HPFS, POST 7045 When running an anti-virus program, all the time-stamps on all files were changed to the time of the execution. This only happened when running 386HPFS file system at the 7045 level. o APAR IC07480 UPS DRIVER WON'T LOAD ON ISA MACHINE, POST 7045 After booting machine, the UPS device driver won't load. "Interrupt level is not available" error message is received. This is only on ISA machines after installing 7045. o APAR IC07524 SERVER NAME TRUNCATED IN NETALIASADD First two characters of the server name in the ai2_server field are truncated if \\ is not used in server name. o APAR IC07540 THE FSI DOES NOT ALLOW THE SERVER DEFINITION OF A DOMAIN CONTROLLER TO BE DELETED If the role of the domain controller has changed and there is a new one, the definition of the original domain controller cannot be removed. This is found in the machine parameters screen of the FSI. o APAR IC07607 LOGON FAILURES TO SERVER RUNNING OS/2 SMP (SYMMETRICAL PROCESSING) PRODUCT AND LAN SERVER LS 3.00.1 running on OS/2 SMP. The server/netlogon services may not handle multiple logon requests correctly. Repeated logon failures and timeouts may occur. o APAR IC07692 APPLICATION RECEIVES INVALID FILE HANDLE AFTER INSTALLING SINGLE SEG OF HPFS386 CODE, POST 7045 When executing basrun.exe, the server returns an invalid file handle and output to screen is error in exe file. o APAR IC07779 SERVER TRAPS AFTER APPLYING CSD 6200 TO REQUESTERS The server displays the following trap data (at IP07045 level). CS:EIP=0027:00001385 CSACC=00fb CSLIM=00002797 The failing routine is Pathmap. Line trace shows filenames greater than 8.3 being passed by client. o APAR IC07833 LOTUS 123 V4 AND AMIPRO 3.0 FILES ARE CORRUPTED AFTER RUNNING CHKDSK ON HPFS386 DRIVE User gets corrupted files after running CHKDSK on HPFS386 drives. Typically, they are Lotus or AmiPro user files that are fine before CHKDSK is run. o APAR IC07853 NET9003E MSG WHEN CREATING RIPL DEFINITIONS FROM A COMPLEX WPS MODEL When creating RIPL definitions from the NET FSI using a model with a complicated workplace shell, a red popup error box will occur displaying a net9003e error message: "An error occurred while trying to create the above subdirectory or files on the remote IPL server...". o APAR IC07861 CACHE386 LAZY WRITE CANNOT ACTUALLY BE TURNED OFF After turning off Lazy Writes, the CACHE386 still displays Lazy Writes being performed. Lazy Writes is not actually disabled; the timer is simply reduced to 1 millisecond. o APAR IC07874 LARGE FILE COPIED FROM SERVER CONTAINS SMB ( SERVER MESSAGE BLOCK ) When user copies 1MB files from the requester to the server and then back and does a COMP locally on the files, intermittently they would miscompare. The files copied to the server were fine. The one copied back to the requester contained a SMB ( Server Message Block ), which is the protocol used by the server/requester embedded at offset 4K in the file. o APAR IC07976 DIR TO REDIR DRIVE HANGS, CD\ AT SERVER TO HUNG ALIAS SUBDIR ALSO HANGS, AUDIT TRAIL SET ON ALIAS SUBDIR User attempt to write to a redirected drive fails with access denied when the user does not have access. After two or three sequential tries/denies, the requesters session hangs, then comes back with a "connection is disconnected" message, and if more write tries are made, "server not found". If you already have other connections established, you can still access these. However, you cannot establish any new connections, and you cannot logon to the server or logoff. o APAR IC08133 HPFS386 DOSFINDFIRST/DOSFINDNEXT RETURNS INCORRECT FILE ENTRIES DOSFindNext is not finding files. HPFS386 returns the next file name that comes after ASCII ".". This means it will not find files that begin with ASCII characters less than, for example, $, !, and -. o APAR IC08170 TRAP IN LRNS1.DLL AFTER APPLYING NEW VERSION ( DATED 062994 ) AND SERVER ACCESSED BY DLR REQUESTERS With interim fix module LRNS1.DLL (with a date of 06-29-94 14:56) applied on the system, the following trap occurs when DLR requesters access the server: **** 3175 or 3171 trap encountered **** System Encountered an access violation in LRNS1.DLL at a537:0106 o APAR IC08475 UPS SHUTDOWN AND REBOOT PROBLEM At level IP07045 UPS.EXE performs the shutdown at the same time as running the cmdfile without looking at the cmdtimer. The result is that the shutdown is performed without completing the cmdfile. The UPS Service traps if the cmdfile runs past the cmdtimer amount of time. External symptom is a trap screen "Insufficient stack space for exception..." o APAR IC08477 HANG IN COPYING LARGE FILES WITH LAZY WRITE OFF A copy of a large file (64K +) to a Network drive on the server will hang the source session (either an OS/2 Requester, DLR, or locally logged on at the server) with /LAZY:OFF specified for RUN=CACHE386.EXE line. o APAR IC08743 THIN386.EXE DOES NOT EDIT THE CONFIG.SYS FILE CORRECTLY THIN386.EXE from IC05283 does not edit the config.sys file correctly. HPFS200.386 should have a path pointing to the file. The new THIN386.EXE does not include the path. o APAR IC08828 SYS3175 IN NETSERVR.EXE, POST 7045 SYS3175 error in NETSERVR.EXE CS:EIP= 001f : 0000e397 CSLIM= 0000ffa3 Netservr.exe was trapping if it received a bad SMB. When doing a C_TCONNANDX function and receiving bad data, NETSERVR.EXE was trapping instead of returning a bad SMB information. o APAR IC08903 ACCESS DENIED ALERTS GENERATED WHEN THEY SHOULD NOT BE Lan Server 7045 level code generates network access denied alerts for OS/2 access denied conditions. o APAR IC08909 INFINITE LOOP IN NETSERVR.EXE Server hangs due to loop in netservr.exe. Loop appears to be in BUFFERTIMEOUT which is part of the Netserver Scavenger code. Chain pointer causing loop is for PSF chain. Only element on the list is pointing to itself. The code is expecting a NULL pointer to end the list. o APAR IC08979 SYS3175 IN NETAPI.DLL ON ALL ADDITIONAL SERVERS All Additional servers in a domain failed with a SYS3175 in NETAPI. DLL. Reviewing the dump showed that NETLOGON.EXE was the thread with the focus, which indicated that the NET.ACC was being updated. The message that was being transmitted exceeded it's 64K limit and therefore the message did not end with the normal two zero bytes. The server was unable to purge the message, because it looks for those last two bytes. This occurred on a user update. o APAR IC09031 /LOGONSERVER PARAMETER NOT WORKING PROPERLY IN IPU7045. NET USER user_name /LOGONSERVER:"" or /LOGONSERVER: results in 'parameter is incorrect'. Also NET USER user_name /LOGONSERVER:\\"" or /LOGONSERVER: results in 'An incorrect Domain Controller has been supplied' o APAR IC09095 NET5303 D7 03 EVERY TIME THE SERVER SERVICE IS STARTED Even with the statement SIDEBAND=0 in the PROTOCOL.INI file, a sideband listen is still being issued. This was causing an immediate return code to be sent back to LAN Server and to be posted in the Error log. o APAR IC09077 IBM LANSTREAMER 32 RE-CABLE PROBLEM With multiple LANStreamer 32 adapters in a LAN Server, remove one of the TR cable from the MAU, then insert it into another port on the same MAU or into a MAU on another ring. The adapter will not work before a re-boot. o APAR IC09399 (LS 4.0 APAR IC09108) LIST.S goes to 0 BYTES when adding resources to user definitions LIST.S goes to 0 BYTES when adding resources to user definitions for a DLR 3.0 Requester from a DLS 4.0 Requester on a LS 3.0 Domain. Not all users are affected, but all users have the same permissions and athority. o APAR IC09451 PH FAILS TO GET LOGON ASSIGNMENTS FROM BACKUP DOMAIN CONTROLLER, POST 7045 NET8194 when attempting to LOGON to a Backup Domain Controller when the customer is doing the DCDB Replication with XCOPY. o APAR IC09597 POST 7045 PREPACL USERS WILL EXPERIENCE A 64K LIMITATION PREPACL command is executed incompletely when trying to restore files access controls. o APAR IC09790 (LS 4.0 APAR IC08989) CACHE386 /O CANNOT DUMP A CACHE SIZE GREATER THAN 64MB CACHE386 using the /O switch to display options such as cache size cannot display a cache size greater then 64MB. o APAR IC09791 (LS 4.0 APAR IC09030) UNABLE TO HANDLE HPFS386 CACHE SIZE GREATER THAN 128MB Due to the use of one WORD to store the number of 2K cache blocks, the maximum cache size for HPFS386 is 128MB. Setting a cachesize greater than this will cause an overflow and the overflow will wrap and the cache size will be smaller than expected. ═══ 8.3.5.2. LAN Requester ═══ This section describes LAN Requester APARs that are corrected for IPx7060. o APAR IC06738 REXX COMMAND DOESN'T WORK UNDER IC05944 Replacing "nullcheck" with a dummy routines somehow causes net.exe to exit with a 255 instead of 0 when the command has completed. o APAR IC06804 FIXACC KILLS UPM WORKER THREAD - DB2/2 & CM/2 CAN'T START NEW SESSION If user stops RDR (redirector which will also stop Server/Requester) via 'net stop rdr' command and then runs FIXACC, FIXACC does not check to see if anyone else is using the UCB shared segment and simply kills any threads, causing major problems with applications. o APAR IC06819 FAILURE TO RESET ARCHIVE ATTRIBUTE ON 386HPFS DRIVE, POST7045 Running Lotus 123 V3.1 for DOS or V4 for Windows and updating or creating a new file does not reset the Archive attribute when saving to a network drive with 386HPFS installed. Works fine when saving to a local drive, HPFS or FAT. File is written to disk using File Save or File Close and the 'A' attribute has not been set therefore the file will not be backed up with an incremental backup. If the 'A' attribute was originally set before being updated in Lotus it is removed from the file. o APAR IC07194 INCORRECT OUTPUT DISPLAYED ON DOMAIN USER LIST POST7045 When the command "NET who /domain:dm202" to another server in the same domain, an incorrect output user list is displayed. o APAR IC07222 ACCESS DENIED IS RECEIVED USING THE WNETADDCONNECTION API Access is denied when userid and password are not specified on a WNetAddConnection API call from a WIN-OS/2 application. The same WIN-OS/2 application works fine if started after logon and NET USE alias. Application, to be used by several people, must be created without specifying the userid and password by program. o APAR IC07246 USING DLR AND ISSUING AN INT 2AH WITH AX=0603 DOES NOT REENABLE THE INTERRUPTS ON RETURN Using DLR and issuing an INT 2Ah with function 06h and subfunction 03h does not reenable the interrupts on return. o APAR IC07285 NET8195 - ERROR IN PROFILE.CMD WITH IP07045 DURING LOGON After applying LAN ServicePak IP07045, a net8195 error is received - error in profile.cmd during logon. If the profile.cmd consists of just NET USE commands, the net8195 still occurs. If the profile.cmd is in REXX format, there is no error. o APAR IC07294 UNABLE TO USE SHARED NETWORK DRIVES While using OS/2 2.11, NTS/2 2.11 (WR6000) and R230 DOS Extended PCS shared folders in a native VDM, if the VNETAPI.OS2 driver is loaded in the OS/2 config.sys file, the PCS shared folder drive can be assigned but not accessed. When the VNETAPI.OS2 device driver is loaded in config.sys, the redirection setting for Native Virtual DOS Machine (NVDM) is turned OFF. Therefore, no additional network drives that rely on this redirecting can be accessed. o APAR IC07326 MSACCESS 1.10 GP FAULT 0001:39FF MSAccess 1.10 gives general protection fault in module os2k386.exe at 0001:39ff after opening and closing help, and then choosing open database. o APAR IC07413 LAN REQUESTER HELP SCREEN INCORRECTLY INDICATES THAT A DLR CAN HAVE A LOGON ASSIGNMENT FOR DRIVES A: THROUGH X: From inside Lan Requester-Definfitions-Users-Logon Details-File Assignments. Press the F1 Key. It brings up a help screen. One of the entries on the help screen says "For users logged on at DLR's type a letter from A through X. This in incorrect. A dlr can only use drives D: through Z: for logon assignments. o APAR IC07446 FIXACC CHANGES PASSWORD LAST CHANGED TO 0 DAYS AGO FIXACC resets password age back to zero. o APAR IC07615 SYSLEVEL.REQ IS INCORRECT WITH THE LS 3.01 MANUFACTURING REFRESH DISKETTE AND CDROM VERSIONS OF THE PRODUCT The SYSLEVEL.REQ that is contained in the LAN Server 3.01 Manufacturing Refresh on both CDROM and DISKETTE is incorrect. The internal product ID is 5010 and must be 5000. o APAR IC07707 IP07045 RASX.EXE MODULES CAUSE THE FSI TO ERROR ON A REQUESTER WHEN A PUB APP IS OPENED With IP07045 applied to the domain controller and the os2 req wkstn, the end user is logged on to the DC with a userid, the Full Screen Interface, definitions, logon details will yield a net2351 and net8002. o APAR IC07876 USING INTERRUPT 21 5F03 CALL IN A VDM SESSION, PASSWORDS FAIL AND ACCESS DENIED IS RECEIVED User uses an interrupt 21 5f03 call to access an external resource via the guest id. The guest id requires a password for access. This will fail with an access denied when trying to use a password in the call. o APAR IC08058 RUNNING CHKSTOR GENERATES SYS3175 AND TRAP00D Issuing CHKSTOR command, with or without parameters, causes SYS3175 and/or TRAP000D in DOSCALL1.DLL. o APAR IC08166 NET USER USERID /WORKSTATIONS:* OR "". RECEIVES NET3502. POST 7045 IP07045 user receives a net3502:OS2 error 87 has occurred, parameter is incorrect. When command is issued at level IP07000 it works. o APAR IC08277 NAMED-PIPE APP HANGS WHILE LOADING DLL OR EXE OVER THE NETWORK During the loading of a DLL or an additional EXE module, a temporary hang occurs if more than one DLR launches the VB app at the same time. o APAR IC08582 TRAP IN NETBIOS.OS2 WHEN USING AT&T ATTISO APPLICATION When an application that used ATTISO (a protocol written by AT&T) was run, netbios.os2 trapped. (ATTISO calls the redirector, which sometimes calls netbios.os2). o APAR IC08793 BACKACC FAILS TO ACCEPT WILDCARD IN PATHNAME WITH NET3563 AND NET3567 BACKACC with WILDCARD fails with NET3563 and NET3567. POST7045. NAR VOL 3, PG C-2 states wilcards are valid in the PATH. o APAR IC09184 AFTER SEVERAL NET VIEW COMMANDS, RECEIVED OS/2 ERROR 54 When issuing a net view \\ with LS + TCPBEUI + \ibmcom\rfcnames.lst, an OS/2 Error 54 "Network busy or out of resources" is intermittently returned. Once the OS/2 Error 54 has been returned, all network operations over TCPBEUI cease to function. o APAR IC09247 UNABLE TO TOGGLE FROM PCSUTIL SCREEN WHEN RUNNING UNDER OS/2 WITH LAN REQUESTOR AND VIRTUAL DOS API SUPPORT INSTALLED When Running PC3270 Full Function DOS in an OS/2 fullscreen and the LAN requestor has DOS LAN API support installed will not jump to the host screen. If the user attempts to toggle ALT-ESC several times and then cursors to the EXIT to HOST bar and Presses Enter the PCSUTIL screen will go away and you will see the ALT-ESC sequences handled. This only occurs when VNETAPI.OS2 in in the CONFIG.SYS. If PCSUTIL is exited then the USER can Toggle normally through the HOST sessions. o APAR IC09687 NAMED PIPE APPLICATION CANNOT BE STOPPED Customer written program for OS/2 will not close completely. Threads stay active in PSTAT. Customer attempts to kill the processes, but the problem remains. The only method to end is to ReBoot the system. o APAR IC09704 NET8215 ERROR REPORTED IN ERROR LOG EVERY TIME LS 4.0 USER LOGS ON Whenever a LS 4.0 user logs on to a LS 3.0 Domain, the following error is logged in the error log of the LS 3.0 DC if the user has never had any logon or public application assignments given: NET8215: OS/2 error number 3 occurred while opening E:\IBMLAN\DCDB\USERS\xxxxxxxx\USER.L. The error does not affect the logon or server in any way. o APAR IC09789 (LS 4.0 APAR IC08932) LIST.X FILES NOT UPDATED WHEN 3.0 DOMAINS ARE ADMINISTERED FROM 4.0 OS/2 SERVERS AND REQUESTERS Create a number of accounts, then defining them to a group. Then proceeded to drag the printer icon over to the group. Select continue because permissions are already defined to the alias. Select to add them to the logon assignments. When they are added as LPT3: DOS requesters do not get the logon assignments. The GUI shows it has been defined but checking the LIST.X for the users shows a blank line on line 3. There is also a problem adding individually using the GUI (through the user id icons). o APAR IC09792 (LS 4.0 APAR IC09033) TRYING TO CONNECT TO A NETWORK PRINTER THROUGH THE GUI GIVES "PARAMETER NOT VALID" MESSAGE. Customer tries to connect to a shared printer but when he tries to add a new assignment an error message "Parameter not valid" comes up. At the help panel, help text "DSS0501" appears. It is not possible to connect to a known printer by alias or any other way. o APAR JR08128 MESSAGE POPUP SCREEN WILL NOT OCCUR AT LOGON VIA A PROFILE.CMD THRU A REXX CMD Logon through LOGON ICON in UPM Folder fails to successfully run users profile.cmd file resulting in a failure to popup the logon message. The message is logged in the message.log. This works OK when the message is written directly rather than from a command file. ═══ 8.3.5.3. User Profile Management (UPM) ═══ The following APARs were corrected in User Profile Management for IPx7060: o APAR IC06780 MSG NET2186- NET START REQ COMMAND, COMMAND REJECTED User installed a maintenance system without PMSHELL.EXE through the SEMAINT.EXE command. User also installed a LAN REQUESTER 3.0. The machine boots correctly but when he executes the NET START REQ command, he gets a NET2186 message and the command is rejected. o APAR IC06838 PROBLEM WITH EXTERNAL SHARED RESOURCES. Getting NET2117 and NET9127E error messages when trying to share a PC Support drive or A: drive. o APAR IC07144 NETUSERSETLOGONASN RETURNS ERROR_INVALID_DATA When NetUserSetLogonAsn is passed the exact data returned by NetUserGetLogonAsn it returns ERROR_INVALID_DATA (13). The FSI however can add/change Logon Assignments. The problem seems to be in the customer's DCDB. o APAR IC07507 THE UF_DELETE_PROHIBITED FLAG NOT CHECKED DURING A NETUSERDEL API CALL The UF_DELETE_PROHIBITED flag, found on page 3-391 of the Application Programming Reference, was not being checked during a NetUserDel API call. o APAR IC07544 POPUP MESSAGE SCREEN DOES NOT DISPLAY " PRESS ESC TO EXIT " AFTER INSTALLING IP07045. After applying IP07045, popup messages no longer display the statement " Press ESC To Exit." All other information apprears normal. o APAR IC08126 RETURN MESSAGE THAT STATES WHICH DOMAIN YOU ARE LOGGING ONTO IS INCORRECT If logged onto a domain and switched to a redirected drive, typing in logon /d: (new domain) and processing through the prompts causes the message below. The message incorrectly states which domain you are going to logon to. "Are you sure you want to end these sessions and logon to domain xxxxxxxx?" where xxxxxxxx is an incorrect domain name. o APAR IC08235 LSM 1.0 HANGS WITH SYS3175 EXCEPTION IN NETAPI.DLL WHEN MAC USERS TRY TO LOGON. Post 7045 Using a backup copy of the NET.ACC to rebuild LSM server, MAC users try to logon but get a blank screen; server hangs with the following sys3175: A program generated an access violation at 15EA3367 NETAPI.DLL 001B:00003367 o APAR IC08888 NETCALLOUTFREE DOESN'T RELEASE DLL, CAUSES TRAP Client using IBM written code to use API to register his own DLL for call. Using NETCALLOUTFREE to release DLL's. However, does not seem to adequetely clean out the table and will TRAP on the next access attempt. o APAR IC08980 SYS3175 WHEN TRYING TO LOGON AFTER UPDATING PW VIA NET PASSWORD. Password updated via NET PASSWORD USERID OLDPW NEWPW and then tried to logon. Received a SYS3175 in NETAPI.DLL at 0018:00002DA6. The CS:EIP= BA5F:00002DA6 and CSLIM= 00003C95. The password was updated and after shut down, and retry, logon was successful. o APAR IC09793 (LS 4.0 APAR IC08972) LOGON PASSWORD TOO SHORT, ERROR MESSAGE WRONG Getting message, "The password is too short, must be at least 0 bytes long". After the password has been expired and a new password is entered that is less than the required minimum characters in length, the above error message will appear. o APAR JR08184 UPM ABORTS FOR CERTAIN USER ID'S UPM will abort when the Manage Users selection has been made. APAR occurs when this file is installed in a LAN Server 3.0 machine with IP07045 installed. This only occurs for certain IDs. o APAR JR08187 OPERATOR PRIVILEGE USERID CHANGES OWN COMMENT, RESULTING IN UPM0058C RC 5 When logged on with a USERID that has Account: Operator privilege, and attempting to update a user comment, userid receives an Access Denied (rc=5) and the comment is not updated. ═══ 8.3.5.4. Fault Tolerance ═══ This section describes Fault Tolerance APARs that are corrected for IPx7060. o APAR IC09255 RUNNING FTREMOTE A SECOND TIME REMOVES CRITICAL ERRORS FROM FTSTATUS.LOG In FTREMOTE, after an unfixable error is written to the status log one time, it is marked as 'shown'. To the user, this error disappears without doing a CORRECT command. This causes problems when FTREMOTE is used to dump periodic status without doing corrections. ═══ 8.3.5.5. Remote IPL Support ═══ This section describes Remote IPL APARs corrected in IPx7060. o APAR IC05332 NET2503, NET2514, NET2511 USING LSP DRIVERS Using LSP Drivers DXMAOMOD.SYS, DXMEOMOD.SYS, and DSMJOMOD.SYS works in non-ripl environment on disk workstation; if same is done under ripling, the workstation gets NET errors or hangs when it tries to load MS-DOS or IBM DOS. o APAR IC06853 INSTALLING LAN SERVER AFTER DATABASE WAS CONFIGURED AND USED CAUSES USERS TO LOSE ACCESS TO POST 7045 DATABASE. Users lose access through UPM after applying LS 3.0 to an already existing ES 1.0 Database. None of the required questions are being asked on initializing the Domain Controller Database. o APAR IC07139 NET9003E WHEN CREATING RIPL USERS AFTER INSTALLING LS 3.00.1 REFRESH After installing the LS 3.00.1 Manufacturing Refresh, some RIPL servers cannot create any RIPL clients. When trying to create a RIPL client, the Full Screen Interface (FSI), displays a red error panel indicating that there is not enough disk space or not enough file handles. o APAR IC07200 MKRDPM ON A 2.88 MB DRIVE MAKES THE DISK UNREADABLE ON ANY 2.88 DRIVE. POST 7045 When creating a bootable RIPL disk via the MKRDPM utility on a different drive type than the diskette was formatted on, diskette is not readable but is still bootable. o APAR IC07389 RPLADD DOES NOT CORRECTLY CREATE ACCESS PERMISSION ON ADDITIONAL SERVER. Using RPLADD on the Additional Server the ACCESS PERMISSIONs are randomly incorrect/missing and FSI must be used to correctly create the right access permission. Using RPLADD on the Domain Controller everythings works fine. o APAR IC08210 NET9010E ERROR WHEN DELETING MULTIPLE RIPL ID's FROM THE FULL SCREEN INTERFACE, POST 7045. Using the Full Screen Interface (FSI) to delete several (more than 30) RIPL id's, a NET9010E error is received and some of the RIPL id's do not get deleted. o APAR IC08699 RIPL STOPS WHEN OPENING T/R CARD ON IBM VALUE POINT SYSTEM WITH HARDWARE CACHE ENABLED. IBM ValuePoint Pentium P60 system hangs with the LSP opening adapter message on the screen when trying to RIPL. If the Hardware Cache is disabled, the RIPL process works. o APAR IC08808 SYS3175 IN LRCI1.DLL ON RIPL SERVER SYS3175 on Server: A program generated an access violation @ 11b02bde LRCI1.DLL. Intermittent sys 3175 on RIPL server. Users already logged on can continue use, new users can not connect to the server. o APAR IC09115 RIPL HANGS WHEN USING AUTO 16/4 T/R MC ADAPTER Using the new Auto 16/4 T/R MC Adapter to RIPL, the Requester will hang. The problem is with RIPLBOOT.SYS. o APAR IC09787 (LS 4.0 APAR IC09214) Support added for RIPL of Warp Remote IPL support has been enhanced to allow RIPL of OS/2 Warp. ═══ 8.4. DOS LAN REQUESTER APARs ═══ This section describes DOS LAN Requester APARs fixed for the previous service levels plus new fixes. ═══ 8.4.1. IPx7003 SelectPak APARs ═══ The following list describes APARs for the DOS LAN Requester component that were fixed by IPx7003 Select Pak. APARs are listed in numerical order. o IC04192 A misleading error occurs when the maximum number of users attempting to access a shared application is exceeded. The error is: "The following panel was not found. CE71". o IC04205 RIPL Server receiving ACCESS DENIED error message during the RIPL Logon. No error messages at the RIPL Workstation or Server. Errors are noticed because ALERTER is running on the Server. No errors in the Server Error Log. o IC04391 When a user attempts to update the Served Applications group in the full-screen interface by adding or deleting shared applications, the system may hang. This occurs only when there are a large number of shared applications defined on the domain. o IC04496 If NET START is attempted from a command prompt started from the DOS Shell, a NET501 error is generated. The workstation then hangs when the user attempts to exit the DOS command prompt. o IC04534, IC05146 The user cannot log on to a Microsoft LAN Manager server. o IC04689 The CURRENT.D file causes the workstation to hang when NET LOGON is attempted after rebooting. o IC04702 The initial logon panel for the DLR Windows interface does not display a cursor if Windows displays a message at startup. o IC04926 The FoxPro database program gives an error and exits. o IC04985 If a user attempts to change screen colors in the full-screen interface and the EIM.PRO file is missing or damaged, a CE08 error message is displayed. o IC05048 The INSTALL.SCR file is damaged when installing Lotus 1-2-3 version 2.3 and version 2.4 from a remote drive. o IC05050 The /UMB parameter for NET START does not work with DOS 5.02. o IC05051 An error occurs at logon when connecting to a logon assignment fileset that is the same as the home directory assignment. The result is either a NET229 error, if logging on from the command line, or a NET9481E error, if logging on from the DLR full-screen interface. o IC05053 If using opportunistic locking (bit 'i' is set to 1 in the /WRK: parameter for NET START), a lock violation is displayed on some lock and unlock requests. o IC05054 When using DLRINST to upgrade from PCLP 1.34 to 2.0 DLR the DOSLAN.INI for DLR gets corrupted. o IC05055 A read/write access violation occurs on a file being accessed simultaneously by multiple users with some LAN applications. o IC05096 A CD-ROM drive is being interpreted as a network drive, causing the workstation to hang. o IC05118 When FIXINI.EXE is run, if the DOSLAN.INI file contains no character past the 10th workheuristic bit (bit 'j') in The /WRK: parameter, bits 11 through 15 are not added. o IC05146 Users on DLR 2.0 workstation fail to get logon assignments that are external resources. Reported error is CW19461. o IC05509 A user gets a "DISK ERROR 64 READING DRIVE X" when printing from Wordperfect 5.1 from DLR 3.0 Workstation. o IC05525 A NET808 network error occurs when attempting a read/write to a redirected drive. ═══ 8.4.2. IPx7045 DLR APARs ═══ This section contains a list of APARS fixed for the DOS LAN Requester portion of the LS 3.0 ServicePak. o APAR IC04261 NET 248 THE DOMAIN CONTROLLER CANNOT BE CONTACTED WHEN A DLR WORKSTATION TRIES THE LOGON TO A BACKUP SERVER If the Domain Controller goes down, Dos Lan Requester will not allow logon if a backup Domain Controller exists. o APAR IC04456 DLR WITH LOAD=C:\WINDOWS\WINPOPUP.EXE IN WIN.INI WILL CONTINUE TO APPEND A WINPOPUP ENTRY AT EACH START OF WINDOWS If a DLR has WINPOPUP fully qualified on the load statement in WIN.INI, (i.e. load = c:\WINDOWS\WINPOPUP) DLR does not recognize that the WINPOPUP statement is there and adds another one. If load = WINPOPUP is coded, it is recognized correctly. o APAR IC04921 ETH_AUT.BAT HAS INCORRECT WORKSATION HEURISTICS VALUES (/WRK) FOR ETHERNET RIPL Apparently the ETH_AUT.BAT was not updated from the LS 2.0 values. The /WRK values in ETH_AUT.BAT are incorrect. o APAR IC05054 DOSLAN.INI IS INCORRECT IF /SRV IS ON PCLP NET START LINE When using DLRINST to upgrade from PCLP 1.3x to DLR 3.0, the DOSLAN.INI for DLR gets corrupted if the PCLP NET START command in the AUTOEXEC.BAT contains parameters that are not separated by at least one blank. o APAR IC05162 WLR0064 WHEN ADDING A SHARED APP TO A GROUP FROM WINDOWS 3.1 If running Windows in standard mode and attempting to add a shared application to a new group, the error WLR0064 may occur. o APAR IC05189 THE FUNCTION 5F04H (CANCEL REDIRECTION) *DOES NOT* RETURN THE CORRECT ERROR CODES WHEN A NETWORK ERROR IS PRODUCED API calls to the VNETAPI driver are returning error codes from the OS/2 redirector instead of a DOS return code which could cause the DOS application confusion. The OS/2 error code needs to be mapped to an appropiate DOS return code. o APAR IC05238 LOGON ASSIGNMENTS FAIL WHEN LOGON IS SERVICED BY BACKUP DOMAIN CONTROLLER The original release of LAN Server 3.0 would not allow for the backup server to perform logon assignments when the primary domain server was disabled and returned a NET8198 error (indicating logon assignment failed). This problem has been corrected and the two dynamic link libraries that were affected were LRRS.DLL and LRSD.DLL (On the backup server). o APAR IC05280 REPLACING THE %2 PARM IN AN EXTERNAL RESOURCE .BAT FILE CAUSES A CW19461 OR CW19462 ERROR For external aliases, a batch file is created with the statement "NET USE %2 \\server\netname". If the %2 in the batch file is replaced with a drive letter or printer, the error CW19462 will occur. o APAR IC05384 LOGON ATTEMPT ACROSS A BRIDGE GIVES NET248 OR NET355 If DLR is started without the /NMS parameter and logon is attempted across a bridge or the server is too busy to respond quickly to the requester logon may fail with a NET248 error. This error is more likely to occur on machine with faster processors. o APAR IC05441 ACCORDING TO THE COMMAND REFERENCE, LOGOFF /D /Y, /N /Y, OR ANY OTHER COMBINATION SHOULD WORK, IT DOES NOT WORK. The help in the Online LAN Server command reference was misleading and has been changed to be identical to that of the hardcopy version of the LOGOFF function. o APAR IC05483 NET COPY FAILS WITH NET810 IF 13 OR MORE NET USES ARE IN EFFECT WHEN NET COPY IS ISSUED The NET COPY command that contains a UNC path (i.e. "net copy \\server\netname\file c:\file") will fail with a NET810 error if it is issued on a DLR machine that has 13 or more NET USE's active. o APAR IC05512 DOS API 4202 LSSEEK TO END OF FILE SETS EOF POINTER INCORRECTLY If a program running DLR issues a series of sequential writes that extent the length of a file and then issue an INT 21H function 4202H (LSSEK to end of file) the program may be returned an incorrect value. This problem has occured with Wordperfect and caused data near the end of the file to be overwritten. o APAR IC05515 DLR RIPL WORKSTATION HAS /WRK PARAMETER #3 SET TO 0 WHILE USING TR 16/4 ADAPTER CAUSES MULTIPLE "COPY" PROBLEMS If workheuristic bit C in the DOSLAN.INI is set to 0, then a DOS COPY or XCOPY of a file has the following problems: 1. A copy of a file from the workstation to the server, when the file does not exist on the server, will get a "file not found" error. 2. A copy of a file from the workstation to the server, when the file does exist on the server, does not change file size. o APAR IC05569 DLR RECEIVES A NET248 ERROR DURING LOGON TO AN EXTERNAL DOMAIN IF THERE ARE INSUFFICIENT NAME RESOURCES AVAILABLE When too few NAMES are specified for the LAN Support Program (DLR requires a minimum of 8 names) and a LOGON to a domain other then the one listed in the DOSLAN.INI file is attempted, the logon fails. If the logon was done at the FSI, a messages displayed slowly pops up saying "the domain controller could not be contacted". If the logon was done at a command line, a NET248 message will be slowly display. After the logon attempt, all responses are very slow. It may take up to 30 minutes for the complete NET248 message to be displayed. o APAR IC05715 LOADING DLR HIGH WITH THE LH NET START AND /UMB PARAMETER IN THE DOSLAN.INI GIVES A NET311 If the network is started with the "LOADHIGH NET START" command, the error "NET017 There is not enough memory to start the network" or "NET311 The NETWORK?.CMD file cannot be accessed" may occur. The error that is received depends on the amount of free UMB memory available. o APAR IC05716 INSTALLING DLR & AUTOEXEC.BAT WITH NO PATH, THE DLR PATH IS APPENDED TO THE AUTOEXEC.BAT WITH NO PATH= STATEMENT If you install DLR onto a machine that does not have a PATH= statement in the AUTOEXEC.BAT, the path where the DLR code was installed is appended to the AUTOEXEC.BAT without PATH= in front of it. For example, the appended line reads "C:\DOSLAN" instead of "PATH=C:\DOSLAN". This results in a BAD COMMAND OR FILENAME error when executing the AUTOEXEC.BAT file. o APAR IC05758 WHEN A DLR NETWORK ADAPTER IS REMOVED FROM THE RING IN THE MIDDLE OF A COPY COMMAND, THERE IS NO ERROR GENERATED When using the Lan Network Manager to remove a Dos Lan Requester's (DLR) adapter from the ring and the DLR is actively copying files, the file copy ends, but no error is generated and the machine hangs. o APAR IC05792 DLR HANG 386MAX PROTECTION VIOLATION In situations where the server is very busy, a Protection Violation Trap in 386MAX may occur. Without 386MAX running this could cause a hang. This error will only occur with NBS set to 3 or 4. o APAR IC05818 LS 3.0 DOSLAN.INI /NTS (NO TIME SYNCHRONIZATION) PARAMETER IS IMPLEMENTED WITH LS 3.0 SERVICEPAK (IP07003 FOR DLR'S) A new parameter /NTS (No Time Sync) has been added. If the /NTS parameter is in the DOSLAN.INI or on the NET START command line, the NET LOGON command will not sync the workstations time with the logon servers. o APAR IC05908 LOGOFF TRAPS WHILE REMOTE CM IS RUNNING In the original release of LAN Server 3.0, the command LOGOFF trapped when a remote Communications Manager was running. The reason was that UPM notifies APPC of logoffs and LOGOFF was trapping in the dosloadmodule call to load APPC.DLL in order to make the logoff notification call. The APPC.DLL had been loaded off a LAN drive that had already been disconnected by LOGOFF when the dosloadmodule call was made. The OS/2 loader trapped because it had an invalid handle to APPC.DLL. This has since been corrected and the deliverable file that is affected is LOGOFF.EXE. o APAR IC05936 DOS 5.0 GETMACHINENAME FUNCTION CALL (5E00H) DOES NOT PAD MACHINE NAME WHEN ISSUED IN VDM The API to get the machine name (INT 21x ax=5e00) should return a machine name that is padded with blanks, it does not. o APAR IC06022 HARVARD GRAPHICS FAILS TO LOAD AFTER INSTALL CHECK The flag byte (in BL) that is returned from the interrrupt 2fx function B800x was being incorrectly set. If an application checked BL on return from this call they would be getting the wrong information, which could indicate the network was not installed when it really was. o APAR IC06088 CLOSE OF PIPE NOT WAITING ON OUTSTANDING DOSREADASYNCNMPIPE REQ If a DosReadAsyncNMPipe is issued and then the pipe is closed before the read completes, the read request will receive an error 109 "Pipe Broken" o APAR IC06166 FSI LOGON HANGS DLR WHEN DLR INSTALLED IN DIR OTHER THAN DOSLAN When DLR is installed in a directory other than DOSLAN and no DOSLAN directory exists, a logon from the FSI will potentially create lost clusters and chains on the hard drive. o APAR IC06270 LOGON ATTEMPT ACROSS A BRIDGE GIVES NET248 OR NET355 If DLR is started without the /NMS parameter and logon is attempted across a bridge or the server is too busy to respond quickly to the requester logon may fail with a NET248 error. This error is more likely to occur on machine with faster processors. o APAR IC06391 SHARE.EXE CAUSES NET810 ON DLR AT 7003 LEVEL Issuing the NET WHO command with SHARE loaded or in a Specific DOS Session (VMB) under OS/2 will result in a NET810 error. o APAR IC06505 RUNLSAPP NOT WORKING WITH FREELANCE Network connections are deleted when starting Freelance Graphics in Windows using RUNLSAPP.EXE. o APAR IC06758 AFTER LOGGING OFF FROM INSIDE WINDOWS AND THEN PERFORMING A NET WHO COMMAND YOU STILL SEE THE MACHINE NAME LOGGED ON A problem exists when logging off from inside windows and then performing a Net Who command from the command line. The machine will still be listed in the table, however the user ID is changed to the machine ID. o APAR IC06824 NET0805 MESSAGE ON DISCONNECTED RESOURCE ON DLR MACHINE WITH /ENC OPTION The problem deals with the /enc parameter in the DOSLAN.INI file, and having a logon assignment on an additional server. If the drive becomes disconnected while logged on, and user tries to use it, a NET805 message will be issued indicating that the network device no longer exists. o APAR IC06904 WINDOWS 3.1 ON DLR DOES NOT PROMPT YOU TO LOGON WHEN YOU ESTABLISH A CONNECTION USING UNC NAMES THRU THE DRIVE ICON When using the windows DRIVES icon, it was possible to gain access to a redirected drive without being prompted to logon. ═══ 8.4.3. IPx7060 DLR APARs ═══ This section describes DLR APARs that were corrected in IPx7060. o APAR IC05909 DLR ALLOWS ILLEGAL FILE, LPTX, TO BE CREATED. When an application tries to print to a printer that the user doen't have, it causes an illegally named file(e.g.,LPTx, PRN) to be created on the network drive. o APAR IC06482 NETWORK APPLICATIONS ABORT WHEN STARTED VIA PROGMAN.INI. With "USER LOGON" enabled at Windows startup, when PROGMAN.INI (which contains the network group information) is used to start network applications, those applications ABORT at Windows Startup because the user LOGON has not yet completed. o APAR IC06505 RUNLSAPP WON'T WORK WITH FREELANCE. When using RUNLSAPP.EXE to launch LOTUS FREELANCE, FREELANCE becomes unstable and both Freelance and Windows fail. Problem does not occur when Freelance is run from Windows Program Manager. This can occur with other Windows applications that have an initial exe that spawns other exe's. o APAR IC06611 CANNOT ENTER THE PASSWORD WHEN THE /ENC IN THE DOSLAN.INI IS SET. WLR0053: "You have specified a password that is not correct" error received while changing expired password on a DLR WINDOWS requester if the /ENC ( encryption ) parameter is specified in the DOSLAN.INI file. o APAR IC06655 APPS HANG WHEN INVOKED FROM DLR 3.0 FSI WITH EITHER NETX OR VLMS With DLR 3.0 (IP07045 applied) and NetX or VLMS configured and loaded, any attempt to start any apps from the DLR full screen interface results in a hang condition, requiring a cold boot. If NetX or VLM is not loaded, then the apps invoke. o APAR IC06804 FIXACC KILLS UPM WORKER THREAD - DB2/2 & CM/2 CAN'T START NEW SESSION If user stops RDR (redirector which will also stop Server/Requester) via 'net stop rdr' command and then runs FIXACC, FIXACC does not check to see if anyone else is using the UCB shared segment and simply kills any threads, causing major problems with applications. o APAR IC06851 WORD PERFECT 6.0 RETURNS 0 BYTES FREE ON PARTITION SIZES > 2 GB ON AN LS 3.0 FILE SERVER Problem occurs when DOS applications attempt to perform a timed backup of work in progress. User-initiated saves have no problem. o APAR IC06906 FIXACC DESTROYS LAST LOGON DATE INFORMATION IN NET.ACC Running FIXACC from lan server 3.0 on a NET.ACC file will remove the LAST LOGON DATE information from the NET.ACC. Data was in the NET.ACC before running was destroyed. o APAR IC07035 WHEN RUNNING UPGRDLR.BAT IT WILL NOT KEEP LOCALLY SERVED APP MENUS. THEY RETURN TO DEFAULT When running the upgrdlr.bat, it will not keep the user defined applications. They are stored on the local files $*.* ($$GROUP.FIL and $GROUP20.FIL). (side note: ls30 and dlr 7000 GA also need a newer fixini.exe or going from dlr 1.3 to 3.0 gives net003 because the doslan.ini /wrk does not contain 15 characters) o APAR IC07055 DLR W/CDROM USING PUBLIC APP THAT ASSIGNS NEXT DRIVE GETS ERROR CE85: PANEL NOT FOUND. Using DLR with CD ROM installed, choosing a public app that assigns the next available drive, gets the following error: Following panel was not found. CE85 Severity ...... : Source ........ : 10 Code .......... : 4 If the application is set up with a specific drive letter for the assigned drive, it works. o APAR IC07261 NET224 ERROR DURING LOGON USING THE /SCRIPTPATH OPTION ON A DLR Using the /scriptpath function to run a file at logon causes DLR to fail with a Net224 error, stating that no user is currently logged on. The Scriptpath file runs before the logon process completes. o APAR IC07678 INVALID DRIVE SPECIFICATION WHEN LOGGING ON TO LS30 VIA DLR TO WINDOWS RUNNING RUNLSAPP. The customer uses RUNLSAPP in Windows and boots directly to Windows after running LSP and NET START. A logon panel is presented and the user tries to logon with a valid Userid and Password. DOS attempts to run the group logon profile but receives an INVALID DRIVE SPECIFICATION. It then returns to program manager with the DOS shell minimized. The user then has to double click on the DOS icon to run the user logon profile. Both the Group and User logon profiles work fine under DOS. o APAR IC07693 DLR30 FIXES CHANGES DRIVE Z TO DRIVE Y After user applies fixes from DLR30.ZIP file, and re-boots/logs on, the previous log assignment with an alias assigned to drive Z now is assigned to drive Y. User previously had another logon assignment to drive Y that is now invalid. o APAR IC07756 DLR HANGS WHEN TRYING TO CANCEL A PRINT JOB Cancelling a print job from the DLR Full Screen Interface (FSI) hangs the workstation. If running QEMM instead of EMM386 on the same machine, QEMM will return following error message: Exception #13 at 373D:027C, error code: 0000 o APAR IC07838 UNEXPECTED WLR0028 MESSAGE FROM DLR WHEN LOGON WITH EXPIRED PASSWORD. When logging on from Windows control panel "network" icon, users with expired passwords may be unable to change them. Users see the message: "You do not have sufficient privilege to perform this operation. WLR0028." o APAR IC07842 POP-UP MESSAGE HANGS ON DLR ON 80286 MACHINES With the DLR installed from LS 3.0 on a PS/2 8560- 071 with 16/4 TR adapter, and with the /POP parameter in the DOSLAN.INI and the Pop-up message service, the Pop-up message hangs and the customer cannot break with ESC. The machine must be rebooted. This error only occurs on a 80286 machine. o APAR IC07878 CE21508 CAN NOT ACCESS PANEL LIBRARY WITH DLR ONLINE REFERENCE Accessing the DLR Online Reference generates panel error CE21508 when there is a backup domain on the network. If the backup domain is shutdown or is busy and can not respond, OLR can be accessed without problems. o APAR IC07962 DLRS AT 7045 LEVEL DO NOT TIMESYNC IF BACKUP DC IS RUNNING. Running TIMESOURCE on Domain Controller, if the backup DC is not running the DLRs get their time from the DC. If the backup DC is running, the DLRs do not timesync. o APAR IC07964 ERROR NET355 WHEN ATTEMPTING TO LOGON FROM DOS LAN REQUESTER ACROSS BRIDGED 56KB LINE TO SERVER Customer receives NET355: Access Denied error when attempting to logon from DOS LAN Requester across bridged 56KB line to LAN Server. Error is returned within 2 seconds or less. o APAR IC08131 REDIRECTED SCREEN OUTPUT FROM DLR ON SRV DRIVE DIDN'T WORK User redirects output from a File transfer to a server drive. The DOS LAN Requester redirects output correctly up to a special size. If the redirected output is too big, the requester hangs but the NUMLOCK key works. No Adapter beep. The same thing happens if you make a redirected screen output from a DIR c:*.* /S command to a server drive. o APAR IC08207 NET3101 MAXUSERS EXCEEDED MESSAGE ON SERVER, NET3502 ON OS/2 REQUESTERS, NET805 ON DLR WHEN USERS TRY TO CONNECT TO RESOURCES. Server logs NET3101 error indicating MAXUSERS has been exceeded when logon alias' are shared at user request. Logged on users can still use their resources, new users may not be able to logon. NET USE to resources on the server from an OS/2 requester results in NET3502, SYS0071. DLR users get NET805. o APAR IC08286 SEGMENT LOAD FAILURE WHEN EXITING WINDOWS APPLICATIONS. When using RUNLSAPP to start Word Perfect for Windows 6.0a on a DLR workstation, the following error is returned when exiting the application: WPWIN60 Caused a Segment Load Failure in module WPWIN60.EXE at 0078:3003 . CLOSE After pressing close, the screen sometimes goes blank and hangs the computer and sometimes goes back to the C: prompt. o APAR IC08557 DOS_READ OF 2152 BYTES TO MESSAGE MODE NAMEDPIPE HANGS SYSTEM. Running app on DOS/Windows client, server opens a namedpipe in message mode. DOS app returns from PEEK_NAMED_PIPE with 2152 bytes, attempts the read, and the DOS client hangs. Successful READs from a client when the data size is greater than or less than 2152. o APAR IC08561 DLR HANGS WHEN FILE EXTENSION IS NOT USED. This problem occurs when a fully qualified path without a file extension is used to execute a program. The DLR hangs can occur: 1. on panel CWSW2 during RIPL or 2. during execution of a batch file or 3. during execution of a program from the Command Line Interface. o APAR IC08682 LOADING LARGE EXECUTABLES ACROSS NETWORK IS SLOW ON DLR. Customer running Btrieve application across the network. Each subsequent DLR to pull up the application takes longer to load. o APAR IC08711 DLR HANGS DURING NAMED PIPE READ WITH IP07045 CODE After installing IP07045 code at the requester, a 3270 program that issues a named pipe read, appears to hang the requester. (NUMLOCK still works.) If program is closed at the server, the requester is released. o APAR IC08791 NET805 FOLLOWED BY DLR HANG WHEN CABLE IS UNPLUGGED If a cable is unplugged from the MAU while a copy command is executed from a local drive to a network drive, a NET805 msg is received, followed by an abort,retry,or fail prompt. If abort is selected,the DLR hangs and needs to be rebooted. If there is no activity on the DLR or if the copy is from a network drive to another network drive,the dlr doesn't hang. o APAR IC08801 RIPL LOGON FAILS WITH MESSAGE ISPFMNT1.PAN COULD NOT BE FOUND. After installing the DLR30.zip fixes on a server, RIPL machines get the message ISPFMNT1.PAN could not be found during the logon process when setting up a user with an expired password. The logon fails, but the user is either put at a Y:\DOSLAN\NET> prompt, or at the Served applications menu, without a userid or domain. o APAR IC09165 DLR INSTALL CREATES A SECOND PATH STATEMENT INSTEAD OF APPENDING TO THE EXISTING PATH Installing DLR 3.0 on a PC formatted with PCDOS 7.0, the PATH= line is not appended with the DOSLAN directory. Instead, a second PATH= statement is added lower in the AUTOEXEC.BAT that overrides the first PATH statement. Thus, the only thing in the final PATH is C:\DOSLAN. o (LS 4.0 APAR IC09256) RESOURCES DISCONNECTED WHEN PASSWORD EXPIRES After a user's password expires at the server during an active session from DLR (user id logged on and using shared resources), the user gets DLS0072 error when accessing a shared drive ("system error reading drive x"). ═══ 8.5. LAPS Enhancements ═══ The following sections explain enhanced LAPS features. Those features that have not appeared in previous ServicePaks are highlighed in blue when this document is displayed. ═══ 8.5.1. THINLAPS - Supports non-LAPS Supplied MAC Drivers ═══ THINLAPS supports the installation and configuration of MAC drivers that do not ship with LAPS. This could include MAC drivers that are shipped by IBM after the release of LAPS or MAC drivers that are supplied by other manufacturers. New MAC drivers shipped by IBM are available on the NTS/2 BonusPak available on many bulletin boards. To use a MAC driver that did not ship with LAPS, do the following on the CID code server: 1. Copy the MAC driver and its associated files (except for the .MSG files) into the \IBMCOM\MACS directory. 2. Copy the .MSG files into the \IBMCOM directory. where is the target directory that was indicated when the LAPSDISK utility was run to copy the LAPS disk to the code server. After the MAC driver files have been copied to the code server, use THINLAPS to configure LAPS on the boot diskettes for use with the adapter that the new MAC driver supports. To do this, run THINLAPS specifying the NIF file associated with the new MAC driver. Following is an example of a PROTOCOL.INI file created with THINLAPS: [protman] driverName = protman$ [netbeui_nif] driverName = netbeui$ bindings = mac ; If running on an ethernet network, remove the semicolon from ; the "ETHERAND_TYPE =" statement to change the protocol ; convention from IEEE 802.3 to DIX 2.0. ; ETHERAND_TYPE = "D" [mac] drivername = ibmtok$ ; EARLYRELEASE ADAPTER = "PRIMARY" ; NETADDRESS = "" MAXTRANSMITS = 6 RECVBUFS = 2 RECVBUFSIZE = 256 XMITBUFS = 1 ; XMITBUFSIZE = ; INTERRUPT = PCMCIA ; RAM = 0x RINGSPEED = 4 ; RAMSIZE = ; MMIO = 0x The following list describes the keyword types in the PROTOCOL.INI example: 1. ADAPTER, MAXTRANSMITS, RECVBUFS, RECVBUFSIZE, XMITBUFS, RINGSPEED o These are keywords with decimal values that have default values associated with them. 2. XMITBUFSIZE, INTERRUPT, RAMSIZE o These are keywords with decimal values that do not have default values associated with them. To activate one of these keywords, remove the semicolon in column one and place a valid value after the equal sign. For example, XMITBUFSIZE = 256. 3. PCMICA o This is a keyword without a value that is defaulted to ON in the .NIF file. 4. EARLYRELEASE o This is a keyword without a value that is defaulted to OFF in the .NIF file. To activate this keyword, remove the semicolon in column one. 5. NETADDRESS o This is a keyword with a string value that does not have a default value associated with it. To activate this keyword, remove the semicolon in column one, and place the desired value within the double quotes. For example, NETADDRESS = "400000274715". 6. RAM, MMIO o These are keywords with hexadecimal values that do not have default values associated with them. To activate one of these keywords, remove the semicolon in column one and place a valid hexadecimal value after the 0x. For example, RAM = 0xA00. Note: Keywords requiring values that do not have default values associated with them and keywords not requiring values that are defaulted to OFF are remarked out with a semicolon in column one in the PROTOCOL.INI file. ═══ 8.5.1.1. User Modification of PROTOCOL.INI: ═══ The PROTOCOL.INI file created by THINLAPS is sufficient for most network environments. However, since the PROTOCOL.INI file may not be appropriate for the network environment, some parameter values in the PROTOCOL.INI file that THINLAPS created may need to be adjusted. Use an ASCII editor to view and change the PROTOCOL.INI file created on the target drive after running THINLAPS. Because THINLAPS supports the configuration of non-IBM supplied MAC device drivers, all keywords with the MAC NIF files are defined in the resulting PROTOCOL.INI file. Following are guidelines for modifying the MAC section in the PROTOCOL.INI file: o To modify the value of a keyword without a semicolon in column one, edit the value in the same format that it appears in the file (decimal, hexadecimal, string, and so on). o To modify the value of a keyword with a semicolon in column one, remove the semicolon from column one, if there is: NO "=" this task is complete. Nothing following the "=" supply a decimal value. For example, 129. A 0x following the "=" supply a hexadecimal value after the 0x. For example, 0xA00. Quotes following the "=" supply an ASCII string inside the quotes. For example, "400000274715". ═══ 8.5.1.2. NOTES: ═══ o All keywords from the NIF file occur in the PROTOCOL.INI file. o Keywords that have defaults are activated and have the default value provided. o Keywords requiring values that do not have default values associated with them are remarked out with a semicolon in column one. o Keywords that do not have values that are defaulted to ON are activated. o Keywords not requring values that are defaulted to OFF in the .NIF file are remarked out with a semicolon in column one. o If there are any questions concerning the keywords or valid values for each of the keywords, use an ASCII editor to view the MAC NIF file, which describes each of the keywords and its valid values. ═══ 8.5.1.3. RESTRICTIONS: ═══ o THINLAPS supports only the configuration of one network adapter. o THINLAPS provides only NetBIOS support. o THINLAPS installs only in the root of the target drive. o THINLAPS works only with valid MAC NIF files. LAPS provides an applet called SNIFFLE that validates .NIF files. View the readme.utl file for more information on the SNIFFLE applet. ═══ 8.5.2. IBMTOK.OS2 MAC device driver upgraded to version 2.6 ═══ The IBMTOK.OS2 MAC device driver has been upgraded to Version 2.6. This new version of the IBMTOK.OS2 MAC driver has added support for both the IBM Auto 16/4 Token-Ring MC Adapter Card and the IBM Auto 16/4 Token-Ring ISA Adapter Card. ═══ 8.5.3. TRACENAMES - New Parameter for NETBIOS Traces ═══ 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 can be specified as either a 16-byte ASCII or 32-byte Hex value. Up to four names can be selected in either format. The asterisk wildcard 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 invalid hex numbers cause an error and NETBEUI will not load. 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 nonzero values to activate any NETBIOS traces. The recommended setting is 0x07FF. NDIS activity will not be filtered if the NDIS bits are activated in OS2TRACEMASK. 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" Activity relevant to the remote NETBIOS is 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 traced by Local Session Number(LSN) after the session is established with the remote machine. A maximum of 12 active sessions is traced. Some NCBs are not associated with a remote name or LSN and are not traced: o Add Name o Add Group Name o Delete Name o Cancel o LAN Status o Session Status o Receive Broadcast Datagram o 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 are traced on completion if they report a session event related to a specified remote machine. ═══ 8.5.4. 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 universally administered address. This requirement is necessary because ODI2NDI must provide the NETADDRESS to the ODI protocol (IPX) before ODI2NDI can obtain the adapter netaddress through the NDIS interface. ODI2NDI.OS2(V1.1) is modified so that it obtains the Network adapter universal address automatically when the NETADDRESS parameter is not configured for ODI2NDI.OS2. To take advantage of this enhancement, the following manual modifications of CONFIG.SYS are required. 1. Configure ODI2NDI for a Network adapter MAC using the LAPS configuration. 2. Manually perform the following updates to CONFIG.SYS: a) Locate the Network adapter 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 b) Position the MAC device driver statement after the PROTMAN.OS2 device driver statement, but before the ODI2NDI.OS2 device driver statement in the CONFIG.SYS file. An example CONFIG.SYS fragment is: : 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 : : c) Save the modified CONFIG.SYS. The computer must be restarted for the change to take effect. The manual updates to the CONFIG.SYS file need to be done only the first time the ODI2NDI protocol is configured for a Network Adapter MAC. Modifying ODI2NDI or MAC parameters does not require additional updates to CONFIG.SYS. Note: This enhancement does NOT work with ALL Network adapters. If the enhancement does not work with the Network adapter on the updated computer, message LT80227 is displayed when the computer is started. This message is also 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. ═══ 8.5.5. LAPS Icon on the Desktop ═══ After NTS/2 LAN Adapter and Protocol Support (LAPS) has been installed and configured on an OS/2 2.x system, a LAPS icon is placed in the System Setup folder. Double clicking on the icon brings up the LAPS installation/configuration utility. ═══ 8.6. LAPS Defects ═══ The following sections describe APAR and Non-APAR defects corrected in this ServicePak. Descriptions are in numerical order by ServicePak. Corrections new for IPx7060 (not fixed in a previous ServicePak) are highlighted on the display. ═══ 8.6.1. NETBIOS Protocol Stack Defects ═══ Files that changed: \IBMCOM\PROTOCOL\NETBEUI.OS2 \IBMCOM\PROTOCOL\NETBEUI.NIF \IBMCOM\PROTOCOL\NETBIOS.OS2 \IBMCOM\LT0.MSG \IBMCOM\LT0H.MSG ═══ 8.6.1.1. APAR fixes ═══ o APAR IC06827 - NETBIOS RETURNS 0x4E FOR RING BEACONING In the event of a beaconing ring for more than 60 seconds, NetBIOS will return a 0x4E return code, clean queues, clean up any shared names, and force a hard reset. Similar events will occur with a cable pull with the exception being a return code of 0x4F instead of 0x4E. o APAR IC07036 - FRAME LENGTH INCORRECT IN A SIDEBAND/ETHERNET ENVIRONMENT Frame length field was incorrect when a small frame was transmitted in an Ethernet environment and netbeui sideband enabled. o APAR IC07038 - NCB.STATUS RETURNED INCORRECT LAN TYPE NCB.STATUS returned LAN type Token Ring even if the LAN connectivity was Ethernet. o APAR IC07151 - NETBEUI ENHANCEMENT FOR SMP ARCHITECTURED SYSTEMS Netbeui module was enhanced to run on SMP architectured systems. o APAR IC07192 - NETBIOS RECEIVE.ANY RETURNS CORRUPTED DATA RECEIVE.ANY NetBIOS command that was aborted because of a hangup, returned an incorrect name ID in the NCB_NUM field. This caused the RECEIVE.ANY to return with an incorrect return code of 0x13. o APAR IC07262 - NETBEUI TRAP ON LAN SERVER ULTIMEDIA SERVER LAN Server Ultimedia using FDDI connectivity removes priority sends from the send queue based on the number of priority sends. With the fcpriority set to 5 on both the server and client workstations, netbeui failed to test for an empty queue condition and a trap D occurred. The fix also checks if the connectivity is FDDI and if so, the bandwidth ack code is disabled but netbeui still sends frames at priority. o APAR IC07768 - NCB.STATUS INDICATES NEGATIVE VALUE FOR NCB COUNTER NCB.STATUS indicated an incorrect value for the current number of free NCBs. o APAR IC07858 - NEW NETBEUI MESSAGE LT00108 CAUSES TRAP IN IBMTOK.OS2 DRIVER New NETBEUI message LT00108 caused a trap to occur in the IBMTOK.OS2 driver. This problem only occurred in LAPS syslevel 2.20.3. o APAR IC07914 - NETBIOS TRAPS ATTEMPTING SHORT TERM MEMORY LOCK NetBIOS passed a bad parameter to the DevHlp short term memory lock if a DevHlp long term memory lock failed. The bad parameter caused the trap to occur. o IC08092 - NEW NetBIOS ERROR MESSAGES Created new NetBIOS error messages. These new messages indicate when a system has run out of UI buffers or datagram buffers (LT00108), a request to use a free NETBEUI GDT selector has failed (LT00105). o IC08278 - DEFAULT NETBEUI CONFIGURATION PARAMETERS CHANGED The following NETBEUI default configuration parameters were changed for performance enhancements: 1. SELECTORS - from 5 to 15 2. T1 - from 500 to 1000 3. NETBIOSRETRIES - from 8 to 2 4. DATAGRAMPACKETS - from 2 to 10 5. LOOPPACKETS - from 1 to 8 6. DLCRETRIES - from 5 to 10 o IC08503 - NETWORK RESOURCE RESERVATION AUTOFAIL FUNCTION IS INCORRECT LAN Server Ultimedia, Network Resource Reservation (NRR) and autofail function did not work correctly. o IC08654 - FILE TRANSFER CAUSES FILE DATA CORRUPTION Transfering of files on a fast processor occassionly caused data corruption in the resulting file. o IC08773 - NAME DEREGISTERED CONDITION AFTER CANCEL ISSUED TO NCB.CALL After a NCB.CALL command was cancelled after the NAMEQUERY was broadcasted. An incorrect NAME_DEGREGISTERED (0x0f) return code was returned as the NCB.CALL was completed. o IC09159 - DATA FROM TIME-OUT SEND STAYS ON SEND QUEUE NCB.SEND times out, but a pointer to the user's data was still remaining on the send queue to be flushed later. This caused the possibility of the user to overwrite that data buffer, and bad data was sent. o IC06115 - Duplicate LAA Causes Errorous Server Name-In-Conflict Two LAN requesters with the same LAA causes a name-in-conflict frame to be sent indicating that the Server's name is in conflict. The name-in-conflict frame caused the Server to remove it's NETBIOS name, shutting down the Server. o IC06224 - NETBEUI Stack Corruption Causes Various Session Control Problems Corrupted NETBEUI stacked caused session abends and Trap E. o IC06398 - Pulled PC-NET Cable Fails To Provide Proper NETBIOS Return Code When executing NETBIOS applications and the PC-NET cable is pulled, all NETBIOS commands appeared to be executing (no return code to indicated a NETBIOS reset was needed). A pull PC-NET cable causes a network status of NO CARRIER and the adapter is NOT closed. NETBIOS now waits 60 seconds before returning a return code to indicate that a NETBIOS reset is needed. o IC06414 - NETBIOS Reset Returns Incorrect Resource Information When a NETBIOS reset is issued to an adapter that is not being used by LAN Server, the reset returns incorrect resource information and completes with a return code 0x09. This problem was introduced in NTS/2 CSD WR07020. o JR07633 - NETBIOS Fails To Detect Bad PC-NET Card During Initial Adapter Open During IPL, NETBIOS failed to execute a check on the hardware status bits during the initial open adapter. If the PC-NET card was open but the hardware status bits indicated a problem, NETBIOS never detected it. o IC04951 - UNC Name failures with IBM Ethernet References to a resource by UNC names failed with error code SYS0240 on the server that was working on the NETBEUI stack with IBM Ethernet. o IC05402 - SOURCE ROUTING FIXES IN NETBEUI Fixes were required for receiving frames on a link that crosses source-routing bridges - the route of the incoming frame should not be assumed to be the same as the route used for outgoing frames. For TEST frames received with 2 bytes of Routing Information, the TEST response was built incorrectly. o IC05486 - TRAP IN NETBEUI ON A VALUEPOINT MACHINE Residual code from an OS/2 EE 1.3 environment remained in NETBEUI. Residual code caused the Trap D. o IC05526 - HPFS386 SIDEBAND TRAP D ON ETHERNET When running HPFS386 on Ethernet and attempting to copy a file from a redirected drive, a Trap D occurred at CS:C08 EIP:8A5. o IC05551 - TRAP D IN NETBEUI - INITDS CORRUPTED Trap D was caused by an invalid selector for low memory data segment. o IC05673 - Four Separate Symptoms o IC05673 - 1) SESSION NOT ESTABLISHED IF SABMES ARRIVE AT WRONG TIME If sessions were being brought up simultaneously on two machines, SABMEs and UAs can conflict causing session establishment to fail. The data area is then corrupted because the link state is wrong. o IC05673 - 2) RECEIVE BROADCAST LOOPING When two or more applications have a receive_broadcast NCB outstanding, issue the next receive_broadcast on appendage. NETBEUI goes into a loop processing the appendage NCB as an additional receive on the receive_broadcast queue. o IC05673 - 3) SESSION_ALIVE SENT WITH INCORRECT LSN NUMBER CAUSES CORRUPTION Session_Alive sent with incorrect LSN number causes corruption of the NTE Listen queue. Links can drop afterward. Fix was to correct sending of Session_Alive frame to have correct LSN number only from links in Normal state. o IC05673 - 4) ADJUST ORDER OF SABME/UA RESPONSES Reordered processing of link establishment and closing prevents case of extra receive ready, or FRMR. o IC05780 - STARTING LS 3.0 WHILE 3270 COMING UP CAUSES COM505 ERROR - If starting LAN Server and Communications Manager 3270 feature at the same time, Communications Manager 3270 will hang with COM505 Error. o IC05794 - NETBIOS RESET RETURNS RC=23 Applications on Token Ring Network can issue "Reset" before NETBIND has completed. When this occurs, NETBIOS returns RC=38 (Requested Resource Not Available) and then RC=23 (Invalid LAN Adapter Number). Serialization of the NETBIND execution process can solve the problem. This fix increases the number of "Reset Retries" which should mask any such race condition. o IC05869 - TRAP E IN NETBEUI Trap E occurs during Remote IPL of OS/2 2.0 or OS/2 2.1. o IC05902 - XMIT_TEST_CMD RESPONSE LOST BY NETBEUI Under certain circumstances Transmit_Test_Cmd is rejected by Netbeui and passed to the next protocol stack. o JR06350 - Redirector failing to Reset NETBEUI was clearing a flag bit whether it actually issued the hard reset or not. Clearing this flag bit when a different flag bit was set prevented NETWKSTA.SYS from issuing the reset. o JR06550 - CLIENT REMOTE BUSY STATE CAUSED SERVER HANG Requester workstations were in a ReMoteBusy state causing the Server to fill up the I-Frame buffer with SessionAlive frames. Eventually this caused the Server to hang if the requester workstations remained in a ReMoteBusy state. ═══ 8.6.1.2. Other fixes ═══ o RING 3 APPLICATION DOESN'T GET IMMEDIATE BAD RETURN CODE Ring 3 applications was not given back an immediate bad returned code. o Access Denied Copying a 583120 Byte File To Server When attempting to copy a 583120 byte file from a requester to a HPFS386 server, an access denied was caused by NETBEUI. o NETBIOS NCB.STATUS Failed To Return Correct Datagram Size The datagram length was calculated incorrectly causing data to be lost. o NAME-IN-CONFLICT Message When a NAME-IN-CONFLICT occurs, a NAME-IN-CONFLICT message LT00102 will be logged to the LANTRAN.LOG file indicated the NETBIOS name-in-conflict and the node address of the workstation sending the NAME-IN-CONFLICT frame. When a NAME-IN-CONFLICT occurs with a LS Server name, the message will also pop-up to the screen. o Prevent NETBIOS Timers From Wrapping NETBIOS timers are now set to maximum value if wrapping occurs. o NETBIOS returns FF Return Code As Final NETBIOS Return Code A NCB.SEND command completed on interrupt before the NCB.SEND was put on a queue with a FF pending code. The final return code was overwritten with FF. Some NETBIOS applications received a NETBIOS return code 13 due to this problem. o Configuration Of Different Netbios Transports Causes Trap D A trap D occurred in NETBIOS.OS2 when two different NETBIOS transports were configured with one of them having insufficient resources configured in protocol.ini for what was requested in ibmlan.ini file. The trap occurred on the first NETBIOS command issued other than a reset. o NETBEUI INITIALIZATION FAILS Some configurations caused NETBEUI to fail to initialize. o INCORRECT PACKET SIZE BROUGHT DOWN LAN SERVER 3.0 An Ethernet-only requester reaching a token-ring Busmaster server through an 8209 bridge eventually caused the server to have multiple sessions and then the server could not communicate with the Ethernet requester or the token-ring requesters. The packet size was being altered by the 8209 bridge. o NETBEUI WAS NOT LOOKING FOR 2 IN MINOR NDIS VERSION IN THE COMMON CHARACTERISTICS TABLE To determine if a MAC driver supports an extension to the MAC Service-Specific Characteristics, NETBEUI should be looking for a 2 in the Minor NDIS Version in the Common Characteristics table. o ILLEGAL FRAME SIZE CAUSED TRAP D When an illegal frame size was checked, it caused a Trap D in NETBEUI. o TRAP D WHILE RUNNING NETSERV.EXE A Trap D occurred in CS:OC78 EIP:EC9 o NETBIOS FAILED TO INITIALIZE ON ANY OS/2 VERSION GREATER THAN 2.0. Install NTS/2 on OS/2 2.1 and configure for NETBIOS. During IPL, NETBIOS failed to initialize. This indicated the wrong version of the operating system. o AFTER RUNNING A LONG PERIOD OF TIME, NETBIOS RETURN ERROR 22 Too many outstanding NCBS (un_freed) cause NETBIOS to return "to Many Commands Pending" (RC=22). This occurs over a varying period of time depending on LAN activity. ═══ 8.6.2. IBM Token Ring MAC Driver Defects ═══ Files that changed: \IBMCOM\MACS\IBMTOK.OS2. ═══ 8.6.2.1. APAR fixes ═══ o IC07131 - XMIT_STATUS Field Incorrect In a SCION TransmitConfirm. The xmit_status field in a SCION TransmitConfirm subsequent to a bridge frame forward indicates the status of the transmitted frame. Incorrect values were being stored in this field. ═══ 8.6.2.2. Other fixes ═══ There are no non-APAR fixes for IBM Token Ring MAC Driver. ═══ 8.6.3. IBM Token Ring Busmaster MAC Driver Defects ═══ Files that changed: \IBMCOM\MACS\IBMTRBM.OS2. ═══ 8.6.3.1. APAR fixes ═══ o JR05729 - BUSMASTER DOES NOT RECOVER FROM LOBE FAULT. LAN Server/Requestor 2.0 could not be restarted on machines equipped with Busmaster cards after the cable was unplugged and replugged. o JR06486 - BUSMASTER TRAP D UNDER HEAVILY STRESSED NETWORK The Busmaster driver was performing a call that was not legal at the time. This caused a Ring 0 Trap D. ═══ 8.6.3.2. Other fixes ═══ o BUSMASTER UNABLE TO RE-ENTER RING AFTER DUPLICATE ADDRESS One machine booted and got a particular token ring address. Another machine (with Busmaster) booted requesting the same address, and got a duplicate address indication, closing the adapter. The first machine left the ring, freeing the address. Any attempt to reopen the previously failed busmaster adapter using Communication Manager failed, still indicating a duplicate address. o WRONG FILTER VALUE USED Prior to deleting an address, the first byte of the address was checked against 80h, which is the equivalent of universal group. It should be checked against C0h, which is local group. This caused what was accepted in the add to be rejected in the delete. Making this change created consistency with the add address. ═══ 8.6.4. IBM Token Ring 16/4 Adapter II (IBM16TR.OS2) ═══ Files that changed: \IBM16TR\IBM16TR.OS2 (Additional Driver Diskette) \IBM16TR\IBM16OS2.NIF (Additional Driver Diskette) ═══ 8.6.4.1. APAR fixes ═══ There are no fixed APARs for IBM Token Ring 16/4 Adapter II ═══ 8.6.4.2. Other fixes ═══ o IBM Token Ring 16/4 Adapter II MAC Driver Upgraded to Version 3.0 The IBM Token Ring 16/4 Adapter II MAC Driver found on the NTS/2 Additional Driver Diskette have been upgraded from Version 1.0 to Version 3.0. ═══ 8.6.5. Configuration Defects (LAPS) ═══ Files that changed: \IBMCOM\DLL\LAPSPM.DLL \IBMCOM\DLL\ LAPSCID.DLL \IBMCOM\DLL\IBMLXCFG.DLL \IBMCOM\IBMLXCFG.HLP \IBMCOM\LAPS.EXE \IBMCOM\XI1.MSG \IBMCOM\LAPSICON.EXE \IBMCOM\LAPSRSP.EXE \IBMCOM\THINLAPS.EXE \IBMCOM\LAPSDISK.EXE ═══ 8.6.5.1. APAR fixes ═══ o APAR IC06825 - KEYPAD DOES NOT FUNCTION CORRECTLY WHEN CONFIGURING LAPS With NUMLOCK ON, the numeric keypad did not function correctly. The 2,3,8 and 9 keys behaved as cursor down, page down, cursor up and page up. o IC05711 - THINLAPS FAILS TO REMOVE PREVIOUS INVOCATION If THINLAPS was executed more than once to a diskette, then multiple LAPS device and run lines were left in CONFIG.SYS file. o IC05794 - RUN STATEMENT CHANGED TO A CALL STATEMENT FOR NETBIND.EXE During IPL the netbind executable in the config.sys binds the configured protocols with the configured adapter cards. On fast processor systems, NetBIOS applications were attempting to issue NetBIOS reset command prior to netbind binding the NetBIOS to the configured adapter cards. This caused NetBIOS to return a return code 0x23 indicating an invalid LAN adapter number. o APAR IC07113 - SYS3175 IN HELP MANAGER WHEN CONFIGURING LAPS A SYS3175 occurred in LAPS after choosing Options-Contents menu item. o IC07132 - Invalid Driver IBMTOK02$ When Configuring for 2 Token-Ring Adapters This problem was introduce in LAPS version 2.20.1. When configuring for two NDIS or NDIS_MULT type drivers, the numeric digit 02 was appended to the driver name in the protocol.ini. During IPL, the second MAC driver failed to bind because the driver name was incorrect. The numeric digit 2 is now appended to the driver name. o IC06187 - Proper Version Of NETBIOS Is Not Copied For CID /E:PREP Install When CID installing LAPS using the /E:PREP option, NETBIOS.LS? was not copied to NETBIOS.OS2 based on the version of LAN Services installed. This problem was introduced with NTS/2 CSD WR07020. o IC06413 - CID Install Of Long File Name Fails CID install using HPFS long file name caused a LAPS return code XI00041. o IC04997 - USING ADAPTER NUMBERS TO GUARANTEE UNIQUENESS FOR LANVMAC LANVMAC requires that its upper boundary be strictly defined; the Media Access Control (MAC) for adapter 0 can only be defined for adapter 0. o IC04999 - LAPS CONFIGURATION NEEDS TO TREAT LANVMAC NETADDRESS LIKE LANDD Function was added that treats the LANVMAC netaddress field the same as the LANDD netaddress field. o IC05159 - MAINTENANCE INSTALL OF LAPS DURING CID FAILS ON OS/2 2.1 When running maintenance LAPS installation using CID on OS/2 2.1, LAPS failed while attempting to update the IBMLVL.INI file. o IC05553 - LAPS INSTALL DID NOT PUT LANVDD AND LANPDD IN THE CONFIG.SYS FILE (LAPSPM.DLL) On OS/2 2.1, the LAPS install did not place statements for LANVDD.OS2 and LANPDD.OS2 in the CONFIG.SYS file. ═══ 8.6.5.2. Other fixes ═══ o LOG FILE NOT PROVIDED FOR CID INSTALL IF TARGET DRIVE DOES NOT EXIST A LAPSHIST.LOG file was not created to indicate that a LAPS install on a non-existent drive partition failed. o DEFAULT HANDLING OF UPGRADE_LEVEL GIVE WRONG CID RETURN CODE LAPS response file upgrade_level parameter was omitted, thus it defaults to old, meaning that reinstallation of LAPS will only occur on systems with the same version of LAPS. On systems with a different version of LAPS, LAPS returned an incorrect return code which indicated a successful LAPS installation even through LAPS was not installed. o LAPS ERROR LOG FILE TRUNCATED WITH EOF MARKERS. The LAPSHIST.LOG file was corrupted occasionally with extra EOF '0A' markers. o UPDATE MESSAGE WHEN INSTALLING LAPS OVER LATER VERSION OF MPTS The message when reinstalling LAPS over a more recent version of MPTS (LS 4.0) was changed to strongly warn the user that if the current install continues, it will disable some of the MPTS functions. o PRESERVE LOCATION OF NETBIOS.OS2 IN CONFIG.SYS FILE NetBIOS device driver statement is now preserved at its current location in the config.sys when reconfiguring LAPS. o LAPS REMOVES DIGIT FROM DRIVERNAME IN PROTOCOL.INI FILE The last digit in a MAC drivername was inadvertently removed, creating an incorrect MAC drivername in the protocol.ini file. o TAB Function Fails With LAPS Configuraton Utility Pressing the TAB key selected the OK pushbutton instead of moving to next configurable parameter within the LAPS configuration utility. o CONFIG.SYS Drive Is Not Correct When Copying NETBIOS.OS2 The wrong CONFIG.SYS drive was used to copy NETBIOS.LS2 or NETBIOS.LS3. This caused NETBIOS.LS3 to always be copied when installed on the non-boot drive. This problem was introduced with NTS/2 CSD WR07020. o LAPS Able To Configure 64 Logical Adapters LAPS configuration utility increased the number of configurable logical adpaters from 16 to 64. o NLS LAPS CID Install Causes Trap D LAPS CID install on various NLS verions caused a Trap D when XI1.MSG message file was used. o ERROR IN NIF VALIDATION WHEN CHECKING DEFAULT AGAINST RANGE (LAPSCID.DLL LAPSPM.DLL IBMLXCFG.DLL) The NIF validation code was incorrectly handling the case in which a default value of type HexString was being checked against the arguments of the Range keyword. The check failed if the default value was enclosed with double quote characters or specified with a "0x" prefix. The problem only occurred in the situation where the parameter was of type HexString, had a default value, had a specified range, and the default value had quotes and/or a prefix. o VDD/PDD CONFIG.SYS PROBLEM Eliminates LANVDD and LANPDD device statements from the CONFIG.SYS file if 802 or NETBIOS are not configured. o FIX REDIRECTOR STATEMENT Fixed redirector statement position in the CONFIG.SYS file. o LAPS CONFIGURATION GENERATES DIFFERENT RESULTS Upon configuring the LANVMACs, LAPS configuration set the drivername on entries 2-n to LANVMA2 and the module names for entries 2-n end in "_nif2". o CREATING RESPONSE FILE FROM LAPSRSP.EXE - IMPROPER TARGET KEYWORD Specifying a target using LAPSRSP.EXE generates a response file containing "target_drive" instead of "target". ═══ 8.6.6. 802.2 Protocol Stack Defects ═══ Files that changed: \IBMCOM\PROTOCOL\LANDD.OS2 \IBMCOM\PROTOCOL\LANDLLDD.OS2 \IBMCOM\DLL\ACSLAN.DLL \IBMCOM\\LANMSGDD.OS2 \IBMCOM\\LT0.MSG \IBMCOM\\LT0H.MSG ═══ 8.6.6.1. APAR fixes ═══ o IC06318 - RIPL SERVICE FAILS TO START When attempting to start the RIPL service in LAN Server, the service was never completed. The problem occurred intermittently and LAN Server net error NET3182 was posted. o IC07486 RING_UTILIZATION FIELD INDICATES 0% UTILIZATION The ring_utilization field in the extended_status_addr section of a DIR.STATUS command indicated ring utilization at 0%. o FFST/2 INSTALLED MESSAGE LT00073 MODIFIED LT00073 message was modified to avoid confusion on whether FFST/2 was properly installed. The message was modified to indicate that FFST/2 was installed, but not started instead of not properly installed. o IC08097 DESTINATION MAC ADDRESS CAUSES LAN DISTANCE MACHINE TO TRAP When using a destination MAC address starting with 4000FFFF, caused a trap when using LAN Distance 1.1. o IC08626 DLC.RESET WITH STATION_ID '0000' FAILS Submitting a CCB DLC.RESET with Station_ID '0000' returned an invalid return code 0x43. o IC07133 - LANDD Loops while MAC Adapters Initialize DMA LANDD was looping while various MAC Adapters were initializing their DMA. This cause the system to appear to be hung for approximately 30 seconds. LANDD thread is now blocked during initializing time. o IC06177 - SNA Gateway Loses Its LU Connections The problem Workstations intermittedly lost their 3270 LU connections to the Gateway machine. The Gateway eventually recovered on its own and the Workstation's LU connections were re-established. The problem occurred because extended registers were not used and caused a memory index problem. o JR07531 - Trap D In LANDD When LAN Station Manager Is Installed A Trap D occurred when LAN Station Manager device driver (LSMMIB2) was loaded. LAN Station Manager declared itself as an NDIS Extension application but did not provide the data structure corresponding to an NDIS Extension. LANDD will now check the length of the data structure to see if it has a NDIS Extension length. o IC04923 - MULTICAST ADDRESS SUPPORT FIX The multicast address support functions in 802.2 fixes to loopback path, error codes, and command codes. o IC05000 - TRAP D IN LANDD CODE RUNNING 75+ WORKSTATION GATEWAY (LANDD.OS2) Each time the links were deactivated, the downstream emulators reactivated the link and the LU-LU sessions were automatically reestablished. A Trap D occurred. o IC05001 - COMMUNICATIONS MANAGER (CM) UNABLE TO STOP NORMALLY OR ABNORMALLY CM was unable to exit because it cannot close the token-ring link to the AS400. The hang was due to the Close.Station being issued on the completion appendage for a Transmit.I.Frame, resulting in a DISC sent to the MAC, the T1 timer started and the Link state set to disconnecting. When the completion appendage returns to NETBEUI, it continues processing the I-frame completion which stops T1. o IC05003 - UNABLE TO REOPEN BUSMASTER ADAPTER AFTER LOBE FAILURE (LANDLLDD.OS2) o IC05360 - TRAP D IN LANDLL; CS=0C38; Attempting to bring up LAN Net Manager (LANDLLDD.OS2) results in TRAP=000D with the CS register at x'0C38' o IC05753 - LANDD INCORRECT FRAME CAUSED TRAP D (LANDD.OS2) The Trap D occurred when remotely configuring a LAN-attached printer. A pop-up said the action was successful, then there was an OK button. If the button was not clicked, after about 20 seconds, a Trap D occurred. ═══ 8.6.6.2. Other fixes ═══ o NDIS 2.0.1 EndReset Supported In LANDD.OS2 LANDD.OS2 was not supporting NDIS 2.0.1 EndReset and was fixed to support the NDIS 2.0.1 EndReset function. o RECEIVE COMMAND WITH RETURN CODE = 20 SHOULD ZERO OUT THE BUFFER POINTER (LANDLLDD.OS2) When the receive command completed with return code = 20 (lost data, no buffers), the buffer pointer should be 0 since there were no partial buffers. o SERVER ACCESS POINT POOL SIZE OF 1000H NOT HANDLED (LANDD.OS2) When the maximum size, 0x1000 was used for pool_length in a DIR.OPEN.DIRECT, a return code of 0x16 was returned. The value should work appropriately. ═══ 8.6.7. 802.2 and NETBIOS Virtual Device Driver Defects. ═══ Files that changed: \IBMCOM\LTSVCFG.COM \IBMCOM\PROTOCOL\LANVDD.OS2 ═══ 8.6.7.1. APAR fixes ═══ o IC06017 - Attachmate Extra For Windows 3270 Causes LANVDD Trap D Stopping a 3270 Attachmate session and starting a new session caused a trap D in the LANVDD.OS2 module. The fix zeroes out various structures on exit. o IC06434 - Attempting To Load PCSUPPORT Router In a VDM Causes Trap D Attempting to load PC-Support (connection for AS/400) in a VDM caused a trap D in the LANVDD.OS2 module. The fix was to restore an index register after returning from a procedure call. o JR06756 - DIR.INTERUPT RETURNS 0 IF ADAPTER NOT OPEN (LANVDD.OS2) Attempting to run an Ethernet packet driver for TCP/IP. It failed when it attempted to initialize, because the executable ran a dir.interrupt command to see if the adapter was open. VDD returned a return code = 0 if the adapter was not open. It should have returned a bad return code. ═══ 8.6.7.2. Other fixes ═══ o THE DOS 8209 BRIDGE UTILITY CAN NOT FIND ADAPTER WITH VDD The DOS version of the 8209 Bridge Utility could not find the adapter when running under the VDD. o LTSVCFG ALWAYS RETURNS NONZERO When LTSVCFG was run, an error code environment variable was always set to nonzero. Even though LTSVCFG executed successfully, a nonzero return code was always returned. o NETBIOS and 802.2 SUPPORTS ONLY 8 DOS SESSIONS DOS Virtual Device Support for Netbios and 802.2 should support 16 sessions, not just eight. ═══ 8.6.8. Protocol Manager Defects ═══ Files that changed: \IBMCOM\PROTMAN.OS2 ═══ 8.6.8.1. APAR fixes ═══ o IC07134 - LANMSGDD.OS2 TRAPS WITH INVALID PROTOCOL.INI FILE A trap in lanmsgdd.os2 device driver occurred during ipl if there was not a square bracket as the first character of the protocol.ini file. ═══ 8.6.8.2. Other fixes ═══ o PROTMAN.OS2 VECTOR SIZE INCREASED Protman.os2's vector size was increased to fix 64 adapter support. o PERFORMANCE AND NDIS SUPPORT IN PROTMAN PROTMAN supports the GET_PPATINFO IOCTL for the NDIS requirements and the GET_MODULE_CHAR_ TABLE IOCTL for the Monitor product. ═══ 8.6.9. IBM Netware Requester Support Defects ═══ Files that changed: IBMCOM\PROTOCOL\ODI2NDI.OS2 IBMCOM\NWFIXUP.EXE IBMCOM\LT8.MSG IBMCOM\LT8H.MSG ═══ 8.6.9.1. APAR fixes ═══ o IC06987 - ODI2NDI COEXISTENCE WITH CM/2 CAUSES 3270 ERRORS When CM/2 coexisted with ODI2NDI.OS2, 3270 sessions were unable to connect to the host and received COM695 errors. The Netware requester, however, functioned properly. If ODINSUP was used, both Netware and the 3270 sessions worked normally. This problem seems to occur mostly on 3COM Ethernet adapters and PCMCIA adapters. o IC07347 - TRAP IN ODI2NDI.OS2 MODULE A trap occurred in ODI2NDI device driver during IPL. o IC07912 - ODI2NDI DEVICE DRIVER DOES NOT RECONNECT AFTER CABLE PULL After pulling the token ring cable on a machine running NetWare requester and ODI2NDI, the sessions did not reconnect. A reboot was required to reconnect. o IC05577 - NWFIXUP Utility Failed To Order Device Driver Statements Properly System configured with ODINSUP. NTS/2 was installed with ODI2NDI device driver and the NWFIXUP utility was executed. During IPL, a LT80221 error occurred. NWFIXUP failed to properly move PROTMAN.OS2 and LANMSGDD.OS2 within the config.sys. o IC06212 - Trap D in ODI2NDI.OS2 Device Driver A Trap D occurred in ODI2NDI.OS2 device driver. This problem was introduced in NTS/2 CSD WR07020. o IC05437 - LOTUS NOTES RUNNING ODI2NDI OVER ETHERNET LOST SESSION While running Lotus Notes over ODI2NDI Ethernet, the session between the server and client was eventually lost. ═══ 8.6.9.2. Other fixes ═══ o ODI2NDI DEVICE DRIVER WRITES UNIVERSAL ADDRESS TO LANTRAN.LOG FILE ODI2NDI writes the universal address of the adapter(s) that it is using to the LANTRAN.LOG file. o IBMCOM PATH ADDED TO ODI2NDI MESSAGE FILE NAME The IBMCOM path has been added to the ODI2NDI message file name to make ODI2NDI easier to use in a RIPL environment. o ODI2NDI FAILS WHEN TCP/IP USES DIRECT STATION OF IEEE 802.2 A NetWare Requester for OS/2 over ODI2NDI stops working when an application using the direct station interface of IEEE 802.2 is started. ═══ 9. Appendix ═══ Appendix of other interesting topics. ═══ 9.1. Printing Information from this On-line Document ═══ The OS/2 view function provides a print capability to the printer defined as the "default" printer for your system. From the "Services" popup, selecting print provides several options; Print All, Marked, or This Section(s), Contents, or Index. All but the Print Marked Sections are fairly self explanatory. To Print "Marked" sections one must first know how to "Mark". It is best to do this with the contents window fully expanded, ie. every section shows up in the content panel. Then simply press the space bar when the section you chose is highlighted or point and click the left mouse button while also holding the ctrl key to "mark" a section for print. The highlighting for "marked sections" is slightly larger than normal highlighting. To notice the difference, select an item in the contents and repeatedly press the space bar. ═══ 9.2. Restarting ServicePak Installation ═══ If the installation procedure stops after selecting the "Continue" button on the Initiating Service Panel and before service is complete, the system may be in an indeterminate state. To complete the service process: o Insert the Bootable Standalone Service Diskette o Restart the system - Ctrl+Alt+Del or Power On. o From the A: Prompt type "FSERVICE" and Enter. ═══ ═══ The item in the title line is a trademark of IBM Corporation ═══ ═══ The item in the title line is a trademark of Microsoft Corporation ═══ ═══ The item in the title line is a trademark of Apple Computer ═══ ═══ The item in the title line is a trademark of Lotus Development Corporation ═══ ═══ The item in the title line is a trademark of Ungermann-Bass, Inc. ═══ ═══ The item in the title line is a trademark of Wall Data Corporation ═══ ═══ The item in the title line is a trademark of Attachmate Corporation ═══ ═══ UPM and UPE files: c:\muglib\mugmsg.msg c:\muglib\logoff.exe c:\muglib\logon.exe c:\muglib\muglexec.exe c:\muglib\mugwepop.exe c:\muglib\mugwlogf.exe c:\muglib\upm.lib c:\muglib\mugaccts.exe c:\muglib\muglrqst.exe c:\muglib\upmaccts.exe c:\muglib\upmcset.exe c:\muglib\dll\netspool.dll c:\muglib\dll\mug.dll c:\muglib\dll\upm.dll c:\muglib\dll\netapi32.dll RIPL files: \ibmlan\rpl\fits\defalt21.fit \ibmlan\rpl\fits\defalt2a.fit \ibmlan\rpl\dosnd3ei.cnf \ibmlan\rpl\dosnd3em.cnf \ibmlan\rpl\dosndet.cnf \ibmlan\rpl\dosndtr.cnf \ibmlan\rpl\os2203ei.cnf \ibmlan\rpl\os2203em.cnf \ibmlan\rpl\os2213ei.cnf \ibmlan\rpl\os2213em.cnf \ibmlan\rpl\os221et.cnf \ibmlan\rpl\os221pc.cnf \ibmlan\rpl\os221tr.cnf \ibmlan\rpl\os22a3ei.cnf \ibmlan\rpl\os22a3em.cnf LAN Server/Requester files: \ibmlan\netprog\net.msg \ibmlan\netprog\stoplan.exe \ibmlan\netprog\cache386.exe \ibmlan\netprog\lsdaemon.exe \ibmlan\install\rib2.exe \ibmlan\netlib\lsworker.dll DLR files: \ibmlan\doslan\dlrinst\cip_main.exe ═══ ═══ Special RIPL Considerations Table of Contents o Special Procedures for OS/2 ServicePaks o OS/2 2.00.1 (OS/2 Preinstall) o Creating New OS/2 2.1 Remote IPL Clients o Creating New OS/2 For Windows Clients o Support For OS/2 2.x 32-bit Display Device Drivers o Updating Master Workplace Shell OS2.INI Files o Supporting Multiple Levels of the OS/2 Operating System o Preserving the Ability to Remote IPL OS/2 1.3 Clients o Special Considerations for Remote IPL of Warp o OS/2 SVGA Support for RIPL Clients ═══ ═══ where WARP* is any one of: o OS/2 WARP for Windows o OS/2 WARP with Windows ═══ ═══ where 2.1* is any one of: o OS/2 2.1 (XRx6000 where x indicates country code.) o OS/2 2.1 Manufacturing Refresh 2.11 o OS/2 2.1 ServicePak XRx6200 ═══ ═══ The OS/2 Selective Install function can be performed by double-clicking on the Selective Install Object in the OS/2 System Setup folder. ═══ ═══ Trademark of IBM Corporation. ═══ ═══ Installing XDF Support on Remote IPL Servers If an OS/2 2.1 or OS/2 2.0 + XR06100 system is used for the code server, modifications must be made to the system in order to read the OS/2 Warp Version 3 XDF format installation diskettes. OS/2 Warp Version 3 systems will read these diskettes without any modification. To modify the OS/2 2.1 or OS/2 2.0 + XR06100 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 OS/2 Warp Version 3 diskette #1 to the \OS2 directory. 3. Add the following line to your CONFIG.SYS file: BASEDEV=XDFLOPPY.FLT o Micro Channel*-bus Systems: 1. Rename IBM2FLPY.ADD to IBM2FLPY.OLD in the \OS2 directory. 2. Copy XDFLOPPY.FLT and IBM2FLPY.ADD from OS/2 Warp Version 3 diskette #1 to the \OS2 directory. 3. Add the following line to your CONFIG.SYS file: BASEDEV=XDFLOPPY.FLT Note: OS/2 1.x and OS/2 2.0 systems below XR06100 cannot be updated to read the OS/2 Warp Version 3 XDF format installation diskettes.