DB2 OS/390 data sharing maint / release issues

[login to unmask email]

DB2 OS/390 data sharing maint / release issues
Hi everyone


1) Has anyone ever experienced any issues when applying maintenenace to ONE
member of a data sharing group and not the other for a period of time.

2) Does anyone know what IBM's recommendation is for applying maintenenace
to a data sharing members?

3) What are the procedures for migrating through DB2 release levels in a
data shring environment


Tom



Stephen Vagnier

Re: DB2 OS/390 data sharing maint / release issues
(in response to ttaylor@CHUBB.COM)
Hello Tom,

I always try to apply maintenance to all members at the same
time. We have our data sharing environments recycled once a
week to help reduce any storage creep problems (still having
some), and during this recycle is when I apply maintenance
to all members. Currently running several data sharing
environments (from 2-way to 4-way).
I believe IBM recommends having members at different
maintenance levels for only a "short" period of time. I not sure what
IBM's definition of "short" is but probably only 2-3 days; not
weeks.
The same goes for migrating DB2 members to a new release
level; the sooner all members are migrated the less chance
for different release level incompatibility problems.


Hope this helps,



****************************************
Steve Vagnier
Principal IT Systems Administrator
American Electric Power
Shared Services
One Riverside Plaza
Columbus, Ohio 43215
Email: [login to unmask email]
Phone: 614-223-3677
Audinet: 200-3677




Tom Taylor
<[login to unmask email] To: [login to unmask email]
.COM> cc:
Sent by: DB2 Subject: DB2 OS/390 data sharing maint / release issues
Data Base
Discussion
List
<[login to unmask email]
M>


01/07/2002
12:10 PM
Please respond
to DB2 Data
Base
Discussion
List






Hi everyone


1) Has anyone ever experienced any issues when applying maintenenace to ONE
member of a data sharing group and not the other for a period of time.

2) Does anyone know what IBM's recommendation is for applying maintenenace
to a data sharing members?

3) What are the procedures for migrating through DB2 release levels in a
data shring environment


Tom








Leslie Pendlebury-Bowe

Re: DB2 OS/390 data sharing maint / release issues
(in response to Stephen Vagnier)
Hi Tom

We only have one set of binaries for our DS members to run off (good and
bad) and part of the reason for this is to have a single point for the
maintenance.

(We are 4-way DS .. very active .. no application split)

bst rgds

Les



-----Original Message-----
From: Tom Taylor [mailto:[login to unmask email]
Sent: Monday, January 07, 2002 5:10 PM
To: [login to unmask email]
Subject: DB2 OS/390 data sharing maint / release issues


Hi everyone


1) Has anyone ever experienced any issues when applying maintenenace to ONE
member of a data sharing group and not the other for a period of time.

2) Does anyone know what IBM's recommendation is for applying maintenenace
to a data sharing members?

3) What are the procedures for migrating through DB2 release levels in a
data shring environment


Tom







**********************************************************************
The information contained in this message or any of its attachments may be confidential and is intended for the exclusive use of the addressee(s). Any disclosure, reproduction, distribution or other dissemination or use of this communication is strictly prohibited without the express permission of the sender. The views expressed in this email are those of the individual and not necessarily those of Sony or Sony affiliated companies. Sony email is for business use only.

This email and any response may be monitored by Sony UK.
(05)
**********************************************************************



Chris Munson

DB2 OS/390 data sharing maint / release issues
(in response to Leslie Pendlebury-Bowe)
Tom,

The basic design of data sharing is such that each member can be at a
difference maintenance level. There have been isolated problems with
maintenance but these are rare. Most of the people that I have spoken with
have one set of libraries for the group so maintenance is applied to that
one library and then the members are recycled one at a time. That way the
whole group gets the same code around the same time. It is clearly not
always convenient to recycle members one after another so it may take some
time to get all of the members recycled and is a perfectly acceptable
approach.

This approach of getting all members at the same maintenance level when you
can is, to me, about the best. There are instances that new functions,
enhancements or fixes are not exploitable until code is on all members.

As far as migrating release levels thru the group it is about the same as
applying maintenance. You bring down one member, start it on the new
release code, run CATMAINT to convert the catalog (preferably during a
non-peak time) then stop/start all other members with the new release code
one at a time. Again the design allows for mixed releases (coexistence)
for different members (which releases tolerated is dependent on which
release you are migrating from) so if it takes you a little time to get the
new release code recycled thru the group that is ok. You should note that
running coexistence is different than running different maintenance levels
of the same release. Coexistence usually has some operational issues and
restrictions in that most new functions will not be available until all
members are at the new release. It is generally expected that the period
of time that you should run coexistence is different than the time you
might run different maintenance levels. IBM has stated in the past that
coexistence should not be considered a 'permanent' configuration and you
should hope to get all members to the new release within several weeks if
possible.

Hope this helps.

Chris Munson
DB2 Development, IBM Silicon Valley Laboratory


From: Tom Taylor
Subject: DB2 OS/390 data sharing maint / release issues


Hi everyone


1) Has anyone ever experienced any issues when applying maintenenace to
ONE
member of a data sharing group and not the other for a period of time.

2) Does anyone know what IBM's recommendation is for applying maintenenace
to a data sharing members?

3) What are the procedures for migrating through DB2 release levels in a
data shring environment


Tom