CA Tuesday Tip from Ryan Bonser, Support Engineer, for September 9, 2014
Is the CA Repository for z/OS 7.2 compatible with DB2 11?
PTFs RO64535 and RO64536 deliver DB2 11 toleration support for
the 'CA Repository for z/OS r7.2' product. PTF RO64535 enables DB2 11
toleration support for the Mass Generation facility of 'CA Repository
for z/OS r7.2'. PTF RO64536 enables DB2 V11 toleration support for the
Catalog Synchronization facility of 'CA Repository Exchange for
DB2 r7.2'.
The limitations of the DB2 11 toleration support are as follows:
1. To generate DB2 11 object definitions the DB2 V9 logic of the Mass
Generation facility is used.
2. A new DB2 scanner - DBXCATA - introduced with PTF RO31042 to process the
DB2 10 NFM objects should also be used to process the DB2 11 NFM and CM objects
that are currently supported by the CA Repository Exchange for DB2 r7.2
*************************************************************************************
*Section 1: Post SMP/E Instructions, describes the BINDS that need to be *
* completed to implement the changes introduced by PTFs RO64535 and RO64536, *
* and which must be run if you are upgrading to DB2 11. *
* NOTE: Execute these instructions only if the CA Repository for *
* z/OS r7.2 is installed and operational. Do not execute these instructions *
* if you are installing CA Repository for z/OS r7.2 for the first time. *
* *
*section 2: New Installations, provides the steps that need *
* to occur if you are a new CA Repository for z/OS r7.2 customer who will *
* be hosting on DB2 11. *
* *
*section 3: Existing Installations, provides the steps that need *
* to occur if you are an existing CA Repository for z/OS r7.2 customer who will *
* be hosting on DB2 11. *
*************************************************************************************
Section 1: Post SMP/E instructions for PTFs RO64535 and RO64536.
NOTE:
One bind job can be executed after both PTFs are applied to
bind any packages delivered with the PTFs.
The breakout below shows what packages are provided with each PTF.
1A: Once RO64535 has been SMP/E APPLIED, request that the BIND
packages in the following list be run by your DB2 DBA.
Bind package list:
o DBXSYNL
o DBXRELT
o DBXDDLM
o DBXDDLB
Use the following parameters with the packages:
DSN SYSTEM(subsys)
BIND PACKAGE(collection name)-
ENCODING(EBCDIC ) -
ENABLE(*) -
PATH(repository qual) -
QUALIFIER(repository qual) -
MEMBER(<see list above>) -
VALIDATE(BIND)
DYNAMICRULES(BIND) -
ISOLATION(CS) -
EXPLAIN(NO) -
FLAG(I) -
RELEASE(COMMIT) -
ACTION(REPLACE) -
CURRENTDATA(NO)
END
Make the following substitutions for the values of the
parameters so they conform to your site's environment.
Change:
- subsys to the DB2 system
- collection name to the repository package collection
- repository qual to the repository owner.
Make sure the DBRMLIB DD statement points to the DBRM library
that contains the DBRMs associated with the PTFs that are
applied.
1B Once RO64536 has been SMP/e APPLIED, request that the BIND
packages in the following two lists be run by your DB2 DBA.
Bind package list:
o DBXSYNC
o DBXCATV
Use the following parameters with the DBXSYNC package:
DSN SYSTEM(subsys)
BIND PACKAGE(collection name)-
ENCODING(EBCDIC ) -
ENABLE(*) -
PATH(repository qual) -
QUALIFIER(repository qual) -
MEMBER(<see list above>) -
VALIDATE(BIND)
DYNAMICRULES(BIND) -
ISOLATION(CS) -
EXPLAIN(NO) -
FLAG(I) -
RELEASE(COMMIT) -
ACTION(REPLACE) -
CURRENTDATA(NO)
END
+
Use the following parameters with the DBXCATV package:
DSN SYSTEM(subsys)
BIND PACKAGE(collection name)-
ENCODING(EBCDIC ) -
ENABLE(*) -
PATH(repository qual) -
QUALIFIER(SYSIBM) -
MEMBER(<see list above>) -
VALIDATE(BIND)
DYNAMICRULES(BIND) -
ISOLATION(CS) -
EXPLAIN(NO) -
FLAG(I) -
RELEASE(COMMIT) -
ACTION(REPLACE) -
CURRENTDATA(NO)
END
Make the following substitutions for the values of the
parameters so they conform to your site's environment.
Change:
- subsys to the DB2 system
- collection name to the repository package collection
- repository qual to the repository owner.
Make sure the DBRMLIB DD statement points to the DBRM library
that contains the DBRMs associated with the PTFs that are
applied.
1C CA Repository for z/OS Exchange for DB2
If you are currently hosting on DB2 8, 9 or 10 and will not be
migrating to DB2 11 but desire to input DB2 11 (NFM or CM) into the CA
Repository for z/OS via the DB2 exchange, you will need to generate the CA
Repository Exchange for DB2 JCL to reflect DB2 11 by specifying 11 as the
DB2 Version on the catsync panel.
Product Configuration Instructions
Before proceeding with the following section, it is important to define
the references that will be used. In the following section reference
is made to hosting on DB2 11. Hosting means that the meta data
collected by the CA Repository will be loaded to a repository installed
on top of DB2.
Processing of input data from various DB2 sources including DB2 11 can
be loaded to the CA Repository using the 'CA Repository Exchange for
DB2 r7.2'. The host repository database can be any of the currently
supported releases DB2 8, 9, 10, 11
section, 2: New Installations, provides the steps that need
to occur if you are a new CA Repository for z/OS r7.2 customer who will
be hosting on DB2 11 using:
o Conversion Mode - Section 2A
o New Function Mode - Section 2B
2A: New CA Repository for z/OS r7.2 Hosting on DB2 11 Conversion Mode(CM)
2A1: SMP/E RECEIVE, APPLY and ACCEPT the CA Repository for z/OS r7.2
from the GA media. Refer to the CA Repository for z/OS
Installation Guide r7.2 Chapters One through Five.
2A2: Complete the steps in the Chapter 6: 'Configuring Your Product'
which is found in the 'CA Repository for z/OS Installation Guide
r7.2'.
o When establishing the 'Define Installation Defaults', the DB2
Load, DB2 Library and Plan names must reflect the respective
DB2 10 libraries.
o When populationg the Define DB2 Defaults' panel, the DB2 Version
parameter will need to be set to '10'.
o After submitting the 'Bind All DB2 Plans and Packages' job in
Chapter 6, check the output of the job for any UNSUCCESSFUL
packages and report them to CA Technical support for advisement on
next steps.
2B: New CA Repository for z/OS r7.2 Hosting on DB2 11 New Function Mode(NFM)
2B1: SMP/E RECEIVE, APPLY and ACCEPT the CA Repository for z/OS r7.2
from the GA media. Refer to the CA Repository for z/OS
Installation Guide r7.2 Chapters One through Five.
2B2: Complete the steps in Chapter 6: 'Configuring Your Product'
found in the 'CA Repository for z/OS Installation Guide r7.2'.
o When establishing the 'Define Installation Defaults', the DB2
Load, DB2 Library and Plan names must reflect the respective
DB2 10 libraries.
o When populationg the Define DB2 Defaults' panel, the DB2 Version
parameter will need to be set to '11'.
o After submitting the 'Bind All DB2 Plans and Packages' job in
Chapter 6, check the output of the job for any UNSUCCESSFUL
packages and report them to CA Technical support for advisement on
next steps.
section 3: Migrating Existing Installations, provides the
steps that need to occur if you currently have CA Repository 7.2
installed using DB2 8, 9 or 10 and will be migrating to DB2 11 using:
o Compatibility Mode - Section 3A
o New Function Mode - Section 3B
3A: Existing CA Repository for z/OS r7.2 Hosting on DB2 11 Conversion Mode(CM)
3A1: Update the dataset names of the DB2 release and plan names
defined in the Default Values panel. Refer to the 'Define
Installation Defaults' step in Chapter 6.
When establishing the installation defaults, the DB2 Load, DB2
Library and Plan names must reflect the respective DB2 11
libraries.
3A2: Refer to the 'Define DB2 Defaults' step in Chapter 6.
Update the WLM environment Name on the DB2 Defaults panel so it
reflects the name of your workload manager.
Ensure that the DB2 Version is set to '10'.
3A3: Migrate the Repository DB2 procedures into the new WLM library.
Refer to the 'Copy the DB2 Stored Procedures' step in Chapter 6.
3A4: Alter the DB2 Stored Procedures to reflect the new WLM name.
3A5: Refresh WLM.
3A6: Update the DSN of the DB2 defined in the STEPLIB member. Refer
to the 'Edit the DB2 Skeleton Library' step in Chapter 6.
3A7: Complete the 'Bind All Plans and Packages' step in Chapter 6.
check the output of the job for any UNSUCCESSFUL
packages and report them to CA Technical support for advisement on
next steps.
3A8: If you will be executing the CA Repository Exchange for DB2,
the release of DB2 will remain at the current level.
3B: Existing CA Repository for z/OS r7.2 Hosting on DB2 11 New Function Mode(NFM)
3B1: Update the dataset names of the DB2 release and plan names
defined in the Default Values panel. Refer to the 'Define
Installation Defaults' step in Chapter 6.
When establishing the installation defaults, the DB2 Load, DB2
Library and Plan names must reflect the respective DB2 11
libraries.
3B2: Refer to the 'Define DB2 Defaults' step in Chapter 6.
Update the WLM environment Name on the DB2 Defaults panel so it
reflects the name of your workload manager.
Ensure that the DB2 Version is set to '11'.
3B3: Migrate the Repository DB2 procedures into the new WLM library.
Refer to 'Copy the DB2 Stored Procedures' in Chapter 6.
3B4: Alter the DB2 Stored Procedures to reflect the new WLM name.
3B5: Refresh WLM.
3B6: Update the DSN of the DB2 defined in the STEPLIB member. Refer
to the 'Edit the DB2 Skeleton Library' step in Chapter 6.
3B7: Complete the 'Bind All Plans and Packages' step in Chapter 6.
check the output of the job for any UNSUCCESSFUL
packages and report them to CA Technical support for advisement on
next steps.
3B8: If you will be executing the CA Repository Exchange for DB2,
you will need to generate the CA Repository Exchange for DB2
JCL to reflect DB2 11 by specifying 11 as the DB2 Version
on the catsync panel.
This completes the PML for CA Repository r7.2 support for DB2 11.