Previous Topic: Examples: AUTOERASE control optionNext Topic: Examples: BACKUP control option


BACKUP—Backup the Security File

Valid on z/OS and z/VM.

Use the BACKUP control option to:

All entry methods are accepted.

Note: The MODIFY command can be used to override the entry in the Parameter File if BACKUP is set to OFF. This option only works if the Backup DD card is included in the start JCL.

This control option has the following format:

BACKUP blank|(hhmm)|(OFF)
blank

If the backup DD statement is in the CA Top Secret STC procedure CA Top Secret immediately backs up the Security File.

hhmm

If the backup DD statement is in the CA Top Secret STC procedure CA Top Secret backs up the Security File at the time specified.

Default: 0100

OFF

CA Top Secret discontinues automatic backup of Security File. CA Top Secret must be restarted to reset BACKUP(OFF).

Use of BACKUP Option

Use of the BACKUP option is contingent on two factors:

When CA Top Secret Will Not Perform BACKUP

CA Top Secret will not back up the Security File on the same day that CA Top Secret is started, unless it is started BEFORE any scheduled backup time.

Multiple CPUs

It is only necessary to perform backup from one CPU in a multiple CPU environment. The site need only activate backup through one CPU's CA Top Secret Parameter File or STC procedure. Multiple backups are redundant, and will not occur at the same time due to device locking.

D37 Abends

D37 abends during backup indicate the Backup File is too small. Recreate the Backup File according to instructions in the Installation Guide.

Recommended Use

Security administrators should use the automatic backup feature to protect the Security File. To use the backup feature, the security administrator or programmer must first create a backup file on an alternate DASD volume. This Backup File should be placed on a different string with a different control unit than the primary file. This will ensure that the Backup File is available in the event of a hardware failure. This Backup File is a copy of the Security File, and as such it must be considered a sensitive, high‑risk data set.