Upgrading AIX from V3.2.2 to V3.2.3

Upgrading AIX from V3.2.2 to V3.2.3

Post by Whe Cha » Thu, 29 Oct 1992 09:22:45



Hi,
We were upgrading our AIX RISC-6000 system from Version 3.2.2 to 3.2.3 and
after committing all update PTFs from 3.2.3,
We typed 'lslpp -h bos.obj' and noticed the output still showed that
the system is running at 3.2.0 level. Should it show 3.2.3 level instead?  
I mean if all PTFs from AIX 3.2.3 are committed, the system history file
would get updated and that lslpp should show the correct operating system
version number?  

Thanks if anyone may provide the answer.

Ko-Whe Chang
FileNet Corporation

 
 
 

Upgrading AIX from V3.2.2 to V3.2.3

Post by Charles Hann » Fri, 30 Oct 1992 02:42:27



Quote:Chang) writes:

> We were upgrading our AIX RISC-6000 system from Version 3.2.2 to
> 3.2.3 and after committing all update PTFs from 3.2.3, We typed
> 'lslpp -h bos.obj' and noticed the output still showed that the
> system is running at 3.2.0 level. Should it show 3.2.3 level instead?  

No.  There is no 3.2.3; technically, it is 3.2.0 with a bunch of
"selective enhance<cough>ments" installed.

This is stupid, actually.  They *could* just make a dummy PTF that
updates the version numbers, give it prereqs of whatever else is on the
tape, and put that at the end.  Thus, you install everything, your
machine says you're at 3.2.3.

