SEO

Hi evenybody,am new to nim but i managed to get it to work for unattended
installation from base OS's.
Now i want to create a new resource with the latest Maintenance level bundle
but after defining the source i get the following messge: (e.g for the
latest 02 bundle for AIX5.2)

warning: 0042-267 c_mk_lpp_source: The defined lpp_source does not have the
"simages" attribute because one or more of the following packages are
missing:
bos
bos.diag
bos.sysmgt
...........

Can anyone help me and tel me what to do to make this work and usable ?
Thanks for any hep.

Matthias

"Matthias" <cronos4me@yahoo.de> wrote in message news:<OliBb.10359$8p5.6888@news.cpqcorp.net>...
> Hi evenybody,am new to nim but i managed to get it to work for unattended
> installation from base OS's.
> Now i want to create a new resource with the latest Maintenance level bundle
> but after defining the source i get the following messge: (e.g for the
> latest 02 bundle for AIX5.2)
>
> warning: 0042-267 c_mk_lpp_source: The defined lpp_source does not have the
> "simages" attribute because one or more of the following packages are
> missing:
> bos
> bos.diag
> bos.sysmgt
> ..........
>
> Can anyone help me and tel me what to do to make this work and usable ?
> Thanks for any hep.
>
> Matthias

If the lpp_Source only contains the filesets from RML02, then this
isn't a problem. But if you wanted to install AIX from this
lpp_source, you need the base level filesets as well, plus of course
creating/upgrading the SPOT.

Steve

"Steve Nottingham" <steve@wakefieldrfc.freeserve.co.uk> wrote in message
news:42862645.0312090952.71bb2c90@posting.google.c om...
> "Matthias" <cronos4me@yahoo.de> wrote in message
news:<OliBb.10359$8p5.6888@news.cpqcorp.net>...
> > Hi evenybody,am new to nim but i managed to get it to work for
unattended
> > installation from base OS's.
> > Now i want to create a new resource with the latest Maintenance level
bundle
> > but after defining the source i get the following messge: (e.g for the
> > latest 02 bundle for AIX5.2)
> >
> > warning: 0042-267 c_mk_lpp_source: The defined lpp_source does not have
the
> > "simages" attribute because one or more of the following packages are
> > missing:
> > bos
> > bos.diag
> > bos.sysmgt
> > ..........
> >
> > Can anyone help me and tel me what to do to make this work and usable ?
> > Thanks for any hep.
> >
> > Matthias
>
> If the lpp_Source only contains the filesets from RML02, then this
> isn't a problem. But if you wanted to install AIX from this
> lpp_source, you need the base level filesets as well, plus of course
> creating/upgrading the SPOT.
>
> Steve

Hi,

thanks for this info but i am not sure what to do now, i have installed a
base 52000 and i have this lpp_source PB_52002 which just contains the
MRL02. now i want to 'upgrade' my installed 5.2 with this lpp_source which
fails - what do i have to do to make this work?
any help is very much appreciated...

bye
Matthias

"Matthias" <cronos4me@yahoo.de> wrote in message news:<UGhDb.10656$jt4.5546@news.cpqcorp.net>...
> "Steve Nottingham" <steve@wakefieldrfc.freeserve.co.uk> wrote in message
> news:42862645.0312090952.71bb2c90@posting.google.c om...
> > "Matthias" <cronos4me@yahoo.de> wrote in message
> news:<OliBb.10359$8p5.6888@news.cpqcorp.net>...
> > > Hi evenybody,am new to nim but i managed to get it to work for
> unattended
> > > installation from base OS's.
> > > Now i want to create a new resource with the latest Maintenance level
> bundle
> > > but after defining the source i get the following messge: (e.g for the
> > > latest 02 bundle for AIX5.2)
> > >
> > > warning: 0042-267 c_mk_lpp_source: The defined lpp_source does not have
> the
> > > "simages" attribute because one or more of the following packages are
> > > missing:
> > > bos
> > > bos.diag
> > > bos.sysmgt
> > > ..........
> > >
> > > Can anyone help me and tel me what to do to make this work and usable ?
> > > Thanks for any hep.
> > >
> > > Matthias
> >
> > If the lpp_Source only contains the filesets from RML02, then this
> > isn't a problem. But if you wanted to install AIX from this
> > lpp_source, you need the base level filesets as well, plus of course
> > creating/upgrading the SPOT.
> >
> > Steve
>
> Hi,
>
> thanks for this info but i am not sure what to do now, i have installed a
> base 52000 and i have this lpp_source PB_52002 which just contains the
> MRL02. now i want to 'upgrade' my installed 5.2 with this lpp_source which
> fails - what do i have to do to make this work?
> any help is very much appreciated...
>
> bye
> Matthias

