Review the following performance consideration if you have configured
your system to use a multiple DFSMShsm host environment:
- ARCGPA and ARCCAT resources are held when a DFSMShsm function
requires an update to or read of a control data set (CDS) record.
While the resources are held, all other functions must wait for the
controlling function to complete its task. In some cases, the wait
is long and can delay new DFSMShsm request or functions from starting.
For example, when a CDS backup task appears to be hung, it might be
waiting for a large data set recall task to complete. Furthermore,
new recall requests wait for both the original recall request and
the CDS backup to complete before being processed. Specifically:
- In a record level sharing (RLS) environment, a CDS backup must
wait for all DFSMShsm functions across the HSMplex to complete.
- In a non-RLS environment, a CDS backup must wait for all DFSMShsm
functions within the same LPAR as the DFSMShsm host performing the
CDS backup to complete.
To minimize this delay, DFSMShsm hosts in the same HSMplex (RLS
environment) or within the same LPAR (non-RLS environment) allow CDS
backup to begin immediately after all pending CDS updates are complete.
The host performing the CDS backup sends a notification to the other
hosts using cross-system coupling facility (XCF) services. All hosts
processing functions and tasks that might delay CDS backup complete
pending CDS updates, suspend new CDS updates, and release all resources
(such as ARCGPA and ARCCAT) necessary for CDS backup to begin. After
CDS backup is complete, suspended functions and tasks resume.
- Because all DFSMShsm activity is quiesced during quiesced journal
backup, user and production jobs that require recall or recovery resources
wait until the entire CDS and journal backup is complete. Therefore,
the impact of journal backup on DFSMShsm availability and performance
should be considered when planning a backup schedule.
Non-intrusive
journal backup can be used to reduce the impact on DFSMShsm availability
and performance when concurrent copy is available for CDS backup and
the SETSYS JOURNAL(RECOVERY) setting is in effect. This method of
journal backup does not hold resources during journal backup, which
allows DFSMShsm activity to continue. Resources are held only at the
end of journal backup while changes to the journal that occurred during
creation of the initial backup copy are appended to the backup copy.
The control data sets are then backed up using concurrent copy. For
more information about the non-intrusive journal backup method, see
the topic Using non-intrusive journal backup.
- When there are multiple HSMplexes within a z/OS® sysplex, the startup procedure keyword PLEXNAME
should be specified. For more information about the SETSYS PLEXNAME
command, see SETSYS command: Establishing or changing the values of DFSMShsm control parameters.