Explanation
Backup of the data set identified by
dsid is
about to begin during DFSMShsm control data set backup processing.
- dsid
- specifies the data set to be backed up. "JRNL" is specified
for the journal data set.
- time
- specifies the time of day the backup started expressed as hh:mm:ss
(hours, minutes, seconds).
- date
- specifies the date the backup started expressed as yy/mm/dd (year,
month, day).
- note
- specifies the first non-intrusive journal backup requirement that
was not met. Values for note are:
- a
- indicates that SETSYS CDSVERSIONBACKUP(DATAMOVER(DSS)) is not
specified.
- b
- indicates that SETSYS JOURNAL(RECOVERY) is not specified.
- c
- indicates that non-intrusive backup was attempted during a previous
journal backup and the journal backup failed. Quiesced journal backup
will be attempted. After a successful quiesced journal backup, the
journal will become eligible for non-intrusive backup again.
- d
- indicates that one or more CDS clusters are not SMS-managed or
that the management class for one or more of the CDS clusters is not
configured to use concurrent copy.
- other
- specifies any special condition (other than those indicated by note)
preventing the use of non-intrusive journal backup.
System action
DFSMShsm continues processing.
Programmer response
If the quiesced journal backup
method is intended, no action is required. If the non-intrusive journal
backup method is intended, but was not used, then:
- Resolve the condition indicated by note or other.
In addition, verify all other requirements to use non-intrusive journal
backup are satisfied:
- SETSYS JOURNAL(RECOVERY) must be specified.
- The control data sets must be backed up using concurrent copy.
To enable concurrent copy for CDS backup: - SETSYS CDSVERSIONBACKUP(DATAMOVER(DSS)) must be specified.
- Each CDS must be SMS-managed.
- The management class for each CDS must be configured to use a
concurrent copy backup copy technique. The standard (S) backup copy
technique cannot be used.
- If note value c was issued, non-intrusive journal backup
will be attempted again after a successful quiesced journal backup.
For more information about non-intrusive journal backup
and configuring the use of concurrent copy, see z/OS DFSMShsm Storage Administration.