Kodak Optistar Drivers

CA View migrates a SYSOUT group to optical disk when all of the following are true:
view
CA View migrates a SYSOUT group to optical disk when all of the following are true:
  • The SYSOUT group is archived on primary disk
  • The SYSOUT group has or will have permanent retention status
  • The number of days since the SYSOUT group was archived exceeds the DSK2DAYS initialization parameter
Note:
After a SYSOUT group is migrated to secondary disk storage, it continues to reside there until it is either deleted or it expires from ERO disk retention. ERO disk retention is specified by the DGENS, DCOPIES, or DRETPD ERO table statements.
Contents
Retrieving SYSOUT Data from Optical Disk (Report-Level Driver Only)
If Your TSO User ID Has MOUNT Authority
When you select a SYSOUT group that shows a status of DSK2, PDK2, or PRM2 (all of which indicate optical disk secondary storage), CA View reloads the entire SYSOUT from optical disk back into the CA View database.
Note:
DSK2, PDK2, or PRM2 all indicate optical disk secondary storage.
You can explicitly request that the SYSOUT group be loaded back to the primary disk database. Use the L line command online or the /LOAD function when you are executing in batch using SARBCH.
If Your TSO User ID Does Not Have MOUNT Authority
You must use the L line command online or the /LOAD function when executing in batch using SARBCH.
After the SYSOUT group is retrieved, it continues to reside in the CA View database (as well as on optical disk storage) until the backup cycle specified by the HOLDTEMP initialization parameter occurs.
You can remove the SYSOUT group from the CA View database before the next backup cycle by:
  • Explicitly requesting its removal using the C line command online
  • Specifying the CLEAN option when starting the CA View started task.
Retrieving SYSOUT Data Is Retrieved from Optical Disk (Page-Level Driver Only)
When you select a SYSOUT group that shows a status of DSK2, PDK2, or PRM2 (all of which indicate optical disk secondary storage), CA View enables you to view or print the SYSOUT group directly. This is the preferred method of operation.
Note:
DSK2, PDK2, or PRM2 all indicate optical disk secondary storage.
If necessary, you can explicitly request that the SYSOUT group be loaded back to the primary disk database using:
  • The L line command online
  • The /LOAD function when executing in batch using SARBCH.
Defining Optical Disk Data Sets
When SYSOUT groups are being migrated to optical disk storage, CA View creates data sets automatically. Only one SYSOUT data set is created for each emulated tape volume.
CA View continues to write SYSOUT groups to the data set on the emulated tape volume until the data set is full. Each SYSOUT group is separated from the next by an EOD record.
When a SYSOUT group is being written to secondary disk and the end of volume is reached, CA View does the following:
  • Terminates the data set
  • Allocates a new data set on the next emulated tape volume in the volume serial number range
  • Continues writing to the new data set
DCB attributes for the data set are:
RECFM=VB LRECL=32756 BLKSIZE=32760
Naming Optical Disk Data Sets
CA View assigns the data sets names as follows:
Syntax:
index.SARDSK2.Tnnnnnnn
where:
  • index
    Specifies the high-level index naming prefix as defined by the DSK2PARM initialization parameter
  • nnnnnnn
    Specifies the sequence number for the emulated tape data set
You specify the unit name and volume serial number range using the DSK2PARM initialization parameter.
Deleting Optical Disk Data Sets
As part of its backup cycle, CA View uncatalogs any emulated tape data set that is no longer needed. This determination is based either on the global settings specified in either the initialization parameters or on the entries in the Expanded Retention Option (ERO) table.