Batch Utilities

Use the ddd batch utilities when you are working on a large number of database definition updates and to catalog a database.
cdat
Use the
CA Datacom® Datadictionary™
batch utilities when you are working on a large number of database definition updates and to catalog a database.
For details about these utilities, see the CA Datacom Datadictionary Batch Facilities. When you perform
CA Datacom® Datadictionary™
tasks in batch, you use an editor to create and edit input which you submit with JCL to execute the various
CA Datacom® Datadictionary™
utilities. The utilities execute
CA Datacom® Datadictionary™
transactions to accomplish each task.
The following batch utilities are important to the using products:
  • DDRTVCAT
    This processing utility is provided for use with the CA using products only. It reads the data definitions in
    CA Datacom® Datadictionary™
    and applies them directly to the CXX. For more details about formatting input to the CXX, see the section about defining multiple databases.
  • DDBTGLM
    The Backup/Transport Generator program creates transactions for use with the DDUPDATE utility from selected entity-occurrences in one
    CA Datacom® Datadictionary™
    which can be used to add or update entity-occurrences in another
    CA Datacom® Datadictionary™
    system. You can also use DDBTGLM to create an archive copy of entity-occurrence information in batch transaction format.
  • DDRMFLM
    This utility is used to reformat CA Datacom data records.
  • DDUPDATE
    This update utility is used in the general maintenance processing of entity-occurrences. You can also perform all
    CA Datacom® Datadictionary™
    report functions with this utility.
  • DDUTILTY
    This report utility provides printing batch reports and generating source language statements. The Source Language Generator (SLG) facility allows the field definitions of ELEMENT, KEY, and RECORD entity-occurrences to be reproduced as high-level language (copysection) statements suitable for COBOL, PL/I, or Assembler.
The following topics are described in this section:
DDRTVCAT - Runtime and Verify Catalog Program
For
CA Datacom®/AD
, use the DDRTVCAT (
CA Datacom® Datadictionary™
Runtime Verify and Catalog) Utility to perform the following functions. When these functions are executed, the
CA Datacom® Datadictionary™
VERIFY function is also executed and any resulting error messages are issued. See the
CA Datacom® Datadictionary™
error messages in CA Datacom/DB Messages.
  • -CXX CATALOG
    Specifies the occurrence name of the database to be cataloged to the CXX.
  • -RTV BASIS
    Specifies the occurrence name of the database to be used as a model or base when running the catalog program. The -RTV BASIS transaction is optional. It is used when making an exact copy of an existing database to have multiple databases.
    The database being cataloged cannot be open for update by the MUF or any Single-User job when running DDRTVCAT.
    The CXX is the heart of the
    CA Datacom®/AD
    production system. Therefore, we recommend that you run the DBUTLTY BACKUP AREA=CXX function before executing the DDRTVCAT program. For information about the BACKUP function, see the DBUTLTY.
    Note:
    The name of the CXX is unique for each occurrence of the physical CXX data set.
    The DDRTVCAT program first compares the database description that was shipped with the CA using product to the newly modified database      description and verifies changes. You are only allowed to redefine existing fields and add keys. DDRTVCAT also verifies that no ther changes are made to the shipped database structure. If the DDRTVCAT checks meet the established criteria, the program copies the database to PRODuction status, catalogs the database structure, and enables it for use with CA Ideal for CA Datacom.