Instead, I currently have to send them a `lslpp -h' listing every time
I report a bug, because they have no idea what I have installed.

Maybe some day...

--

 /\ \   PGP public key available on request.  MIME and NextMail accepted.
Scheme  White hetero* atheist male (WHAM) pride!

 
 
 

Upgrading AIX from V3.2.2 to V3.2.3

Post by David L. Cr » Thu, 29 Oct 1992 13:41:14



>We were upgrading our AIX RISC-6000 system from Version 3.2.2 to 3.2.3 and
>after committing all update PTFs from 3.2.3,
>We typed 'lslpp -h bos.obj' and noticed the output still showed that
>the system is running at 3.2.0 level. Should it show 3.2.3 level instead?  

    The term "AIX Version 3.2.3" refers to a collection of PTFs (selective
  enhancements and selective fixes) that are applied to a GOLD AIX 3.2
  system.  No matter how many PTFs you apply to your system, you have a
  GOLD 3.2 (3.2.0.0) system with a certain mix of PTFs.  The command

      lslpp -h bos.obj

  will always return:

  Name
  --------------------
    Fix Id  Release         Status     Action     Date       Time     User Name
    ------- --------------- ---------- ---------- ---------- -------- ----------
Path: /usr/lib/objrepos
  bos.obj
            03.02.0000.0000 COMPLETE   COMMIT     12/31/69   18:00:00 root

Path: /etc/objrepos
  bos.obj
            03.02.0000.0000 COMPLETE   COMMIT     12/31/69   18:00:00 root

  This will be true no matter how many PTFs you apply.
--
 ----------- Opinions expressed are mine, not my employer's ----------

 |  IBM AWS Graphics Systems    |  IBM VNET: CROW at AUSTIN          |
 |  Austin, Republic of Texas   |  (512) 838-1134  T/L 678-1134      |

 
 
 

Upgrading AIX from V3.2.2 to V3.2.3

Post by Gerry Hawki » Wed, 04 Nov 1992 00:06:12





>>We were upgrading our AIX RISC-6000 system from Version 3.2.2 to 3.2.3 and
>>after committing all update PTFs from 3.2.3,
>>We typed 'lslpp -h bos.obj' and noticed the output still showed that
>>the system is running at 3.2.0 level. Should it show 3.2.3 level instead?  

>    The term "AIX Version 3.2.3" refers to a collection of PTFs (selective
>  enhancements and selective fixes) that are applied to a GOLD AIX 3.2
>  system.  No matter how many PTFs you apply to your system, you have a
>  GOLD 3.2 (3.2.0.0) system with a certain mix of PTFs.  The command

>      lslpp -h bos.obj

>  will always return:

>  Name
>  --------------------
>  Fix Id  Release         Status     Action     Date       Time     User Name
>  ------- --------------- ---------- ---------- ---------- -------- ----------
>Path: /usr/lib/objrepos
>  bos.obj
>            03.02.0000.0000 COMPLETE   COMMIT     12/31/69   18:00:00 root

>Path: /etc/objrepos
>  bos.obj
>            03.02.0000.0000 COMPLETE   COMMIT     12/31/69   18:00:00 root

>  This will be true no matter how many PTFs you apply.
>--
> ----------- Opinions expressed are mine, not my employer's ----------

> |  IBM AWS Graphics Systems    |  IBM VNET: CROW at AUSTIN          |
> |  Austin, Republic of Texas   |  (512) 838-1134  T/L 678-1134      |

I had opened an problem report against uname() for this very reason.
It was rejected as the current behavior of uname() was not considered
to be broken. (ie. "works as designed")

My motivation behind that request was fairly straight forward. I wanted
to know what level of AIX is on a given RS6000. This is very important
for us as our application is generally only qualified under the most
current OS level. We are unable to differentiate between AIX 3.2.0,
3.2.1, 3.2.2 and now 3.2.3! This will cause us and our customers
problems.

Currently this command has a an option, "-r", which should print the
operating system release level. From the man page on the RS6000:
   -r  Displays the release number of the operating system.
       Currently this returns the value '2'.   :-(

In comparison from a current SGI machine:
   -r  Print the operating system release. This string has one of the
       following forms: m.n or m.n.a where m is the major release
       number, n is the minor release number and a is the (optional)
       maintenance level of the release; e.g. 3.2 or 3.2.1.
       Currently this returns the value '4.0.5'.   :-)

Also, from a SUN:
   -r  Print the operating system release.
       On a SparcStation 1 I get 4.1.1.   :-)

And from an HP:
   -r  Print the operating system release.
       On a 700 it gives: A.08.07   :-)

I am very frustrated by the release policy that IBM has regarding AIX.
Am I expected to write a program to parse the output of an lslpp comand
to check for the fixes that we need to properly run our application?

When can we expect something other than another collection of selective
fixes and enhancments from IBM?

----------------------------------------|       ///\

A product of genius is also,            |     //  \\ __   Corporate Headquaters
a product of enthusiasm.                |    //    \\\/   TORONTO, Canada

 
 
 

Upgrading AIX from V3.2.2 to V3.2.3

Post by Max Makl » Sat, 07 Nov 1992 10:58:56


:^()  
:^()  I had opened an problem report against uname() for this very reason.
:^()  It was rejected as the current behavior of uname() was not considered
:^()  to be broken. (ie. "works as designed")
:^()  
:^()  My motivation behind that request was fairly straight forward. I wanted
:^()  to know what level of AIX is on a given RS6000. This is very important
:^()  for us as our application is generally only qualified under the most
:^()  current OS level. We are unable to differentiate between AIX 3.2.0,
:^()  3.2.1, 3.2.2 and now 3.2.3! This will cause us and our customers
:^()  problems.
:^()  
:^()  Currently this command has a an option, "-r", which should print the
:^()  operating system release level. From the man page on the RS6000:
:^()     -r  Displays the release number of the operating system.
:^()         Currently this returns the value '2'.   :-(
:^()  
:^()  In comparison from a current SGI machine:
:^()     -r  Print the operating system release. This string has one of the
:^()         following forms: m.n or m.n.a where m is the major release
:^()         number, n is the minor release number and a is the (optional)
:^()         maintenance level of the release; e.g. 3.2 or 3.2.1.
:^()         Currently this returns the value '4.0.5'.   :-)
:^()  
:^()  Also, from a SUN:
:^()     -r  Print the operating system release.
:^()         On a SparcStation 1 I get 4.1.1.   :-)
:^()  
:^()  And from an HP:
:^()     -r  Print the operating system release.
:^()         On a 700 it gives: A.08.07   :-)
:^()  
:^()  
:^()  I am very frustrated by the release policy that IBM has regarding AIX.
:^()  Am I expected to write a program to parse the output of an lslpp comand
:^()  to check for the fixes that we need to properly run our application?
:^()  
:^()  When can we expect something other than another collection of selective
:^()  fixes and enhancments from IBM?
:^()  

There are not the only ones, SCO's uname is also broken on SCO 3.2.4.
uname -r return 2 and uname -v returns 2.  It's a nightmare for software
installs that depend on a reliable value.

Max
--
Max Maklin                                                P.O. Box 9707
Technical Analyst                                  3755 Riverside Drive
Cognos Incorporated                              Ottawa, Ontario CANADA

 
 
 

Upgrading AIX from V3.2.2 to V3.2.3

Post by r.. » Sun, 08 Nov 1992 02:01:46




>:^()  My motivation behind that request was fairly straight forward. I wanted
>:^()  to know what level of AIX is on a given RS6000. This is very important
>:^()  for us as our application is generally only qualified under the most
>:^()  current OS level. We are unable to differentiate between AIX 3.2.0,
>:^()  3.2.1, 3.2.2 and now 3.2.3! This will cause us and our customers
>:^()  problems.

I think you are going to have a problem here as 3.2.2, 3.2.3, etc...
aren't real levels in the sense that they were in AIX 3.1.*. Most
people just selectively apply PTFs to fix the problems that effect
them. I think that there are supposed to be some type of cumulative
fixes in the future that can really be considered level changes.

At least this is my understanding.