When a user or job attempts to create, extend, rename or delete a disk data set, the operat- ing system calls the DADSM post-processing exit (IGGPOST0) when the storage request completes. RTM uses the exit to capture storage management events.
RTM also enables real-time access to HSM log records using an IEFU83 SMF exit. The exit is dynamically installed and activated during RTM initialization. RTM can then inter- cept the HSM specific SMF records.
Each point of interception is termed an environment. The product uses the DEFENV state- ments in the RTMRULES member to determine which environments should be inter- cepted during the allocation request. By default, all RTM environments are active when RTM is started. The product processes the rule definitions in RTMRULES with the ENVI- RON symbolic field set to the current environment name. If applicable, the sub-environ- ment field (&ENVS) is also set.
Whenever RTM intercepts a DADSM post-processing call or an HSM log records, RTM will call RTMRULES with the ENVIRON symbolic name as one of following values.
Table 4-1. RTM environment
| Environment | Description |
|
ALLOCATE
EXTEND SCRATCH RELEASE RENAME PARTREL VSAMEXT |
RTM monitors DADSM events at the data set level. Whenever a data set is created, extended, renamed, deleted or releases space, RTM intercepts the event and builds records for Explorer. When RTM is active, it moni- tors all DADSM activity and records information for events that occur on volumes as well as data sets. |
| DEFAULT DEFENV MODE: ACTIVE | |
| Available subenvironments (&ENVS) on EXTEND: | |
| EXTENDCV Extend Current Volume | |
| EXTENDCAT Extend Catalog | |
| EXTENDPDSE Extend PDSE | |
| EXTENDNV Extend New Volume | |
| EXTENDDS Extend Data Space | |
| EXTENDICFCAT Extend ICF Catalog | |
| Note: The DADSM Post-Processing exit (IGGPOST0) is not available on the Hitachi VOS3 systems. |
Table 4-1. RTM Environment (Continued)
| Environment | Description |
| HSM_SMF |
The MON-RTM component can be used to capture the HSM log records as they are written to SMF. When RTM is started, DIF can install an IEFU83 SMF exit. As delivered, the exit only gets control for SMF records written by the HSM started task. The exit can also co-exist with other IEFU83 exits used by your installation. The Monitor can process the following HSM records obtained by the SMF IEFU83 exit: DSR FSR VSR |
|
When the Monitor IEFU83 extracts an HSM record from SMF data, the information in the record is made available to the RTMRULES routine using symbolic field names. On entry to the RTMRULES, the &ENVIRON symbolic is set to “HSM_SMF”. The &HSMENV is set to the record type: DSR, FSR or VSR. Your installation can develop rules to watch for specific HSM events, or forward records to the Monitor HSM ISPF application database. |
|
|
DEFAULT DEFENV MODE: ACTIVE Available subenvironments (&ENVS): none |