home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 17 Fixes30
/
17-Fixes30.zip
/
un0959b1.dsk
/
UN00959.INF
(
.txt
)
< prev
Wrap
OS/2 Help File
|
1996-10-03
|
25KB
|
686 lines
ΓòÉΓòÉΓòÉ 1. Introduction ΓòÉΓòÉΓòÉ
This FixPak can be applied to:
o TCP/IP Version 3.0 (TCP/IP in WARP Connect)
o TCP/IP Version 3.1 (TCP/IP in WARP Server)
Warning: 1 - In order for an updated TCP/IP Version 3.0 or Version 3.1 to
function properly, the installation of MPTS ServicePak WRx8210 is required.
Warning: 2 - Archiving is not enabled for this ServicePak.
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.
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
UNx0959 (where x indicates the country code.)
SYSLEVEL.TCP IBM TCP/IP Version 3.0 for OS/2
IBM TCP/IP Version 3.1 for OS/2 WARP Server
SYSLEVEL.DHS IBM OS/2 Dynamic Host Configuration Protocol Server
Version 3.1
SYSLEVEL.DDN IBM OS/2 Dynamic Domain Name Server Version 3.1
ΓòÉΓòÉΓòÉ 1.2. Trademarks ΓòÉΓòÉΓòÉ
The following are trademarks of IBM Corporation:
o AT
o DOS
o IBM
o Operating System/2
o OS/2
o OS/2 Warp
o OS/2 Warp Connect
o Presentation Manager (PM)
o XGA
The following are trademarks of other Corporations:
o Lotus 1-2-3 (Lotus Development Corporation)
o Microsoft (Microsoft Corporation)
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 FixPak uses Corrective Service Facility (CSF) Version 2-B (provided on the
tool diskette of this FixPak) 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 Service 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 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.
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 ΓòÉΓòÉΓòÉ
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.
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.
CAUTION:
Before using FSERVICE to apply corrective service, review the sample response
file (RESPONSE.FIL) located on the Service Tool 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 (UN_0959.CID) that
may prove useful in setting up a CID server for this FixPak.
The sample UN_0959.CID assumes the following:
o The Service Tool diskette files are placed on the code server using "XCOPY
A:\*.* /S" (or equivalent) in 'x:\img\csd\tcp\un_0959' 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\tcp\un_0959.'
o The sample RESPONSE.FIL (or equivalent) is placed on the code server in
x:\rsp\csd\tcp\un_0959.
o The following CID server directory structure contains the contents of the
FixPak and the Service Tool diskette.
img\csd\tcp\un_0959 * Root directory of FixPak diskette 1
img\csd\tcp\un_0959 * Service Tool diskette files
img\csd\tcp\un_0959\FIX * No files
img\csd\tcp\un_0959\FIX\TCP.1 * TCP/IP Fixes
rsp\csd\tcp\un_0959 * RESPONSE.FIL (from sample on Service
Tool diskette)
o A log directory exists at 'x:\log\csd\tcp\un_0959' 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 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 and Diskette 1 of 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 3.x Installation Diskette and Diskette 1. Call
them SA1 and SA2 respectively.
2. 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 select Network Administrators Task Icon:
Creating a 386 HPFS Boot Diskette, or Command and Utilities Icon: LAN
Server Utilities.
3. Ensure the country code, codepage, and the keyboard information in the
config.sys file on the boot diskette matches the corresponding information
on the target workstation's config.sys. Verify that the 386 HPFS Bootable
Standalone Service Diskettes work properly and that, after rebooting,
Local Security and Fault Tolerance are working as expected.
ΓòÉΓòÉΓòÉ 2.4. Special Situation Install ΓòÉΓòÉΓòÉ
This method will apply all fixes to all partitions and directories:
FSERVICE is used for CID installation of this FixPak, 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 (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 Service Tool 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 ΓòÉΓòÉΓòÉ
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 ΓòÉΓòÉΓòÉ
From the Network Administrators Task Online reference perform the following steps:
1. Select Using LAN Server: Overview
2. Select Task List
3. Select Task For Using Utilities
4. Select From Table 18. Tasks
5. Select the section on creating system diskettes that use 386 HPFS
ΓòÉΓòÉΓòÉ <hidden> LAN Server Utilities ΓòÉΓòÉΓòÉ
From the Commands and Utilities Online reference perform the following steps:
1. Select LAN Server Utilities
2. Select Miscellaneous Utlities
3. Select MAKEDISK Utility
ΓòÉΓòÉΓòÉ 3. Things that Changed ΓòÉΓòÉΓòÉ
The following sections describe changes that have been made to the product's
executables, and messages/helps.
ΓòÉΓòÉΓòÉ 3.1. TCP/IP Version 3.1 ΓòÉΓòÉΓòÉ
The following is a list of all APARs included in FixPak UN00959, with a one
line description.
o APAR IC12448
PMANT INTERNAL APAR FOR WARP SERVER V3.1. CONTAINS FIXES FROM PN72675
PN66579 PN65202 PN75965 IC10506 PN82161 (OS/2 PMANT)
o APAR IC12449
TN3270 INTERNAL APAR FOR WARP SERVER V3.1. CONTAINS FIXES FROM PN72675
PN66579 PN75623 PN77563 PN82161 (OS/2 TN3270)
o APAR IC12662
LPRPORTD CONNECTION TIMES OUT PRINTING LARGE FILES.
o APAR IC12678
NEED SINGLE ROUTE BROADCASTING TO BE DEFAULT.
o APAR IC12771
PORTMAPPER FAILS WITH 32-BIT RPC APPLICATIONS
o APAR IC12809
SENDMAIL RETURNS INCORRECT RETURN CODE AFTER FAILING TO CONNECT TO A HOST
FROM NAMESERVER MX RECORDS
o APAR IC12815
TRAILING BLANK IN DHCPSD.CFG CAUSES DNS UPDATES TO FAIL
o APAR IC12852
FTPPM CAN NOT HANDLE > 1024 FILES
o APAR IC12884
DHCPSD DOES GETHOSTBYADDR TO GET OPTIONS 12 & 15
o APAR IC12943
MISSING COLORS ON TN5250 TO AS/400, THEN AS/400 TN3270 TO S/390
o APAR IC12974
OS/2 TCP/IP V3.0 SLIP, PPP, HOSTID, ROUTED CONSOLIDATED FIXES FOR WARP
CONNECT CUSTOMERS
o APAR IC12981
PPPTERM DOES NOT ACCEPT KEYSTROKES
o APAR IC12982
ROUTED CAUSES UNCONTROLLED GROWTH OF THE SWAPPER.DAT FILE CAUSING EVENTUAL
SYSTEM LOCKUP.
o APAR IC13003
PMPING CAUSES SYSTEM TO LOCK AFTER 2-3 DAYS WHEN RUNNING 24/7.
o APAR IC13114
AUTOSTARTING TFTPD USING INETD CAUSES A USER TO BE UNABLE TO TFTP
SUCCESSFULLY TO THAT MACHINE AFTER IC12482 FIX.
o APAR IC13140
SLIPPM DOES NOT HAVE PROPER ERROR LOGGING FACILITIES IF THE PM PROGRAM HALTS
TO START
o APAR IC13150
BOOTPD ISN'T WORKING PROPERLY WITH THE HD TAG AND BOOTFILE PASSED IN BOOTP
REQUEST PACKET
o APAR IC13176
BOOTP SERVER NOT PROCESSING HARDWARE ADDRESS CORRECTLY
o APAR IC13215
TN3270.EXE DOES NOT ALLOW USER TO SELECT AN OPTION PROPERLY FROM VM MENUS
o APAR IC13239
ROUTED DELETES INTERFACE LAN0 (WITH TWO INTERFACES IN MACHINE) EVEN WHEN
DIRECTED NOT TO USING "PASSIVE" DIRECTIVE IN GATEWAYS
o APAR IC13327
WHEN BOOTP CLIENT IS GOING THROUGH A BOOTP RELAY:DHCP SERVER SENDS RESPONSE
TO SERVER PORT67 INSTEAD OF 68
o APAR IC13335
PROXYARP OPTION OF PPP FAILS TO UPDATE ARP TABLE PROPERLY ON A MULTIHOMED
SYSTEM.
o APAR IC13443
NEWSREADER/2 TRUNCATES ARGUMENTS FIELD IN EDITOR CONFIGURATION DIALOG TO 32
CHARACTERS
o APAR IC13447
TELNET TELNETPM WARP SERVER V3.1. CONTAINS FIXES FROM PN74719 PN74585
PN79926 IC11619 IC11622 IC11770 IC11868 IC12232
o APAR IC13452
PMANT WARP SERVER 3.1 ROUTE OF PN84273 / IC13408
o APAR IC13454
SETTERM.EXE WARP SERVER 3.1 ROUTE OF IC12539
o APAR IC13455
TN5250.EXE WARP SERVER 3.1 ROUTE OF IC12315
o APAR IC13468
TELNETDC APAR FOR WARP SERVER V3.1. CONTAINS FIX FOR APAR PN76784.
o APAR IC13587
BOOTP 'INVALID TAG' MESSAGE AND INTERFACE NOT CONFIGURED
o APAR IC13614
PPP TERMINATES A CONNECTION DURING NEGOTIATION IF THE CLIENT CHOOSES NOT TO
USE VJ HEADER COMPRESSION
o APAR IC13780
RPCINFO -P HOSTNAME FAILS WITH SYS2070. TNLS32->WNLINITGLOBAL COULD NOT BE
LOADED (RC=127).
o APAR IC13856
FROM FIELD IN CONFIGURE POSTING OF NEWSREADER V1.2.5 IS ADDING A SPACE
BETWEEN EMAIL ADDRESS & NAME IN ( ) WHEN RESTARTING.
o APAR IC13857
NEWSREADER/2 DOES NOT PROPERLY PARSE "ADDRESS FROM" WHEN REPLYING TO A
USENET POSTING
o APAR IC13859
NEWSREADER/2 GENERATES A SYS3175 IN NR2.EXE WHEN REFRESHING A GROUP WITH A
LONG NAME MANUALLY
o APAR IC13873
NEWSREADER V1.2.5 HIGHLIGHTS UNREAD ARTICLES AS READ AFTER VIEWING SAME
SUBJECTS IN LARGE ARTICLE LISTS
o APAR IC13879
BOOTP SERVER NOT RETURNING SERVER IP ADDRESS
o APAR IC13887
ESCAPE KEY DOES NOT DISMISS "MAIL..." DIALOG IN NEWSREADER/2 WHEN USING AN
EXTERNAL EDITOR.
o APAR IC13892
NEWSREADER HALTS WITH A SYS3175 IN NR2.EXE AT 0027:00000C18 WHEN CONNECTING
TO A CERTAIN ALTERNATE PROVIDER'S NEWS SERVER.
o APAR IC13927
TCP/IP ON WARP CONNECT- CANNOT ENTER ARABIC DATA IN TELNETPM
o APAR IC14236
NSUPDATE INTERMITTENTLY CAUSES A PERFORMANCE DEGRADATION OF THE DHCP SERVER
o APAR IC14282
INCOMING SENDMAIL CONTAINING CARRIAGE RETURN CR , TRUNCATES MESSAGE
o APAR IC14283
FTP PROXY GET FAILS AFTER PROXY OPENING THE SAME FTP SERVER ALREADY LOGGED
IN TO WHEN USING THE RXFTP API.
o APAR IC14284
FTP INCORRECT HANDLING OF FILES NAMES CONTAINING % SIGN IN MGET AND MPUT
o APAR IC14285
FTP GET FAILS WITH RC=206 WHEN DOWNLOADING A FILE WITH A LONG FILE NAME TO A
DRIVE WHICH IS FORMATTED FAT
o APAR IC14288
ATTEMPTS TO USE FTPPROXY BETWEEN THE REMOTE GATEWAY AND A SECOND FAIL EVEN
THOUGH THE RETURN CODE FROM THE FTPPROXY() IS 0.
o APAR IC14566
TN5250 FLAGS DATASTREAM AS INVALID
o APAR IC14567
TN5250 USES THE WRONG KEYBOARD TRANSLATION TABLE
o APAR IC14568
TN3270 NOT DISPLAYING DATA CORRECLTY FROM AND MVS HOST
o APAR IC14569
PMANT.EXE CHANGE HIGHLIGHT COLORS DOES NOT WORK.
o APAR IC14570
TELNET DOES NOT HONOR THE -H ( SESSION HEIGHT) OPTION
o APAR IC14656
SYS3175 IN VT100.DLL CS:EIP=77A7:00000018 CSLIM=00000147
o APAR IC14689
RXFTPADD IS CASE SENSITIVE WHEN FTPLOAD FUNC IS USED AS THE THIRD PARAMETER.
o APAR IC14690
CONCURRENT MGET FAILS WHEN FTP'ING FROM AN OS/2 COMMAND LINE.
o APAR IC14691
FTP TO A HOST, GET A FILE, DURING TRANSFER OF FILE, HIT CNTL-C, REINVOKE THE
GET COMMAND AND THE SESSION HANGS.
o APAR IC14694
G:PERMISSION DENIED WITH FTP AND A NETRC FILE. NO G: DIRECTORY IS INVOLVED.
o APAR IC14758
FTPD PORT COMMAND DOESN'T VALIDATE PARAMETERS
o APAR IC14759
TELNET HFT EMULATION DOES NOT DO A PROPER SCREEN REFRESH. THE SCREEN JUMPS
ONE LINE EACH DISPLAYED SCREEN.
o APAR IC14760
TRANSMITTING MORE THEN 32MB W/ TFTP RESULTS IN A CONNECTION TIME OUT
o APAR IC14761
SENDING DATA FROM AN AIX MACHINE TO AN OS2 MACHINE USING TFTPD DOES NOT SEND
THE END OF LINE FOR EACH LINE.
o APAR IC14804
SOME DOS BOX APPLICATIONS DO NOT CONNECT WITHIN A SPECIFIED TIME.
o APAR IC14805
ISOCKET ERROR 10038, SOCENOTSOCK
o APAR IC14806
FAILURES WITH LOTUS NOTES AND NETSCAPE USING DOSBOX AND/OR TRAP 000E RUNNING
NETSCAPE UNDER WINOS2 UNDER OS/2 WARP
o APAR IC14807
CANNOT HAVE EMBEDDED SPACES IN THE USERID USING FTPPM: OTHER
o APAR IC14808
WHEN CUST INPUT THE DATE THAN 1991-12-31 BEFORE, SYSTEM ERROR.
o APAR IC14809
SYS3170 DOSCALL1 AT 1A050323 RUNNING REXEC EXCEPTION C0010001 AT 1A050323
o APAR IC14810
RSH INCORRECTLY INTERPRETS CR(0D)/LF(0A), IF 0D IS THE 512TH BYTE OF THE
BUFFER AND 0A IS THE NEXT OR 1ST BYTE OF THE NEXT BUFFER
ΓòÉΓòÉΓòÉ 4. Appendix ΓòÉΓòÉΓòÉ
Appendix of other interesting topics.
ΓòÉΓòÉΓòÉ 4.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 Lotus Development Corporation