Expanded Retention Option › Writing ERO Table Statements › Primary Disk Retention

Primary Disk Retention

The following are parameters used to define disk retention; this list provides the following:

• Clarification of ERO processing
• Explanation of how the parameters pertain to Primary/Secondary Disk Retention
• Definition of the default processing that occurs when specific parameters are missing.

COPIES=nnnnn

Specifies the total number of unique copies of a report that are to be retained by CA View (valid values are 0 to 32767). If DCOPIES is specified and COPIES is omitted, COPIES defaults to DCOPIES. If the value of DCOPIES exceeds COPIES, the value in DCOPIES will be used for COPIES.

If COPIES, GENS, and RETPD are not specified, DCOPIES, DGENS, DRETPD, and D2RETPD will define the total retention.

DCOPIES=nnnnn

Specifies the number of copies of the report that are to be retained on primary disk or optical/secondary disk for the SYSOUT ID (valid values are 0 to 32767).

DCOPIES is intended to be specified with COPIES to limit the number retained on disk. If COPIES is specified and DCOPIES is omitted, DCOPIES defaults to COPIES.

If the report is migrated to optical/secondary disk, DCOPIES will govern the optical/secondary disk retention unless D2RETPD is specified.

DGENS=nnnnn

Specifies the number of generations of the report that are to be retained on primary disk or optical/secondary disk (valid values are 0 to 32767). DGENS is intended to be specified with GENS to limit the number retained on disk. If GENS is specified and DGENS is omitted, DGENS defaults to GENS.

If the report is migrated to optical/secondary disk, DGENS will govern the optical/secondary disk retention unless D2RETPD is specified.

DRETPD=nnnnn

Specifies the number of days that a report is to be retained on primary or optical/secondary disk (valid values are 0 to 32767). DRETPD is intended to be specified with RETPD to limit the number retained on disk. If RETPD is specified and DRETPD is omitted, DRETPD defaults to RETPD.

If the report is migrated to optical/secondary disk, DRETPD will govern the optical/secondary disk retention unless D2RETPD is specified.

If DRETPD is omitted and D2RETPD is specified, then DRETPD will default to D2RETPD.

Note: See DRETPD under the Optical/Centera options.

D2RETPD=nnnnn

Specifies the number of days that a report is retained on optical/secondary disk (valid values are 0 to 32767).

D2RETPD is intended to be specified with DRETPD to provide separate retention for optical/secondary disk and primary disk.

If D2RETPD is not specified, DCOPIES, DGENS, and DRETPD will govern the optical/secondary disk retention and the report will be deleted from primary disk after it is migrated.

GENS=nnnnn

Specifies the total number of generations of a report that are to be retained by CA View (valid values are 0 to 32767). If DGENS is specified and GENS is omitted, GENS defaults to DGENS. If the value of DGENS exceeds GENS, the value in DGENS will be used for GENS.

IRETPD=nnnnn

Specifies the number of days (0 to 32767) that any page indexes defined for the reports are retained on disk.

LRETPD=nnnnn

Specifies the number of days (0 to 32767) since the report was last accessed, before it is deleted from primary disk.

The DSK2DAYS parameters (initialization parameter and ERO table parameter) should not be greater than LRETPD, because if a report is deleted from primary disk, it will not be available for migration to optical disk.

LRETPD overrides the HOLDTEMP initialization parameter. HOLDTEMP sets a global default for the number of backup cycles to occur before a temporary disk report (loaded from tape to disk) is deleted.

REGDAYS=nnnnn

REGDAYS controls the number of days that a report will be non-deletable in CA View. When the parameter is used in the ERO table, matching reports will be flagged as non-deletable until a calculated REGDAYS date has been reached. (Valid values are 0 to 32767).

Be aware of the following:

• The REGDAYS date is calculated by adding REGDAYS to the report ARCHIVE date.
• Once a REGDAYS date is assigned to a report, it can only be extended and never shortened via changes in the ERO table.
• The SARBCH /CHANGE ARCHDATE function will fail with a message if the target report is under REGDAYS control.

Example 1:

• If a report was archived on 10/01 with REGDAYS=20, it cannot be deleted before 10/21.
• If on 10/05 the ERO table entry is changed to REGDAYS=5, new reports for that day (10/05) will be non-deletable until 10/10 but the 10/01 copy will be non-deletable until 10/21.

Example 2:

• If on 10/05 the ERO table entry is changed to REGDAYS=25, new reports for that day (10/05) will be non-deletable until 10/30.
• Note that the 10/01 copy will be non-deletable until 10/26 because the new REGDAYS value (25) was greater than its old REGDAYS value (5).

Note: Even if a user is authorized to delete the report, the delete will fail if it is prior to the REGDAYS date.

Centera Considerations:

Any time a report under REGDAYS control is migrated to Centera storage, the Centera retention period will be set to the CA View REGDAYS date.

Centera retention is specified in seconds from the Centera creation date which is based on GMT time. CA View will apply a local time zone adjustment to number of seconds so report is retained until midnight local time.

LRETPD=nnnnn

Specifies the total number of days that a report is to be retained by CA View (valid values are 0 to 32767). If DRETPD is specified and RETPD is omitted, RETPD defaults to DRETPD. If the value of DRETPD exceeds RETPD, the value in DRETPD will be used for RETPD.