VitalSigns for VM, Specifications
VitalSigns for VM provides performance information regarding VM hardware and operating system. VitalSigns for VM accomplishes this goal by utilizing three service machines.
- VITALMON collects the data from the MONITOR system and passes the data to the VITALBM machine for storage.
- VITALBM saves the data and summarizes it for use by the online and historical reporting systems. VITALBM also monitors for exceptions, and can executes a routine (or EXEC) to handle the exception.
- VITALSXA contains all of the programs to run the online system and produce the historical reports.
The three service machines interact as a single virtual machine. VITALMON and VITALBM can also operate as disconnected service machines. IUCV is used for communication between the three service machines. Online and historical data can be accessed from the VITALSXA user ID or from any user ID with a read-only link to the VITALSXA minidisk.
The VITALMON machine requires at least 4 Mb of virtual storage.
The VITALDBM machine requires at least 6 Mb of virtual storage. Depending on the device, the 192 minidisk needs 55 to 75 cylinders or 72,000 blocks to store two to three days’ worth of data. Automatically logging off idle users requires privilege class A.
The VITALSXA machine requires at least 4 Mb of virtual storage. Depending on the DASD device, VITALSXA requires 24 to 34 cylinders or 36,000 blocks for the 191 minidisk.
Installation of VitalSigns VM
VitalSigns for VM operates on any installation of VM that includes IBM’s *MONITOR system service. To gather data, VitalSigns for VM uses one to two percent of a processor’s resources. IUCV is required for communications among the VitalSigns for VM subsystems, *MONITOR, and MONWRITE.
VitalSigns for VM is distributed on tape in VMFPLC2 format. To install it: Define the *MONITOR saved segment in your system. Add CP user directory entries to define the service machines and format the minidisks. Load the software from tape and let the menus guide you through the installation. Set up the service machines and verify installation.