Configure the Optical Disk Interface

These instructions provide an overview of the steps required to configure CA View to use the optical disk storage drivers. The information in this section applies to all CA View optical disk drivers, unless indicated otherwise by the block label (for example, the DSK2PARM parameter explanation in the following section).
view
These instructions provide an overview of the steps required to configure CA View to use the optical disk storage drivers. The information in this section applies to all CA View optical disk drivers, unless indicated otherwise by the block label (for example, the DSK2PARM parameter explanation in the following section).
Read the instructions thoroughly before attempting the configuration.
Contents
The ERO Parameters that Control Retention on Disk Storage
The following ERO Parameters control the disk and total retention of SYSOUTs on Primary and Secondary Disk Storage:
  • DSK2DAYS
  • DRETPD
  • D2RETPR
DSK2DAYS
The syntax of the DSK2DAYS control statement parameter is as follows:
Syntax:
DSK2DAYS=
nnn
The default is 999.
Valid values are 0-999.
  • This parameter determines when a SYSOUT is to be migrated to secondary disk storage. DSK2DAYS can be coded as an Initialization Parameter or as an ERO Table Entry parameter.
  • If DSK2DAYS is coded as an Initialization Parameter and set to a value other than 999, it causes all SYSOUTs to be migrated to secondary disk storage.
    You can perform selective migration by coding 999 for the Initialization Parameter, and coding DSK2DAYS on the selected ERO Table entries.
  • The DSK2DAYS parameters (initialization parameter and ERO table parameter) must not be greater than DRETPD because if a report is deleted from primary disk, it is not available for migration to secondary disk.
DRETPD
The syntax of the DRETPD parameter is as follows:
Syntax:
DRETPD=
nnnnn
If RETPD is coded, and DRETPD is not, the default for DRETPD is RETPD. If both are coded, DRETPD must be less than or equal to RETPD.
Valid values are 0-32767
Specifies the number of days (0 to 32767) that a report is retained on primary disk storage. DRETPD is intended to be specified with RETPD and optionally D2RETPD to limit the number retained on disk.
Note:
With this enhancement, the primary disk storage copy can be kept on primary disk even though the SYSOUT has been migrated to secondary disk storage.
D2RETPD
The syntax of the D2RETPD parameter is:
Syntax:
D2RETPD=
nnnnn
Notes:
  • If D2RETPD is omitted, it defaults to the value specified in DRETPD.
  • If DRETPD is omitted and D2RETPD is specified, DRETPD defaults to D2RETPD.
  • If both DRETPD and D2RETPD are specified, DRETPD must be less than or equal to D2RETPD.
  • This parameter does not cause reports to be migrated to secondary disk. Migration is controlled by the DSK2DAYS parameter.
Valid values are 0-32767
This value specifies the number of days (0 to 32767) that a report is to be retained on optical/secondary disk. D2RETPD is intended to be specified with DRETPD to provide separate retention for optical/secondary disk and primary disk.
Note:
The DSK2DAYS parameters (initialization parameter and ERO table parameter) must not be greater than DRETPD, because if a report is deleted from primary disk, it will not be available for migration to secondary disk.
If DSK2NOTP is coded on the same ERO Table Entry, no tape backup of the SYSOUT is processed. The SYSOUT is completely deleted from CA View when D2RETPD expires regardless of any other retention parameter.
Overview of Configuration Steps
This section presents an overview of the process you must use to configure CA View to use the optical disk interface. These steps are explained in the sections that follow.
  1. Use the DSK2DRVR SARINIT initialization parameter to specify which optical disk driver you are using.
  2. Use the DKS2PARM SARINIT initialization parameter to specify the page-level drivers.
  3. Set optical migration options in the ERO table (with disk and tape migration options), using the following keywords:
    DSK2DAYS DSK2NOTP
  4. Customize optical migration scheduling with the following initialization parameters:
    DSK2MIGD DSK2TIME DSK2INTV
    Note:
    By default, the CA View backup cycle performs all optical migration.
  5. Run SARINIT to implement your initialization parameter settings to the database.
Step 1 Specify the Optical Disk Storage Driver
Specify the optical disk driver that you are using with the DSK2DRVR SARINIT initialization parameter.
This parameter is required; there is no default value.
Syntax:
DSK2DRVR=SARD2D0
n
where:
Value
Description
SARD2D00
IBM ESA/370 and ESA/390 3995 Optical Library Dataserver, model 153, page-level access
SARD2D01
Kodak Optistar report-level access
SARD2D02
FileTek report-level access
SARD2D03
FileTek page-level access
SARD2D04
Kodak Optistar page-level access
SARD2D05
IBM ESA/370 and ESA/390 3995 Optical Library Dataserver, models 132 and 133, page-level access
Step 2 Configure the Page-Level Drivers
Specify the appropriate values for the DSK2PARM SARINIT initialization parameter.
The values for each of the drivers are explained in the sections that follow.
DSK2PARM IBM Page-Level Driver for Models 131, 132, 133
Specify the high-level index prefix for creating the collection and object names for OAM.
Syntax:
DSK2PARM=
index
/
storclas
/
mgmtclas
/
db2id
Notes:
  • The index can be a maximum of 17 characters.
  • The default value for index is the high-level index of the CA View database.
  • Specify the SMS storage class as storclas.
  • Specify the SMS management class as mgmtclas.
  • Specify the DB2 system identifier as db2id.
This identifier must match the entry specified on the SMS subsystem definition in member IEFSSNxx in SYS1.PARMLIB.
DSK2PARM IBM Page Level Driver for Model 153
Specify the high-level index prefix for creating the optical disk data sets.
Syntax:
DSK2PARM=
index
/
unit
/
blksize
Notes:
  • The index can consist of a maximum of 17 characters.
  • If you change the index, older data sets must be renamed with the new index name to be accessible. You can set up a special user's catalog for all of these MVS data sets.
  • The default value for index is the high-level index of the CA View database.
  • Specify the unit name of the pool of optical disk volumes as unit.
  • Specify the block size to be used as blksize. The default is 1/2 track 3390.
DSK2PARM Kodak Optistar Page Level Driver
Specify the unit name of the optical disk for unit.
Syntax:
DSK2PARM=
unit
/
volser1
/
volser2
/
ssid
Notes:
  • Specify the lowest volume serial number in the range as volser1 and the highest volume serial number in the range as volser2.
    The serial numbers for the range of emulated tape volumes must be the same length, must end with one or more digits, and must have matching beginning alphabetic characters (if any).
  • Whenever a new emulated tape is required for archival, the next tape in the range is used. When the end of the range is reached, the first tape in the range is used.
  • The range of emulated tape volumes must already be defined and initialized within the optical disk device.
  • Specify the MDRS one-character subsystem identifier for ssid. The default ssid is S.
DSK2PARM FileTek Drivers
Specify the high-level index prefix for creating file names on the Storage Machine as INDEX. The syntax is as follows:
Syntax:
DSK2PARM=
index
/
account
/
password
/
smid
Specify the high-level index prefix to use to create file names on the Storage Machine as INDEX. The syntax is:
Syntax:
DSK2PARM=index/account/password/smid
Notes:
  • The index can consist of a maximum of 17 characters.
    The default value for index is the high-level index of the CA View database.
  • The value for account specifies the account identification code for the storage machine as account and can be a maximum of 8 characters.
  • The value for password specifies the account password for the storage machine and can be a maximum of 8 characters.
  • The value for smid specifies the storage machine identifier and can be a maximum of 6 characters.
Example: FileTek DSK2PARM
To use the default storage machine, omit the SMID parameter. For example:
DSK2PARM=SARP.SYSTEM1/VIEW/SARPSWD
This example specifies an index prefix of VIEW.SYSTEM1, an account
identification code of VIEW, an account password of SARPSWD, and a default
smid
.
DSK2PARM Kodak Optistar Report Level Driver
Specify the unit name of the optical disk for UNIT. The syntax is as follows:
Syntax:
DSK2PARM=
unit
/
volser1
/
volser2
Notes:
  • Specify the lowest volume serial number in the range as volser1 and the highest volume serial number in the range as volser2.
    The serial numbers for the range of emulated tape volumes must be the same length, must end with one or more digits, and must have matching beginning alphabetic characters (if any).
  • Whenever a new emulated tape is required for archival, the next tape in the range is used.
    When the end of the range is reached, the first tape in the range is used.
  • The range of emulated tape volumes must already be defined and initialized within the optical disk device.