Error Messages
The DDRTVCAT error messages are listed in the CA Datacom/DB Messages in the
CA Datacom® Datadictionary™
numbered messages section. The format is DDRTV
cnnnn
.
When to Use
The DDRTVCAT utility is provided for use with
CA Datacom®/AD
. It can, however, also be executed in a full CA Datacom/DB environment.
During the installation of the CA using product, your
CA Datacom® Datadictionary™
is fully populated with the definitions required by the CA using product. If you find that you need to tailor
CA Datacom® Datadictionary™
for your particular requirements, use the DDRTVCAT utility to catalog these changes to the Directory (CXX).
-CXX CATALOG - Cataloging the Definitions to the Directory
Use the -CXX CATALOG transaction submitted through the DDRTVCAT utility to verify the database structure and catalog the occurrence definitions to the
CA Datacom®/AD
Directory (CXX). You can catalog TEST and PRODuction status DATABASE structures.
For the CA Datacom/DB Accounting database, use the DBUTLTY ACCT CATALOG option. See the DBUTLTY Reference  topic.
The syntax for this transaction is:
►►─ -CXX ─ CATALOG ─ ,DATABASE ─
,occ-name
(stat ─┬──────────────┬─ ) ────────►◄ ├─ ,pswd,ovrd ─┤ ├─ ,pswd ──────┤ └─ ,,ovrd ─────┘
  • ,DATABASE
    (Required)
    Indicates that the occurrence is a DATABASE occurrence.
  • ,occ-name
    (Required)
    Specifies a valid DATABASE occurrence name.
    • Valid Entries:
      Any valid DATABASE occurrence name
    • Default Value:
      (No default)
  • (stat)
    (Required)
    Specifies the status of the occurrence used as input to the DDRTVCAT execution.
    • Valid Entries:
      T001 to T999
      PROD
    • Default Value:
      (No default)
  • ,pswd
    (Optional)
    Enter the user-assigned password for the DATABASE occurrence within the parentheses surrounding the stat parameter. If the occurrence is not protected by a password and you must enter an override code, enter the preceding comma.
    • Valid Entries:
      Password assigned to the occurrence
    • Default Value:
      (No default)
  • ,ovrd
    (Optional)
    Enter the system override code within the parentheses surrounding the stat parameter if you are selecting an occurrence which is protected from unauthorized update or access by a lock level. If the occurrence is not protected by a lock level, you can omit the override code and its preceding comma.
    • Valid Entries:
      System override code
    • Default Value:
      (No default)
-RTV BASIS - Modeling a Database
Use the -RTV BASIS transaction to identify the existing database structure on which to model the new database structure.
The following is the format for this transaction:
►►─ -RTV ─ BASIS
,occ-name
────────────────────────────────────────────────────►◄
  • ,occ-name
    (Required)
    Specifies the DATABASE occurrence name for the structure provided by the CA product that is being installed or upgraded.
    • Valid Entries:
      Any valid DATABASE occurrence name
    • Default Value:
      (No default)
Sample Job Streams and Report
z/OS Example JCL
The following sample JCL catalogs the DATABASE structure MY-CLONED-DB (which is validated against the CA-ORIGINAL-DB structure) definition to the CXX.
Note:
Use the following as a guide to prepare your JCL. The JCL statements are for example only. Lowercase letters in a statement indicate a value you must supply. Code all statements to your site and installation standards.
//jobname
See the note above and
Listing Libraries for CA Datacom Products in JCL. // EXEC PGM=DDRTVCAT,REGION=600K //STEPLIB
See the note above and
Listing Libraries for CA Datacom Products in JCL
.
\ //SYSPRINT DD SYSOUT=a Print output //SYSPUNCH DD SYSOUT=b Punch output //SNAPER DD SYSOUT=a dumps //SYSUDUMP DD SYSOUT=a System dumps //SYSIN DD * Input transactions -USR sample-user,password Authorized user information -CXX CATALOG,DATABASE,MY-CLONED-DB(T001) -RTV BASIS,CA-ORIGINAL-DB /*
Sample Report - DDRTVCAT
The report contains the following:
  • The information that can be entered for this transaction followed by the transaction as entered.
    CODE FUNCTION,ENTITY-TYPE,OCCURRENCE(VERS,PSWD,OVRD) -CXX CATALOG,DATABASE,MP602(T001) ; CODE FUNCTION,BASIS -RTV BASIS,MP300
  • The first function is the
    CA Datacom® Datadictionary™
    VERIFY function to compare the existing database definition to the new database definition.
FUNCTION = VERIFY-OLD-TO-NEW ENTITY-TYPE = DATABASE OCCURRENCE = MP303
  • The next VERIFY function compares the new database definition to the existing database definition.
    FUNCTION = VERIFY-NEW-TO-OLD ENTITY-TYPE = DATABASE OCCURRENCE = MP303 *** VERIFY ERROR MESSAGES *** TOTAL ERRORS 0
  • CA Datacom® Datadictionary™
    copies the new database definition from TEST to PRODuction status.
    FUNCTION = COPY-TO-PROD ENTITY-TYPE = DATABASE OCCURRENCE = MP303
  • CA Datacom® Datadictionary™
    catalogs the new database to the Directory (CXX).
    FUNCTION = CATALOG-STRUCTURE ENTITY-TYPE = DATABASE OCCURRENCE = MP303
  • CA Datacom® Datadictionary™
    enables the new database definition.
    FUNCTION = ENABLE-STRUCTURE E ENTITY-TYPE = DATABASE OCCURRENCE = MP303
  • A message indicating that the job has ended.
* END OF JOB