Write Statements

ERO table statements are made up of SYSOUT IDs (including wildcards), parameters, and the values you set for those parameters.
view
ERO table statements are made up of SYSOUT IDs (including wildcards), parameters, and the values you set for those parameters.
Expanded retention table entries are input to the
View
started task using the SARPATAB DD statement. Expanded retention table statements are written as follows:
/
sysout-id
{ALL|MARK|LAST} RETPD=
nnnnn
GENS=
nnnnn
COPIES=
nnnnn
DRETPD=
nnnnn
DGENS=
nnnnn
DCOPIES=
nnnnn
IRETPD=
nnnnn
LRETPD=
nnnnn
STORGRP=
storage-group-name
DSK2DAYS=
nnnnn
DSK2NOTP D2RETPD=
nnnnn
REGDAYS=nnnnn
VIEWTAPE={YES|NO} XCOND={YES|NO} EXCLUDE DELETE
  • The data set can be either a sequential file or a member of a partitioned data set. The data set attributes should be Fixed or Fixed Blocked with a Logical Record Length from 80 to 256 characters in length. Code the slash in column 1 followed immediately by the SYSOUT ID.
  • One or more blanks must follow the SYSOUT ID and separate it from the ERO table parameters.
  • Parameters are separated by one or more blanks and/or commas, and can be specified in any order.
  • A statement that exceeds the Logical Record Length minus 8 characters must be continued on additional statements. The last 8 columns of each logical record are reserved for statement numbering. When continuing a statement, interrupt the statement between complete parameters only, and omit the slash on the continuation statement.
  • An asterisk in column 1 indicates a comment line.
