The ACFDBVSM utility merges CMS database records into existing VSAM databases. If no existing VSAM databases exist, it creates them. Only sites running VSAM can use this utility.
Before you can run ACFDBVSM, you must define the input CMS databases with FILEDEFs and define the output VSAM databases with DLBLs.
You might also need to run the ACFLINIT utility before you can create or merge the VSAM databases. See ACFLINIT ‑ Initializing VSAM Databases later in this chapter for information.
The syntax to define the input CMS databases is:
FILEDEF ddname DISK fn DATABASE fm
The ddname of the CMS file where the data to merge or create resides. Valid options are LID, RULES, or INFO.
The filedef of a disk file (always DISK).
The filename of the database file to merge or create.
The filetype of the database (must be DATABASE).
The filemode of the minidisk containing the backup file to merge or create.
Enter the following command to define a DLBL for the VSAM catalog:
DLBL IJSYSCT fm DSN catname (VSAM
The filemode of the disk where the catalog resides.
The DSN of the catalog.
Enter the following command to define a DLBL for the VSAM files to be merged or created:
DLBL ddname fm DSN dsn (VSAM
The ddname of the VSAM database to merge into. Valid options are VLID, VRULES, or VINFO.
The filemode of the disk where the VSAM database resides.
The actual VSAM data set name that IDCAMS defined that is to be merged.
ACFDBVSM merges or creates all three, or any combination of, CA ACF2 for z/VM databases. The syntax for this utility is:
{ [ LID ]}
ACFDBVSM { ALL | [ RULES ]} [NOUPD] [NOAUDIT]
{ [ INFO ]}
Indicates you want to merge or create all three CA ACF2 for z/VM databases (Logonid, Rule, and Infostorage).
Indicates you want to merge or create the Logonid database.
Indicates you want to merge or create the Rule database.
Indicates you want to merge or create the Infostorage database.
Indicates CA ACF2 for z/VM does not modify the specified databases. You can use this parameter for a test run.
Suppresses the records normally written to the audit file during the rule database merge.
Execute ACFDBVSM with the NOUPD option before actually merging the databases. Using the NOUPD option produces a report highlighting the affected records without actually updating them.
CA ACF2 for z/VM displays messages indicating that it replaced or inserted records when the utility successfully executes.
A sample of the ACFDBVSM utility (ACFVSM SAMPEXEC) is provided with CA ACF2 for z/VM Security for VM. To use the sample exec, edit it and make appropriate modifications to the FILEDEF statements.
After ACFDBVSM executes, CA ACF2 for z/VM creates the RULES AUDIT A file that contains any rules that CA ACF2 for z/VM could not merge. Examine this file to determine why ACFDBVSM could not merge any specific rules. Also determine if you need to manually compile these rules.
After running ACFDBVSM, the shared databases have the characteristics shown below.
ACFDBVSM does not alter any records that existed only in the VSAM database. It merges any logonid records that only existed on the CMS database into the VSAM database unaltered.
If any logonid records existed in both the CMS and VSAM databases, the VSAM records remain unmodified, with the following exception. If the record in the CMS database was updated or logged onto more recently than the VSAM record, ACFDBVSM uses the password from the CMS database record.
ACFDBVSM does not alter any rule record that existed only on the VSAM database. It copies rules that existed only on the CMS database over to the VSAM database.
If a rule existed on both databases, ACFDBVSM merges the rule entries and replaces the resulting rule in the VSAM database. If an error occurs merging the rule entries, ACFDBVSM creates the RULES AUDIT file that contains the rule. The VSAM rule remains unmodified.
ACFDBVSM does not alter any record that existed only on the VSAM database. It copies records that existed only on the CMS database over to the VSAM database. If a record existed in both databases, no action occurs (the VSAM record remains unmodified).
|
Copyright © 2009 CA Technologies.
All rights reserved.
|
|