home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 29 Fixes_o
/
29-Fixes_o.zip
/
ip0t600.zip
/
IP08605.INF
(
.txt
)
< prev
next >
Wrap
OS/2 Help File
|
2002-04-17
|
34KB
|
829 lines
ΓòÉΓòÉΓòÉ 1. Introduction ΓòÉΓòÉΓòÉ
IBM OS/2 Warp Server for e-business
FixPak IP08605
This FixPak can be applied to:
- IBM OS/2 Warp Server for e-business
This FixPak contains fixes for the product listed above and for the following
components of these products: OS/2 LAN Server, OS/2 LAN Requester, UPM, HPFS,
RIPL, and Fault Tolerance.
Warning: 1 - This FixPak must be installed using Corrective Service
Facility (CSF) 2-B Version 1.42 or above.
Warning: 2 - Archiving is not enabled for this FixPak.
Please review the entire Installation section before proceeding. Service to
servers that use "Advanced Features" can be complex.
Good Insurance!
Have appropriate Bootable Standalone Service Diskettes.
ΓòÉΓòÉΓòÉ 1.1. Affected SYSLEVEL Files ΓòÉΓòÉΓòÉ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Γöé
Γöé AFFECTED SYSLEVELS Γöé
Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
After installing this FixPak for some or all of the components listed below,
the CURRENT FixPak level of the associated SYSLEVEL file(s) will indicate
IPx8605 (where x indicates the country code.)
SYSLEVEL.SRV IBM OS/2 LAN Server
SYSLEVEL.REQ IBM OS/2 LAN Requester
SYSLEVEL.UPE IBM OS/2 User Profile Management - Extended
SYSLEVEL.MUG IBM OS/2 User Profile Management
SYSLEVEL.HFS IBM OS/2 LAN Server - Advanced
ΓòÉΓòÉΓòÉ 1.2. Trademarks ΓòÉΓòÉΓòÉ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Γöé
Γöé TRADEMARKS Γöé
Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
The following are trademarks of IBM Corporation:
o ADSM
o AT
o CM/2
o DB/2
o DB2/2
o IBM
o LAN Server
o MERVA
o Micro Channel
o Operating System/2
o OS/2
o OS/2 Warp
o OS/2 Warp Connect
o OS/2 Warp Server
o OS/2 Warp Server for e-business
o Presentation Manager (PM)
o PS/ValuePoint
o VisualAge
o Win-OS/2
o WorkSpace On-Demand
o XGA
The following are trademarks of other Corporations:
o Adaptec (Adaptec, Inc.)
o ATTISO (AT&T Corporation)
o C++ (American Telephone & Telegraph Company)
o Data Ease (International)
o Lotus 1-2-3 (Lotus Development Corporation)
o Microsoft (Microsoft Corporation)
o MS-DOS (Microsoft Corporation)
o SYTOS (Sytron Corporation)
o Q&A (Symantec)
o Q+E Database Editor (Pioneer)
o TE/2 (Oberon)
o Unicenter (Computer Associates International, Inc.)
o Windows (Microsoft Corporation)
o Windows NT (Microsoft Corporation)
o Word for Windows (Microsoft Corporation)
ΓòÉΓòÉΓòÉ 2. Installation ΓòÉΓòÉΓòÉ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Γöé
Γöé INSTALLATION Γöé
Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
This FixPak uses Corrective Service Facility (CSF) 2-B Version 1.42 (provided
on the tool diskette of this FixPak) for installation. If you try to use
Version 1.37B with this FixPak, you will get the message "No products were
found on the target system to service."
Warning: Once you use Version 1.42 of the FixTool, you will not be able to use
FixTool Version 1.37B or anything prior to 1.37B. Version 1.42 can be used to
apply other FixPaks if needed.
You will receive the following error message if you try to use Version 1.37B
after using Version 1.42 of the FixTool:
"An error occurred while searching for files to update. The reason may be old
or corrupt CSF logfiles, CSF_SEL.000 file, or file system corruption. See
README file for more information."
To resolve this error message, use Version 1.42 of the FixTool to apply the FixPak.
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 FixTool Diskette.
Please read the CSF instructions for information on the use of CSF Version 2-B
backup and restore capabilities. You should also read the READ.ME file on the
FixTool diskette. It describes the new features included with Version 1.42 of
the FixTool.
Note: - Archiving is not enabled for this FixPak.
Installing the FixPak 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 FixPak
Use one of the following methods to replace system files with those
provided on this FixPak:
Selective Install
Redirected (CID) Install
Phase 3 - Return the Serviced System to Normal Operation
Perform a normal system boot.
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 FixPak files.
ΓòÉΓòÉΓòÉ 2.1. Selective Install ΓòÉΓòÉΓòÉ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Γöé
Γöé 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 Service Tool diskette in the A drive.
3. At an OS/2 command prompt, type "A:SERVICE" and press Enter.
4. Insert FixPak Diskette 1 when prompted.
5. 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.
6. Enter (optional) backup path then choose the OK push button.
7. If the APPLICATION IN USE locked files panel is presented, choose
CONTINUE.
8. Follow prompts to complete the process.
9. Remove the diskette from drive A:, then perform the system
Shutdown procedure.
10. Reboot the system normally.
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 ΓòÉΓòÉΓòÉ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Γöé
Γöé REDIRECTED INSTALLATION Γöé
Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
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.
CAUTION:
Before using FSERVICE to apply corrective service, review the sample response
file (RESPONSE.FIL) located on the FixTool diskette. Edit the RESPONSE.FIL, if
necessary, to ensure the service logfile is created in the correct location on
the target workstation.
:LOGFILE d:\os2\install\service.log
where d:\os2\install is the drive and location for the service logfile.
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_8605.CID) that
may prove useful in setting up a CID server for this FixPak.
The sample IP_8605.CID assumes the following:
o The FixTool diskette files are placed on the code server using
"XCOPY A:\*.* /S" (or equivalent) in 'x:\img\csd\wseb\ip_8605'
where 'x:' is the drive seen by the client.
o The FixPak files are placed on the code server using "XCOPY A:\*.*
/S" (or equivalent) in 'x:\img\csd\wseb\ip_8605.'
o The sample RESPONSE.FIL (or equivalent) is placed on the code
server in x:\rsp\csd\wseb\ip_8605.
o The following CID server directory structure contains the contents
of the FixPak and the FixTool diskette.
img\csd\wseb\ip_8605 * Root directory of FixPak
diskette 1
img\csd\wseb\ip_8605 * FixTool diskette files
img\csd\wseb\ip_8605\FIX * No files
img\csd\wseb\ip_8605\FIX\REQ.1 * Requester Fixes
img\csd\wseb\ip_8605\FIX\UPE.2 * Extended UPM Fixes
img\csd\wseb\ip_8605\FIX\HFS.3 * HPFS Fixes
img\csd\wseb\ip_8605\FIX\MUG.4 * User Profile Management Fixes
img\csd\wseb\ip_8605\FIX\SRV.5 * Server Fixes
rsp\csd\wseb\ip_8605 * RESPONSE.FIL (from sample on
FixTool diskette)
o A log directory exists at 'x:\log\csd\wseb\ip_8605' for the log
files.
ΓòÉΓòÉΓòÉ 2.3. Bootable Standalone Service Diskettes ΓòÉΓòÉΓòÉ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Γöé
Γöé BOOTABLE STANDALONE SERVICE DISKETTES Γöé
Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Sometimes it becomes necessary to boot from diskette in order to perform
certain operations on fixed-disk, like installing this FixPak 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, Diskette 1, and Diskette 2 of Warp Server for
e-business. Escape to A:
o Or, if your hardware has been set up to boot from a CD, use the Server Pak
Installation CD and press F3 when prompted to escape to a command prompt.
CAUTION:
Servers that utilize 386 HPFS 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.
To create these custom boot diskettes, see Section 3.2.10 of the README.DOC
file in the IBMLAN directory.
ΓòÉΓòÉΓòÉ 2.3.1. Making OS/2 Bootable Diskettes ΓòÉΓòÉΓòÉ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Γöé
Γöé MAKING OS/2 BOOTABLE DISKETTES Γöé
Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Instructions for creating OS/2 bootable diskettes for requesters.
o For Warp Server for e-business versions:
Use the Install diskette, Diskette 1, and Diskette 2 of Warp Server
for e-business. Escape to A:
ΓòÉΓòÉΓòÉ 2.4. Special Situation Install ΓòÉΓòÉΓòÉ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Γöé
Γöé SPECIAL SITUATION INSTALL Γöé
Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
This method will apply all fixes to all partitions and directories:
FSERVICE is used for CID installation of this FixPak, 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 (RESPONSE.FIL on the Service
Tool diskette) and modify as needed to reflect the configuration
of the system to be serviced. Ensure the service logfile is
created in the correct location on the target workstation.
:Logfile d:\os2\install\service.log
where d:\os2\install is the drive and location for the service logfile.
2. Boot from the Bootable Standalone Service Diskettes.
3. Establish A: as the Current Directory.
4. Replace the Boot Diskette with the FixTool Diskette.
5. From the A: prompt, type "FSERVICE" and press Enter.
6. At the panel titled "Installing this Service Pak" press Enter
(Option 1).
7. Follow the prompts provided by the Corrective Service Facility.
8. Reboot the system normally.
ΓòÉΓòÉΓòÉ <hidden> Locked Files ΓòÉΓòÉΓòÉ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Γöé
Γöé 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 Install Diskettes ΓòÉΓòÉΓòÉ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Γöé
Γöé ESCAPE TO COMMAND LINE FROM INSTALL DISKETTES Γöé
Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
To obtain the A: prompt when using the Warp Server for e-business 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 When prompted - Insert Diskette 2, press Enter.
o At the IBM OS/2 Warp Server for e-business Setup and Installation
screen - Press F3 to go to a command prompt.
The A: prompt should appear. OS/2 programs, including FSERVICE.EXE, can be
run from here.
ΓòÉΓòÉΓòÉ 3. Post Installation Procedures ΓòÉΓòÉΓòÉ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Γöé
Γöé POST INSTALLATION PROCEDURES Γöé
Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
If the Server is intended to support Remote IPL WorkSpace On-Demand clients,
RPLS8605.CMD will need to be executed after the fixpak is installed. See
Updating Remote IPL Servers
ΓòÉΓòÉΓòÉ 3.1. Updating Remote IPL Servers ΓòÉΓòÉΓòÉ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Γöé
Γöé UPDATING REMOTE IPL SERVERS Γöé
Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
If the Server is intended to Remote IPL WorkSpace On-Demand II clients, then
the following steps are necessary after complete installation of this FixPak:
o Run RPLS8605.CMD to:
- Update the DFBB20US.FIT file to reflect the server name.
Note: If WorkSpace On-Demand is not installed on the server, then it is not
necessary to run RPLS8605.CMD.
ΓòÉΓòÉΓòÉ 4. Existing Problems ΓòÉΓòÉΓòÉ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Γöé
Γöé EXISTING PROBLEMS Γöé
Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
There are no known problems with this FixPak at this time.
ΓòÉΓòÉΓòÉ 5. - NEW FUNCTION - ΓòÉΓòÉΓòÉ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Γöé
Γöé NEW FUNCTIONS Γöé
Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
This FixPak does not contain any additions or enhancements that do not have
APARs associated with them.
It is our policy not to include new function in FixPaks. However, as with any
policy there may be exceptions. If any exception occurs in the future, we will
communicate them to you in this section of the documentation.
ΓòÉΓòÉΓòÉ 6. Things that Changed ΓòÉΓòÉΓòÉ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Γöé
Γöé THINGS THAT CHANGED Γöé
Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
The following sections describe APAR fix changes that have been made to the
product's executables, messages, or help text.
ΓòÉΓòÉΓòÉ 6.1. Warp Server for e-business IPx8602 APARs ΓòÉΓòÉΓòÉ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Γöé
Γöé INCLUDED APARS Γöé
Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Note: This section describes Warp Server for e-business APARs that are
corrected in IPx8602.
o APAR = IC24478 IF THE BIT NO. 10 OF SRVHEURISTICS IN IBMLAN.INI IS SET TO A
VALUE >= 6,THE SCAVENGER WAITS TOO LONG BEFORE WAKING UP.
If the bit 10 of srvhueristics in ibmlan.ini is set to a value >=6, the
scavenger thread of netservr.exe waits too long before waking up. Hence
listens are not posted on all the adapters and a 'net view' command from
certain clients fails.
o APAR = IC24817 INCORRECT DIR LISTINGS IN A DOS WINDOW FROM A REDIRECTED
DRIVE CONNECTED TO WARP SERVER FOR E-BUSINESS
Incorrect dir listings in a DOS window on a redirected drive of the client
connected to Warp Server for e-business.
o APAR = IC24950 TRAP BY COPY FILES ON WINNT TO WARP SERVER SMP OR DIR COMMAND
When issuing COPY x:\path\*.* c:\temp while x: is network shared drive of
Windows-NT (both fat and ntfs) and c: is the 386hpfs local drive, if those
files are too many (we usually have it with 400 files), it causes trap at
CS:\EIP=33b8:\0000268f on Warp Server smp machine. This problem also happens
with dir /ad command (around 10%), or simply dir command (a few %) also.
o APAR = IC24960 NETAPI.DLL TRAPS BECAUSE OF STACK OVERFLOW.
When a 32bit API is called, it traps in 16 bit NETAPI.dll because of low
stack space. The test exe runs successfully on W3 and W4, but traps on WSeB.
o APAR = IC25155 PENDING ASYNC CLOSES CAUSE THE REDIRECTOR /CLIENT TO HANG.
Async closes are sent out by the redirector. These calls are completed on
the next request sent to the server. Until then the call remains pending in
the redirector table. Given a large number of servers this could lead to
the client hanging when the table gets full. For example, copying a file
from a client to over 25 servers using UNC style redirection could cause the
client to hang.
o APAR = IC25503 LANINST.EXE TRAPS IN NETAPI.DLL ON WARP SERVER FOR E-BUSINESS
WHEN JFS VOLUME IS PRESENT.
A Trap occurs when LANINST is run on Warp Server for e-business machine
which also has JFS volume. Even though the trap screen shows trap in
DOSCALL1.DLL, actually NETAPI.DLL traps due to non-existing semaphore.
o APAR = IC26138 MEMORY LEAK IN LANPROBE.DLL
Logon to a BDC fails with access denied but logon to PDC works fine. Net
error on BDC gives: NET3226: An error occurred while synchronizing with the
primary domain controller, PDC. The hex data 08 00 indicates a lack of
memory on the system.
o APAR = IC26281 MUG_GET_UID INTERFACE FUNCTION NEVER CHECKS FOR THE USERID
AND PASSWORD OF AN API LOGON DONE BY ANOTHER PROCESS IN SAME SESSION
The UPM interface function MUG_GET_UID never checks for the userid logged on
the same session using a logon API like UPMELGN, UPMEULGN, U32EULGN etc.
That is, if a process A does a UPMELGN and then it spawns another process B,
a MUG_GET_UID call in B never returns the API logon done by A. The return of
userid from B is a must for external programs like DB2 which use the
interface function MUG_GET_UID.
o APAR = IC26416 NET USER USERID /ASSIGN PUBLIC:APPNAME DOES NOT SAVE THE
UPDATE.
The NET USER USERID /ASSIGN PUBLIC:APPNAME command does not save the update.
If we issue NET USER USERID to get the information about the user after
issuing the above command, it shows no application is assigned to that user.
o APAR = IC26424 TRAP IN NETWKSTA WHEN DOING A RAW READ AND LOGOFF IS FORCED
BEFORE THE READ IS COMPLETED.
We observed a trap in netwksta when it is doing a network read. For example,
copy a remote file to local machine using RAW READ, and a logoff is forced
before the RAW read is completed.
o APAR = IC26425 REMOTE LAN ADMINISTRATION USING CLI AUDITS "***" AS A USERID
IN AUDIT.LOG FILE INSTEAD OF ACTUAL USERID.
o APAR = IC26426 NET SESS SHOWS NULL USERID WHEN LOGGED ON FROM PLC OR CLC
CLIENTS FOR WINNT
1) Logon to OS2 server from WinNT with CLC or PLC.
2) Run NET SESS command on OS/2 server.
You will find NULL user id displayed on the screen.
NT opens a NULL session on OS/2, and OS/2 server is not aware of that.
o APAR = IC26427 TRAP IN HPFS386 FINDNEXT ROUTINE DUE TO BAD SMB.
Trap occurs in hpfs386 FindNext routine. Reason: The SMB has a path name
whose terminating character is a DBCS lead byte which confuses hpfs386
leading to a trap.
o APAR = IC26430 ALL THE COMMANDS IN THE *.LST FILE FOR THE LOCKED FILE DEVICE
DRIVER IBMLANLK.SYS AND IBMLANLK.EXE ARE NOT EXECUTED.
All the commands in the *.lst file for the locked file device driver
ibmlanlk.sys and ibmlanlk.exe are not executed in Warp v4. Generally the
process fails to complete when the *.lst file has more than 1000 command
lines. For example, when the command MOVE is used to move more than 1500
files, only first 1216 MOVE commands statements are executed and the
remaining files remain in the source directory itself.
o APAR = IC26433 PRINT SERVER TRAPS
Print Server traps in NETAPI NB_OPEN_R_2.
o APAR = IC26437 NET USER USERID /ASSIGN PUBLIC:APPNAME DOES NOT SAVE THE
UPDATE.
The NET USER USERID /ASSIGN PUBLIC:APPNAME command appears to work but does
not save the information.
o APAR = IC26438 TRAP OR HANG IN HPFS386
Trap or hang in hpfs386. Failing routines are: FindDir, TrimSBDir, MHF. Heap
corruption and other traps can also result. Get trap 0e in hpfs386 due to
race condition when multiple threads open a new file.
o APAR = IC26439 TRAP IN NETWKSTA WHEN DOING A RAW READ AND LOGOFF IS FORCED
BEFORE THE READ IS COMPLETED.
We observed a trap in netwksta when it is doing a network read. For
example, copy a remote file to local machine using RAW READ, and a logoff is
forced before the RAW read is completed.
o APAR = IC26440 API U32EUSRL, REFERS NETWKSTA.SYS TO DETERMINE LANROOT
The api U32EUSRL when used to determine the users logged on to the domain,
refers to netwksta.sys to determine the lanroot. Since there is no file
netwksta.sys (netwksta.200), this search fails and the default search for
muglib dir is searched. In the WSOD environment since all request from the
client go to the server, this causes a lot of unnecessary traffic.
o APAR = IC26441 HPFS386 SWAPPER FILE CORRUPTION CAUSING TRAP 0E IN REXX.DLL
The swapper.dat file on HPFS386 drive gets corrupted if there is growth
failure. This causes traps in applications, rexx.dll in this case, due to
failed swap in requests. Problem is that HPFS386 fails to reset the file
size in OFT correctly after a growth failure, say due to lack of requisite
amount of free space.
o APAR = IC26442 HFS0019 AFTER AUTOCHECK IS RUN ON LARGE HPFS386 DRIVES
When HPFS386 runs autocheck, chkdsk may invoke CHKDSK.SYS if the drive is
large and there is not enough physical memory below 16MB. But then, after
the autocheck is done, HPFS386 may not be able to complete the init (not
enough mem for heap/cache) there by hanging the system with HFS0019. Note
that if we complete the init, then system will be rebooted by CHKDSK.SYS
later on in its INIT_COMPLETE processing. So, to avoid this hang, we must
reboot the system from HPFS386 itself, through a new IOCtl provided by
CHKDSK.SYS (PJ26974).
o APAR = IC26465 HANG IN HPFS386 UNDER HEAVY STRESS DUE TO CORRUPTED B_LCNT
Hang in HPFS386 under heavy stress due to corrupted value in B_LCNT.
Symptoms will be:
- number of threads blocked waiting for PBUFs (Path buffers)
- theads holding PBUFs blocked on a different buffer whose
B_LCNT happens to be 0xff, which clearly is invalid.
ΓòÉΓòÉΓòÉ 6.2. Warp Server for e-business IPx8603 APARs ΓòÉΓòÉΓòÉ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Γöé
Γöé INCLUDED APARS Γöé
Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Note: This section describes Warp Server for e-business APARs that are
corrected in IPx8603.
o APAR = IC24201 NET RUN COMMAND ISSUED SIMULTANEOUSLY FROM A RIPL CLIENT
CAUSES SYS3175 ERROR
When NET RUN is issued simultaneously the os/2 session gets hung giving a
SYS3175 access violation error.
o APAR = IC26156 IBMNULL.DRV MAPPED INCORRECTLY IN FIT FILE
In the default fit file for WSOD R2 and WSOD R1 the mapping for ibmnull.drv
is incorrect in the dfbb20xx.fit
o APAR = IC27016 TRAP 0D IN NETWKSTA.200 WHILE DOING A DIR/S FROM A WSEB
CLIENT AGAINST A NET USED NT SHARE.
Trap 0D in Netwksta.200 while doing a dir/s from a WSeB client against a net
used NT share.
o APAR = IC29008 HFS0019 AFTER AUTOCHECK IS RUN ON LARGE HPFS386 DRIVES
When HPFS386 runs autocheck, chkdsk may invoke CHKDSK.SYS if the drive is
large and there is not enough physical memory below 16MB. But then, after
the autocheck is done, HPFS386 may not be able to complete the init (not
enough mem for heap/cache) there by hanging the system with HFS0019. Also
needs CHKDSK.SYS from FP01 or later.
o APAR = IC29009 HANG IN HPFS386 UNDER HEAVY STRESS DUE TO CORRUPTED B_LCNT
Hang in HPFS386 under heavy stress due to corrupted value in B_LCNT.
o APAR = IC29010 HPFS386 GIVES SYS0015 WHEN NET DASD /ENABLE IS RUN.
SUBSEQUENT DRIVE ACCESS RESULTS IN A TRAP IN THE ROUTINE CRITERROR
Running the command "NET DASD /ENABLE" on an HPFS386 drive results in
SYS0015.
ΓòÉΓòÉΓòÉ 6.3. Warp Server for e-business IPx8605 APARs ΓòÉΓòÉΓòÉ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Γöé
Γöé INCLUDED APARS Γöé
Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Note: This section describes Warp Server for e-business APARs that are
corrected in IPx8605. This FixPak is cumulative, containing fixes from
all previous FixPaks for this product. This includes fixes from
IPx8602 and IPx8603.
o APAR = IC24881 RIPL CLIENT NOT BOOTING ON WS E-BUSINESS SERVER The RIPL
Client with Adaptec SCSI cards not getting booted in the Aurora environment.
o APAR = IC27707 LOGON /L COMMAND ACCEPTS INVALID USERIDS & PASSWORDS AND DOES
A LOCAL LOGON IF THE PRIVILEGE OF THE SYSTEM 'GUEST' ID IS ALTERED
The local logon command 'logon /l' accepts any userid and password for the
logon and completes the logon successfully if the privilege of the system
defined 'guest' user is altered.
o APAR = IC28523 NET SESS COMMAND RETURNS INCOMPLETE OUTPUT ON AURORA WITH
HPFS386 INSTALLED.
o APAR = IC28829 NET ERROR LOG FILE IS FILLED UP WITH REPEATED NET5352 ERRORS
WHEN A TOKENRING HUB IS DISCONNECTED.
o APAR = IC29008 HFS0019 AFTER AUTOCHECK IS RUN ON LARGE HPFS386 DRIVES
o APAR = IC29012 THE TREE CONNECT SMB SENT FOR THE CORE PROTOCOL FROM THE WSEB
SERVER TO FLEX OS IS NOT IN CORRECT FORMAT.
o APAR = IC29350 BDC LOGS REPL-CLIENT NET3228 FOR NON EXISTANT USERIDS When
the server services are started, the Backup Domain Controller logs
REPL-CLIENT Net3228 error into net.err for non existant userids. The error
logging is induced by adding/deleting a userid in the Entry Server system
o APAR = IC29591 ON THE IMPORTER, THE REPLICATOR DELETES THE SUBDIRECTORY IF
SOME FILES ARE ADDED OR DELETED FROM THAT SUBDIRECTORY AT EXPORTER.
On the IMPORTER, the REPLICATOR service deletes the complete content of a
subdirectory if one or more files are added to or deleted from that
subdirectory at the EXPORTER.
o APAR = IC29722 TRAP IN NETSERVR.EXE
o APAR = IC29799 NETLOGON THREADS RUNNING AT TIMECRITICAL PRIORITY CAUSE A
HANG ON FAST MACHINES.
o APAR = IC30143 AFTER CID INSTALL,LSI0216 ERROR SHOW UP IN THE CID LOG
After LANSRV (GR) CID installation, warnings about these parameters were
found in LOG-file:
ThreshAlertNames = *:ADMINS
ThreshAlertDelay = *:10
ThreshAlertUser = *:yes
DirFullAlertNames = *:ADMINS
DirFullAlertDelay = *:10
DirFullAlertUser = *:yes
o APAR = IC30410 IN IBMLAN.INI,THE ALERTS FOR THE THRESHALERTNAMES AND
DIRFULLALERTNAMES ARE SENT TO THE WRONG IDS.
In IBMLAN.INI,if ThreshAlertNames/DirAlertNames params is set to
*:USER1 USER2 F:USER3 and threshold for drive F is reached or
F:\ directory full is reached, then USER1 and USER2
do not receive any alert messages. Instead only USER3 receives
messages for drive F. Here drive F is any drive letter which is
also specified by *.
o APAR = IC30427 RESTACC COMMAND RETURNS NET3502 : OS/2 ERROR 87 WHEN TRYING
TO RESTORE THE ACLS BACKED UP BY BACKACC COMMAND.
Restacc command returns NET3502 : os/2 error 87 while trying to restore the
ACLS backed up by backacc command. The problem does not recreate every time.
The issue occurs when the ACLS from one system is restored to another one
with the same directory structure.
o APAR = IC30614 FAILS TO RECONNECT RESOURCES AT LOGON FOR MCP CLIENT
The connection to a shared resource fails to automatically reconnect after
logging off and again logging on even if the option "Connect to resource at
logon" is checked during creating the connection.
o APAR = IC30623 TRAP D ON CLIENTS IN ABORTSTUCKVCS IN NETWKSTA
o APAR = IC31742 ERROR LOGGED IN IBMZIP.LOG FILE DUE TO IMPROPER INVOCATION OF
CLIFI.EXE
ΓòÉΓòÉΓòÉ 7. Appendix ΓòÉΓòÉΓòÉ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Γöé
Γöé APPENDIX Γöé
Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Appendix of other interesting topics.
ΓòÉΓòÉΓòÉ 7.1. Printing Information from this On-line Document ΓòÉΓòÉΓòÉ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Γöé
Γöé PRINTING INFORMATION Γöé
Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
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