Contents
SYSOUT ID Guidelines
The SYSOUT ID is the first parameter in the statement. The wildcard character (*) can be specified at any position in the ID to indicate that any single character can match in that position (for example, AB**D* is a valid SYSOUT ID entry).
You should list SYSOUT IDs from the most specific to the most general because ERO evaluation is triggered from the first matching entry found, searching from the top of the table.
The following is an example of specific-to-general listing statements:
/ABCD* SPECIFICATION2 /ABC* SPECIFICATION1
Note:
We recommend that you end the table with a "/* ALL …" entry. This entry governs any reports that did not match any previous entry in the table. Use this "catch-all" entry to specify retention for nonmatching reports on this database. A typical statement is:
/* ALL DRETPD=5 RETPD=30
This statement indicates that if a report is not matched by any other ERO table statement, it will stay on disk for 5 days and on tape for 30.
If a SYSOUT is selected for retention through the online K command or SARBCH /PERM statement), the PCOPIES initialization parameter is used as the default value for tape and disk retention.
Note:
If the SYSOUT-Id contains spaces, enclose it in quotes (single or double). Any quotes in Report-id must be entered as a pair of quotes because a non-paired quote will end the ID. For example, if the value were JIM’S REPORT it must be entered as ‘JIM’’S REPORT’ or “JIM’S REPORT”.
Selection Parameters
If the ALL, LAST, or MARK parameter is not specified, the initialization parameter POPT is used as a default. We recommend that you specify MARK, ALL, or LAST in each statement, to understand and verify the effects of the statements in your expanded retention table.
  • ALL
    Specifies that all reports for the SYSOUT ID from the current generation are evaluated for ERO processing.
    If you also set the initialization parameter EROPRO=ALL, the entire database is considered for the next backup cycle, not just the current generation. If EXCLUDE is also specified, then all SYSOUT groups are excluded, and are governed by NGEND and NGENT. If ALL is specified, MARK and LAST must not be specified.
    If EXCLUDE is also specified, all SYSOUT groups are excluded; the NGEND and NGENT parameter values are used.
    If ALL is specified, MARK and LAST must not be specified.
  • LAST
    Specifies that the last (most recent) report from the current generation is evaluated for ERO processing.
    LAST is typically used for program compilation listings. If you also set the initialization parameter EROPRO=ALL, the last SYSOUT from every generation is considered, not just the current generation. If LAST is specified, MARK and ALL must not be specified.
  • MARK
    Specifies that all reports for the SYSOUT ID for the current generation are evaluated for ERO processing, only if marked manually.
    Manual marking for ERO selection is done with the online K (KEEP) command, and in batch with the PERM statement of the SARBCH utility. If MARK is specified, LAST and ALL must not be specified.
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
    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
    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
    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
    View
    REGDAYS date.
    Centera retention is specified in seconds from the Centera creation date which is based on GMT time.
    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
    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.
Disk Retention Parameter Guidelines
Specifying the amount of retention in days with the DRETPD parameter for disk and RETPD parameter for tape clarifies the effect of the ERO table on a report's retention -- it will be kept for
nn
days. Specifying the DRETPD parameter is the most efficient processing method, because
View
can use a simple arithmetic calculation on the archival date.
When the tape retention criteria are satisfied, the SYSOUT ID is no longer in expanded status, even if the disk retention criteria are not satisfied.
We recommend that you specify the following disk parameters with the corresponding tape retention:
Disk Retention Parameter
Tape Retention Parameter
DRETPD
RETPD
DCOPIES
COPIES
DGENS
GENS
Note:
If you do not specify a disk retention parameter, disk retention is the same as the tape retention. If you specify disk retention, but not tape retention, tape retention will be the same as disk retention. If you specify both tape and disk retention, that is. RETPD=5 DRETPD=10, tape retention will be changed to the larger value, in this case 10.
Tape Retention Parameters
COPIES=nnnnn
Specifies the total number of unique copies of a report (0 to 32767) that are retained on tape for the SYSOUT ID.
RETPD=nnnnn
Specifies the total number of days (0 to 32767) that a report with the SYSOUT ID is retained on tape.
GENS=nnnnn
Specifies the total number of
View
generations (0 to 32767) that a report with the SYSOUT ID is retained on tape.
Tape Retention Parameter Guidelines
We recommend that you use only one tape retention parameter per entry; however, if you use more than one parameter, each parameter must be satisfied before a SYSOUT no longer has expanded retention (PERM) status. For example, suppose you have COPIES=3 and RETPD=30 for a SYSOUT that is created daily. All copies are kept for 30 days. The most recent three copies are kept indefinitely.
When the tape retention criteria are satisfied, the SYSOUT ID is no longer in expanded status, even if the disk retention criteria are not satisfied.
If no ERO tape or disk retention is specified (COPIES, DCOPIES, RETPD, DRETPD, GENS, DGENS), then the initialization parameter PCOPIES is used as the default.
Tape Location (STORGRP)
STORGRP
specifies the tape storage group for SYSOUT. These group names can be unique for your location -- they are linked to STORGRP1 through STORGRP9.
For more information about tape, see
Initialization Parameters
.
Syntax:
STORGRP=group-name
Notes:
  • If you use the expanded access server for tape and robotics, you should consider grouping reports based on how frequently they are accessed to minimize tape mounts and improve performance. You can also group reports by their retention requirements, so the distribution of expired reports on tape is less fragmented, reducing the need for tape consolidation.
  • We recommend that you assign STORGRP1 the group name with the largest number of reports to enhance backup cycle performance. You use the SARINIT initialization parameter STORGRP1 to assign the group, for example:
    STORGRP1=largest-group-name/
  • The ERO Table Statement STORGRP parameter is used to direct these reports to the storage group. For example:
    /PAYROLL* ALL DRETPD=30 RETPD=365 STORGRP=YEAR1
Tape Online Access VIEWTAPE
VIEWTAPE specifies whether the SYSOUT can be viewed if it resides
only
on tape.
Syntax:
VIEWTAPE=YES|NO
The default is YES.
Optical Disk Migration DSK2DAYS
DSK2DAYS specifies the number of days (1 to 998) a report remains on primary disk before it is migrated to secondary disk.
Syntax:
DSK2DAYS=
nnn
Setting the value to 0 specifies that SYSOUT groups be migrated to secondary disk during the next
View
backup, scheduled run of the migration subtask, or migration batch job. Setting the value to 999 specifies that SYSOUT groups will never be migrated to secondary disk.
In addition, a DSK2DAYS initialization parameter sets a global default value.
Optical Disk Retention DSK2NOTP
Use the DSK2NOTP parameter to specify that if a report resides on optical disk and a tape backup exists, it is to be deleted from the tape backup.
Syntax:
DSK2NOTP
If you do not specify this parameter, tape backups are still maintained. If you specify:
DSK2DAYS=0 DSK2NOTP
and a report recently archived to the
View
database migrates to DSK2 before the next backup cycle, no tape backup is ever created.
Exceptional Condition Processing
Use the XCOND keyword for reports that contain JCL MSGCLASS data.
Syntax:
XCOND={YES|NO}
With XCOND you can specify whether
View
is to consider SYSOUTs that had exceptional conditions, for example, JCL errors, ABENDS, and so on, for ERO evaluation.
  • YES
    The report is selected even though an exception is present.
  • NO
    The report is bypassed for ERO processing when an exception is present.
You can set the following parameters:
  • ERO initialization parameter PXCOND=NO to bypass JCL reports containing exceptional conditions for the entire database.
  • ERO table parameter XCOND=NO for any individual table entry to bypass reports with exceptional conditions governed by that entry.
You can further refine conditional selection for ERO processing by creating user-defined exceptional conditions.
Notes:
The default for XCOND depends on the setting of PXCOND:
    • The default for PXCOND is YES, which in turn sets the default for XCOND to YES.
      To exclude individual reports from ERO processing, set XCOND to NO when PXCOND is set to or defaulted to YES.
    • To include individual reports in ERO processing, set XCOND to YES when PXCOND is set to NO.
Excluding Reports
Use EXCLUDE to specify that the reports are not to be retained by ERO. These reports are retained in the database based on the NGEND and NGENT initialization parameters.
Syntax:
EXCLUDE
The Keyword DELETE
Use DELETE to specify that when the ERO retention TOTAL criteria expires, the report is deleted (and does not revert to the control of the
View
initialization parameters NGENT).
Syntax:
DELETE
If PRETAIN=TABLE, DELETE is not required and reports are deleted when they expire from the table. DELETE does not affect disk retention. (When disk retention criteria expire, the SYSOUT goes to initialization parameter NGENT control, unless PRETAIN=TABLE.)
We recommend that you specify PRETAIN=TABLE to make the ERO table a single point-of-control.
Considerations:
  • If you specify MARK (or POPT=M), marked reports are assigned the retention specified in the ERO table entry.
    Unmarked reports are considered expired; therefore, they are deleted during the first standard backup cycle following their archival to
    View
    .
  • If you specify LAST (or POPT=L), the retention specified in the ERO table entry is assigned to the last report in the generations being processed.
    The copies that precede the last copy in the generations being processed are considered expired; therefore, they are deleted during the first standard backup cycle following their archival to
    View
    .