DB2 OS/390 maintenance

Tina Hilton

DB2 OS/390 maintenance
I know that the subject regarding DB2 maintenance has been discussed several
times in the past, but I'd like a little more detail than was previously
given. At my previous jobs, we received monthly PUT tapes. When I wanted
to put maintenance on, I'd receive the maintenance and then apply all but
the last 2-3 tapes. Of course, we were always behind the times
release-wise, so there weren't very many PTFs to put on most of the time.

Now, I order a maintenance-only CBPDO. I actually did try to order an ESO
tape this time, but it wouldn't take all my FMIDs so I went back to the PDO.
I read in the included documentation that if you applied all the RSU*
sourceids then you would end up with a system that was thoroughly tested by
IBM. When I look at all the PTFs I received, though, there are quite a few
that (354 out of 1372) that don't have an RSU* sourceid assigned to it so
these would never go on with this method unless they were applied via the
GROUPEXTEND. I could just try to apply everything, but that makes me
nervous because of past problems with PTFs going PE just after I applied
them.

So, how do you guys do the apply? Do you apply everything on the PDO tape
that will go on? Do you use the SOURCEID(RSU*) keyword? Do you select all
PUT* sourceids up to 2-3 months back? Or is there another option I haven't
thought of?

Thanks,

Tina Hilton

Database Analyst
arvato systems



Mark Buzzard

Re: DB2 OS/390 maintenance
(in response to Tina Hilton)
Hi Tina,

I asked my sysprog that does the db2 installs, here is his response:

Most of the time I use the SOURCEID(RSU*) keyword (although with our
current scenario I am just installing it again to a different SMP/E
environment). I always have to do the GROUPEXTEND as well.



Jeremiah Eden

Re: DB2 OS/390 maintenance
(in response to Mark Buzzard)
We have been using the CSTs/RSUs since before it officially came out (2
years now) and have had not problems. We apply the latest RSU. Then on top
of that, any PTFs that will fix known problems at our site. Then applicable
HIPER and PE fixes that were released 3 weeks prior to when the maintenance
will be installed in our Production system. We call it the three week rule
and it hasn't let us down yet. Usually it will go PE in that time if there
is a problem. We always check the Status several days before the final
install.

