Thanks. Its location makes sense when one stops and thinks about it!!
I guess one learns every day
Merci, Pierre.
--
Pierre Saint-Jacques
SES Consultants Inc.
514-737-4515
"Jean-Marc Blaise" <nobody@nowhere.com> a écrit dans le message de
news:423686e6$0$19357$8fcfb975@news.wanadoo.fr...
> Pierre, it's located in the DB2 code only,
> ESE\DB2\WINDOWS\UTILITIES\DB2IPRUNE.
>
> Darin, thanks for this further information.
>
> Regards,
>
> Jean-Marc
>
> "Pierre Saint-Jacques" <sescons@invalid.net> a écrit dans le message de
> news:lmtZd.55392$WM1.1220622@wagner.videotron.net. ..
> > Jeaqn-Marc, I search for the db2iprune command on my DB2 PDE B.82 Fix#7a
> and
> > it tells me it can't find this.
> > Is this a Windows command? and where does it "rest".
> > Thanks for the help, Pierre.
> >
> > --
> > Pierre Saint-Jacques
> > SES Consultants Inc.
> > 514-737-4515
> > "Darin McBride" <dmcbride@naboo.to.org.no.spam.for.me> a écrit dans le
> > message de news:gw9Zd.670249$Xk.353112@pd7tw3no...
> > > Jean-Marc Blaise wrote:
> > >
> > > > "Darin McBride" <dmcbride@naboo.to.org.no.spam.for.me> a écrit dans
le
> > > > message de news:LHQYd.660992$6l.35593@pd7tw2no...
> > > >
> > > >> This is complex solely because you gave a list of what you want to
> > > >> keep, rather than what you want to remove. If you want to remove
all
> > > >> German and Polish support, just run:
> > > >>
> > > >> rm IBM_db2{ms,jh,ch}{de,pl}81*.rpm
> > > >>
> > > >> I'm not sure that this really is any more complicated (for a unix
> user)
> > > >> than db2iprune (for a windows user).
> > > >
> > > > Thanks for your reply. The thing you don't mention about db2iprune
is
> > that
> > > > you work thru a list of components you uncomment to make them
remove.
> Of
> > > > course, on windows, the CAB files have such a complicated name that
> you
> > > > cannot guess.
> > >
> > > :-) Not all the CAB files are directly visible in the list of
> > > components, I think. They're inferred (e.g., if A and B require C,
and
> > > C is not visible, and you select to remove both A and B, I think C
gets
> > > removed automatically). That's just to make things just a bit more
> > > fun.
> > >
> > > > To remove on Unix or Linux for someone who doesn't know, you have to
> > > > analyse first all rpms or fileset and make a decision. Then, rm or
> > >
> > > You can get more info about each RPM or fileset using the OS install
> > > commands. For example, on Linux:
> > >
> > > $ rpm -qip IBM_db2mscn81-8.1.0-64.i386.rpm
> > >
> > > This will tell you more information about the RPM, if you're looking
at
> > > v8.2's CDs. (Adjust for the actual filenames in your fixpak)
> > >
> > > If you want more info on something that's installed, just remove the
> > > "p" in "-qip" and remove everything after and including the first "-":
> > >
> > > $ rpm -qi IBM_db2mscn81
> > >
> > > AIX has similar queries using lslpp - see the man pages for lslpp,
rpm,
> > > pkginfo, or swlist, depending on your unix/linux platform.
> > >
> > > > whatever can be used in a nutshell. For the example in the command
you
> > > > gave to remove Cerman and Polish support it seems to me the rpm list
> is
> > > > not complete in the command you gave: IBM_db2{ms,jh,ch}*.rpm, what
> about
> > > > IBM_db2de* ? Is it so simple that anyone knows to remove chinese
> > support,
> > > > you should remove *cn*, *Cn*, *CN* ?
> > >
> > > Ah, you point out what I missed. The "{ms,jh,ch}" part should
actually
> > > be "{ms,je,ch,de}" - de is for the Eclipse-based Documentation, new in
> > > v8.2, which is why I keep forgetting about it. This de has nothing to
> > > do with German, although there is an IBM_db2dede81 RPM for German
> > > documentation.
> > >
> > > Note that Chinese support comes in both ch and tw styles - for
> > > simplified and traditional Chinese, respectively.
> > >
> > > The simplest way to prune your fixpak is to look at what you actually
> > > have installed. Run:
> > >
> > > rpm -qa | grep IBM_db2.*81 | sed 's/-.*//' > /nfs/$hostname.rpmlist
> > >
> > > on each machine, where /nfs is a shared (writable) NFS partition, and
> > > $hostname is the local hostname (you can use `hostname` instead). You
> > > may need to put in a domain name if the hostname itself isn't unique
> > > (e.g., if your company has *.canada.nowhere.com and *.usa.nowhere.com,
> > > thus you could have a hostname "nobody" both in Canada and the US:
> > > nobody.canada.nowhere.com and nobody.usa.nowhere.com).
> > >
> > > Once you've got this master list, we want to create a real master
list.
> > > This step is somewhat optional, but you may find the results
> > > interesting nonetheless, and can speed up later steps. You can do
this
> > > like this:
> > >
> > > cat /nfs/*.rpmlist | sort | uniq > /tmp/complete.rpmlist
> > >
> > > This may take a bit, depending on how many machines you're doing this
> > > for. Note also we're creating the final list locally, not that it
> > > matters too much.
> > >
> > > Once you're here, you have a list of all the RPMs you care to keep.
> > > You don't need to know which one is which, what individual RPMs do, or
> > > anything. You just need to remove anything from the fixpak that isn't
> > > in this list - it won't be used later if it's not here.
> > >
> > > Note that once in a while, the Linux fixpaks have added extra RPMs to
a
> > > system that didn't already have them if they were now required. This
> > > happened once in v7 for all Linux systems, and once in v8 for
Linux/PPC
> > > and once in v8 for Linux/390. It's not likely to happen again.
> > >
> > > (I will likely need to update these instructions in v9.)
> > >
> >
>
>