IBM Peer Fixpak for Warp 4.0 (IP_8402) - Korea v. IP_8402 (7/11/1997, International Business Machines Corporation (IBM)) |
Readme/What's new |
IBM Peer for OS/2 Version 4.0 FixPak IPQ8402 (Korean)
Fixes for OS/2 LAN Requester and UPM are also included in this FixPak.
After applying this FixPak, these products will be Year-2000 compliant.
This FixPak supercedes IP08401.
WARNING: Archiving is not enabled for this FixPak.
IP08402.INF, located on the first diskette of the FixPak, contains
installation, and other useful information about this FixPak.
Please review before installation of service.
NOTE : APAR IC16787 (MULTIPLE LOGON ATTEMPTS POSSIBLE)
was included in this FixPak, although it is not
documented in the INF file.
************************************************************************
Diskettes can be created using the LOADDSKF utility.
There are 6 files/images included in this package.
************************************************************************
CSFTOOL1 DSK FixPak Tool Diskette 3.50"
LQ8402B1 DSK Peer Diskette #1 3.50 1.44MB
LQ8402B2 DSK Peer Diskette #2 3.50 1.44MB
LQ8402B3 DSK Peer Diskette #3 3.50 1.44MB
LQ8402B4 DSK Peer Diskette #4 3.50 1.44MB
LQ8402B5 DSK Peer Diskette #5 3.50 1.44MB
INCLUDED APARS
Note: This section describes OS/2 Version 4.0 Peer APARs that are corrected for IPx8402.
o APAR = IC16787 MULTIPLE LOGON ATTEMPTS POSSIBLE
The banking application IBM MERVA/2 needs users maintained by UPM for access to DB/2 and LAN Server. To achieve a single-logon concept and to re-use UPM's functions such as password control, logon panels, and password encryption, the same user entries are also used for access control to MERVA/2. The problem is that an extremely important function is missing in UPM--the detection of multiple invalid logon retries and disabling of the user. UPM has to count invalid attempts for Local AND Domain Logons as well as for NetUserValidate2 calls, reset the count for a valid logon, and disable the user when the retry limit is encountered.
o APAR = IC18903 LAN AUDIT LOG HAS Y2K DATE ERROR
LAN Server Error Log has Y2K date error. To recreate:
Change the date on the domain controller to 1-1-2000. Start the domain controller and logon from a requester. CTRL-ALT-DEL the domain controller. At the requester, try to do a net use of a shared directory on the domain controller. Because the domain controller is still booting up, the net use will fail. This should cause an entry in the error log. The entry in the error log should show something similar to the following example:
Program Date Time Message
Requester 1-1-100 00:08:45 Text of error message goes here.
NOTE: When the date is set to 2001 it shows as 1/1/101.
o APAR = IC18905 LAN: INCORRECT TIME RANGE WHEN ADDING NEW USER
While attempting to create a new user account from the command line, LAN gives an incorrect time range. The format of the command was as shown below:
NET USER IT04R01U UPW04R01 /ADD /PRIV:USER /TIMES:M,11pm-12am
When executing this command on dates prior to 12/31/99, the command completes successfully. On 12/31/99 or later, the command returns an error.
NET3769: An incorrect time range has been supplied.
o APAR = IC18962 NAMED PIPE ON SERVER SHOULD RETURN ERROR_MORE_DATA ON READ
Customer created client and server applications. When the client opens and reads the pipe on a server, the return code is incorrect under the following circumstances: The server writes more data than the following client read request. The server should return ERROR_MORE_DATA but instead returns 0 as the return code. |
Add new comment