Previous Topic: Create Schema for CA Datacom Users

Next Topic: Allocate CAIKRPAR


Create and Load Tables

To execute JCL members CAKRTBLI and CAKRTBLO follow this two-step procedure. Both members invoke the CAKRTAB procedure found in the CAJRPROC library. Update CAKRTAB according to directions found in the member, before executing CAKRTBLI and CAKRTBLO.

  1. Member CAKRTBLI in CAJRJCL allocates and loads the required tables for JARS/OLF. This member also creates indexes and synonyms for the owner ID and loads and commits the startup definitions.

    This jobstream consists of four steps. Each of these steps utilizes input from additional CAJRSQL members. An overview of the steps and the input statements is provided in this table. The last two columns of the table indicate whether customization is required for DB2 or CA Datacom.

Step

Description

Input

DB2

Datacom

STEP010

Creates Tables

CAKRDC8

N/A

Y

 

 

CAKRDB8

Y

N/A

STEP020

Create Synonyms

CAKRCR84

Y

Y

STEP030

Load Dispatch Tables

CAKSCR81

N

N

STEP040

Load JARS/OLF Tables-IVP

CAKRCR88

N

N

For CA Datacom, customize input members CAKRDC8 and CAKRCR84. In member CAKRDC8, change PMA490 to reflect the correct database name. In member CAKRCR84, change owner ID to the DB owner ID.

For DB2, customize CAJRSQL library members CAKRDB8 and CAKRCR84. For member CAKRDB8, change DSNDB04 to reflect the correct database name. For member CAKRCR84, change owner ID to the DB owner ID.

Continue by, customizing the CAJRJCL library member CAKRTBLI. The STEP010 step must be reviewed to make sure that the INPUT symbolic reflects the appropriate input, either CAKRDC8 or CAKRDB8. To verify that processing complete, submit the job and review the output with a return code of 0.

Note: Input members are from CAJRSQL.

  1. Member CAKRTBLO loads JARS/OLF IRD/ORD tables. Edit this member and select only the tables that you want to load.

    Note: For more information, see the predefined JARS History Records of the CA PMA Chargeback JARS/OLF User Guide.

CAJRSQL library members that are distributed with the product are used as input to program CAKRINST include SQL COMMIT statements after every one hundred inserts. All work to the point of the comment statement is entered into the database and held storage is freed.

Important! This procedure removes the ROLLBACK capability if the job fails for any reason. Create necessary BACK-UPS for tables that will be modified after initial installation before using CAKRINST.