|
|
|
The CA MICS VM Data Transfer Option for VM/CMS is a utility that simplifies the task of moving data from a VM system to the MVS system, so it can be processed by a CA MICS Data Integration Application: o VM Monitor and VM Account data are transferred for processing by the CA MICS Analyzer Option for VM/CMS. o CA NetSpy, NPM, NetView, and CA NetMaster data are transferred for processing by the CA MICS Network Analyzer Option. o VSE/POWER account data is transferred for processing by the CA MICS Analyzer Option for VSE/Power. o EREP data from both VM and VSE is moved for processing by the CA MICS System Reliability Analyzer Option. WHY IS A DATA TRANSFER PROGRAM REQUIRED? One of the main features of CA MICS is its ability to combine data from different sources into a single database. When a data source is not located in the same system that runs CA MICS, a method must be found to transmit that data so CA MICS can access it. The CA MICS VM Data Transfer Option for VM/CMS formats and transfers data from the originating VM system to the MVS system that runs CA MICS. It handles the data records noted below. VM ACCOUNT DATA VM Account records are written to a VM spool file using the virtual punch interface; that is, records are written as 80-byte card images. These records may be manipulated by any standard CMS utility which supports punch spool files, such as the READCARD command. VM Account records are collected and kept in storage by CP. Records are then placed into a disk file by the RETRIEVE command issued from the accounting virtual machine for later processing and analysis. CA VM:ACCOUNT DATA CA VM:Account has a userid known as a retriever machine. The retriever machine is a service virtual machine that collects the CP accounting records from CP and passes them in spool files to CA VM:Account. CA VM:Account processes the CP raw data records and calculates charges based on rates from it's cost tables and master description files. The processed records are written to the PERIODTE CURRENT file which is reformatted with an additional 160 bytes containing customer, package, project, and charge information. The PERIODTE CURRENT file is written to the CA VM:Account minidisk. VM MONITOR DATA VM Monitor data can be written to tape or to spool by VM. When data is written to tape, the tape is unlabeled. Most installations prefer not to use this method because unlabeled tapes are difficult to manage and they require manual intervention. When the data is written to spool, a special interface routine is used to embed the data into a VM spool block. Because VM Monitor data uses a special format, it cannot be processed by standard CMS spool data access routines. The VM Monitor data must be accessed through the DIAGNOSE interface used for input spool file manipulation. This block is decoded so the data can be usable by an analysis program, such as the CA MICS Analyzer Option for VM/CMS, or is moved from one system to another via a job submission network. VM Monitor facility collects and stores Monitor data in the saved segment. The IBM MONWRITE program that runs under CMS retrieves Monitor data from the saved segment and then writes it to disk or to labeled or unlabeled tape. VM NETWORK DATA Network data is ordinarily written to a CMS minidisk by the originating software. CA NetSpy data is written to a single CMS file. NPM, NetView, and CA NetMaster data are written to separate CMS files. VSE/POWER ACCOUNT DATA VSE/POWER Account data is written to a data set on a VSE DASD by POWER. The CA MICS VM Data Transfer Option for VM/CMS reads the VSE disk file directly from CMS to transfer the data to MVS. EREP DATA The CA MICS VM Data Transfer Option for VM/CMS can process EREP history files from all VM systems and VSE systems. In VM, the history files reside on a CMS minidisk. In VSE, the history file resides in a VSE data file. The CA MICS VM Data Transfer Option for VM/CMS can handle all of the data formats mentioned above.
This section contains the following topics:
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |