Data Sets and Environmental Considerations

This article describes the data sets that the system uses. Review this article and also the articles about the
View
Database and .
view122
This article describes the data sets that the system uses. Review this article and also the articles about the
View
Database
and Environmental Considerations.
2
Tape Archival Data Set
View
automatically creates and deletes the tape archival data sets (also referred to as backup tape data sets). One data set is created per tape volume. SYSOUT groups and the backup of the master index are written sequentially to the same tape data set and are separated from each other by EOD records. The first record written to the tape for a SYSOUT group is the group's GCR. Using the high-speed block ID positioning,
View
can quickly "spin down" to any SYSOUT group for retrieval.
As much SYSOUT as can fit on a tape is written to that tape. When the end of the tape is sensed or an I/O error occurs,
View
terminates the tape data set. Then, it allocates a new data set on another tape volume, and continues writing to the new volume.
Initialization Parameters and Tape Archival
The unit name used for allocation is specified on the STORGRP
n
(0-9) initialization parameter. The TVSER1 and TVSER2 sub parameters can be specified to assign a range of tapes for
View
to use. The MAXGENT initialization parameter can be used to limit the number of generations of SYSOUT that are written to the same tape volume.
As part of its backup cycle,
View
uncatalogs any tape that is no longer needed.
Note:
Tapes created by the backup cycle do not uncatalog until all of the following conditions are true:
  • All reports are expired
  • The tape is older than five days
  • The highest generation on the tape is less than the current generation minus the NGENI initialization parameter value
The EXPDT initialization parameter can be used to determine when a tape is available for scratch.
Uncataloging Tapes
As part of the backup cycle,
View
creates backup copies of reports on tape and catalogs the tapes. Retain these tapes under catalog retention in your tape management product. Doing so prevents the tapes from being returned prematurely to the scratch pool, which could result is loss of data.
Most tape management products use a special expiration date (for example, 99000) to indicate catalog retention. Determine this special expiration date for your tape management product. Specify this date on the EXPDT initialization parameter.
View
manages the use of these tapes and uncatalogs the tapes under the following conditions:
  • All reports are expired or no longer reside on the tape
  • The tape is older than five days
  • The highest generation on the tape is less than the current generation minus the NGENI initialization parameter value
You can optionally use your tape management product to uncatalog
View
tapes under the following conditions:
  • View
    tapes are part of a test database. The test database and tape are no longer needed.
  • View
    tapes were the original tapes from a merged database, and the tapes have been consolidated onto new tapes. Before you uncatalog a tape, verify that it is no longer being used, by performing a SARTSLST on any applicable databases.
  • The backup tape is being copied to a new volume, whereby the old tape is being uncataloged and the new tape is being cataloged.
Over time, you might decide to change the high-level qualifier of the tape data sets; typically, you use the STORGRP0 initialization parameter. Making this change results in
View
managing tapes that are historically related but have different high-level qualifiers. If you have made this change but you later decide that you want all historically related tapes to have the same high-level qualifier, consider the following options:
  • Consolidate the historically related tapes under the new high-level qualifier. Use the SARPAC tape consolidation utility.
  • Load the reports to disk and mark them to be backed up again to tape. Use the /CHANGE BACKUP=OFF statement of the SARBCH utility.
    Do not use your tape management product to uncatalog the tape data set under an old high-level qualifier name.
    View
    uncatalogs these tapes when they are no longer needed.
Copying Tapes
Due to the special format of the
View
tape archival data sets, normal utilities generally cannot be used to copy archival tapes. A special utility, SARTCP, is provided for this purpose. In addition, the utility maps the contents of a tape and can be used to salvage SYSOUT from a damaged tape.
Note:
For more information about tapes, see Database Utilities.
Attributes and Naming Convention
RECFM=VB LRECL=32756 BLKSIZE=32760
The data sets are assigned names in the following format:
Syntax
index.SARTAPE.Tnnnnnnn
Where
  • index
    Specifies the high-level index used to name the
    View
    database. This high-level qualifier can be overridden on the STORGRPn(0-9) initialization parameter.
  • nnnnnnn
    Specifies the sequence number of the tape data set.
