AIX 2.2.1 Upgrade Induced Headaches

Robin D. Wilson/1000000 robin at sabre.austin.ibm.com
Wed Jul 11 02:06:31 AEST 1990


In article <364 at ucunix.SAN.UC.EDU> Tom.Pitman at UC.Edu writes:
<After a bit of examination, I was thoroughly confused.  I
<proceeded to call IBM's AES support line, who told me that this was a
<well known problem, and that the way to avoid it is not to upgrade the
<OS.  I, in turn, explained that in order to have a version of NFS that
<supports File Locking, it was necessary to perform the upgrades.  The
<gentleman from AES support told me to call IBM AIX Defect Support and
<reference a long outstanding APAR (8395), that was opened on this very
<same problem.
<
<Upon calling AIX Defect support and explaining the situation, I was
<basically told the following.  The problem is not with AES nor is it
<with AIX, but the problem relates to X-Windows 1.1 which is an
<unsupported product.  He then told me to find two files from the
<installation diskettes (/usr/lib/ogsl.txt and /usr/lib/libogsl.a) and
<restore them.  I didn't find these files on the installation disks,
<but I did find them on a backup tape from many Eons ago.  (Naturally,
<upon restoring them, X-windows 1.1 won't even start.)
<
<My questions are as follows:
<
<1) Does anyone out there have slightly more up to date versions of these
<   files, that I might be able to get my grubby little hands on?
<   (Please send me E-mail, and maybe we can arrange something)  I was
<   up to level 2705 before all the madness started...
<
<2) How can any self respecting company offer a piece of Supported
<   Software (AES) that runs on top of a piece of non-supported software
<   (X-windows 1.1) and then not make any effort to try to correct
<   problems that occur as a result of system upgrades?  Or maybe IBM
<   should get a version of AES out that works under the new X-windows?
<
<Tom Pitman (Tom.Pitman at UC.Edu)

Tom (and anybody else who has this problem),

Xwindows 1.1 is still a supported product until August 1990.  Also, the 
referenced APAR (8395) has had a code changed made to fix the problem.  
The fix is not yet available for general distribution, but can be had
on an emergency fix basis.  To request an emergency fix, just call defect 
support and reference APAR IX08395, tell them that you are aware that this
apar is not yet being distributed, but that a development fix should be
available.  If there is any problem getting the fix, have them call me 
(Robin Wilson -- I am level 3 RT/AIX field support).  The fix has not yet
been regression tested so it is unclear as to its reliability, but 
it should work OK.

I am sorry if level 2 gave you eronious information, but it seems like they 
were just trying to get you a "workaround" until the problem is actually 
fixed.


+-----------------------------------------------------------------------------+
|The views expressed herein, are the sole responsibility of the typist at hand|
+-----------------------------------------------------------------------------+
|UUCP:     cs.utexas.edu!romp!ibmchs!auschs!sabre.austin.ibm.com!robin        |
|USNail:   701 Canyon Bend Dr.                                                |
|          Pflugerville, TX  78660                                            |
|          Home: (512)251-6889      Work: (512)823-4526                       |
+-----------------------------------------------------------------------------+



More information about the Comp.unix.aix mailing list