DB2 z/OS V10 Maintenance - Backout plan

Mike Martin

DB2 z/OS V10 Maintenance - Backout plan
Hi all,

We are about to apply a lot of PTFs to our DB2 V10 subsystems (prepping for V11 upgrade).

We are contemplating what is required for backing out the maintenance if necessary. What do shops do for backing out maintenance if a problem is introduced... specifically backing out catalog or directory changes that may have happened?

Mike Martin

This email may contain confidential and privileged material for the sole use of the intended recipient. If you are not the intended recipient, please contact the sender and delete all copies. Any review or distribution by others is strictly prohibited. Personal emails are restricted by policy of the State Employees' Credit Union (SECU). Therefore SECU specifically disclaims any responsibility or liability for any personal information or opinions of the author expressed in this email.

Venkat Srinivasan

RE: DB2 z/OS V10 Maintenance - Backout plan
(in response to Mike Martin)

Items that cause catalog changes are CATMAINTs, DSNTIJRT and Binds.
CATMAINT during maintenance fixes prior issues in which case you will be OK. If it introduces new function the change itself should be backward compatible.
DSNTIJRT can be rerun anytime from old maintenance.
Binds are versioned anyway and should not cause issues unless you cleanup all prior versions.
Occasionally there may be SQL ALTERS which move functions from one SPROC environment to another and you should have corresponding backout SQL as part of holddata analysis.
In the maintenance stream that you have, how many catmaints are there and what are they. The holddata has adequate information about the changes it performs.

If you have the ability to do full system backup you can use that for recovery but what will you do if the issue is found 10 days after applying maintenance.
What I do is the following. Apply maintenance, if an issue is found after applying maintenance, work with the support to analyze the issue and if it is seriously impacting backout the module that caused the regression.
Backup the SMPE environment before begining your maintenance. Your normal backup for catalog / application data should be sufficient. If a problem occurs research the issue and decide if you want to backout the PTF that causes the issue (by working with support).
Venkat   



In Reply to Mike Martin:

Hi all,

We are about to apply a lot of PTFs to our DB2 V10 subsystems (prepping for V11 upgrade).

We are contemplating what is required for backing out the maintenance if necessary. What do shops do for backing out maintenance if a problem is introduced... specifically backing out catalog or directory changes that may have happened?

Mike Martin

This email may contain confidential and privileged material for the sole use of the intended recipient. If you are not the intended recipient, please contact the sender and delete all copies. Any review or distribution by others is strictly prohibited. Personal emails are restricted by policy of the State Employees' Credit Union (SECU). Therefore SECU specifically disclaims any responsibility or liability for any personal information or opinions of the author expressed in this email.

Mike Martin

DB2 z/OS V10 Maintenance - Backout plan
(in response to Venkat Srinivasan)
Great information. Thanks Venkat!

From: Venkat Srinivasan [mailto:[login to unmask email]
Sent: Tuesday, May 16, 2017 4:32 PM
To: [login to unmask email]
Subject: [DB2-L] - RE: DB2 z/OS V10 Maintenance - Backout plan


Items that cause catalog changes are CATMAINTs, DSNTIJRT and Binds.
CATMAINT during maintenance fixes prior issues in which case you will be OK. If it introduces new function the change itself should be backward compatible.
DSNTIJRT can be rerun anytime from old maintenance.
Binds are versioned anyway and should not cause issues unless you cleanup all prior versions.
Occasionally there may be SQL ALTERS which move functions from one SPROC environment to another and you should have corresponding backout SQL as part of holddata analysis.
In the maintenance stream that you have, how many catmaints are there and what are they. The holddata has adequate information about the changes it performs.

If you have the ability to do full system backup you can use that for recovery but what will you do if the issue is found 10 days after applying maintenance.
What I do is the following. Apply maintenance, if an issue is found after applying maintenance, work with the support to analyze the issue and if it is seriously impacting backout the module that caused the regression.
Backup the SMPE environment before begining your maintenance. Your normal backup for catalog / application data should be sufficient. If a problem occurs research the issue and decide if you want to backout the PTF that causes the issue (by working with support).
Venkat


In Reply to Mike Martin:
Hi all,

We are about to apply a lot of PTFs to our DB2 V10 subsystems (prepping for V11 upgrade).

We are contemplating what is required for backing out the maintenance if necessary. What do shops do for backing out maintenance if a problem is introduced... specifically backing out catalog or directory changes that may have happened?

Mike Martin

This email may contain confidential and privileged material for the sole use of the intended recipient. If you are not the intended recipient, please contact the sender and delete all copies. Any review or distribution by others is strictly prohibited. Personal emails are restricted by policy of the State Employees' Credit Union (SECU). Therefore SECU specifically disclaims any responsibility or liability for any personal information or opinions of the author expressed in this email.

-----End Original Message-----
This email may contain confidential and privileged material for the sole use of the intended recipient. If you are not the intended recipient, please contact the sender and delete all copies. Any review or distribution by others is strictly prohibited. Personal emails are restricted by policy of the State Employees' Credit Union (SECU). Therefore SECU specifically disclaims any responsibility or liability for any personal information or opinions of the author expressed in this email.

Roy Boxwell

DB2 z/OS V10 Maintenance - Backout plan
(in response to Mike Martin)
Normally nothing... Backing out those changes is "non trivial" Even in DB2 12 the CATMAINT is a "one way street" and there is no fall back.
Naturally if you copy the world then you can recover but only if zero application work has happened and, by definition, that cannot be as you have found a bug...

Roy Boxwell

SOFTWARE ENGINEERING GMBH and SEGUS Inc.
-Product Development-

Heinrichstrasse 83-85
40239 Duesseldorf/Germany
Tel. +49 (0)211 96149-675
Fax +49 (0)211 96149-32
Email: [login to unmask email]<mailto:[login to unmask email]>
http://www.seg.de http://www.seg.de

Software Engineering GmbH
Amtsgericht Düsseldorf, HRB 37894
Geschäftsführung: Gerhard Schubert, Bettina Schubert

From: MARTIN, MIKE [mailto:[login to unmask email]
Sent: Tuesday, May 16, 2017 8:36 PM
To: [login to unmask email]
Subject: [DB2-L] - DB2 z/OS V10 Maintenance - Backout plan

Hi all,

We are about to apply a lot of PTFs to our DB2 V10 subsystems (prepping for V11 upgrade).

We are contemplating what is required for backing out the maintenance if necessary. What do shops do for backing out maintenance if a problem is introduced... specifically backing out catalog or directory changes that may have happened?

Mike Martin


This email may contain confidential and privileged material for the sole use of the intended recipient. If you are not the intended recipient, please contact the sender and delete all copies. Any review or distribution by others is strictly prohibited. Personal emails are restricted by policy of the State Employees' Credit Union (SECU). Therefore SECU specifically disclaims any responsibility or liability for any personal information or opinions of the author expressed in this email.

-----End Original Message-----

Mahmood Wadee

RE: DB2 z/OS V10 Maintenance - Backout plan
(in response to Venkat Srinivasan)

Hi Venkat ,

Would you still recommend that a CATMAINT be run even if the script supplied by the PTF produces no offending rows ?

Venkat Srinivasan

RE: DB2 z/OS V10 Maintenance - Backout plan
(in response to Mahmood Wadee)

I dont run catmaint if a sql was given and the sql does not produce any rows. If you were to run nothing will happen.

Venkat

In Reply to Mahmood Wadee:

Hi Venkat ,

Would you still recommend that a CATMAINT be run even if the script supplied by the PTF produces no offending rows ?