Packaging an environment (Not a DB2 DBRM/Package)

Philip Sevetson

Packaging an environment (Not a DB2 DBRM/Package)
Question about configuration management on z/OS.

I'm responsible for IMS and DB2 in an enterprise with multiple platforms (two prod z/OS LPARs and several test, with several subsystems and multiple testing environments/schemas, lots and lots of *NIX and Oracle). We're having a lot of trouble getting our mainframe code and data assets, in test, to be consistent with production (except, of course, for changes in progress!).

I've used DB2 compare-and-reconcile products from CA, BMC, and IBM, and eventually some of them work pretty well for DB2. However, all of our other code assets (and IMS) are pretty much roll-your-own as far as retrofitting new production to test, and more importantly, verifying that the test environment is a valid representation (with object renames and so forth) of the prod environment. I'm getting very tired of ISPF 3.3, ISPF 3.13, and even FileAid/MVS, which is much better but I can't see how to script it to where it's push button!!

I'm wondering if I'm barking up the wrong tree here. Is there a product or suite which will verify that a particular test environment has all of the same code and structures/metadata as a Production (or other) environment, across multiple languages (JCL, COBOL, various utility controls, IMS libraries, etc)? And is there a product (hopefully the same one) which will script the needed changes?

--Phil Sevetson
**This e-mail, including any attachments, may be confidential, privileged, or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy, or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system.**

John Bucaria

Packaging an environment (Not a DB2 DBRM/Package)
(in response to Philip Sevetson)
Hi Phil,

We use the CA Endevor source manager for all of our COBOL, JCL and control statement library members with excellent results. Elements can move to/from Prod and any number of Test/Dev locations.

-John

From: Sevetson, Phil <[login to unmask email]>
Sent: Friday, January 11, 2019 11:42 AM
To: [login to unmask email]
Subject: [DB2-L] - Packaging an environment (Not a DB2 DBRM/Package)

Question about configuration management on z/OS.

I'm responsible for IMS and DB2 in an enterprise with multiple platforms (two prod z/OS LPARs and several test, with several subsystems and multiple testing environments/schemas, lots and lots of *NIX and Oracle). We're having a lot of trouble getting our mainframe code and data assets, in test, to be consistent with production (except, of course, for changes in progress!).

I've used DB2 compare-and-reconcile products from CA, BMC, and IBM, and eventually some of them work pretty well for DB2. However, all of our other code assets (and IMS) are pretty much roll-your-own as far as retrofitting new production to test, and more importantly, verifying that the test environment is a valid representation (with object renames and so forth) of the prod environment. I'm getting very tired of ISPF 3.3, ISPF 3.13, and even FileAid/MVS, which is much better but I can't see how to script it to where it's push button!!

I'm wondering if I'm barking up the wrong tree here. Is there a product or suite which will verify that a particular test environment has all of the same code and structures/metadata as a Production (or other) environment, across multiple languages (JCL, COBOL, various utility controls, IMS libraries, etc)? And is there a product (hopefully the same one) which will script the needed changes?

--Phil Sevetson
**This e-mail, including any attachments, may be confidential, privileged, or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy, or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system.**
-----End Original Message-----

Philip Sevetson

Packaging an environment (Not a DB2 DBRM/Package)
(in response to John Bucaria)
John,

Thanks. We're using ClearCase, but I haven't investigated whether they can do this - they don't start on Z, but they do have a buildout which theoretically works there.

--Phil

From: Bucaria, John [mailto:[login to unmask email]
Sent: Friday, January 11, 2019 12:43 PM
To: [login to unmask email]
Subject: [DB2-L] - RE: Packaging an environment (Not a DB2 DBRM/Package)

Hi Phil,

We use the CA Endevor source manager for all of our COBOL, JCL and control statement library members with excellent results. Elements can move to/from Prod and any number of Test/Dev locations.

-John

From: Sevetson, Phil <[login to unmask email]>
Sent: Friday, January 11, 2019 11:42 AM
To: [login to unmask email]
Subject: [DB2-L] - Packaging an environment (Not a DB2 DBRM/Package)

Question about configuration management on z/OS.

I'm responsible for IMS and DB2 in an enterprise with multiple platforms (two prod z/OS LPARs and several test, with several subsystems and multiple testing environments/schemas, lots and lots of *NIX and Oracle). We're having a lot of trouble getting our mainframe code and data assets, in test, to be consistent with production (except, of course, for changes in progress!).

I've used DB2 compare-and-reconcile products from CA, BMC, and IBM, and eventually some of them work pretty well for DB2. However, all of our other code assets (and IMS) are pretty much roll-your-own as far as retrofitting new production to test, and more importantly, verifying that the test environment is a valid representation (with object renames and so forth) of the prod environment. I'm getting very tired of ISPF 3.3, ISPF 3.13, and even FileAid/MVS, which is much better but I can't see how to script it to where it's push button!!

I'm wondering if I'm barking up the wrong tree here. Is there a product or suite which will verify that a particular test environment has all of the same code and structures/metadata as a Production (or other) environment, across multiple languages (JCL, COBOL, various utility controls, IMS libraries, etc)? And is there a product (hopefully the same one) which will script the needed changes?

--Phil Sevetson
**This e-mail, including any attachments, may be confidential, privileged, or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy, or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system.**
-----End Original Message-----

-----End Original Message-----
**This e-mail, including any attachments, may be confidential, privileged, or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy, or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system.**