You want to upgrade a node with the update ? How does it fail ? What
error messages ?

Steve

"Steve Nottingham" <steve@wakefieldrfc.freeserve.co.uk> wrote in message
news:42862645.0312151443.4bec68a8@posting.google.c om...
> "Matthias" <cronos4me@yahoo.de> wrote in message
news:<UGhDb.10656$jt4.5546@news.cpqcorp.net>...
> > "Steve Nottingham" <steve@wakefieldrfc.freeserve.co.uk> wrote in message
> > news:42862645.0312090952.71bb2c90@posting.google.c om...
> > > "Matthias" <cronos4me@yahoo.de> wrote in message
> > news:<OliBb.10359$8p5.6888@news.cpqcorp.net>...
> > > > Hi evenybody,am new to nim but i managed to get it to work for
> > unattended
> > > > installation from base OS's.
> > > > Now i want to create a new resource with the latest Maintenance
level
> > bundle
> > > > but after defining the source i get the following messge: (e.g for
the
> > > > latest 02 bundle for AIX5.2)
> > > >
> > > > warning: 0042-267 c_mk_lpp_source: The defined lpp_source does not
have
> > the
> > > > "simages" attribute because one or more of the following packages
are
> > > > missing:
> > > > bos
> > > > bos.diag
> > > > bos.sysmgt
> > > > ..........
> > > >
> > > > Can anyone help me and tel me what to do to make this work and
usable ?
> > > > Thanks for any hep.
> > > >
> > > > Matthias
> > >
> > > If the lpp_Source only contains the filesets from RML02, then this
> > > isn't a problem. But if you wanted to install AIX from this
> > > lpp_source, you need the base level filesets as well, plus of course
> > > creating/upgrading the SPOT.
> > >
> > > Steve
> >
> > Hi,
> >
> > thanks for this info but i am not sure what to do now, i have installed
a
> > base 52000 and i have this lpp_source PB_52002 which just contains the
> > MRL02. now i want to 'upgrade' my installed 5.2 with this lpp_source
which
> > fails - what do i have to do to make this work?
> > any help is very much appreciated...
> >
> > bye
> > Matthias
>
> You want to upgrade a node with the update ? How does it fail ? What
> error messages ?
>
> Steve


Hi Steve,

what i have done so far:

i created a patch bundel resource with:
nim -o define - t lpp_source -a location=/nim/lpp_source/patch/5.2/02 - a
server=master PB52002
i then installed a new system with 5200 and wanted to 'patch' to new 52002
level with the bundle i have built.
i have done this by choosing 'update software' in wsm.
this worked fine with 51003 upgrade to 51005 budle i have built in the same
way.
with 52002 bundle the following error message shows up:

FILESET STATISTICS
------------------------
233 Selected to be installed, of which:
233 Passed pre-installation verification
6 Additional requisits to be automatically installed

LICENSE AGREEMENT FAILURES
---------------------------------------
The software you have selected for installation contain license
agreement(s) that must be accepted before proceeding. Failure to accept
the license term will prevent the installation of the software.
Accept the licencse agreement by selecting "yes" in the
"Accept new license agreements" field or by specifying
the -Y option to the installp command.

Filesets Requiring Software License Acceptance
------------------------------------------------
devices.pci.14106602.ucode

0042-175 nim: processing error encountered on "master":
0042-001 m_cust: processing error encountert on "tcaix01":
0042-175 c_script: An unexpected result was returned by the
"/usr/sbin/installp" command:
See the log file:
/var/adm/ras/nim.installp
for details or use the "showlog" operation.

