The following keywords are defined as they pertain to the CBROAM
xx PARMLIB
member SETOSMC statement:
- FIRSTBACKUPGROUP(global_1st_bugroup)
- Specifies
the default Object Backup storage group that OSMC uses to store the
first backup copy of objects when:
- The Object storage group to which the object belongs is not specified
in a SETOSMC statement on the FIRSTBACKUPGROUP parameter, and
- The management class that is assigned to the object specifies
that a backup copy is to be written.
- SECONDBACKUPGROUP(global_2nd_bugroup)
- Specifies
the default Object Backup storage group that OSMC uses to store the
second backup copy of objects when:
- The Object storage group to which the object belongs is not specified
in a SETOSMC statement on the SECONDBACKUPGROUP parameter, and
- The management class that is assigned to the object specifies
that more than one backup copy is to be written.
- CYCLEWINDOW(start_mode)
- Specifies
the start window mode for the OSMC storage management cycle for a
given Object or Object Backup storage group. You can choose either
the default STARTONLY mode or the STARTSTOP mode for the CYCLE START
and CYCLE STOP times. The START/ONLY mode defines only the start time
for processing the storage group. The START/STOP mode defines both
the start and end times for processing the storage group. You can
use this keyword at the global level only. The CYCLEWINDOW keyword
is valid for storage groups that were started automatically.
To
start the storage management cycle for an Object storage group automatically,
specify the Cycle Start Time, End Time, and OSMC Processing System
fields in the ISMF Object Storage Group Define/Alter panel. For an
Object Backup storage group, specify the Cycle Start Time, End Time,
and OSMC Processing System fields in the ISMF Object Backup Storage
Group Define/Alter panel.
Restriction: If you manually
start the storage management cycle by issuing one of the following
commands, the CYCLEWINDOW mode and the start and stop times for the
storage group cycle are ignored:
- MODIFY OAM,START,STORGRP,group_name
- MODIFY OAM,START,OSMC
- STARTONLY
- Uses the storage group's defined cycle start and end times as
a start window only. OSMC starts processing the storage group at the
defined start time. If you initialize OSMC before or during the times
that this start window specifies, processing for that storage group
completes, regardless of how much time it takes. If you omit the CYCLEWINDOW
parameter, STARTONLY is the default mode.
- STARTSTOP
- Uses the storage group's defined cycle start and end times to
automatically begin processing that storage group. OSMC starts processing
the storage group at the defined start time and stops processing the
storage group at the defined end time. Processing stops in the same
way as if you had issued a STOP command for that storage group. No
new work is scheduled, and all work in progress is allowed to complete.
- STORAGEGROUP(name)
- Specifies
the name of an Object storage group that was previously defined using
ISMF. This is the name of the storage group to which the following
subparameters apply:
- FIRSTBACKUPGROUP(1st_bugrp)
- Specifies
the Object backup group to which the first backup copy of an object
belonging to the Object storage group name is
directed when that object is associated with a management class that
specifies that a backup copy is to be written.
- SECONDBACKUPGROUP(2nd_bugrp)
- Specifies
the Object backup group to which the second backup copy of an object
belonging to the Object storage group name is
directed when that object is associated with a management class that
specifies that more than one backup copy is to be written.
- MAXRECALLTASKS(nnn)
- Specifies
the maximum number of RECALL tasks that can be run concurrently. Valid
values are 0–255. The default is 0. A value of 0 indicates that
no RECALL operations are to be run. This applies to both implicit
(recalls through SETOSMC enablement) and explicit (recalls through
OSREQ macro requests with the RECALL keyword) recalls.
- RECALLDISKSUBLEVEL(n)
- Specifies
the disk sublevel where objects residing on optical or tape devices
will be placed when they have been recalled. This keyword can be specified
at the global level or at the storage group level and applies to both
explicit and implicit recalls. This parameter may be abbreviated to
RECALLD. Valid values for n are:
- 1
- Specifies that objects will be recalled to disk sublevel 1 of
the OAM storage hierarchy (DB2 object storage tables). This is the
default value.
- 2
- Specifies that objects will be recalled to disk sublevel 2 of
the OAM storage hierarchy (file system)
- RECALLOPTICAL(nnn)
- Specifies
that objects residing on optical devices are recalled to disk for nnn days
when retrieved. Valid values are 0–255. The default is 0. The
object's pending action date in the object directory is set to today's
date + the number of days specified in nnn. A value of 0 indicates
that the RECALL is for the current day only. On the next OSMC cycle
the object is restored to removable media. This applies to implicit
recalls only. This keyword can be specified at the global level or
at the storage group level.
- RECALLTAPE(nnn)
- Specifies
that objects residing on tape devices are recalled to disk for nnn days
when retrieved. Valid values are 0–255. The default is 0. The
object's pending action date in the object directory is set to today's
date + the number of days specified in nnn. A value of 0 indicates
that the RECALL is for the current day only. On the next OSMC cycle
the object is restored to removable media. This applies to implicit
recalls only. This keyword can be specified at the global level or
at the storage group level.
- RECALLALL(nnn)
- Specifies
that objects residing on optical or tape devices are recalled to disk
for nnn days when retrieved. Valid values are 0–255.
The default is 0. The object's pending action date in the object directory
is set to today's date + the number of days specified in nnn.
A value of 0 indicates that the RECALL is for the current day only.
On the next OSMC cycle the object is restored to removable media.
This applies to implicit recalls only. This keyword can be specified
at the global level or at the storage group level.
- RECALLNONE
- Specifies
that objects residing on optical or tape devices are not recalled
to disk when retrieved. This applies to implicit recalls only. This
keyword can be specified at the global level or at the storage group
level.
- RECALLOFF(mode)
- Specifies
whether objects residing on tape or optical devices are to be recalled
to DB2 when retrieved. This keyword can be specified at the storage
group level only, and allows recall processing to be disabled at the
storage group level regardless whether the RECALL parameter is specified
on the OSREQ RETRIEVE request. This keyword applies to both implicit
and explicit recalls. Valid values for mode are:
- OFF
- Explicit and implicit recalls are enabled. This is the default.
- ON
- Explicit and implicit recalls are disabled.
- CLEAROLDLOC(mode)
- Specifies
whether OAM is to retain the original volume location information
when OSMC processing transitions objects from optical or tape media
to the DB2 sublevel or file system sublevel. Values for mode are:
- OPT
- Specifies that previous volser and sector location values be cleared
in the object directory when an optical object transitions from optical
media to DB2.
- TAPE
- Specifies that previous volser and blockid location values be
cleared in the object directory when an optical object transitions
from tape media to DB2.
- BOTH
- Specifies that previous volser and sector or blockid location
values be cleared in the object directory when an optical or tape
object transitions from tape or optical media to DB2.
- NONE
- This is the default. Specifies that previous volser and sector
or blockid location values be left unchanged in the object directory
when an optical object transitions from tape or optical media to DB2.
Old location values are cleared only when an object
transitions from optical or tape to the DB2 sublevel or file system
sublevel during an OSMC cycle. The old location values are not cleared
when an object is recalled to the DB2 sublevel or file system sublevel,
even if CLEAROLDLOC is active.
- BACKUPDELETE(ON|OFF)
- An
optional parameter that specifies whether OSMC should delete any existing
backup copies of an object that exceed the required number of backup
copies for the object's current management class. (For example, if
two backup copies exist, but the management class only requires one,
the second backup copy is deleted.) The default value is OFF, which
means that all existing backup copies are kept.
Note: This is a
global specification only and cannot be specified at the storage group
level. Additionally, the BACKUPDELETE specification cannot be modified
using the MODIFY OAM,UPDATE command.