Backing Up the User Profile Database › Reasons to Backup

Reasons to Backup

There are many reasons to save the CA Auditor user profile database (DBASE1). By backing up this database, you ensure that all of the data CA Auditor retained is available for later review, even if new versions of CA Auditor are installed since you last used the database. For example, you might need the data for follow up comparisons of programs or files that you “froze” during an earlier review. Similarly, CA Auditor traveling license users can back up the database on tape upon completion of their reviews. In any case, because the user profile database is the only data set that is actually modified when you run CA Auditor, it is a good precaution to periodically make a backup copy. Establish a regular schedule for making backups of the user profile database.

You can use the following sample JCL to create or restore a backup copy of the user profile database, prefix.EXAMINE.DBASE1. Because the database is implemented using a standard partitioned data set (PDS), you can use IEBCOPY unload and load operations to create and restore backup copies. You can also use this backup and restore sequence to increase the size of the data set.

In both sample job streams, make appropriate substitutions for the JOB statement and DD statement operands that appear in lowercase.

If you are moving from an earlier release of CA Auditor, you need to double the size of the storage allotted to DBASE1.