It's clear that it interrupts because of this missing license agreement but
how can i accept it and where?.

hope you can give me the deciding hint.

thanks a lot,
Matthias

>
> what i have done so far:
>
> i created a patch bundel resource with:
> nim -o define - t lpp_source -a location=/nim/lpp_source/patch/5.2/02 - a
> server=master PB52002
> i then installed a new system with 5200 and wanted to 'patch' to new 52002
> level with the bundle i have built.
> i have done this by choosing 'update software' in wsm.
> this worked fine with 51003 upgrade to 51005 budle i have built in the same
> way.
> with 52002 bundle the following error message shows up:
>
> FILESET STATISTICS
> ------------------------
> 233 Selected to be installed, of which:
> 233 Passed pre-installation verification
> 6 Additional requisits to be automatically installed
>
> LICENSE AGREEMENT FAILURES
> ---------------------------------------
> The software you have selected for installation contain license
> agreement(s) that must be accepted before proceeding. Failure to accept
> the license term will prevent the installation of the software.
> Accept the licencse agreement by selecting "yes" in the
> "Accept new license agreements" field or by specifying
> the -Y option to the installp command.
>
> Filesets Requiring Software License Acceptance
> ------------------------------------------------
> devices.pci.14106602.ucode
>
> 0042-175 nim: processing error encountered on "master":
> 0042-001 m_cust: processing error encountert on "tcaix01":
> 0042-175 c_script: An unexpected result was returned by the
> "/usr/sbin/installp" command:
> See the log file:
> /var/adm/ras/nim.installp
> for details or use the "showlog" operation.
>
> It's clear that it interrupts because of this missing license agreement but
> how can i accept it and where?.
>
> hope you can give me the deciding hint.
>
> thanks a lot,
> Matthia

OK, you need a resource for a bosinst.data file, if you look in / you
should find a file already there. I think the resource in NIM is
called bosinst_data, bit it will tell you in the NIM A to Z redbook or
the NIM manual.

Steve

On 16/12/03 7:19 pm, in article
42862645.0312161119.65212902@posting.google.com, "Steve Nottingham"
<steve@wakefieldrfc.freeserve.co.uk> wrote:

>>
>> what i have done so far:
>>
>> i created a patch bundel resource with:
>> nim -o define - t lpp_source -a location=/nim/lpp_source/patch/5.2/02 - a
>> server=master PB52002
>> i then installed a new system with 5200 and wanted to 'patch' to new 52002
>> level with the bundle i have built.
>> i have done this by choosing 'update software' in wsm.
>> this worked fine with 51003 upgrade to 51005 budle i have built in the same
>> way.
>> with 52002 bundle the following error message shows up:
>>
>> FILESET STATISTICS
>> ------------------------
>> 233 Selected to be installed, of which:
>> 233 Passed pre-installation verification
>> 6 Additional requisits to be automatically installed
>>
>> LICENSE AGREEMENT FAILURES
>> ---------------------------------------
>> The software you have selected for installation contain license
>> agreement(s) that must be accepted before proceeding. Failure to accept
>> the license term will prevent the installation of the software.
>> Accept the licencse agreement by selecting "yes" in the
>> "Accept new license agreements" field or by specifying
>> the -Y option to the installp command.
>>
>> Filesets Requiring Software License Acceptance
>> ------------------------------------------------
>> devices.pci.14106602.ucode
>>

This is a bug in NIM. I've seen this recently. The new smitty install now
caters for licenses but NIM update_all doesn't! As such, you're trying to
update a file bun NIM doesn't give you the option to accept the license
file.

The solution is a two part. First, use NIM -> Install from all available
software and only select the devices.pci.14106602.ucode. You will now be
able to accept the license.

When finished, then do a NIM update_all and you won't be asked to accept the
license as you've already installed the problem fileset.

Hope IBM looks at this. It's a bit of a pain but not too bad.

