SEO

Recently upgraded from 4.3.3ML-11 to Aix 5.2ML-02
Everything running fine, all apps are ok, no errors.
Here is the output from the lppchk command, and output from
the lslpp command, for bos.rte
I don't understand why lppchk would indicate inconsistent state, given
the output of lslpp.
Any comments welcome.

(/home/wdd) # lppchk -v
lppchk: The following filesets need to be installed or corrected to
bring
the system to a consistent state:

bos.rte v<5 (not installed; requisite
fileset)

(/home/wdd) # lslpp -L |grep bos.rte |grep Runtime
bos.rte 5.2.0.12 C F Base Operating
System Runtime

I can't imagine bos.rte is hosed, given all apps on system running
perfectly.

Don Davis wrote:
>
> Recently upgraded from 4.3.3ML-11 to Aix 5.2ML-02
> Everything running fine, all apps are ok, no errors.
> Here is the output from the lppchk command, and output from
> the lslpp command, for bos.rte
> I don't understand why lppchk would indicate inconsistent state, given
> the output of lslpp.
> Any comments welcome.
>
> (/home/wdd) # lppchk -v
> lppchk: The following filesets need to be installed or corrected to
> bring
> the system to a consistent state:
>
> bos.rte v<5 (not installed; requisite
> fileset)
>
> (/home/wdd) # lslpp -L |grep bos.rte |grep Runtime
> bos.rte 5.2.0.12 C F Base Operating
> System Runtime
>
> I can't imagine bos.rte is hosed, given all apps on system running
> perfectly.

It isn't bos.rte that is hosed.
The problem is that you have another fileset installed
which has an explicity pre-req for "bos.rte v<5". Note
the "v<5" which means it wants to see bos.rte at a level
less than version 5. This may be some package which is
only supposed to run on AIX v4. I think the command:
lslpp -p all
will show you which fileset is looking for bos.rte <5.

Paul Landay

Paul Landay <landay@us.ibm.com> wrote in message news:<40CDBB43.75E0524C@us.ibm.com>...
> Don Davis wrote:
> >
> > Recently upgraded from 4.3.3ML-11 to Aix 5.2ML-02
> > Everything running fine, all apps are ok, no errors.
> > Here is the output from the lppchk command, and output from
> > the lslpp command, for bos.rte
> > I don't understand why lppchk would indicate inconsistent state, given
> > the output of lslpp.
> > Any comments welcome.
> >
> > (/home/wdd) # lppchk -v
> > lppchk: The following filesets need to be installed or corrected to
> > bring
> > the system to a consistent state:
> >
> > bos.rte v<5 (not installed; requisite
> > fileset)
> >


> > (/home/wdd) # lslpp -L |grep bos.rte |grep Runtime
> > bos.rte 5.2.0.12 C F Base Operating
> > System Runtime
> >
> > I can't imagine bos.rte is hosed, given all apps on system running
> > perfectly.
>
> It isn't bos.rte that is hosed.
> The problem is that you have another fileset installed
> which has an explicity pre-req for "bos.rte v<5". Note
> the "v<5" which means it wants to see bos.rte at a level
> less than version 5. This may be some package which is
> only supposed to run on AIX v4. I think the command:
> lslpp -p all
> will show you which fileset is looking for bos.rte <5.
>
> Paul Landay




must be this:

xlC.rte 6.0.0.0 At least 1 of the following must be installed {
At least 3 of the following must be installed {
*prereq bos.rte v<5
*prereq bos.rte v=4 r=3
*prereq xlC.aix43.rte 6.0.0.0
}
At least 2 of the following must be installed {
*prereq bos.rte v=5 r=0
*prereq xlC.aix50.rte 6.0.0.0

lslpp shows:

(/home/wdd) # lslpp -L |grep xlC
xlC.aix50.rte 6.0.0.0 C F C Set ++ Runtime for AIX 5.0
xlC.cpp 5.0.2.0 C F C for AIX Preprocessor
xlC.msg.en_US.cpp 5.0.2.0 C F C for AIX Preprocessor
xlC.msg.en_US.rte 6.0.0.0 C F C Set ++ Runtime
xlC.rte 6.0.0.0 C F C Set ++ Runtime

Does aix 5.2 require different C compiler than aix 4.3.3?

Don Davis wrote:
> Paul Landay <landay@us.ibm.com> wrote in message news:<40CDBB43.75E0524C@us.ibm.com>...
>
>>Don Davis wrote:
>>
>>>Recently upgraded from 4.3.3ML-11 to Aix 5.2ML-02
>>>Everything running fine, all apps are ok, no errors.
>>>Here is the output from the lppchk command, and output from
>>>the lslpp command, for bos.rte
>>>I don't understand why lppchk would indicate inconsistent state, given
>>>the output of lslpp.
>>>Any comments welcome.
>>>
>>>(/home/wdd) # lppchk -v
>>>lppchk: The following filesets need to be installed or corrected to
>>>bring
>>> the system to a consistent state:
>>>
>>> bos.rte v<5 (not installed; requisite
>>>fileset)
>>>
>
>
>
>>>(/home/wdd) # lslpp -L |grep bos.rte |grep Runtime
>>> bos.rte 5.2.0.12 C F Base Operating
>>>System Runtime
>>>
>>>I can't imagine bos.rte is hosed, given all apps on system running
>>>perfectly.
>>
>>It isn't bos.rte that is hosed.
>>The problem is that you have another fileset installed
>>which has an explicity pre-req for "bos.rte v<5". Note
>>the "v<5" which means it wants to see bos.rte at a level
>>less than version 5. This may be some package which is
>>only supposed to run on AIX v4. I think the command:
>> lslpp -p all
>>will show you which fileset is looking for bos.rte <5.
>>
>>Paul Landay
>
>
>
>
>
> must be this:
>
> xlC.rte 6.0.0.0 At least 1 of the following must be installed {
> At least 3 of the following must be installed {
> *prereq bos.rte v<5
> *prereq bos.rte v=4 r=3
> *prereq xlC.aix43.rte 6.0.0.0
> }
> At least 2 of the following must be installed {
> *prereq bos.rte v=5 r=0
> *prereq xlC.aix50.rte 6.0.0.0
>
> lslpp shows:
>
> (/home/wdd) # lslpp -L |grep xlC
> xlC.aix50.rte 6.0.0.0 C F C Set ++ Runtime for AIX 5.0
> xlC.cpp 5.0.2.0 C F C for AIX Preprocessor
> xlC.msg.en_US.cpp 5.0.2.0 C F C for AIX Preprocessor
> xlC.msg.en_US.rte 6.0.0.0 C F C Set ++ Runtime
> xlC.rte 6.0.0.0 C F C Set ++ Runtime
>
> Does aix 5.2 require different C compiler than aix 4.3.3?

Well, sure it does. But what confuses me is that my memory says that 6
is the minimum required for 5.2 and is backwards compatable witht 4.3.3
(it was introduced while 4.3.3 was still under maintenance).

Have you applied the bundle of fixes for the C compiler? I don't have
an ML2 pile handy to see if they are included there, but my memory
(there it is again) says they are not.

Just a SWAG.

Don Davis wrote:
> must be this:
> xlC.rte 6.0.0.0 At least 1 of the following must be installed {
> At least 3 of the following must be installed {
> *prereq bos.rte v<5
> *prereq bos.rte v=4 r=3
> *prereq xlC.aix43.rte 6.0.0.0
> }
> At least 2 of the following must be installed {
> *prereq bos.rte v=5 r=0
> *prereq xlC.aix50.rte 6.0.0.0
> lslpp shows:
> (/home/wdd) # lslpp -L |grep xlC
> xlC.aix50.rte 6.0.0.0 C F C Set ++ Runtime for AIX 5.0
> xlC.cpp 5.0.2.0 C F C for AIX Preprocessor
> xlC.msg.en_US.cpp 5.0.2.0 C F C for AIX Preprocessor
> xlC.msg.en_US.rte 6.0.0.0 C F C Set ++ Runtime
> xlC.rte 6.0.0.0 C F C Set ++ Runtime
>
> Does aix 5.2 require different C compiler than aix 4.3.3?

The /usr/lpp/bos/README file has an item which lists
the levels of the C compiler that are supported and
what PTFs are needed.

Paul Landay

No problem exists. If you'll look at the prereqs for xlC.rte again:

> xlC.rte 6.0.0.0 At least 1 of the following must be installed {
> At least 3 of the following must be installed {
> *prereq bos.rte v<5
> *prereq bos.rte v=4 r=3
> *prereq xlC.aix43.rte 6.0.0.0
> }
> At least 2 of the following must be installed {
> *prereq bos.rte v=5 r=0
> *prereq xlC.aix50.rte 6.0.0.0
> }

This means:

EITHER:

(bos.rte before 5.0, bos.rte at 4.3, AND xlC.aix43.rte 6.0)

OR

(bos.rte 5.0 AND xlC.aix50.rte 6.0)

You only need to satisfiy either set; you have bos.rte at least 5.0 and
you also have xlC.aix50.rte at least 6.0.0.0. So you are all good.
Nothing's broken.

How do you figure 'EITHER'? Well, it says 'At least 1 of the following
must be installed', and there are only two (sets of) options.

-Dan

In article <slrnccsnj3.ke6.usenet@gaia.roc2.gblx.net>, Dan Foster <usenet@evilphb.org> wrote:
> No problem exists. If you'll look at the prereqs for xlC.rte again:
>
> You only need to satisfiy either set; you have bos.rte at least 5.0 and
> you also have xlC.aix50.rte at least 6.0.0.0. So you are all good.
> Nothing's broken.

That may be true, but upon thinking about it, I'm suddenly struck by the
thought it may be a bug in lppchk if it's expecting to see every
possible prereq satisfied, including non-applicable ones.

So there may be a problem, but it doesn't seem to be with your setup.

-Dan

post output of

lppchk -v -m3

Holger van Koll <holger@vankoll.de> wrote in message news:<1087301402.937993@ftpgate>...
> post output of
>
> lppchk -v -m3


lppchk -v -m3 returns no output