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, create [set the rcm variable for your book] models and the Object Migrator configuration PDS and members. In addition, update the OFAPROC started task, and MJETJOM model JCL.

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

Important! This step must be performed manually outside of CA Chorus™ Software Manager.

The OFAPROC started task ID needs READ permission for BPX.SERVER.

Note: 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. The OFAPROC started task was created and customizing during the configuration of the Object Framework Services agent (OFA) during the installation of the CA Database Management Solutions for DB2 for z/OS. For more information about configuring the OFA agent, see the CA Database Management Solutions for DB2 for z/OS Installation Guide.

Note: To execute the [set the rbp variable for your book], 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:

Create a default model for global configuration and optional user-specific models for individual user configurations by completing the following steps using [set the rcm variable for your book]:
Note: Any @DEFAULT model can be used.
1. Type PROF on the [set the rcm variable for your book] Main Menu and press Enter.
  The Expert Profile panel appears.
2. Type 6 for Utility Model Services on the Option line and press Enter.
  The General Model Services panel appears.
3. Type T next to an existing model to create a template (copy).
  The General Model Utilities panel appears.
4. Specify a name for the model in the Model ID field and press PF3.
  The model is created and saved with the name (model ID) and creator. These models are used during the DB2 object migration when the migration is submitted for analysis.
Create the Object Migrator configuration data set (config.om.pds) and members by completing the following steps:
1. Create the Object Migrator configuration PDS with the following attributes:
  - Tracks: 2
  - Record format: FB
  - Record length: 80
  - Block size: 27920
  The configuration PDS is defined.
2. Create an @DEFAULT member in the configuration PDS and optional members for each Object Migrator user.
  The members appear in the configuration data set members list. Object Migrator user members override global settings that are defined in the @DEFAULT member.
3. Add the following JCL to the @DEFAULT member, replacing the italicized text with site-specific values:
  Note: The members must include the desired JOB statement for z/OS batch jobs and the model name and creator.
```
<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>
```
  Note: Use the JOB statement, model name (ID), and creator values for overriding global settings that are defined in the @DEFAULT member. For more information about overriding high-level qualifiers for work data set allocations, see the CA Chorus for DB2 Database Management User Guide.
  
  <JOB CARD> </JOB CARD>
  
  Specifies the JOB statement details.
  
  <MODEL4></MODEL4> and <MODEL4C>/</MODEL4C>
  
  Specifies information that is required for the Object Migrator configuration including the model ID and creator. The model ID specifies an existing [set the rcm variable for your book] model name. Specify @DEFAULT for the global configuration member. If you created models, the model ID and creator must match the models that you created. The creator specifies the model creator user ID.
  
  Save your changes.
  
  The @DEFAULT global configuration member is created.
4. Repeat the previous step.
  The JCL is added to the individual user members.
Update the OFAPROC started task JCL:
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.