New Features › New Database Structure Using CA Datacom/AD

New Database Structure Using CA Datacom/AD

In this version, tables in a CA Datacom/AD database replace the VSAM database (SASJOB, SASDS, IDS, ARF, and VRM) and the status queue data sets. This CA Datacom/AD database that replaces these files is defined, allocated, and initialized in the steps after the CA Datacom/AD installation but before the CA WA CA 7 Edition installation SYSGEN process.

Moving to the relational CA Datacom/AD database provides several advantages over the previous structures:

• Backup while open (24 hours a day, 7 days a week up time).
• Built-in logging and audit capabilities.
• Inherited compatibility with new storage device types.
• Built-in growth and scalability.
• SQL reporting facilities.

With this version, a single CA Datacom/AD MUF can contain more than one CA 7 instance database. For example, you can execute instances CA71, CA72, and CA73 all in the same LPAR or sysplex. All three instances can use the same CA Datacom/AD MUF for their copy of the database. They are distinguished from one another by a logical database name. Carefully consider the naming of the logical database, as multiple databases can occur in one MUF. Also, workload moves from one system to another. In this case, a logical database name of CA71 can present a conflict when moving to another MUF that already has a logical database name of CA71. The logical database name can contain up to 16 characters. We recommend that the name indicates the type of system the instance represents, such as DEVELOPMENT or INTERNALSYSTEMS.

The logical database name for a CA WA CA 7 Edition system is specified using the DBNAME keyword on the U7PARMS initialization file statement in the SYSGEN process. The logical database name is also found in the DBPARMS file where the “ALLVSAM” data sets were previously defined.

As a result, with this version, review all jobs using CA WA CA 7 Edition utilities, procedures, user modifications such as tables and exits, and other items relating to CA WA CA 7 Edition. Many items require only updating the STEPLIB (if CA WA CA 7 Edition modules are not in the linklist). If you have tables and user exits, reassemble them using the Version 12.0 libraries. CA WA CA 7 Edition can now detect whether the tables or exits were assembled using the current release.

Note: For more information about the installation and conversion, see the Installation Guide.

Many changes in this version result from using CA Datacom/AD. Read through this entire guide. The significant changes are mentioned here in this section, but other changes are mentioned in the next chapter.

Note: For more information about the exits and backup and recovery, see the Systems Programming Guide.