Adding the MOUNT Attribute Kodak Optistar Report Level Driver Only
This step is optional. Because the Kodak Optistar optical disk device appears to the system as a tape device, the emulated tape volumes must be mounted before being accessed.
If you are using the report-level driver and you intend to allow TSO users to access SYSOUT groups on optical disk storage, you must assign the mount attribute to those TSO users. Consult your optical disk device documentation for possible alternatives to setting the mount attribute.
Note:
The Kodak Optistar page level driver uses the services of MDRS, which performs the mounts automatically for the TSO user. Do not assign the mount attribute for users of the page-level driver.
The TSO ACCOUNT command can be used to assign the mount attribute as follows:
ACCOUNT C (
user ID
) MOUNT END
Step 3 Set Initialization and ERO Table Parameters
Set optical migration options in the ERO table (with disk and tape migration options) using the following keywords:
DSK2DAYS DSK2NOTP
The values for these keywords are explained in the following sections.
DSK2DAYS Initialization Parameter and ERO Table Parameter
The DSK2DAYS ERO table parameter specifies the number of days a SYSOUT group with expanded retention status is to remain on primary disk before it is migrated to secondary disk and deleted from primary disk.
Syntax:
DSK2DAYS=
nnn
Only SYSOUT groups with permanent retention status are eligible for migration to optical disk.
The DSK2DAYS SARINIT initialization parameter sets a global default for a CA View database.
Setting DSK2DAYS=0 specifies that SYSOUT groups are to be migrated to optical disk with the next scheduled optical migration. The default is 999, which specifies that SYSOUT groups are never to be migrated to optical disk.
Notes:
  • For more information, see
    ERO Table
    .
  • For more information about using SARINIT, see
    Initialization Parameters
    .
DSK2NOTP ERO Table Parameter
The DSK2NOTP ERO table parameter specifies that once a report resides on optical disk, the tape backup, if it exists, is deleted. If the parameter is not specified, tape backups are still maintained.
Syntax:
DSK2NOTP
Example
Use the following statement to indicate that a tape backup is never to be created by the SAR standard backup cycle.
DSK2NOTP DSK2DAYS=0
However, if these circumstances occur:
  • You specify that the CA View backup cycle is to perform optical migration (B value for DSK2MIGD initialization parameter)
  • An INTERIM backup runs before the report migrates to optical
the report will be backed up to tape.
Customization using SARD00UX User Exit
Sites that use the IBM model 3995 153 optical drives can code user exit SARD00UX to customize optical migration completely. SARD00UX has access to all attributes of the report, as contained in the GCR (group control record).
Possible applications are:
  • Reports that are under 25 KB do not migrate to optical
  • Reports that are over 3 MB do not migrate to optical
Migration Options
You have many options for how and when reports will be migrated to optical disk. The following table shows all migration options, and how to implement them. Migration to optical means that a report on primary disk is written to optical, and then the report is deleted from primary disk.
Reports with these requirements
Should have these ERO statements
(Report ID: DAILY)
Stay on primary disk for 3 days
Stay on tape backup for 6 months
Never go to optical disk
/DAILY DRETPD=3 RETPD=180 DSK2DAYS=999 ALL
(Report ID: MONTHEND)
Stay on primary disk for 30 days
Migrate to optical after 30 days, and stay for 7 years
Also kept on tape backup for 7 years
/MONTHEND RETPD=2557 DSK2DAYS=30 ALL
DRETPD includes both primary (DASD) and secondary (optical) disk retention.
(Report ID: QRTREND)
Stay on primary disk and tape backup for 90 days
Migrate to optical after 90 days, and stay there for 7 years
Deleted from tape backup when migrated to optical
/QRTREND RETPD=2557 DSK2DAYS=90 DSK2NOTP ALL
When you use DSK2NOTP, disk retention (DRETPD, DGENS, DCOPIES) and tape retention (RETPD, TGENS, TCOPIES) are to be equal.
In this example, even though RETPD=2557, the reports are deleted from tape when they go to optical (90 days).
(Report ID: BIGRPT)
Migrate to optical from primary disk at the next opportunity
Stay on optical for 7 years
Never backed up to tape
/BIGRPT DSK2DAYS=0 RETPD=2557 DSK2NOTP ALL
The reports are never backed up to tape, unless an interim backup cycle is run before the report migrates to optical.
Step 4 (Optional) Customize Optical Migration Scheduling
Optionally, you can use the following parameters to customize optical migration scheduling:
DSK2MIGD DSK2TIME DSK2INTV
Notes:
  • These parameters work with the DAYS initialization parameter, which defines when the CA View backup cycle (migration to tape) is to occur.
    You can set a separate optical migration schedule for each day of the week.
  • For automatic migration by the optical migration subtask, specify ranges of time for migration to occur, and ranges of idle time.
  • This step is optional. By default, the CA View backup cycle performs all migration to optical disk.
