This manual covers the configuration and use of the MON-RTM. The Monitor product suite includes the following components:
- MON-SNAPSHOT is used to perform snapshot and interval processing at the volume, pool or data set level. This component is run as a batch job or started task.
- MON-RTM is used to monitor real-time storage management events using the DADSM POST processing exit and capture HSM events using the SMF U83 exit. This component can also be used to feed storage event records to a MON- EXPLORER database. The MON-EXPLORER PC-GUI application can use the database for Storage Analysis and Trends evaluation.
- MON-ISPF is an ISPF application interface with SCC Monitor. The interface uses result sets from Explorer to create and display ISPF tables. The result sets are the same ones used by the Explorer and iPhone applications.
- MON-EXPLORER is a PC-based client that communicates through DIF to work with SCC Monitor, MVS Console and TSO commands, system utilities, as well as third party software products. The application can display information in a variety of formats, reports and graphs. The Explorer can also perform storage management and installation defined actions on the host. An optional database tier can also be added to collect storage management events for historical and trend analysis.
- MON-IPHONE is an iPhone application that communicates through DIF to work with SCC Monitor, MVS Console and TSO commands, system utilities, as well as third party software products. The application can also perform storage management and installation defined actions on the host.
- MON-JCLQA performs JCL Validation and Quality Assurance. JCLQA was designed to scan individual JCL job streams, entire JCL libraries, or job streams extracted from job scheduling systems. The product can be used to enforce instal- lation standards, or perform a system validation test. The system validation tests can be performed on either the local system, or remote systems that are also run- ning JCLQA.
- MON-PRECALL (Predictive Recall) minimizes production delays caused by recalls of migrated data. Migrated production datasets will be recalled prior to their actual use, resulting in an overall shorter batch window. The product uses the information from the Job Scheduler to create a list of production datasets that will be accessed in the next production cycle and determines if any of those data- sets have been migrated. HRECALL commands are generated and passed directly to the Inactive Data Mover. To avoid any impact on the production work- load, the Predictive Recall job can be scheduled to run when the system is under- utilized, prior to the production cycle.