-----Original Message-----
From: Hilton, Tina, arvato systems - NMI -PM
[mailto:[login to unmask email]
Sent: Thursday, January 02, 2003 6:40 AM
To: [login to unmask email]
Subject: DB2 OS/390 maintenance


I know that the subject regarding DB2 maintenance has been discussed several
times in the past, but I'd like a little more detail than was previously
given. At my previous jobs, we received monthly PUT tapes. When I wanted
to put maintenance on, I'd receive the maintenance and then apply all but
the last 2-3 tapes. Of course, we were always behind the times
release-wise, so there weren't very many PTFs to put on most of the time.

Now, I order a maintenance-only CBPDO. I actually did try to order an ESO
tape this time, but it wouldn't take all my FMIDs so I went back to the PDO.
I read in the included documentation that if you applied all the RSU*
sourceids then you would end up with a system that was thoroughly tested by
IBM. When I look at all the PTFs I received, though, there are quite a few
that (354 out of 1372) that don't have an RSU* sourceid assigned to it so
these would never go on with this method unless they were applied via the
GROUPEXTEND. I could just try to apply everything, but that makes me
nervous because of past problems with PTFs going PE just after I applied
them.

So, how do you guys do the apply? Do you apply everything on the PDO tape
that will go on? Do you use the SOURCEID(RSU*) keyword? Do you select all
PUT* sourceids up to 2-3 months back? Or is there another option I haven't
thought of?

Thanks,

Tina Hilton

Database Analyst
arvato systems








Tina Hilton

Re: DB2 OS/390 maintenance
(in response to Jeremiah Eden)
And you do this with a just-received CBPDO tape?

-----Original Message-----
From: Mark Buzzard [mailto:[login to unmask email]
Sent: January 02, 2003 8:52 AM
To: [login to unmask email]
Subject: Re: DB2 OS/390 maintenance


Hi Tina,

I asked my sysprog that does the db2 installs, here is his response:

Most of the time I use the SOURCEID(RSU*) keyword (although with our
current scenario I am just installing it again to a different SMP/E
environment). I always have to do the GROUPEXTEND as well.








Mark Buzzard

Re: DB2 OS/390 maintenance
(in response to Tina Hilton)
Yes. We had some problems where our SMP/E seemed to be out of whack. We
just received the lastest tape from IBM in December. I think it was at
level RSU0210.




Tina Hilton
<[login to unmask email] To: [login to unmask email]
YSTEMS.COM> cc:
Subject: Re: DB2 OS/390 maintenance
Sent by: DB2 Data
Base Discussion List
<[login to unmask email]
SOC.COM>


01/02/2003 08:13 AM
Please respond to
DB2 Data Base
Discussion List






And you do this with a just-received CBPDO tape?

-----Original Message-----
From: Mark Buzzard [mailto:[login to unmask email]
Sent: January 02, 2003 8:52 AM
To: [login to unmask email]
Subject: Re: DB2 OS/390 maintenance


Hi Tina,

I asked my sysprog that does the db2 installs, here is his response:

Most of the time I use the SOURCEID(RSU*) keyword (although with our
current scenario I am just installing it again to a different SMP/E
environment). I always have to do the GROUPEXTEND as well.



the





the DB2-L webpage at http://listserv.ylassoc.com. The owners of the list
can



Jeremiah Eden

Re: DB2 OS/390 maintenance
(in response to Mark Buzzard)
Yes. We just receive the tape and order and receive the 3 week HIPERS and
PEs from the online PSPs. Then we do an apply check on (RSU* HIPER and PRP).
After resolving any issues, we will print out the Hold data from the list of
PTFs that will get applied, and then go from there.

-----Original Message-----
From: Tina Hilton [mailto:[login to unmask email]
Sent: Thursday, January 02, 2003 8:14 AM
To: [login to unmask email]
Subject: Re: DB2 OS/390 maintenance


And you do this with a just-received CBPDO tape?

-----Original Message-----
From: Mark Buzzard [mailto:[login to unmask email]
Sent: January 02, 2003 8:52 AM
To: [login to unmask email]
Subject: Re: DB2 OS/390 maintenance


Hi Tina,

I asked my sysprog that does the db2 installs, here is his response:

Most of the time I use the SOURCEID(RSU*) keyword (although with our
current scenario I am just installing it again to a different SMP/E
environment). I always have to do the GROUPEXTEND as well.













Mark Ediger

Re: DB2 OS/390 maintenance
(in response to Jeremiah Eden)
Hello Tina,

First, before I get into the apply process, let me suggest that you
move to ordering you service throught ShopzSeries (
https://www14.software.ibm.com/webapp/ShopzSeries/ShopzSeries.jsp )
Having had to hang tapes since the 9" reel days, I have found this to
be the best thing to come along in systems programming in some time.
Your will never have to worry about PDO, ESO, or and other XXO again if
you go to this method. By they way, I have also used SUF and have liked
that too, but the last z/OS announcement indicated that ShopzSeries was
the direction for future maintenance support and also, many systems
programmers hate SUF (I don't know why).

If you have z/OS and crypto services on your machine then you can run
your Receive directly from the IBM package site with "Receive from
Network".
Even if you haven't got there yet, you can order the latest RSU level
and retrieve via FTP either from your z/OS system or from the desktop.

Once you have the latest RSU level received, I suggest you pick a
quarter that the rest of your teams (CICS, MVS, MQ) are at or going to
and apply that. I am currently doing RSU0209 while RSU0211 is the
current one. Don't worry if some of the PTFs do not have RSU
assignments. Generally, I have found that PTFs for RSU02nn will have
PTFS at PUT02nn-3. Some recommend applying all hipers too. I take the
time to go through each one and determine which ones are applicable to
our environment and apply only those.

You are right to worry about applied PTFS going PE, as the maintenance
rolls out to our various subsystems, I periodically run FTP on the IBM
site:
SERVICE.BOULDER.IBM.COM and get the file s390/holddata/month.txt.
I then receive it and run the SMPE report ERRSYSMODS on my target zone.
This tells me if any of the ptfs applied to my systems are PE. It also
tells me what the correcting PTF is and whether I have it applied. It
will also list new Hipers that are not applied. I will examine any that
have the codes PRF (purvasive) and FUL (Function Loss) for a fit to our
environment and apply if necessary.

There are many different sites with many different methods of
maintenance but I have had not production DB2 outages since going to
this method.

Good luck. Happy New Year

Mark Ediger
Acxiom

>>> [login to unmask email] 01/02/03 06:39AM >>>
I know that the subject regarding DB2 maintenance has been discussed
several
times in the past, but I'd like a little more detail than was
previously
given. At my previous jobs, we received monthly PUT tapes. When I
wanted
to put maintenance on, I'd receive the maintenance and then apply all
but
the last 2-3 tapes. Of course, we were always behind the times
release-wise, so there weren't very many PTFs to put on most of the
time.

Now, I order a maintenance-only CBPDO. I actually did try to order an
ESO
tape this time, but it wouldn't take all my FMIDs so I went back to the
PDO.
I read in the included documentation that if you applied all the RSU*
sourceids then you would end up with a system that was thoroughly
tested by
IBM. When I look at all the PTFs I received, though, there are quite a
few
that (354 out of 1372) that don't have an RSU* sourceid assigned to it
so
these would never go on with this method unless they were applied via
the
GROUPEXTEND. I could just try to apply everything, but that makes me
nervous because of past problems with PTFs going PE just after I
applied
them.

So, how do you guys do the apply? Do you apply everything on the PDO
tape
that will go on? Do you use the SOURCEID(RSU*) keyword? Do you select
all
PUT* sourceids up to 2-3 months back? Or is there another option I
haven't
thought of?

Thanks,

Tina Hilton

Database Analyst
arvato systems



visit the DB2-L webpage at http://listserv.ylassoc.com. The owners of
the list can



Jeremiah Eden

Re: DB2 OS/390 maintenance
(in response to Mark Ediger)
It would probably be good for you to visit this site as well if you are
going to go
with the CST/RSUs. It will give you a procedure to follow for the install.

http://www-1.ibm.com/servers/eserver/zseries/zos/servicetst/

-----Original Message-----
From: Mark Ediger [mailto:[login to unmask email]
Sent: Thursday, January 02, 2003 8:36 AM
To: [login to unmask email]
Subject: Re: DB2 OS/390 maintenance


Hello Tina,

First, before I get into the apply process, let me suggest that you
move to ordering you service throught ShopzSeries (
https://www14.software.ibm.com/webapp/ShopzSeries/ShopzSeries.jsp )
Having had to hang tapes since the 9" reel days, I have found this to
be the best thing to come along in systems programming in some time.

>snip

Mark Ediger
Acxiom

>>> [login to unmask email] 01/02/03 06:39AM >>>
I know that the subject regarding DB2 maintenance has been discussed
severaltimes in the past, but I'd like a little more detail than was
previously given.

>snip



Tina Hilton

Re: DB2 OS/390 maintenance
(in response to Jeremiah Eden)
Thanks everyone for your suggestions and for this web site. I searched
through IBM trying to find the latest recommendations, but couldn't find
anything worthwhile.

Tina

-----Original Message-----
From: Jeremiah Eden [mailto:[login to unmask email]
Sent: January 02, 2003 11:08 AM
To: [login to unmask email]
Subject: Re: DB2 OS/390 maintenance


It would probably be good for you to visit this site as well if you are
going to go
with the CST/RSUs. It will give you a procedure to follow for the install.

http://www-1.ibm.com/servers/eserver/zseries/zos/servicetst/

-----Original Message-----
From: Mark Ediger [mailto:[login to unmask email]
Sent: Thursday, January 02, 2003 8:36 AM
To: [login to unmask email]
Subject: Re: DB2 OS/390 maintenance


Hello Tina,

First, before I get into the apply process, let me suggest that you
move to ordering you service throught ShopzSeries (
https://www14.software.ibm.com/webapp/ShopzSeries/ShopzSeries.jsp )
Having had to hang tapes since the 9" reel days, I have found this to
be the best thing to come along in systems programming in some time.

>snip

Mark Ediger
Acxiom

>>> [login to unmask email] 01/02/03 06:39AM >>>
I know that the subject regarding DB2 maintenance has been discussed
severaltimes in the past, but I'd like a little more detail than was
previously given.

>snip








Ron Johnson

Re: DB2 OS/390 maintenance
(in response to Tina Hilton)
Tina,
Here's is what I do when doing DB2 maintenance (and have always wondered if
it was the best thing)...
I order a service-only CBPDO. I apply with the GROUPEXTEND option (and the
CHECK option initially, of course) and with sourceids of RSU*, HIPER, and
PRP. If I have a known bug and this approach doesn't bring in the fixing
ptf, I add it by specifying the specific sysmod ID. I review the holddata
to see what extra things I should do or pay attention to. I exclude or
bypass error holds depending on how it affects our shop. With this approach
I occasionally will put on a ptf that has since become an error. I try to
watch for these with the ASAP notification list on IBMLINK but sometimes
they get by me.

It sounds like the RSU approach is to help coordinate with other z/OS
software levels. It doesn't work that way here because I don't have any
influence on when and what maintenance they put on. We try to coordinate
with them as to when it will go into production so we can test at levels (of
other z/OS software) that will be present in production.

This approach has worked pretty well for us. I'm always open for
suggestions to improve this process.

Ron Johnson
Data-Tronics Corp.

-----Original Message-----
From: Hilton, Tina, arvato systems - NMI -PM
[mailto:[login to unmask email]
Sent: Thursday, January 02, 2003 6:40 AM
To: [login to unmask email]
Subject: DB2 OS/390 maintenance


I know that the subject regarding DB2 maintenance has been discussed several
times in the past, but I'd like a little more detail than was previously
given. At my previous jobs, we received monthly PUT tapes. When I wanted
to put maintenance on, I'd receive the maintenance and then apply all but
the last 2-3 tapes. Of course, we were always behind the times
release-wise, so there weren't very many PTFs to put on most of the time.

Now, I order a maintenance-only CBPDO. I actually did try to order an ESO
tape this time, but it wouldn't take all my FMIDs so I went back to the PDO.
I read in the included documentation that if you applied all the RSU*
sourceids then you would end up with a system that was thoroughly tested by
IBM. When I look at all the PTFs I received, though, there are quite a few
that (354 out of 1372) that don't have an RSU* sourceid assigned to it so
these would never go on with this method unless they were applied via the
GROUPEXTEND. I could just try to apply everything, but that makes me
nervous because of past problems with PTFs going PE just after I applied
them.

So, how do you guys do the apply? Do you apply everything on the PDO tape
that will go on? Do you use the SOURCEID(RSU*) keyword? Do you select all
PUT* sourceids up to 2-3 months back? Or is there another option I haven't
thought of?

Thanks,

Tina Hilton

Database Analyst
arvato systems








Mark Ediger

Re: DB2 OS/390 maintenance
(in response to Ron Johnson)
This Link is a white paper titled "z/Series Maintenance Suggestions to
Help Improve Availability in a Parallel Sysple Environment"

http://www1.ibm.com/servers/eserver/zseries/library/whitepapers/psos390maint.html

There is a section at the end addressing "Maintenance Process
Suggestions for s/390 Products".

I have found this paper usefull.


Mark Ediger
Acxiom

>>> [login to unmask email] 01/02/03 12:59PM >>>
Thanks everyone for your suggestions and for this web site. I
searched
through IBM trying to find the latest recommendations, but couldn't
find
anything worthwhile.

Tina

-----Original Message-----
From: Jeremiah Eden [mailto:[login to unmask email]
Sent: January 02, 2003 11:08 AM
To: [login to unmask email]
Subject: Re: DB2 OS/390 maintenance


It would probably be good for you to visit this site as well if you
are
going to go
with the CST/RSUs. It will give you a procedure to follow for the
install.

http://www-1.ibm.com/servers/eserver/zseries/zos/servicetst/

-----Original Message-----
From: Mark Ediger [mailto:[login to unmask email]
Sent: Thursday, January 02, 2003 8:36 AM
To: [login to unmask email]
Subject: Re: DB2 OS/390 maintenance


Hello Tina,

First, before I get into the apply process, let me suggest that you
move to ordering you service throught ShopzSeries (
https://www14.software.ibm.com/webapp/ShopzSeries/ShopzSeries.jsp )
Having had to hang tapes since the 9" reel days, I have found this to
be the best thing to come along in systems programming in some time.

>snip

Mark Ediger
Acxiom

>>> [login to unmask email] 01/02/03 06:39AM >>>
I know that the subject regarding DB2 maintenance has been discussed
severaltimes in the past, but I'd like a little more detail than was
previously given.

>snip



visit the
DB2-L webpage at http://listserv.ylassoc.com. The owners of the list
can be




visit the DB2-L webpage at http://listserv.ylassoc.com. The owners of
the list can



Tina Hilton

Re: DB2 OS/390 maintenance
(in response to Mark Ediger)
I like the idea of doing it this way. I thought about just including the
RSUs up to the last quarter (currently this would be RSU0209), but that's a
more cluttered apply. The instructions on the web site that Jeremiah posted
(http://www-1.ibm.com/servers/eserver/zseries/zos/servicetst/) recommends
applying sourceid(RSU*), then run "report errsysmods", then analyze HIPER
and PE-fixing service, and lastly installing those HIPER and PE-fixing PTFs
that want. That's a bit more complicated.

Tina

-----Original Message-----
From: Ron Johnson [mailto:[login to unmask email]
Sent: January 02, 2003 2:37 PM
To: [login to unmask email]
Subject: Re: DB2 OS/390 maintenance


Tina,
Here's is what I do when doing DB2 maintenance (and have always wondered if
it was the best thing)...
I order a service-only CBPDO. I apply with the GROUPEXTEND option (and the
CHECK option initially, of course) and with sourceids of RSU*, HIPER, and
PRP. If I have a known bug and this approach doesn't bring in the fixing
ptf, I add it by specifying the specific sysmod ID. I review the holddata
to see what extra things I should do or pay attention to. I exclude or
bypass error holds depending on how it affects our shop. With this approach
I occasionally will put on a ptf that has since become an error. I try to
watch for these with the ASAP notification list on IBMLINK but sometimes
they get by me.

It sounds like the RSU approach is to help coordinate with other z/OS
software levels. It doesn't work that way here because I don't have any
influence on when and what maintenance they put on. We try to coordinate
with them as to when it will go into production so we can test at levels (of
other z/OS software) that will be present in production.

This approach has worked pretty well for us. I'm always open for
suggestions to improve this process.

Ron Johnson
Data-Tronics Corp.

-----Original Message-----
From: Hilton, Tina, arvato systems - NMI -PM
[mailto:[login to unmask email]
Sent: Thursday, January 02, 2003 6:40 AM
To: [login to unmask email]
Subject: DB2 OS/390 maintenance


I know that the subject regarding DB2 maintenance has been discussed several
times in the past, but I'd like a little more detail than was previously
given. At my previous jobs, we received monthly PUT tapes. When I wanted
to put maintenance on, I'd receive the maintenance and then apply all but
the last 2-3 tapes. Of course, we were always behind the times
release-wise, so there weren't very many PTFs to put on most of the time.

Now, I order a maintenance-only CBPDO. I actually did try to order an ESO
tape this time, but it wouldn't take all my FMIDs so I went back to the PDO.
I read in the included documentation that if you applied all the RSU*
sourceids then you would end up with a system that was thoroughly tested by
IBM. When I look at all the PTFs I received, though, there are quite a few
that (354 out of 1372) that don't have an RSU* sourceid assigned to it so
these would never go on with this method unless they were applied via the
GROUPEXTEND. I could just try to apply everything, but that makes me
nervous because of past problems with PTFs going PE just after I applied
them.

So, how do you guys do the apply? Do you apply everything on the PDO tape
that will go on? Do you use the SOURCEID(RSU*) keyword? Do you select all
PUT* sourceids up to 2-3 months back? Or is there another option I haven't
thought of?

Thanks,

Tina Hilton

Database Analyst
arvato systems













Jeremiah Eden

Re: DB2 OS/390 maintenance
(in response to Tina Hilton)
There's a lot of CST/RSU going around today. Must be everyone planning for
this years maintenance. I know we have been frozen for 3 months. Anyone, I
hate to toot IBM's horn
again, but the CST/RSU is NOT dependant on other product software levels.
Yes, it is good to coordinate these if you can, but usually you don't
upgrade Z/OS, CICS, IMS and DB2 on the same
day. Anyone out there do this on a production system? I have gone through
the Aches and Pains of figuring out what level of maintenance is safe, and I
never felt safe. "Like a box of chocolates...you never know what you are
going to get". But I've read all the CST documents, I've talked to the
people who put them together and test them, and those who update the WEB
site, and even made suggestions which are now implemented to make sure you
get all the HOLD DATA and nonsuped PTFs on the orders. The first CSTs (word
of mouth only) had a few problems, but these showed up on the apply check.
We have never had a problem with an RSU. We are so comfortable with them
now, that we put the latest one on every month except during the 'golden
quarter of retail sales'. This is tested maintenance that is aged, plus the
HIPER and PEs that
you would want anyway. Don't know much more to say except Thanks to IBM, who
finally realized how hard it was to figure out what maintenance level++ to
put on DB2. Has anyone had any problems with CSTs/RSUs? If so, I would be
interested to know.

-----Original Message-----
From: Ron Johnson [mailto:[login to unmask email]
Sent: Thursday, January 02, 2003 1:37 PM
To: [login to unmask email]
Subject: Re: DB2 OS/390 maintenance


>snip

It sounds like the RSU approach is to help coordinate with other z/OS
software levels. It doesn't work that way here because I don't have any
influence on when and what maintenance they put on. We try to coordinate
with them as to when it will go into production so we can test at levels (of
other z/OS software) that will be present in production.

This approach has worked pretty well for us. I'm always open for
suggestions to improve this process.

Ron Johnson
Data-Tronics Corp.

-



Bill Johnson

Re: DB2 OS/390 maintenance
(in response to Jeremiah Eden)
I think the link should be:
http://www-1.ibm.com/servers/eserver/zseries/library/whitepapers/psos390maint.html
Bill Johnson



Mark Ediger
<[login to unmask email] To: [login to unmask email]
N.COM> cc:
Sent by: DB2 Data Subject: Re: DB2 OS/390 maintenance
Base Discussion
List
<[login to unmask email]
ASSOC.COM>


01/02/2003 02:51
PM
Please respond to
DB2 Data Base
Discussion List






This Link is a white paper titled "z/Series Maintenance Suggestions to
Help Improve Availability in a Parallel Sysple Environment"

http://www1.ibm.com/servers/eserver/zseries/library/whitepapers/psos390maint.html


There is a section at the end addressing "Maintenance Process
Suggestions for s/390 Products".

I have found this paper usefull.


Mark Ediger
Acxiom



Jeremiah Eden

Re: DB2 OS/390 maintenance
(in response to Bill Johnson)
You should be doing all of this anyway with any PTF(s) you put on. The RSU,
just takes the guesswork out of what safe level to go to. Anyone from IBM
out there that wants to chime in?
My generator is running low.

-----Original Message-----
From: Hilton, Tina, arvato systems - NMI -PM
[mailto:[login to unmask email]
Sent: Thursday, January 02, 2003 2:05 PM
To: [login to unmask email]
Subject: Re: DB2 OS/390 maintenance


I like the idea of doing it this way. I thought about just including the
RSUs up to the last quarter (currently this would be RSU0209), but that's a
more cluttered apply. The instructions on the web site that Jeremiah posted
(http://www-1.ibm.com/servers/eserver/zseries/zos/servicetst/) recommends
applying sourceid(RSU*), then run "report errsysmods", then analyze HIPER
and PE-fixing service, and lastly installing those HIPER and PE-fixing PTFs
that want. That's a bit more complicated.

Tina

-----Original Message-----
From: Ron Johnson [mailto:[login to unmask email]
Sent: January 02, 2003 2:37 PM
To: [login to unmask email]
Subject: Re: DB2 OS/390 maintenance


Tina,
Here's is what I do when doing DB2 maintenance (and have always wondered if
it was the best thing)...
I order a service-only CBPDO. I apply with the GROUPEXTEND option (and the
CHECK option initially, of course) and with sourceids of RSU*, HIPER, and
PRP. If I have a known bug and this approach doesn't bring in the fixing
ptf, I add it by specifying the specific sysmod ID. I review the holddata
to see what extra things I should do or pay attention to. I exclude or
bypass error holds depending on how it affects our shop. With this approach
I occasionally will put on a ptf that has since become an error. I try to
watch for these with the ASAP notification list on IBMLINK but sometimes
they get by me.

It sounds like the RSU approach is to help coordinate with other z/OS
software levels. It doesn't work that way here because I don't have any
influence on when and what maintenance they put on. We try to coordinate
with them as to when it will go into production so we can test at levels (of
other z/OS software) that will be present in production.

This approach has worked pretty well for us. I'm always open for
suggestions to improve this process.

Ron Johnson
Data-Tronics Corp.

-----Original Message-----
From: Hilton, Tina, arvato systems - NMI -PM
[mailto:[login to unmask email]
Sent: Thursday, January 02, 2003 6:40 AM
To: [login to unmask email]
Subject: DB2 OS/390 maintenance


I know that the subject regarding DB2 maintenance has been discussed several
times in the past, but I'd like a little more detail than was previously
given. At my previous jobs, we received monthly PUT tapes. When I wanted
to put maintenance on, I'd receive the maintenance and then apply all but
the last 2-3 tapes. Of course, we were always behind the times
release-wise, so there weren't very many PTFs to put on most of the time.

Now, I order a maintenance-only CBPDO. I actually did try to order an ESO
tape this time, but it wouldn't take all my FMIDs so I went back to the PDO.
I read in the included documentation that if you applied all the RSU*
sourceids then you would end up with a system that was thoroughly tested by
IBM. When I look at all the PTFs I received, though, there are quite a few
that (354 out of 1372) that don't have an RSU* sourceid assigned to it so
these would never go on with this method unless they were applied via the
GROUPEXTEND. I could just try to apply everything, but that makes me
nervous because of past problems with PTFs going PE just after I applied
them.

So, how do you guys do the apply? Do you apply everything on the PDO tape
that will go on? Do you use the SOURCEID(RSU*) keyword? Do you select all
PUT* sourceids up to 2-3 months back? Or is there another option I haven't
thought of?

Thanks,

Tina Hilton

Database Analyst
arvato systems