Run db2updv8 after installing fixpack 9a?

[Mark A]

On the forum at ibm.software.db2.udb it was mentioned that one should run
db2updv8 after installing fixpack 9 (or 9a). But there is no mention of
db2updv8 in FP9a installation readme file. Anyone know what is going on?

[Gert van der Kooij]

In article <AM*****************************************@comca st.com>,
Mark A (no****@nowhere.com) says...

On the forum at ibm.software.db2.udb it was mentioned that one should run
db2updv8 after installing fixpack 9 (or 9a). But there is no mention of
db2updv8 in FP9a installation readme file. Anyone know what is going on?

After installing a fixpack I always run db2updv<7/8>. Just to be
sure. It isn't mentioned in every readme file but it's just one of
those things. I also always rebind db2ubind.lst and db2cli.lst.

With FP9a it should have been in the readme because new functions are
available only after running db2updv8.

[Mark A]

"Gert van der Kooij" <ge**@invalid.nl> wrote in message

After installing a fixpack I always run db2updv<7/8>. Just to be
sure. It isn't mentioned in every readme file but it's just one of
those things. I also always rebind db2ubind.lst and db2cli.lst.

With FP9a it should have been in the readme because new functions are
available only after running db2updv8.

Rebind db2ubind.lst and db2cli.lst are mentioned in the readme file for FP9a
(and every readme file I recall seeing).

What do mean "it's just one of those things"? Don't people read RTFM
anymore?. There is no mention of db2updv8 in the FP9a readme file. Since
when are people expected to correctly install fixpacks if the instructions
are bad?

So what am I supposed to do now? Tell my customer that I need to schedule
another outage because IBM fixpack install instructions were incorrect? I
doubt that my customers would even believe me and instead blame me for the
mistake.

Someone in IBM management needs to roll some heads. The installation
instructions have always been hard to read and poorly organized, but this is
gross negligence.

[Gert van der Kooij]

In article <aa********************@comcast.com>, Mark A
(no****@nowhere.com) says...

"Gert van der Kooij" <ge**@invalid.nl> wrote in message

After installing a fixpack I always run db2updv<7/8>. Just to be
sure. It isn't mentioned in every readme file but it's just one of
those things. I also always rebind db2ubind.lst and db2cli.lst.

With FP9a it should have been in the readme because new functions are
available only after running db2updv8.

Rebind db2ubind.lst and db2cli.lst are mentioned in the readme file for FP9a
(and every readme file I recall seeing).

What do mean "it's just one of those things"? Don't people read RTFM
anymore?. There is no mention of db2updv8 in the FP9a readme file. Since
when are people expected to correctly install fixpacks if the instructions
are bad?

So what am I supposed to do now? Tell my customer that I need to schedule
another outage because IBM fixpack install instructions were incorrect? I
doubt that my customers would even believe me and instead blame me for the
mistake.

Someone in IBM management needs to roll some heads. The installation
instructions have always been hard to read and poorly organized, but this is
gross negligence.

I ran into it after installing some V7 update which wasn't mentioned
also. Since then I always run db2updv.. But if you don't need to use
the new functionality your customers won't need another outage.

I agree it should have been mentioned in the readme, that's just 'one
of those things'. Updating the docs and making them available to the
customers when adding functionality is another one.

[Gert van der Kooij]

In article <aa********************@comcast.com>, Mark A
(no****@nowhere.com) says...

Mark, something seems to be wrong with the date on your posts. In my
newsreader it looks like they are sent at 05:36 on august 21 western
europian time ??

[Mark A]

"Gert van der Kooij" <ge**@invalid.nl> wrote in message

Mark, something seems to be wrong with the date on your posts. In my
newsreader it looks like they are sent at 05:36 on august 21 western
europian time ??

I have fixed it now. I had to reset the CMOS on my machine yesterday after
flashing my bios, and I entered the new date incorrectly (PM instead of AM).
Thanks.

[mryan]

db2updv8 *is* documented in the FP10 fixpak readme. We have
investigated why it was not included in the FP9 fixpak readme, and we
are making process changes to correct the root cause of the problem.