Tape Duplex Data Set
The tape duplexing feature of
View
allows a site to obtain a duplicate copy of their backup tape data sets. When this feature is activated, an additional tape is mounted during the backup cycle and during direct to tape archival. All I/O to the original backup tape is simultaneously written to the duplex tape data set. This feature is activated by specifying
unit2-name
which is a subparameter of the STORGRP
n
(0-9) initialization parameter.
Unit2-name
is used to allocate the tape duplex data set.
DTVSER1 and DTVSER2 can be specified to assign a range of duplex tapes for
View
to use. DTVSER1 and DTVSER2 are sub parameters of the STORGRXn(0-9) initialization parameter.
Attributes and Naming Convention
DCB attributes for the data sets are:
RECFM=VB LRECL=32756 BLKSIZE=32760
The data sets are assigned names in the following format:
Syntax
index.SARDPLX.Tnnnnnnn
Where
  • index
    Specifies the high-level index used to name the
    View
    database. This high-level qualifier can be overridden on the STORGRPn(0-9) initialization parameter.
  • nnnnnnn
    Specifies the sequence number of the tape data set.
    This number is the same as the sequence number from the original backup tape.
DR Tape Data Set
The DR tape feature of
View
allows a site to create a separate backup tape (or tapes) containing all reports that were created since the last backup cycle. This tape can immediately be taken offsite as a DR backup. Unlike the primary or duplex tapes, reports are not appended to the DR tape during the next backup cycle.
To use the DR tape feature, specify DRTAPE=YES in the SARINIT parameters. When the DRTAPE parameter is set to ACTIVE,
View
creates the DR tapes and attempts to access reports on tape using the copy stored on the DR tape. If that copy is not available, the copy stored on the primary or duplex tape is used.
Attributes and Naming Convention
DCB attributes for the data sets are:
RECFM=VB LRECL=32756 BLKSIZE=32760
The data sets are assigned names in the following format:
Syntax
index.SARDRTP.Tnnnnnnn
Where
  • index
    Specifies the high-level index specified in the SARINIT DRTIDX parameter.
  • nnnnnnn
    Specifies the sequence number of the tape data set.
Load/Unload Data Sets
The UNLOAD SARDBASE database function creates a sequential data set for backup purposes. The database records are written in ascending key sequence order to the data set. This data set can be used at a later time to restore the contents of the designated database using the LOAD function.
If the output data set is tape, duplexing is not done.
Attributes and Naming Convention
DCB attributes for the data sets are:
RECFM=VB LRECL=32756 BLKSIZE=32760
The output data set is assigned a name as designated by the user.
Recovery Data Set
This data set resides on a direct-access volume and is used by the backup process of the archival task to keep track of the tapes used to back up the database. The recovery data set is allocated as part of the installation procedure.
This data set is referenced by the
View
archival task and other utilities by using the SARRECV DD statement.
Note:
For more information about recovery data set, see Recovery Data Set.
Attributes
DCB attributes for the data set are:
RECFM=F LRECL=12288 BLKSIZE=12288
Forward Recovery Data Set
This data set resides on a direct-access volume and is used by the archival task to store SYSOUTs that are archived to the database. The forward recovery data set is allocated as part of the installation procedure.
Note:
For more information about forward recovery, see Back Up and Recover Database.
Attributes and Naming Conventions
DCB attributes for the data set are:
RECFM=U LRECL=0 BLKSIZE=32760
The data sets are assigned names in the following format:
index
.SARFRDS.D
nnnnnnn
Where
  • index
    Specifies the high-level index used to name the
    View
    database.
  • nnnnnnn
    Specifies the sequence number of the disk data set.
Accounting File
The accounting file is a direct-access data set used to maintain accounting data on jobs for use by the archival started task. The data set is defined and initialized as part of the installation procedure.
A logical record in the file contains an 8-byte job name and 20 bytes of accounting data selected from type-20 SMF records by the SARACTUX user exit. The location of the logical record in the file corresponds to the job ID of the job.
The accounting file is only used when job accounting is initiated as a
View
extension.
Attributes
DCB attributes for the file are:
RECFM=FB LRECL=28 BLKSIZE=6160
Exceptional Condition Table
The exceptional condition table or exception table is a sequential data set that contains control statements defining specifications for exceptional condition checking. The data set is allocated to the
View
archival started task with the SARXCTAB DD statement.
Note:
For more information about exceptional condition, see Exceptional Conditions.
Attributes
DCB attributes for the file are:
RECFM=F or FB LRECL=80 BLKSIZE=
nnnnn
where
nnnnn
is a multiple of 80.
Expanded Retention Table
The expanded retention table is a sequential data set that contains control statements defining specifications for automatic retention of SYSOUT. The data set is allocated to the
View
archival started task with the SARPATAB DD statement.
Note:
For more information about ERO, see Expanded Retention Option.
Attributes
DCB attributes for the file are:
RECFM=F or FB LRECL=80 to 256 BLKSIZE=
nnnnn
where
nnnnn
is a multiple of LRECL.
The rightmost nine characters of each record (columns 71-80 for a data set with LRECL=80) are ignored and can contain sequence numbers or comment information. If the parameters for a retention specification do not fit on one line, they can be supplied on subsequent lines.