home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 29 Fixes_o
/
29-Fixes_o.zip
/
ls8150b1.dsk
/
IP08150.INF
(
.txt
)
< prev
next >
Wrap
OS/2 Help File
|
1995-09-21
|
98KB
|
2,916 lines
ΓòÉΓòÉΓòÉ 1. Introduction ΓòÉΓòÉΓòÉ
IBM OS/2 LAN Server 4.0 ServicePak IP08150
IBM PTF IP08150
This ServicePak can be applied to:
- IBM OS/2 LAN Server Version 4.0
Fixes for OS/2 LAN Server, OS/2 LAN Requester, UPM, HPFS, RIPL, and Fault
Tolerance are also included in this package.
This package also includes LAN Support Program, version 1.38, and DOS LAN
Services, version 4.00.1, as separately installable packages.
Install and fix information for DLS is available on the 1st DLS diskette.
An additional diskette is enclosed with corrections to appletts that were
available on the LS 4.0 Productivity Aids diskettes. These appletts can be
used to replace the gold versions. Install and fix information is available on
the diskette.
Warning: 1 - After upgrading LS 4.0 with this package, the ENCLOSED LAN
Support Program version 1.38 and DOS LAN Services version 4.00.1 MUST be used
instead of any previous copies of these packages.
Warning: 2 - Before installing this ServicePak, ARCHOFF.EXE (located on the
ServicePak tool diskette) must be executed to rename any ARCHIVE logs that have
been created by previously installed LS 4.0 FixPaks. This ServicePak WILL NOT
install properly if ARCHOFF.EXE is not run prior to starting SERVICE. With the
ServicePak tool diskette in the A drive, type A:ARCHOFF at an OS/2 command
prompt to execute this pre-install program.
Warning: 3 - 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
IPx8150 (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.HFS IBM OS/2 LAN Server - Advanced
Note: IBM LAN Support Program version 1.38 and DOS LAN Services version
4.00.1 are 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 and SYSLEVEL.DLS will indicate a current CSD level of
IPx8150 and a current version of 4.00.1.
ΓòÉΓòÉΓòÉ 1.2. Trademarks ΓòÉΓòÉΓòÉ
The following are trademarks of IBM Corporation:
o AT
o DB/2
o Communication Manager (CM)
o DOS
o DOS LAN Requester (DLR)
o IBM
o LAN Server
o LAN Support Program (LSP)
o LAN Server Utimedia (LSU)
o Micro Channel
o Network Resource Reservation (NRR)
o Operating System/2
o OS/2
o OS/2 REXX
o OS/2 Warp
o OS/2 Warp Connect
o Presentation Manager (PM)
o RIPL
o SPM/2
o UPS
o User Profile Management (UPM)
o Win-OS/2
o WorkFrame/2
o XGA
The following are trademarks of other Corporations:
o ATTISO (AT&T Corporation)
o Lotus 1-2-3 (Lotus Development Corporation)
o Microsoft (Microsoft Corporation)
o Q+E Database Editor (Pioneer)
o Unicenter (Computer Associates International, Inc.)
o Windows (Microsoft Corporation)
o Windows NT (Microsoft Corporation)
o Word for 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. (This includes doing a 'net stop server').
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 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. At an OS/2 command prompt, perform a 'net stop server'.
2. Insert ServicePak Tool diskette in the A drive.
3. At an OS/2 command prompt, type "A:ARCHOFF" to execute this pre-install
program (if you haven't already done so).
4. At an OS/2 command prompt, type "A:SERVICE" and press Enter.
5. Insert ServicePak diskette 1 when prompted.
6. 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.
7. Enter (optional) backup path then choose the OK push button.
8. If the APPLICATION IN USE locked files panel is presented, choose CONTINUE.
9. Follow prompts to complete the process.
10. Remove the diskette from drive A:, then perform the system Shutdown
procedure.
11. 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 MPTS. 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_8150.CID) that
may prove useful in setting up a CID server for this ServicePak.
The sample IP_8150.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\ls40\ip_8150' 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\ls40\ip_8150.'
o The sample RESPONSE.FIL (or equivalent) is placed on the code server in
x:\rsp\csd\ls40\ip_8150.
o The following CID server directory structure contains the contents of the
ServicePak and the tool diskette.
img\csd\ls40\ip_8150 * Root directory of ServicePak diskette 1
img\csd\ls40\ip_8150 * ServicePak Tool diskette files
img\csd\ls40\ip_8150\FIX * No files
img\csd\ls40\ip_8150\FIX\REQ.1 * Requester Fixes
img\csd\ls40\ip_8150\FIX\SRV.2 * Server Fixes
img\csd\ls40\ip_8150\FIX\HFS.3 * HPFS Fixes
img\csd\ls40\ip_8150\FIX\MUG.4 * User Profile Management Fixes
img\csd\ls40\ip_8150\FIX\UPE.5 * Extended UPM Fixes
rsp\csd\ls40\ip_8150 * RESPONSE.FIL (from sample on ServicePak
tool diskette)
o A log directory exists at 'x:\log\csd\ls40\ip_8150' 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 ΓòÉΓòÉΓòÉ
Instructions for creating OS/2 bootable diskettes for Requesters and Entry
Version Servers are dependent on the OS/2 version.
o For OS/2 2.x versions:
1. Make a copy of the OS/2 2.x Installation Diskette and Diskette 1. Call
them SA1 and SA2 respectively.
2. Delete SYSINST2.EXE from Diskette SA2.
3. Delete BUNDLE from Diskette SA2 (this will be on OS/2 versions 2.1 or
greater).
4. Modify CONFIG.SYS on SA2 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 SA2.
o For OS/2 3.x versions:
Use the Install diskette and Diskette 1 of OS/2 3.x. Escape to A:
ΓòÉΓòÉΓòÉ 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 SA1 and SA2 respectively.
2. Delete SYSINST2.EXE from Diskette SA2.
3. Delete BUNDLE from Diskette SA2 (this will be on OS/2 versions 2.1 or
greater).
4. With Boot Diskette SA2 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 SA2.
6. Verify that the 386 HPFS Bootable Standalone Service Diskettes work
properly.
o Shutdown the system.
o Insert the Bootable Standalone Service Diskette SA1 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 4.0 ServicePak to your Bootable Standalone Service Diskette
SA2.
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 SA2.
DEVICE=DISKFT.SYS
3. At an OS/2 command prompt, make the current drive A:, and have the 386 HPFS
Bootable Standalone Service Diskette SA2 in drive A. Type "FTCOPY" to copy
the customized Fault Tolerance configuration information to the 386 HPFS
Bootable Standalone Service Diskette SA2.
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. Review the FSERVICE Response File (RESONSE.FIL on the ServicePak tool
diskette) and modify as needed to reflect the configuration of the system
to be serviced.
2. Boot from the Bootable Standalone Service Diskettes.
3. Establish A: as the Current Directory.
4. Replace the Boot Diskette with the ServicePak Tool Diskette.
5. From the A: prompt, type "ARCHOFF" and press enter to execute a pre-install
program (if you haven't already done so).
6. From the A: prompt, type "FSERVICE" and press Enter. Click here for
additional steps needed for multi-boot systems.
7. At the panel titled "Installing this Service Pak" press Enter (Option 1).
8. Follow the prompts provided by the Corrective Service Facility.
9. 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
ΓòÉΓòÉΓòÉ <hidden> 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.
ΓòÉΓòÉΓòÉ <hidden> 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.
ΓòÉΓòÉΓòÉ <hidden> Creating a 386 HPFS Boot Diskette Refer to ΓòÉΓòÉΓòÉ
Appendix H in:
Operating System/2 Local Area Network Server
Network Administrator Reference Volume 1: Planning and
Installation
Version 4.0
ΓòÉΓòÉΓòÉ <hidden> LAN Server Utilities ΓòÉΓòÉΓòÉ
Refer to Appendix B, Miscellaneous Utilities MAKEDISK in:
Operating System/2 Local Area Network Server
Network Administrator Reference Volume 3: Network Administrator
Tasks
Version 4.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. Follow
the steps below to install the LSP 1.38 image included in this package:
1. Open the IBM LAN Services icon on the desktop and select the OS/2 LAN
Services Installation/Configuration icon.
2. Follow the prompts, selecting the TAILORED method of configuration on the
EASY OR TAILORED 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 Service
OS/2 Remote IPL 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 diskettes included in this package when
requested.
9. At the File Backup panel, press OK, then follow panel instructions to
shutdown and reboot 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 4.0 with this package, the ENCLOSED LAN Support
Program diskettes 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. Install DLS 4.0 Images ΓòÉΓòÉΓòÉ
DOS LAN Services version 4.00.1 is required for Remote IPL Servers. Follow the
steps below to install the DLS 4.0 image included in this package:
1. Open the IBM LAN Services icon on the desktop and select the OS/2 LAN
Services Installation/Configuration icon.
2. Follow the prompts, selecting the TAILORED method of configuration on the
EASY OR TAILORED 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
5. On the COPY PROGRAMS panel, highlight DOS LAN Services, 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, and insert the DOS LAN Services diskettes
included in this package when requested.
9. At the File Backup panel, press OK, then follow panel instructions to
shutdown and reboot the system.
After successful installation of DOS LAN Services provided with this package,
SYSLEVEL.DLS will indicate a current CSD level of IPx8150 (where x indicates
country code) and a current version of 4.00.1.
Warning: After upgrading LS 4.0 with this package, the ENCLOSED DOS LAN
Services diskettes MUST be used instead of any previous copy of DLS.
ΓòÉΓòÉΓòÉ 3.3. 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.1, OS/2 for Windows, or OS/2
Warp 3.0 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.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 3.0 does not have to be installed in the Remote IPL directory
prior to running RPLS8150.CMD.
3. Run RPLS8150.CMD to:
o Update the DEFALT30.FIT file to reflect the server name.
o Update the OS/2 Warp 3.0 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.
4. Start the Server.
5. Logon with Administrator Authority.
6. 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 4.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.
ΓòÉΓòÉΓòÉ 4. Existing Problems ΓòÉΓòÉΓòÉ
This section contains descriptions of existing problems and their workarounds.
ΓòÉΓòÉΓòÉ 4.1. Changing a password from a LS4.0 client to a LS4.0 Server ΓòÉΓòÉΓòÉ
This package contains a modification to the password change function to assist
with interoperability with future IBM LAN products. If this package is applied
to a client, the package must also be applied to any LAN Server 4.0 server that
is the target of a user's password change. It is strongly recommended that
this package be applied to all servers before any clients.
ΓòÉΓòÉΓòÉ 5. Remote IPL Information ΓòÉΓòÉΓòÉ
This section contains additional information for Remote IPL.
ΓòÉΓòÉΓòÉ 5.1. LAN Server Remote IPL Service Upgrade Summary ΓòÉΓòÉΓòÉ
The following changes/additions have been made to Remote IPL Service:
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.1* or OS/2 for Windows,
OS/2 Warp 3.0 with Windows, OS/2
Warp Connect
2.0 + SP 2.1* or OS/2 for Windows,
OS/2 Warp 3.0 with Windows, OS/2
Warp Connect
2.00.1 2.1* or OS/2 for Windows,
OS/2 Warp 3.0 with Windows, OS/2
Warp Connect
2.1* OS/2 Warp 3.0 with Windows, OS/2
Warp Connect
ΓòÉΓòÉΓòÉ 5.2. Valid OS/2 / Remote IPL Configurations ΓòÉΓòÉΓòÉ
The following table identifies valid OS/2 / Remote IPL configurations:
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Γöé Operating System to be Remote IPLed Γöé _
ΓöéServer Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéOperatingΓöé Γöé Γöé Γöé Γöé OS/2 WarpΓöé OS/2 WarpΓöé Γöé
ΓöéSystem Γöé OS/2 ΓöéOS/2 2.0+ Γöé OS/2 ΓöéOS/2 forΓöé 3.0 for Γöé 3.0 with Γöé OS/2 WarpΓöé
Γöé Γöé 2.0 ΓöéService PakΓöé 2.1 ΓöéWindows Γöé Windows Γöé Windows Γöé Connect Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 2.x Γöé Yes Γöé Yes Γöé Yes(1)Γöé Yes(1) Γöé Yes(2) Γöé Yes(2) Γöé Yes(2,3) Γöé
Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé
Γöé 3.0 Γöé Yes Γöé Yes Γöé Yes(1)Γöé Yes(1) Γöé Yes(2) Γöé Yes(2) Γöé Yes(2,3) Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
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. Only one version of OS/2 Warp 3.0 may be installed in the RIPL tree.
The OS/2 Warp version may be one of the following:
o OS/2 Warp 3.0 for Windows
o OS/2 Warp 3.0 with Windows
o OS/2 Warp Connect.
Note: 3. Only the base operating system portion of OS/2 Warp Connect may be
installed for remote IPL. The network portions of the OS/2 Warp Connect product
are not enabled for installation in the remote IPL environment.
ΓòÉΓòÉΓòÉ 5.3. Special RIPL Considerations ΓòÉΓòÉΓòÉ
The following sections describe items that need special consideration when a
Remote IPL is to be performed.
ΓòÉΓòÉΓòÉ 5.3.1. Creating New OS/2 Warp 3.0 Remote IPL Clients ΓòÉΓòÉΓòÉ
IBM LAN Server 4.0 has been updated to support the remote IPL of OS/2 Warp 3.0
clients.
o The DEFALT30.FIT configuration file has been updated.
o Server records for OS/2 Warp have been added into the RPL.MAP file.
o GETRPL has been updated to support OS/2 Warp.
o The RPLSETD.CMD REXX procedure has been updated to support OS/2 Warp.
ΓòÉΓòÉΓòÉ 5.3.2. Creating New OS/2 Warp 3.0 for Windows Remote IPL Clients ΓòÉΓòÉΓòÉ
The Microsoft Windows 3.1 code must be installed into the remote IPL directory
tree prior to using RIPLINST to install OS/2 for Windows or OS/2 Warp 3.0 for
Windows in the RIPL tree. If you will be installing OS/2 Warp 3.0 for Windows,
then the Windows 3.1 code must be installed into the directory
\IBMLAN\RPL\OS2.30\WINDOWS. 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 d:\IBMLAN\RPL\OS2.30\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.30\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 d:\WINDOWS d:\IBMLAN\RPL\OS2.30\WINDOWS /S /E
ΓòÉΓòÉΓòÉ 5.3.3. Supporting Multiple Levels of the OS/2 Operating System ΓòÉΓòÉΓòÉ
It is possible to install and support multiple levels of the OS/2 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 or 3.0 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, OS221*.CNF or OS230*.CNF. A semicolon (;) in column 1
indicates the record is disabled. GETRPL will enable/disable the
appropriate records based upon what OS/2 version(s) you installed.
ΓòÉΓòÉΓòÉ 5.3.4. Special Considerations for Remote IPL of OS/2 Warp 3.0 ΓòÉΓòÉΓòÉ
The following sections provide information needed to Remote IPL on an OS/2 Warp
system.
ΓòÉΓòÉΓòÉ 5.3.4.1. XDF Diskette Support Requirement ΓòÉΓòÉΓòÉ
The OS/2 Warp 3.0 installation diskettes are delivered in XDF diskette format.
Remote IPL servers running OS/2 2.1 or older must be upgraded to support the
XDF diskette format before the OS/2 Warp 3.0 remote IPL 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 2.0 systems below ServicePak XRx6100 cannot be upgraded to
support the XDF diskette format. Remote IPL support for OS/2 Warp 3.0 can not
be installed on such systems.
ΓòÉΓòÉΓòÉ 5.3.4.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 3.0 XDF
format installation diskettes. OS/2 Warp 3.0 servers will be able to 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 3.0 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 3.0 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 3.0 diskette 1 to the
\OS2 directory.
3. Add the following line to your CONFIG.SYS file:
BASEDEV=XDFLOPPY.FLT
Note: OS/2 2.0 server systems below XR06100 cannot be updated to read the
OS/2 Warp 3.0 XDF format installation diskettes.
ΓòÉΓòÉΓòÉ 5.3.4.3. Migrating Existing RIPL Clients To OS/2 Warp 3.0 for Windows ΓòÉΓòÉΓòÉ
Existing RIPL clients that are defined as OS/2 2.x type RIPL clients can not be
migrated to OS/2 Warp 3.0 for Windows. Such clients must be deleted and
recreated to switch to OS/2 Warp 3.0 for Windows.
ΓòÉΓòÉΓòÉ 5.3.4.4. Migrating Existing RIPL Clients To OS/2 Warp 3.0 with Windows (FullPak) ΓòÉΓòÉΓòÉ
Existing RIPL clients that are defined as OS/2 2.x type RIPL clients can be
migrated to OS/2 Warp 3.0 with Windows clients using the RPLSETD.CMD REXX
procedure.
To migrate to OS/2 Warp 3.0 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 3.0 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 3.0 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.3.4.5. Creating New OS/2 Warp Remote IPL Clients ΓòÉΓòÉΓòÉ
IBM LAN Server 4.0 has been updated to support the remote IPL of OS/2 Warp RIPL
clients.
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.3.4.6. Special Considerations for Migrating Customized Desktops ΓòÉΓòÉΓòÉ
When a RIPL client is migrated to OS/2 Warp 3.0 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 files to remove the LAUNCHPAD
option from the SET AUTOSTART line.
ΓòÉΓòÉΓòÉ 5.3.4.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.3.5. 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 542x
The SVGA support has the following prerequisites:
1. OS/2 REXX support.
2. OS/2 2.11 Manufacturing Refresh, the OS/2 2.11 ServicePak.
3. RIPL clients must be using one of the video chip sets listed above.
4. IBM PS/ValuePoint machines used as RIPL client must be at BIOS level
L6ET53A or later.
ΓòÉΓòÉΓòÉ 5.3.5.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.3.5.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.3.5.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.3.5.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.3.5.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.4. 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.4.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.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 3.0 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.4.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 3.0 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 3.0 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.4.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 3.0 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 3.0 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.4.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 3.0 with Windows(FullPak), OS/2 Warp Connect(FullPak) Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 2.00.1 Γöé 2.0+ServicePak 1/2, 2.1, 2.1+ServicePak, 2.11, Γöé
Γöé Γöé Warp 3.0 with Windows(FullPak), OS/2 Warp Connect(FullPak) Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 2.0+ServicePak 1/2 Γöé 2.1, 2.1+ServicePak, 2.11, Γöé
Γöé Γöé Warp 3.0 with Windows(FullPak), OS/2 Warp Connect(FullPak) Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 2.1 or 2.11 Γöé Warp 3.0 with Windows(FullPak), OS/2 Warp Connect(FullPak) Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NOTE: There is no support for converting a remote IPL client from a newer Γöé
Γöé version of OS/2 to an older version. After a client is converted to a newer Γöé
Γöé version, RPLSETD cannot be used to convert back to the original, older version. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
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.4.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 3.0)
S3SVGA SVGA display driver for S3 chip sets
(OS/2 2.11 and OS/2 Warp 3.0)
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.4.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.4.3. GETRPL.EXE Utility ΓòÉΓòÉΓòÉ
Refer to the IBM OS/2 LAN Server Version 4.0 Network Administrator Reference
Volume 3: Network 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.4.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.
ΓòÉΓòÉΓòÉ 6. Things that Changed ΓòÉΓòÉΓòÉ
The following sections describe changes that have been made to the product's
executables, and messages/helps.
ΓòÉΓòÉΓòÉ 6.1. 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.
ΓòÉΓòÉΓòÉ 6.1.1. New feature summary ΓòÉΓòÉΓòÉ
This section describes features that are included in this ServicePak.
ΓòÉΓòÉΓòÉ 6.1.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 the ServicePak APPLETT diskette in
SMBTOOL.ZIP. To unpack the trace tool into the desired directory,
insert the ServicePak APPLETT diskette into drive A: and issue the
following command:
PKUNZIP2 A:\SMBTOOL.ZIP <path>\
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.
ΓòÉΓòÉΓòÉ 6.1.1.2. IBM DOS Version 7 Support ΓòÉΓòÉΓòÉ
A REXX procedure is now available to upgrade the DOS Remote IPL Service to use
IBM PC DOS Version 7. This procedure, RPLDOS7.CMD, is available on the
ServicePak APPLETT diskette.
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
ΓòÉΓòÉΓòÉ 6.1.2. Additional Information ΓòÉΓòÉΓòÉ
This section contains additional changes to LAN Server 4.0 that are included in
this ServicePak.
o Changing a password from a LS4.0 client to a LS4.0 Server
Modifications were made to the password change function to assist with
interoperability with future IBM LAN products. If this package is
applied to a client, the package must also be applied to any LAN Server
4.0 server that is the target of a user's password change. It is
strongly recommended that this package be applied to all servers before
any clients.
ΓòÉΓòÉΓòÉ 6.2. OS/2 LAN Server and LAN Requester ServicePak APARs ΓòÉΓòÉΓòÉ
This section describes APARs that have been corrected in this ServicePak.
ΓòÉΓòÉΓòÉ 6.2.1. IPx8150 APARs ΓòÉΓòÉΓòÉ
The following section describes APARs that are corrected with the IPx8150
ServicePak. APARs are described in numerical order by functional area.
ΓòÉΓòÉΓòÉ 6.2.1.1. LAN Server ΓòÉΓòÉΓòÉ
This section describes LAN Server APARS corrected for IPx8150.
o APAR= IC08510 GRADUAL LOGON FAILURES ON LS 4.0.
After some period of time, logons are unsuccessful. Another symptom is
that NET USE from requesters fail because response is slow.
o APAR= IC08556 LAN TUNING ASSISTANT CANNOT OPEN ON HIGH-RESOLUTION
DISPLAY
When a high-resolution display adapter is used, the LS 4.0 Tuning
Assistant object will not open.
o APAR= IC08989 CACHE386 /O CANNOT DUMP A CACHE SIZE GREATER THAN 64MB
For CACHE386, the /O switch to display options, such as cache size,
cannot display a cache size greater than 64MB.
o APAR= IC09015 NET START SERVER FAILS WITH NET3062 AND NET4968 INDICATING
ACCOUNT EXPIRED
NET START SERVER fails with a NET3062 and error log contains a "NET4968:
Limit exceeded. Account expired."
o APAR= IC09023 LS 4.0 WITH DLR 3.0 PUBLIC APPS PROBLEM
When running LAN Server 4.0 (with CSD level IPx8000) on the server and
DOS LAN Requester 3.0 (with CSD level IPx7045) on the requester, and an
application is assigned for use as public application to one normal user
and one administrator:
- If the administrator starts DLR, the application can be started
normally.
- If the user starts the DLR the following message appears (after a
long time): CE524 - A required system file is is already being used
by another user. Try again later. Using the DLR 4.0, there are no
problems starting the application.
o APAR= IC09025 LAN SERVER 4.0 UPGRADE VERSION UPS.EXE AND UPSDRV.OS2 WILL
NOT ALLOW UPS SERVICE TO START AFTER UPGRADE WAS COMPLETE.
After an upgrade from LS 3.0 to LS 4.0, the UPS service would not start
using the upgraded package. The following error message is returned:
NET3230: A power failure has been detected.
o APAR= IC09241 NET5303 D7 03 WHEN DOING NET START SERVER IF SIDEBAND = 0
IS IN THE PROTOCOL.INI FILE.
This problem can occur when turning sideband off in the PROTOCOL.INI
file, and then doing a NET START server. The server starts but a
NET5303 error with a D7 (sideband listen) 03 (invalid command) is
posted.
o APAR= IC09252 SERVER SERVICE FAILS TO START (CONTINUOUS DOTS) WHEN
NUMREQBUF IS SET BETWEEN 522 AND 529 INCLUSIVE.
When the NUMREQBUF parameter in the IBMLAN.INI is changed to 522 to 529,
inclusive, the Server service does not start. The dots just keep rolling
out. On a Warp machine, a SYS3175 is generated. The system does not
lock, but the only way to start the server is to change NUMREQBUF
parameter and boot.
o APAR= IC09254 NUMBER OF FILES AND DIRECTORIES THAT CAN BE REPLICATED IS
TOO SMALL.
When replication or DCDB replication are used, the number of files and
directories supported is inadequate.
o APAR= IC09370 RESOURCES SET TO 'SHARED AT STARTUP' ARE NOT BEING SHARED.
Environment: OS/2 2.11, LS 4.0
After shutdown and restarting server, network shared resources are not
being shared at startup, though that is how they are set when defined.
Missing resources are physically located on the Backup Domain
Controller. Resource definitions are intact, just not being shared at
startup. NET ERROR yields NET8181 for the resources that failed. "The
logon assignment of files alias *** to *** failed.
o APAR= IC09440 ALIAS ON AN ADDITIONAL SERVER IS SET TO SHARE AT SERVER
STARTUP, BUT DOESN'T SHARE IF BACKUP DC IS UP AND PRIMARY DC IS DOWN.
Primary domain controller, Backup domain controller and Additional
server all go down, and the Backup domain controller and Additional
server come up. Any aliases that are on the Additional server that are
set to share at server startup, do not share. The DCDBREPL server runs
fine prior to the servers going down, and shares on the Backup domain
controller are fine. But if you do a NET SHARE at the Additional
server, none of the aliases physically on the Additional server are
shared. You have to do a NET SHARE NETNAME=RESOURCE manually.
o APAR= IC09452 RUNNING FTREMOTE A SECOND TIME REMOVES CRITICAL ERRORS
FROM FTSTATUS.LOG
The FTSTATUS.LOG is overwritten each time FTREMOTE is run.
o APAR= IC09455 UPSDRV.OS2 CONFLICTS WITH SDLCDD.SYS
If UPSDRV.OS2 is installed in CONFIG.SYS after Communication Manager
SDLCDD.SYS, a SYS1201 error is displayed when LAN Server 4.0 is started.
o APAR= IC09460 LS40TUNE DOES NOT TAKE NETBIOS WORK AREA 64K LIMITATION
INTO ACCOUNT IN ITS CALCULATIONS
When tuning for NetBIOS, LS40TUNE.EXE does not taken into account the
NetBIOS 64K work area limitation and can generate parameter values that
may exceed the 64K limit. This can cause work-area-exceeded errors to
occur when NetBIOS is loaded.
o APAR= IC09462 WHEN CALCULATE KEY IS PRESSED, LS40TUNE SOMETIMES EXITS
If an end-of-file marker does not exist in CONFIG.SYS, IBMLAN.INI, or
HPFS386.INI, the LS 4.0 Tune program exits abnormally.
o APAR= IC10152 ALIAS NOT SHARED AT STARTUP WHEN MANY ARE DEFINED
On a 16-megabyte domain controller with LAN Server 4.0 installed and
MAXSHARES=1000, only 600 alias can be defined shared at startup.
o APAR= IC10270 UPS SERVICE SHUTDOWN STARTS UNDER INCORRECT CONDITIONS.
ERRONEOUS MESSAGE FROM INTERNAL UPS SERVICE.
On an uninterruptible power supply (UPS) connected to a PS/2 Mod 95
running OS/2 2.11 (latest level CSDs installed) and LS 4.0, the internal
UPS service displays a "low battery" message and initiates system
shutdown if the serial cable between the PC and UPS is disconnected and
again after the cable is reconnected and the system is restarted.
o APAR= IC10322 SECOND DLS CLIENT CANNOT OPEN DATABASE.
Some database applications cannot be accessed by more than one DLS
client.
o APAR= IC10740 LIST.A IS NOT UPDATED WHEN DOS PUBLIC APP IS CREATED ON A
3.0 REQUESTER WITH A 4.0 DC.
When a LAN Server 4.0 domain is being administered from a LS 3.01
requester and a public DOS application is created, the application is
not available from the DLR because LIST.A is not updated.
o APAR= IC10741 TUNING ASSISTANT GENERATES INCORRECT SESSION PARAMETERS.
After the Tuning Assistant is used, the system can fail to restart
because two of the updated configuration files use the same session
number.
o APAR= IC10781 LS 4.0 TUNING UTILITY ONLY DISPLAYS THE FIRST TWO DIGITS
OF SERVER MEMORY IF SERVER HAS MORE THAN 99 MEG OF RAM.
On the first page of the LS 4.0 tuning notebook in the Server Hardware
section Memory in server is displayed. If a server has more than 99
megabytes of RAM, the field only displays the first two characters.
(example: 120 megs is displayed as 12). This does not affect the tuning
parameters, just the GUI display.
o APAR= IC10803 TUNING ASSISTANT HIGHLIGHTS ALL LINES IN UPDATED FILE
FOLLOWING FIRST CHANGED LINE AFTER ADDING A SECOND NETWORK CARD.
LAN Server 4.0 Tuning Assistant provides an 'Updated' file, which should
show the changed lines as highlighted ones. After adding and configuring
a second network card for the server, when Tuning Assistant is run the
first time, too many lines are highlighted in the changed file.
o APAR= IC10938 LOGONS FAIL AFTER ADDING USERS TO DOMAIN DUE TO SLOWDOWN
OF NETWORK AND INCREASED ACTIVITY ON ADDITIONAL SERVERS.
When 2 users are added to the domain, the network slows up to the point
of not accepting logons or logons are very slow (3 to 10 minutes). Many
additional servers are reestablishing sessions with the domain
controller and then requesting a full update of the NET.ACC data when
they should be requesting only partial updates.
o APAR= IC10972 NETLOGON RANDOMIZE IS NOT SO RANDOM AFTER ALL.
The randomize function performed by an additional server using the
RANDOMIZE= parameter from the domain controller might not work
correctly. Sometimes, the additional servers pick the RANDOMIZE= value
as the time to wait before requesting a delta or full synchronization of
NET.ACC from the domain controller. This causes all the additional
servers to deluge the domain controller with synchronization requests at
the same time rather than spreading them out.
o APAR= IC10973 SYS3175 IN NETAPI.DLL AT CS:EIP= A2CF:000011FF AND CSLIM=
000017E5 ON ALL ADDITIONAL SERVERS IN DOMAIN.
Customer reported that all of the additional servers in a domain failed
with a SYS3175 in NETAPI.DLL.
ΓòÉΓòÉΓòÉ 6.2.1.2. LAN Requester ΓòÉΓòÉΓòÉ
This section describes LAN Requester APARs that are corrected for IPx8150.
o APAR= IC08582 TRAP IN NETBIOS.OS2 WHEN USING AT&T ATTISO APPLICATION
Running an application that calls the AT&T ATTISO protocol results in a
trap error in NETBIOS.OS2.
o APAR= IC08660 PROBLEM ASSIGNING HOMEDIRS WHEN NO USER ALREADY ALLOCATED
An attempt to assign a home directory on an additional server results in
the following error message: "NET2221 - The userid cannot be found."
o APAR= IC08730 CREATE ANOTHER IS REMOVED FROM ICONS ON DESKTOP AFTER LS
4.0 INSTALLATION
After installing LAN Requester 4.0, the Create Another option in the
objects on the Desktop is removed.
o APAR= IC08862 SERVER 'VIEW STATISTICS' DISPLAY SHOWS WRONG TIME
In the Server Statistics window, accessible through LAN Server
Administration Defined Servers folder, the End Gathering Time displayed
is one hour different than the system clock time.
o APAR= IC08911 LS 4.0 GUI FAILS TO CREATE USER TEMPLATE
In Warp with LS 4.0 environment, the Template-box in the notebook, which
creates a user template from a user icon, does not remain checked when
system is shut down and restarted. The user template reverts to a
normal icon again.
o APAR= IC08932, IC08958 LIST.X FILES NOT UPDATED WHEN LS 3.0 DOMAINS ARE
ADMINISTERED FROM LS 4.0 OS/2 SERVERS AND REQUESTERS
When LS 3.0 domains are administered from LS 4.0 servers and requesters,
the user's LIST.X files are not updated.
ADDITIONAL NOTE:
After you apply the fix, to update the user's LIST.X files (mainly the
LIST.U) you need to open the user's icon and look at the logon
assignments. When you view the logon assignments they should look
correct, but the LIST.X file will not be properly updated unless you
highlight one of the assignments and then press the SET button at the
bottom of the window. This action should update the LIST.X files.
o APAR= IC08935 ACP creation conflict between resource drive and
redirected drive.
Client accessing LS3.0 domain, unable to use LS4.0 LAN Server
Administration to create an ACP for a resource residing on physical
drive with same letter as requester redirected drive.
o APAR= IC08992 TEMPLATE BOX IS NOT PRESENT ON SYS ICONS, GO TO
SETTINGS/GENERAL
For various system icons (for example, the OS/2 System icon), in the
Settings notebook, General page, the Templates box does not appear. This
happens on both OS/2 2.11 and Warp systems when LS 4.0 is installed.
o APAR= IC09016 NET START PEER FAILS WITH NET3062, AND ERROR LOG CONTAINS
A NET4698
NET START PEER fails with a NET3062 with a NET4968 error in the error
log.
o APAR= IC09033 TRYING TO CONNECT TO A NETWORK PRINTER THROUGH THE GUI
GIVES "PARAMETER NOT VALID" MESSAGE.
In an OS/2 2.11, LS 4.0 environment, a shared printer cannot be accessed
using the instructions of LS 4.0 "Up and Running," chapter 11. The
error message "Parameter not valid" is displayed.
An alternate procedure described in "IBM OS/2 LAN Server 4.0 Features"
(GG24-4428-00) at page 94 "Overcoming the Single Session Limitation"
does not work either.
o APAR= IC09042 WHEN USERID TEMPLATE IS USED TO CREATE A CUSTOM TEMPLATE
AND THEN THE NEW TEMPLATE IS USED TO CREATE A USER ICON, THE USER ICON
ACTS AS A TEMPLATE.
When you create a custom user ID template from the main user ID
template, then create a user ID from that template, the user ID icon
appears as a template icon (with yellow note pad on lower right corner).
o APAR= IC09050 SORT FUNCTION FOR ADD USER LIST NOT THERE
In the Add Users to a Group panel (reached from a Group Settings
notebook, Users page, Add button), you cannot sort the list of users.
o APAR= IC09055 NETBIOS32SUBMIT HANGS
The netbios32submit API hangs when executed within a program.
o APAR= IC09108 LIST.S GOES TO 0 BYTES WHEN ADDING RESOURCES TO USER
DEFINITIONS FOR DLR 3.0 REQUESTER FROM A DLS 4.0 REQUESTER ON LS 3.0
DOMAIN
On an LS 3.0 domain, when resources are added to user definitions for a
DLR 3.0 requester from a DLS 4.0 requester, LIST.S drops to 0 bytes.
o APAR= IC09117 FROM USER ACCOUNTS OF LAN SERVER ADMIN GUI, YOU CANNOT
TELL WHAT PERMISSIONS A USER HAS FOR ANY ALIAS ON THE LIST OF ALIASES.
From the LAN Server Administration GUI, User Accounts folder, you cannot
view permissions for a user's assignments.
o APAR= IC09151 LS 4.0 GUI WILL NOT ALLOW AN ALIAS CREATED ON A LS 3.0
DOMAIN CONTROLLER TO BE DELETED AND RECREATED
The LAN Server 4.0 GUI does not allow an alias to be deleted and
recreated when that alias was originally created on a LAN Server 3.0
domain controller.
o APAR= IC09204 UNABLE TO MOVE PRINTER ALIAS WITH LAN SERVER 4.0 SETTING
NOTEBOOK
The Printer Alias Settings notebook allows you to specify a change in
the location of a defined printer alias; however, when the Set button is
selected, the change is not applied.
o APAR= IC09211 TRAP000D WITH CS:EIP= 0148:0000272F AND CSLIM= 00008992 IN
OS2 KERNEL HEAP BECAUSE OF NETWKSTA.200 PASSING BAD SELECTOR.
When the ring 3 server tries to dynamically allocate an additional large
buffer, a trap error occurs.
o APAR= IC09212 DRAG AND DROP TO CREATE A NEW USER WITH HOME DIRECTORY
GIVES NET2351, NET3106 91 18, NET3106 92 08, INVALID MACHINE ID, ETC.
When signed on as an administrator to a LAN Server 4.0 workstation, you
cannot drag and drop a user template to create a home directory on a LAN
Server 3.0 Post7045 additional server. Errors include NET2351, NET3106
91 18, NET3106 92 08, NET3191, Invalid Machine ID, and Access Denied.
o APAR= IC09216 UNABLE TO USE * DRIVE ASSIGNMENT FOR ADDITIONAL RESOURCE
OF PUBLIC APPLICATIONS
In the LAN Server 4.0, LAN Server Administration GUI, you cannot define
a drive as next available (*) for any additional resources for an OS/2
public application.
o APAR= IC09231 LR 4.0 LOGGING ONTO A LS 3.0 DOMAIN: ALL PUBLIC APPS SHOW
UP AS OS/2 WINDOWED APPS EVEN THOUGH THEY ARE DEFINED OTHERWISE.
In a LAN Server 3.0 domain, all public applications appear to be OS/2
window applications, even though some or all of the applications have
been defined as OS/2 Presentation Manager or PROTMODE (protect-mode)
applications.
o APAR= IC09232 LR 4.0 LOGGING ON TO A LS 3.0 DOMAIN: APPS THAT ARE
DEFINED TO PROMPT USER FOR ADDITIONAL PARAMETERS DO NOT.
When a LS 3.0 domain is accessed from a LS 4.0 requester, programs
started from the Network Applications folder do not prompt the user for
additional parameters when they are supposed to do so.
o APAR= IC09233 STARTING THE NETWORK MESSAGING WITHOUT THE /MIN PARAMETER
CAUSES IT TO COME UP BLANK. NO COLUMNS FOR FROM, DATE, ETC.
In LS 4.0, starting Network Messaging without specifying the /MIN
parameter causes the Network Messaging panel to appear blank, that is,
without its columns for From, Date, Time, and so on. Network Messaging
has the /MIN parameter in the Startup folder, but might not have it in
the IBM LAN Services folder.
o APAR= IC09240 LR 4.0 LOGGING ON TO LS 3.0 DOMAIN: DOS PUBLIC APPS SHOW
UP IN THE NETWORK APPLICATIONS WITH THE OS/2 PUBLIC APPS.
When a LS 3.0 domain is accessed from a LS 4.0 requester, and a user is
assigned both DOS and OS/2 public applications, the Network Applications
folder might return a SYS0039 error about the drive not being ready. On
subsequent opens of the Network Applications folder, it incorrectly
displays the DOS public applications icons as blank icons. Clicking on
a blank icon produces a prompt for a path.
o APAR= IC09254 NUMBER OF FILES AND DIRECTORIES THAT CAN BE REPLICATED IS
TOO SMALL.
When replication or DCDB replication is used, the number of files and
directories supported is inadequate.
o APAR= IC09306 SYS3170 RETURNED WHEN SAVING WORD FOR WINDOWS 6.0A
DOCUMENT TO A:\ DRIVE.
After creating a document in Word for Windows 6.0a, an attempt to save
the file to drive A: returns a SYS3170 error message.
o APAR= IC09322 CHANGE TO PUBLIC APPLICATION INVOCATION COMMAND NOT
REFLECTED
A change in the name of a DOS application through LS 4.0 GUI (that is, a
change in the name of the .exe), is not updated in the \DCDB\APPS
directory. Consequently, DOS LAN Requesters cannot execute the program
from their selector menu.
o APAR= IC09335 PRINTING FROM Q+E ON LAN SERVER NETWORK PRINTER RESULTS IN
SYS3175 IN LSWORKER.DLL
In a LS 4.0 environment, an attempt to print from Q+E on a network
printer causes a SYS3175 error.
o APAR= IC09341 CANNOT DELETE THE MESSAGE.LOG FILE WITH LS 4.0
The procedure for deleting the MESSAGE.LOG file on p. 223 of LS 4.0
Commands and Utilities reference does not work. The following error
message is returned:
MSG: SYS0032: The process cannot access the file because it is
being used by another process.
o APAR= IC09363 SYS2070 IS RETURNED WHEN LS 4.0 PUBLIC APPLICATION IS
USING A .CMD FILE THAT CONTAINS THE START COMMAND.
On a LAN Server 4.0 requester, using the START command in a .CMD file
causes error SYS2070: A program in this session encountered a problem
and cannot continue, when the command file is invoked.
o APAR= IC09372 LS 4.0 PUBLIC APPLICATIONS. PROGRAM LOCATION-ASSIGNED
DRIVE NOT WORKING CORRECTLY
In LAN Server 4.0 Advanced, Public Application's Settings notebook,
Program Location page, setting the Assigned Drive field to Next
Availiable does not cause a drive letter to be assigned by LS 4.0. This
same problem occurs for a public application when the Assigned Drive
field is set to Specified Drive on an LS 4.0 server, but accessed from a
LS 3.0 requester.
o APAR= IC09449 NETAPPADD API FAILS WHEN DRIVE LETTER IS "|".
The NetAppAdd API fails when a drive letter value of | is specified.
o APAR= IC09466 LR 4.0 LOGS ON TO A LS 3.0 DOMAIN WITH PUBLIC APPS DEFINED
AND DOES NOT GET ANY OF THE ASSIGNED PUBLIC APPS.
When you access a LS 3.0 domain from a LS 4.0 requester, your Network
Applications folder does not contain any of the public applications
assigned to your user ID.
o APAR= IC09524 UPMEULGF CALL RETURNS 0XFB13 NOT 0XFB14 IN LS 4.0
UPMEULGF returns 0XFB13 instead of 0XFB14 in LS 4.0.
o APAR= IC09526 AFTER MIGRATION FROM LS 3.0 TO LS 4.0, EXTERNAL RESOURCES
ARE NOT "LOGON ASSIGNABLE"
After migration from LS 3.0 to LS 4.0 with external resources, these
resources exist in resource definition view, but when an attempt is made
to assign logon assignments, these resources do not appear in the list
of resources.
o APAR= IC09527 AFTER CHANGING ALIAS NAMES (FILE,PRINT,SERIAL) IN GUI,
SHUTDOWN, AND REOPEN, THE NAMES DID NOT CHANGE
From the Alias Settings notebook, General page, changes made to the
original alias name cannot be saved by selecting the Set or Apply
button, nor by closing the settings notebook.
o APAR= IC09605 AFTER APPLYING DLS40.ZIP FOR IC08691 FIX TO DLS 4.0
REQUESTER, IT WILL HANG
After installation of the DLS40.ZIP fix pak for IC08691, the workstation
hangs in Windows or DOS and requires restarting the PC.
o APAR= IC09736 ALIAS SETTINGS PARAMETER MAXIMUM CONNECTIONS DOES NOT WORK
More than one user can log on and access public application when the
Maximum Concurrent Connections parameter is set to 1.
o APAR= IC09763 WHEN HE ISSUES AT 12:00 /E:SU DIR, HE GETS NET3505. IT
OCCURS ONLY HE DEFINES SU.
On a Japanese LAN Server, a NET3505 message, invalid parameter, is
received when the AT command is issued with the /E:SU (SUNDAY)
parameter.
o APAR= IC09770 MESSAGE POPUP SCREEN DOES NOT OCCUR AT LOGON WHEN A
PROFILE.CMD FILE IS USED WITH A REXX COMMAND.
When a PROFILE.CMD file is used in a REXX command for sending a message,
logon through User Profile Management (UPM) does not result in a message
pop-up, even though the message is being sent to the message log. Logon
through the command line works correctly.
o APAR= IC09864 SYNTAX CHANGED FOR RESTORING CONNECTION TO A HOME
DIRECTORY
In LS 4.0, when a connection to a home directory was lost, an error
prevented the use of NET USE x: aliasname to reconnect to the home
directory. This has been corrected and the old syntax now works
correctly.
o APAR= IC10102 LOGON ASSIGNMENT FAILURES OF PRINTER AND SERIAL DEVICES
WITH LS 4.0 BACKUP DOMAIN CONTROLLER ON LS 3.0 DOMAIN.
In a LAN Server 3.0 domain which has an OS/2 2.11, LS 4.0 backup domain
controller, logon assignments to printer and serial devices can fail
resulting in error message NET8182: the logon assignment of serial
device queue failed, or NET8183: the logon assignment of printer queue
failed.
o APAR= IC10134 NET2140 INTERNAL SOFTWARE ERROR, IF A FORWARD SLASH IS
USED IN THE NAMES FIELD OF USER OR GROUP ID MANAGEMENT GUI
In a LAN Server and Warp environment, when any invalid character (such
as " / \ * ?) is used in the Names field of the User or Group Settings
notebook, the system should respond with error message NET2202; however
/ returns error message NET2140: an internal requester-server error
occurred. If a user was added to a group before the group was created,
a NET2140 error is returned first, and then the GUI crashes with a
SYS3175 error.
o APAR= IC10141 CREATING USER ID HOME DIRECTORIES FROM A LS 4.0 ADDITIONAL
SERVER WITH A LS 3.0 DOMAIN CONTROLLER TO A LS 3.0 ADDITIONAL SERVER
TARGET DRIVE GIVES NET2351 OR SYS0053.
An attempt to create a user ID home directory from an LS 4.0 additional
server that has an LS 3.0 domain controller to a target drive on an LS
3.0 additional server causes error SYS0053: Network path not found, or
NET2351: This machine ID is not valid.
o APAR= IC10186 A NETBIOSSUBMIT CALL WHERE CHAINED NCB'S ARE PASSED CAUSES
THE PROGRAM TO CRASH. SYS3175 IN NETAPI.DLL
The NetBiosSubmit API call causes the program to crash with a SYS3175
error message when using chained NCBs in an LS 4.0, Warp environment.
o APAR= IC10206 USER WITH ACCOUNTS OPERATOR PRIVILEGE CANNOT ADMINISTER
ANOTHER USER'S APPLICATION ASSIGNMENTS IF DOMAIN CONTROLLER IS LS 3.0
AND REQUESTER IS LS 4.0
When an LS 3.0 domain controller is accessed from a LS 4.0 requester, a
user with accounts-operator privilege cannot administer another user's
application assignments.
o APAR= IC10244 VNETAPI RETURNS NO REDIRECTION INFORMATION FOR NETUSEENUM
API
A problem was found in VNETAPI. If NetUseEnum API is called, the
correct number of entries for the redirection list is returned, but the
buffers of information for those redirections are empty.
o APAR= IC10250 Auditing shows **** for any changed made by
administrator.
Customer has several administrators and a server with some highly
classified personnel information on. He is finding if he sets auditing
on a resource to full, the audit log shows a load of stars for changes
made by an administrator. The customer sees this as a defect as he
feels that the user id should be shown for any changes made.
o APAR= IC10257 INTERRUPTS ARE NOT BEING PROCCESSED CORRECTLY IN DOS VDM
INT 80 THRU FF.
Customer has an application NOSTOP (NETWORK.COM is a TSR) and another
application called ALERT.COM ( WHICH IS A TSR). Network.com invokes
interrupt 80 and Alert.com is keyed off of interrupt 80. Alert.com is
supposed to display a message on the screen to inform customer a
disconnect from the network. This is not happening under the VDM.
Customer has tried INT 80 THRU FF with no resolution.
o APAR= IC10283 DOCUMENTATION OF BACKACC "/S" PARAMETER IS WRONG.
The LAN Server 4.0 documentation for the BACKACC Utility /S parameter is
incorrect.
o APAR= IC10347 TRAP000D 0C58:00008126 NETWKSTA _COPYMEM + 50
After installation of a new build of a DOS-OS/2 application, a trap
error occurs with the following information.
o APAR= IC10364 SERVER FILE CORRUPTION CAUSED BY LARGE WRITE REQUESTS.
Error in NETWKSTA.200 causes data corruption when requester writes to
files on server. The server logs incomplete error messages indicating
errors in the requester.
o APAR= IC10409 SYSTEM HANGS USING 32-BIT SEMAPHORE
Various errors, including system hangs, occur when running applications
using 32-bit semaphores.
o APAR= IC10518 LSGUI DOES NOT SEEM TO HAVE A TEMPLATE FOR CREATING
WINDOWS PUBLIC APPS
The implication made by the LAN Server GUI providing only DOS and OS/2
public applications templates is that Windows applications cannot be
defined as public applications; however, they can be.
o APAR= IC10527 THE JUNE 16TH BUILD FOR DLS40.ZIP CAUSES LOSS OF
FUNCTIONALITY WITHIN WINDOWS.
After installation of DLS40.ZIP from the June 16, 1995 build, there is a
loss of network functionality within Windows. No NET commands are
available in the DOS box within Windows. All of the pull down menu
items with network functions fail. The result of the failure is either
a flashing cursor in the DOS box, or an hour glass on the Program
Manager desktop. Windows may only be recovered by issuing a
Ctrl-Alt-Del, and pressing Enter at the blue screen.
o APAR= IC10659 WHEN AN ALIAS IS CREATED USING THE COMMAND LINE OR GUI, AN
IPE IS GENERATED INSTEAD OF AN ERROR MESSAGE.
An Internal Processing Error at location 0140:0e46 - 000a:0e46 is
generated on the domain controller when an administrator creates an
alias from the command line or GUI and the path is <drive>:.
o APAR= IC10740 LIST.A IS NOT UPDATED WHEN DOS PUBLIC APP IS CREATED ON A
3.0 REQUESTER WITH A 4.0 DC.
When a LAN Server 4.0 domain is being administered from a LS 3.01
requester and a public DOS application is created, the application is
not available from the DLR because LIST.A is not updated.
o APAR= IC10766 SYS3175 GENERAL ACCESS VIOLATION AT IBF801B0 DOSCALL1.DLL
CS:EIP=DFC6:000001B0 CSLIM=0000035F
When issued from a LAN Server 4.0 additional server, the command CHKSTOR
/ALL returns error message SYS3175: A program generated an access
violation.
o APAR= IC10820 LSRXUTIL DOES NOT SHOW THE CORRECT RESULT, POST GA
SYS3175.
In an LS 4.0 environment with LS40AIDS.ZIP applied, the LSRXUTIL utility
does not show the correct result after an application has been removed
using the command NET APP appname /REMOVE from the command line. Error
message SYS3175 is returned.
o APAR= IC10871 WHEN LS40GUI.ZIP IS APPLIED, A NET2310 IS GIVEN WHEN
ACCESS CONTROLS ARE CHANGED FROM THE GUI AND THE SET BUTTON IS PRESSED.
After application of the LS40GUI.ZIP fix, an attempt made from the LAN
Server Administration GUI, Alias settings notebook, Manage Access page
to change the access controls for a different machine results in error
message NET2310: resource does not exist. The failure occurs only for
resources not residing on the domain controller.
o APAR= IC10948 32-BIT APPLICATION GETS ACCESS VIOLATION ON FIRST CALL TO
NETBIOS RUNNING WARP, LR 4.0.
In a Warp, LAN Server 4.0 requester environment, a 32-bit application
gets an access violation error when on its first call to NetBIOS.
ΓòÉΓòÉΓòÉ 6.2.1.3. User Profile Management (UPM) ΓòÉΓòÉΓòÉ
The following APARs were corrected in User Profile Management for IPx8150:
o APAR= IC08467 MESSAGE TEXT SHOWS INCORRECT DOMAIN NAME WHEN ISSUING A
LOGON /D:(DOMAIN) COMMAND IF ON A REMOTE DRIVE.
When you enter the command LOGON /D:new domain from a remote drive, a
prompt that has the correct user ID and domain is displayed. However,
when you press Enter, a message box specifies that you are going to
logon to the old domain and not the new domain.
o APAR= IC09055 NETBIOS32SUBMIT HANGS
The netbios32submit API hangs when executed within a program.
o APAR= IC09101 LS40 WILL NOT ALLOW USAGE OF ALIASES POINTING TO PCLP
RESOURCES EVEN THOUGH A NET USE CAN BE DONE WITH DIRECT PATHING
SPECIFIED
The customer migrated from a Lan Server 3.0 system to a Lan Server 4.0
system, both were Advanced Servers. The LS30 system had functioning
External Resources for remote printers off PCLP Servers, running on
PC/AT's. This environment was functioning with LS20 and LS30 Requesters
on OS/2. After migration to LS 4.0, although the Resource folder
contains the correct aliases for remote printers attached to PCLP
servers and the IBMLAN\DCDB\PRINTERS subdirectory contains the correct
*.CMD and *.BAT files, when a user issues a NET USE to the printer
alias, it fails with a 'NET3502: OS/2 error 67 has occurred' and a
'SYS0067: the network name cannot be found'.
o APAR= IC09117 FROM USER ACCOUNTS OF LAN SERVER ADMIN GUI, YOU CANNOT
TELL WHAT PERMISSIONS A USER HAS FOR ANY ALIAS ON THE LIST OF ALIASES.
From the LAN Server Administration GUI, User Accounts folder, you cannot
view permissions for a user's assignments.
o APAR= IC09242 UNABLE TO CREATE PRINTER ASSIGNMENTS ON LS 4.0 SERVER
USING AN LS 3.0 REQUESTER
In the administration of an LS 4.0 domain from an LS 3.0 OS/2 requester,
the selection of Logon Details, Printer Assignments for a particular
user returns error message NET9503M: There are no printer aliases
defined to this domain.... However, the correct printers are listed
when the same selections are made for a user with administrative
privileges.
o APAR= IC09268 CANNOT CREATE DIRECTORY ALIAS FROM LS 3.0 REQUESTER
A directory alias cannot be created from an LS 3.0 requester
administration GUI. The error NET9336E is returned. The directory is
not created.
o APAR= IC09269 UNABLE TO CREATE A HOME DIRECTORY FROM A 3.0 REQUESTER
A home directory cannot be assigned for a user from an LS 3.0 requester.
The error NET9527 is returned. The directory is created.
o APAR= IC09299 SYS3175 IN NETAPI.DLL WHEN PC LAN CLIENT ACCESSES LS 4.0
RESOURCE USING WRONG PASSWORD.
On LS 4.0, when an invalid password is specified on a NET USE command
from a PC LAN Client, the 'invalid password' message is not returned.
Instead the following error is returned:
SYS 3175 OS/2 SYSTEM ERROR during process ID 35
access violation at 17af119c netapi.dll 0010:0000119c____
CS:EIP= bd7f : 0000119c CSACC= 00fb CSLIM= 00001845
o APAR= IC09348 RAS3 ERROR WHEN USING LS3.0 REQUESTER AND OPENING A PUBLIC
APP THAT RESIDES ON LS4.0 DOMAIN CONTROLLER.
When a public application that resides on an LS 4.0 domain controller is
opened by an LS 3.0 requester, a RAS3 error is returned.
o APAR= IC09526 AFTER MIGRATION FROM LAN SERVER 3.0 TO LAN SERVER 4.0
EXTERNAL RESOURCES ARE NOT "LOGON ASSIGNABLE"
After migration from LS 3.0 to LS 4.0 with external resources, these
resources exist in resource definition view, but when an attempt is made
to assign logon assignments, these resources do not appear in the list
of resources.
o APAR= IC09658 SYS3175 IN NETAPI.DLL WHEN CREATING EXT PRN RESOURCE ON DC
Creating an external printer resource from a LAN Server 3.0 requester to
a LAN Server 4.0 domain controller results in error SYS3175 at the
server in NETAPI.DLL.
o APAR= IC09736 ALIAS SETTINGS PARAMETER MAXIMUM CONNECTIONS DOES NOT WORK
More than one user can log on and access public application when the
Maximum Concurrent Connections parameter is set to 1.
o APAR= IC09769 CUSTOMER HAS A HANG ON THE DC CAUSED BY A SYS3175 IN
BACKGROUND. NETAPI.DLL AT CS:EIP= A2D7:000011A9 CSLIM= 000017E5.
Session disconnects result from hang of the domain controller, which in
turn is hung because of a SYS3175 error, a trap in the NETAPI.DLL.
o APAR= IC09864 SYNTAX CHANGED FOR RESTORING CONNECTION TO A HOME
DIRECTORY
In LS 4.0, when a connection to a home directory was lost, an error
prevented the use of NET USE x: aliasname to reconnect to the home
directory. This has been corrected and the old syntax now works
correctly.
o APAR= IC10122 UPM: A LOGON ... /DOMAIN ERASED DB/2 USER LOGON PROFILE.
On a system running OS/2 3.0 Warp, LanRequester 4.0, and DB/2 2.2, the
LOGON /DOMAIN command erases the DB/2 user profile. This only occurs
when users of DB2/2 or Communications Manager use the user logon profile
function.
o APAR= IC10256 GET ERROR ACCESS DENIED WHEN ATTEMPTING TO CHANGE PASSWORD
FROM LS 4.0 REQUESTER TO ID ON NT SERVER
When an ID is setup on an NT Server, 'Make user change password at first
logon' is specified, and logon is attempted from an LS 4.0 requester,
then an error 5 (access denied) is returned and the logon routine quits.
o APAR= IC10938 LOGONS FAIL AFTER ADDING USERS TO DOMAIN DUE TO SLOWDOWN
OF NETWORK AND ADDITIONAL SERVERS INCREASE ACTIVITY.
When 2 users are added to the domain, the network slows up to the point
of not accepting logons or logons are very slow (3 to 10 minutes). Many
additional servers are reestablishing sessions with the domain
controller and then requesting a full update of the NET.ACC data when
they should be requesting only partial updates.
o APAR= IC10973 SYS3175 IN NETAPI.DLL AT CS:EIP= A2CF:000011FF AND CSLIM=
000017E5 ON ALL ADDITIONAL SERVERS IN DOMAIN.
Customer reported that all of the additional servers in a domain failed
with a SYS3175 in NETAPI.DLL.
ΓòÉΓòÉΓòÉ 6.2.1.4. HPFS ΓòÉΓòÉΓòÉ
This section describes HPFS APARS corrected for IPx8150.
o APAR= IC08503 USING LSU 1.0.1, LSU 4.0 AND NRR(NETWORK RESOURCE
RESERVATION), "AUTOFAIL" DOESN'T WORK CORRECTLY
The Autofail parameter functions incorrectly when LSU 1.0.1 or LSU 4.0
is running with Network Resource Reservation (NRR).
o APAR= IC08891 CANNOT COPY, XCOPY OR TYPE FILES WITH .FNT EXTENSIONS IN
HPFS386 ENVIRONMENT.
In an HPFS386 environment, the commands COPY, XCOPY or TYPE do not work
for .FNT files. The COPY and TYPE commands return a SYS0005 error
message. The XCOPY command returns a SYS1186 error. COPY puts filename
with zero (0) bytes out to selected target drive (either FAT or HPFS).
o APAR= IC08901 ARCHIVE (A) BIT NOT SET ON CHANGED FILE USING LOTUS 123G
IF IT WAS NOT SET WHEN FILE WAS OPEN. HPFS386 ONLY.
If the archive bit (A) does not exist on a file, when the file is opened
and changed and then saved from LOTUS (tm) 123G to an HPFS386 drive, the
bit is not turned on.
o APAR= IC09030 UNABLE TO HANDLE HPFS386 CACHE SIZE GREATER THAN 128MB
Setting a cache size greater than this 128MB for HPFS386 causes an
overflow. The overflow wraps resulting in a cache size that is smaller
than expected.
o APAR= IC09150 ARCHIVE BIT NOT SET ON HPFS386 VOLUME WHEN SAVING A FILE
IN LOTUS 123G V2.0
When Lotus is used and a file that previously did not have the Archive
(A) bit set is saved, the bit remains unset.
o APAR= IC09410 NET3195 AN NCB ERROR OCCURRED: NET1. THE NCB IS THE DATA.
C1 06 SAME AS IC07107
In an LS 4.0, Warp environment, the server disappears from the ring and
all requester sessions are terminated and cannot be reestablished. The
NET3195 error message is returned.
o APAR= IC09448 PARAMETERS PLACED AT TOP OF HPFS386.INI WITHOUT A SECTION
HEADER GENERATES NO ERROR
Placing valid or invalid parameters at the top of HPFS386.INI without a
valid section header causes no error to be generated by HPFS386.
o APAR= IC10063 TIME SPENT PROCESSING RAW READS
For an Advanced server, in the SPM/2 Dump report the "time spent
processing raw reads" (TMRORawRds) is always about one minute (the
collection interval) even when no read has been done. The data obtained
with core reads seems to be OK.
o APAR= IC10648 SERVER RUNNING ULTIMEDIA/WINDOWS PUBLIC APPS. CLIENT
EXPERIENCES HANGS RUNNING ANY APPLICATION.
The server running Ultimedia and Windows public applications hangs when
any application is run.
o APAR= IC10828 HPFS386 FIXES FOR COMPUTER ASSOCIATES UNICENTER PRODUCT
These are fixes so that the Computer Associates product Unicenter will
work on HPFS386.
o APAR= IC10832 NET COPY LEADS TO MSGNET3745 AND MSGNET3502 IF LS40HPFS
FIXPAK IP08028 IS INSTALLED FOR LS4.0
In LS 4.0 environment, the NET COPY command returns error messages
NET3745 and NET3502.
o APAR= IC10844 CUSTOMER IS RECEIVING INCORRECT OUTPUT FROM NET DASD.
When OS/2 clients access drives that have been "partitioned" with NET
DASD, the correct drive capacity is displayed. However when DLS clients
access those drives, an erroneous drive capacity is displayed.
ΓòÉΓòÉΓòÉ 6.2.1.5. Remote IPL ΓòÉΓòÉΓòÉ
This section describes RIPL APARS corrected for IPx8150.
o APAR= IC08509 ADD LS 4.0 RIPL SUPPORT FOR SVGA USING WARP
Warp RIPL support for SVGA displays has been added to LS 4.0
o APAR= IC09156 REXX SYNTAX ERRORS IN FRENCH VERSION OF RPLSDMSG.CMD.
The French version of RPLSDMSG.CMD has numerous REXX syntax errors. The
main ones are absent of double quotes when there are accented characters
in the French messages. Typical REXX error is REX0006 with reference to
the line number and REX0040 error 40 in line 1546 of RPLSETD.MSG.
o APAR= IC09214 PROBLEM WHEN RIPLING IS TO BE USED TO RIPL THE WARP
FULL-PACK.(WARP THAT INCLUDES WIN-OS2)
LS 4.0 RIPL is enhanced to support OS/2 Warp that includes WIN-OS/2.
o APAR= IC09239 RPL PC HANGS WHEN USING THE AUTO 16/4 T/R MC ADAPTER
Using the new auto 16/4 T/R MC adapter to RIPL, the requester hangs.
o APAR= IC10677 WARP CONNECT CANNOT BE RIPL'ED UNDER GA LEVELS OF LAN
SERVER 4.0
RIPL has been enhanced to support RIPL'ing WARP Connect using LS40.
ΓòÉΓòÉΓòÉ 7. Appendix ΓòÉΓòÉΓòÉ
Appendix of other interesting topics.
ΓòÉΓòÉΓòÉ 7.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.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
The item in the title line is a trademark of IBM Corporation
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
The item in the title line is a trademark of Microsoft Corporation
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
The item in the title line is a trademark of Apple Computer
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
The item in the title line is a trademark of Lotus Development Corporation
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
The item in the title line is a trademark of Ungermann-Bass, Inc.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
The item in the title line is a trademark of Wall Data Corporation
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
The item in the title line is a trademark of Attachmate Corporation
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
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
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
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
Special RIPL Considerations Table of Contents
o Creating New OS/2 2.1 Remote IPL Clients
o Creating New OS/2 for Windows Clients
o Supporting Multiple Levels of the OS/2 Operating System
o Special Considerations for Remote IPL of Warp
o OS/2 SVGA Support for RIPL Clients
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
where WARP* is any one of:
o OS/2 Warp 3.0 for Windows
o OS/2 Warp 3.0 with Windows (FullPak)
o OS/2 Warp Connect
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
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
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
The OS/2 Selective Install function can be performed by double-clicking on the
Selective Install Object in the OS/2 System Setup folder.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
Trademark of IBM Corporation.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
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 3.0 XDF
format installation diskettes. OS/2 Warp 3.0 server systems will be able to
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 3.0 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 2.0 systems below XR06100 cannot be updated to read the
OS/2 Warp 3.0 XDF format installation diskettes.