"Nigel P. Longbottom" <aqsc42@dsl.pipex.com> wrote in message
news:BC060AA3.39A2%aqsc42@dsl.pipex.com...
> On 16/12/03 7:19 pm, in article
> 42862645.0312161119.65212902@posting.google.com, "Steve Nottingham"
> <steve@wakefieldrfc.freeserve.co.uk> wrote:
>
> >>
> >> what i have done so far:
> >>
> >> i created a patch bundel resource with:
> >> nim -o define - t lpp_source -a location=/nim/lpp_source/patch/5.2/02 -
a
> >> server=master PB52002
> >> i then installed a new system with 5200 and wanted to 'patch' to new
52002
> >> level with the bundle i have built.
> >> i have done this by choosing 'update software' in wsm.
> >> this worked fine with 51003 upgrade to 51005 budle i have built in the
same
> >> way.
> >> with 52002 bundle the following error message shows up:
> >>
> >> FILESET STATISTICS
> >> ------------------------
> >> 233 Selected to be installed, of which:
> >> 233 Passed pre-installation verification
> >> 6 Additional requisits to be automatically installed
> >>
> >> LICENSE AGREEMENT FAILURES
> >> ---------------------------------------
> >> The software you have selected for installation contain license
> >> agreement(s) that must be accepted before proceeding. Failure to accept
> >> the license term will prevent the installation of the software.
> >> Accept the licencse agreement by selecting "yes" in the
> >> "Accept new license agreements" field or by specifying
> >> the -Y option to the installp command.
> >>
> >> Filesets Requiring Software License Acceptance
> >> ------------------------------------------------
> >> devices.pci.14106602.ucode
> >>
>
> This is a bug in NIM. I've seen this recently. The new smitty install now
> caters for licenses but NIM update_all doesn't! As such, you're trying to
> update a file bun NIM doesn't give you the option to accept the license
> file.
>
> The solution is a two part. First, use NIM -> Install from all available
> software and only select the devices.pci.14106602.ucode. You will now be
> able to accept the license.
>
> When finished, then do a NIM update_all and you won't be asked to accept
the
> license as you've already installed the problem fileset.
>
> Hope IBM looks at this. It's a bit of a pain but not too bad.
>
>


Hi Nigel,

thanks for this information, you were right, installing the
devices.pci.14106602.ucode
upfront and afterwards the rest of the ML52002 bundle solved the problem.

Thank you very very much for this workaround !

regards,
Matthias

In article <H5zEb.11130$IJ.1661@news.cpqcorp.net>,
Matthias <cronos4me@yahoo.de> wrote:
>
>"Nigel P. Longbottom" <aqsc42@dsl.pipex.com> wrote in message
>news:BC060AA3.39A2%aqsc42@dsl.pipex.com...
>> On 16/12/03 7:19 pm, in article
>> 42862645.0312161119.65212902@posting.google.com, "Steve Nottingham"
>> <steve@wakefieldrfc.freeserve.co.uk> wrote:
>>
>> >>
<snip>
>>
>> This is a bug in NIM. I've seen this recently. The new smitty install now
>> caters for licenses but NIM update_all doesn't! As such, you're trying to
>> update a file bun NIM doesn't give you the option to accept the license
>> file.
>>
>> The solution is a two part. First, use NIM -> Install from all available
>> software and only select the devices.pci.14106602.ucode. You will now be
>> able to accept the license.
>>
>> When finished, then do a NIM update_all and you won't be asked to accept
>the
>> license as you've already installed the problem fileset.
>>
>> Hope IBM looks at this. It's a bit of a pain but not too bad.
>>
>>
>
>
>Hi Nigel,
>
>thanks for this information, you were right, installing the
>devices.pci.14106602.ucode
>upfront and afterwards the rest of the ML52002 bundle solved the problem.
>
>Thank you very very much for this workaround !
>
>regards,
>Matthias
>
>

Also, the latest bos.rte.install (55 on my 5.1 box) fixes the issue of the
license field in the update_all screen.
--
"I'm a big fan of ignorance based techniques, because humans
have a lot of ignorance, and we want to play our strong suit."
Eric Lander New Scientist