Scheduling Parameters DSK2MIGD
The DSK2MIGD specifies the type of optical migration that is to occur on each day of the week beginning with Monday. The syntax is as follows:
Syntax:
DSK2MIGD=
xxxxxxx
where:
  • A
    Specifies automatic scheduling.
    Migration occurs during the time set by DSK2TIME.
    Note:
    The optical migration subtask scans the database intelligently (not a repeat full pass each time), so processing time is minimized.
    If a time range that is specified by DSK2TIME goes past midnight (for example, Friday 11 p.m. to 2 a.m. Saturday), only the day that the range begins (Friday) must be specified with an A.
  • M
    Specifies that no automatic scheduling occurs.
    Optical migration occurs when it is manually requested, through the operator commands.
  • B
    Specifies that optical migration is performed by the CA View standard backup cycle.
    Note
    : This option only migrates reports created in the current generation. If you reindex or manually mark an OPTICAL report from a previous generation, it remains on disk until you run SARDSK2B.
  • N
    Specifies that no backup migration is to occur.
    Backup does not occur even if operator commands to start up the optical migration task are issued .
    This option is provided so that you can be certain that no optical migration can occur during a specific time.
The default is BBBBBBB.
Scheduling Parameters DSK2TIME
The DSK2TIME parameter specifies the time intervals during which optical migration is to automatically occur.
Syntax:
DSK2TIME=
nnnn-nnnn
,…
Automatic migration is activated by an A value for the DSK2MIGD parameter. Up to four ranges can be specified.
The default is 0000 to 2400.
Scheduling Parameters DSK2INTV
DSK2INTV specifies the amount of time the optical migration task is to wait (idle time) before scanning the database again.
Syntax:
DSK2INTV=
hhmm
Notes:
  • This parameter works with the DSK2MIGD and DSK2TIME parameters to schedule automatic optical migration.
  • Automatic migration is activated by an A value for the DSK2MIGD parameter.
  • DSK2INTV is also used as the idle time interval whenever the optical migration task is manually started..
The default is 0015.
Valid values for
hh
are 00-24. Valid values for
mm
are 00-59. The maximum value for this parameter is 2400.
Scheduling Optical Migration
You have many options for scheduling optical migration. This table lists the possible scheduling requirements and how to implement them.
Optical migration occurs
When you specify these parameters
Each night by the CA View standard backup cycle
DSK2MIGD=BBBBBBB
DAYS=YYYYYYY
The DAYS initialization parameter determines what days of the week the CA View backup cycle is run.
Automatically, by the optical migration subtask, Monday
through Friday only
Every 45 minutes from 9 p.m. to 11 p.m., and every 45 minutes from 1 a.m. to 5 a.m.
DSK2MIGD=AAAAANN
DSK2INTV=0045
DSK2TIME=2100-2300,0100-0500
When the system administrator manually invokes the optical migration subtask (no automatic migration)
DSK2MIGD=MMMMMMM
Step 5 Run SARINIT
Run SARINIT to set the initialization parameters you specified in Step 3 for the database. For more information about setting the initialization parameters for a CA View database by running SARINIT, see
Initialization Parameters
.