CICS VSAM Transparency for z/OS, Version 1.2


DB2 considerations

A DDM contains SQL and produces a DB2® DBRM that is bound into a DB2 package in the step called BIND. The parameters that CICS® VT uses in this step are provided by a skeleton that you can customize.

The skeleton is a member in the my .SVIDSAMP. custom data set, and the default name is VIDBIND. Customize this member so that the DB2 parameters for the DDM conform to your local DB2 standards. Tailoring instructions are included as comments in the default member.

Start of change CICS VT requires the default DB2 plan to match the DIM name. You can override the plan name using a JCL DD statement, which is explained in Overriding the default DB2 plan name . End of change

Instead of updating the VIDBIND member, you can create one or more alternative members in my .SVIDSAMP. custom . Specify the name of the member you want to use in the CICS VT main menu option BIND model in SVIDSAMP . For example, your DB2 local standards might dictate that you have different collections for different migrated data sets. In this case, create multiple bind skeletons, and specify which one to use in the panel shown in Figure 3 . You should also consider creating a bind skeleton with the EXPLAIN (YES) option in order to verify that your DB2 access paths are correct. The PLAN_TABLE should show a matching index scan for all CICS VT access paths.

If your application program already contains SQL, then you will have existing DB2 packages bound into an existing plan. In this case, rebind the existing application plan to include both the existing packages and the CICS VT DDM driver package. You should understand clearly the operational implications of migrating a VSAM data set to DB2 before you migrate your first file. These are detailed in CICS VT operational and recovery considerations .





Last updated: May 25, 2012 20:43:59