How to Enable DB2 Object Migration

Additional CA Chorus for DB2 Database Management Configuration › How to Enable DB2 Object Migration

How to Enable DB2 Object Migration

Before you can use the Object Migrator function in CA Chorus for DB2 Database Management to migrate DB2 objects, perform the tasks in the following procedure manually outside of CA Chorus Software Manager. This procedure creates the OFA configuration PDS and members, updates the OFAPROC started task JCL, and updates the MJETJOM model JCL.

Note: This configuration is not required for integration with CA Chorus Infrastructure Management for Networks and Systems.

Note: To execute the Batch Processor, you must be granted EXECUTE authority on the Batch Processor plan. For more information about granting product authorizations, see the CA Database Management Solutions for DB2 for z/OS General Facilities Reference Guide.

Follow these steps:

Confirm that at least one CA RC/Migrator utility model ID exists.
Note: The @DEFAULT model is created during CA RC/Migrator post-installation DB2 catalog customization. Confirm that an @DEFAULT model exists for CA RC/Migrator. You can create this model and additional models using the CA RC/Migrator profile option (PROF). Select Utility Model Services, and then use the template (T) option to create a model using an existing model as a template. For more information about creating models, see the CA RC/Migrator User Guide.
Allocate a configuration PDS with the following attributes for use by the Object Framework Services agent (OFA):
Note: The OFA is created and customized during post-installation processing of the CA Database Management Solutions for DB2 for z/OS. For more information about post-installation processing, see the CA Database Management Solutions for DB2 for z/OS Implementation Guide.
- Tracks: 2
- Record format: FB
- Record length: 80
- Block size: 27920
The OFA configuration PDS is allocated.
Define global configuration parameters:
1. Create the default global configuration member (@DEFAULT) in the OFA configuration PDS.
2. Add the following JCL:
```
<JOB CARD> 
//jobcard JOB (ACCT INFO),'job title',CLASS=A,MSGCLASS=X,
//       MSGLEVEL=(1,1),REGION=0M,NOTIFY=userid
</JOB CARD>                                                
<MODEL4>                                                   
MODEL4 model ID
</MODEL4>                                                  
<MODEL4C>                                                  
MODEL4C creator                                           
</MODEL4C>
```
3. Replace the italicized text with site-specific values. Include the desired JOB statement for z/OS batch jobs (<JOB CARD>, </JOB CARD), the model ID or name (<MODEL4>, </MODEL4), and creator (<MODEL4C>, </MODEL4C>).
4. Save your changes.
  The @DEFAULT global configuration member is created.
Important! By default, the DBA Command Manager and Object Migrator functions will create temporary work data sets using the TSO PREFIX of each user as the high-level qualifier. You can override the default settings as described in Step 4.
(Optional) To specify an alternate high-level qualifier for use with temporary work data sets:
1. Create a member in the OFA configuration PDS for each Object Migrator user that is named the same as their user ID. You can use the @DEFAULT member in the OFA configuration PDS as a template.
  Note: Use the JOB statement, model name (ID), and creator values for overriding global settings. The model ID and creator must match the members that you create. The creator specifies the member creator user ID.
2. Add the following tags:
```
<SYSTEM:lpar>
<PREFIX>
hlq;
</PREFIX>
</SYSTEM:lpar>
```
3. In this JCL, specify the LPAR name (lpar) and the high-level qualifier (hlq) to be used with the creation of temporary work data sets for this user.
  Note: The hlq must be terminated with a semi-colon.
  
  For example:
```
<SYSTEM:LPAR1> 
<PREFIX>      
MYPREFIX.CHORUS;
</PREFIX>     
</SYSTEM:LPAR1>
```
  Note: For more examples of overriding high-level qualifiers for work data set allocations, see the CA Chorus for DB2 Database Management User Guide.
4. Save your changes.
  The user member is created.
For example:

When you are done adding members, the members appear in the configuration data set members list. These members are used during DB2 object migration when the migration is submitted for analysis. The user members override global settings that are defined in the @DEFAULT member.
Update the OFAPROC started task JCL:
Notes:
- The OFAPROC started task is created and customized during configuration of the Object Framework Services agent (OFA). For more information about configuring the OFA, see the CA Database Management Solutions for DB2 for z/OS Implementation Guide.
- The OFAPROC started task ID needs READ permission for BPX.SERVER.
- If the EZB.STACKACCESS resource is protected, the appropriate READ permissions are needed for the user ID associated with the OFAPROC started task and the users requesting access to the Object Migrator function.
1. Add the CFGFILE and SYSTCPD DD statements.
```
//CFGFILE  DD DISP=SHR,DSN=config.om.pds
//SYSTCPD  DD DISP=SHR,DSN=&tcpdata
```
  config.om.pds
  
  Specifies the name of the PDS that was previously created for the Object Migrator configuration.
  
  &tcpdata
  
  Specifies a TCPDATA data set from SYSTCPD of TCPIP PROC.
  
  Default: TCPIP.TCPIP.DATA
2. (Optional) If you want to direct output to a data set instead of SYSOUT (the default):
  - Add the following DD statements for the sequential log data sets:
    //LOGGER1 DD DISP=SHR,DSN=hlq.LOGGER1
    
    //LOGGER2 DD DISP=SHR,DSN=hlq.LOGGER2
  - Allocate the sequential log data sets manually with the following attributes:
    Record format: VB
    
    Record length: 1028
    
    Block size: 6144
    
    Cylinders: 20.
  Note: To turn off the logging capability for OFAPROC, contact CA Support for instructions.
Save your changes.

The OFAPROC started task JCL is updated.

Note: Enable these changes by recycling the agent.
Update the MJETJOM model JCL member in your_db2tools.hlq.CDBAMDL as follows:
1. (Optional) If you are using JES3, replace the /*JOBPARM S=%SYSTEM statement with //*MAIN SYSTEM=%SYSTEM.
2. Set %CHRPFX to the high-level qualifier prefix for the CA Chorus target library data set name prefix (hlq.CETJPLD). This value must match the value that is specified during the installation of CA Chorus.
3. Add the following DD statement for the TCPDATA data set name to all steps executing FLQMASTT:
```
//SYSTCPD  DD DISP=SHR,DSN=&tcpdata
```
  &tcpdata
  
  Specifies a data set from SYSTCPD of TCPIP PROC.
  
  Default: TCPIP.TCPIP.DATA
Save your changes.

The MJETJOM model is updated and Object Migrator is configured for use in the CA Chorus Investigator.