6. DATA SOURCES › 6.1 Data Collection and Transport to CA MICS

6.1 Data Collection and Transport to CA MICS

The CA MICS VAX/VMS Analyzer processes data from three
sources:  VMS ACCOUNTING data, VMS MONITOR data, and CA MICS
VMS System Usage data.  The data from each of these three
data sources is independent.  VMS ACCOUNTING data is similar
to MVS SMF data in that it is job or process oriented.  VMS
MONITOR data is similar to MVS RMF data in that it is
interval oriented.  CA MICS VMS System Usage data is a
collection of measurements taken on a daily basis, according
to the schedule you establish, typically once per day.  Any
or all of these three data sources can be used as input to
the CA MICS VAX/VMS Analyzer.  The most complete view of your
system is gained by using all three data sources.


OBTAINING INPUT DATA FOR THE VAX/VMS ANALYZER

The CA MICS VAX/VMS Analyzer is designed to process VMS
ACCOUNTING data in its original state as output to the
Accounting log file and process VMS MONITOR data as output to
a Monitor disk recording file in binary format.  The Analyzer
also processes CA MICS VMS System Usage (DEXSUS) data as
written on the VMS system.  The CA MICS VAX/VMS Analyzer
performs the data conversions necessary for CA MICS
processing so you should not attempt to translate the data
before providing it as input to CA MICS. This fact should be
taken into consideration when establishing a method for
transporting the VMS ACCOUNTING, VMS MONITOR, and CA MICS
DEXSUS data to your CA MICS system under MVS.

For most VAX processors, other than MicroVAX, Accounting is
started automatically when the system is started.  Accounting
collects system usage statistics to a log file, normally
called SYS$MANAGER:ACCOUNTNG.DAT.  You can control the
logging performed by Accounting using the SET ACCOUNTING
command in DCL, if you have the privilege to do so.  For
instance, using this command, you can close the current log
and open a new version.

To obtain VMS MONITOR data for CA MICS, you must initiate a
background Monitor session that records to disk in binary
format for the time period you wish to measure.  You will
need to set up a regular processing schedule on your VMS
system to record this data on a daily basis.

To obtain DEXSUS data for CA MICS, you must invoke the
DEXSUS.COM routine on a periodic basis, typically once per
day.  A sample routine called DEXSUSJ1.COM is supplied with
the CA MICS VAX/VMS Analyzer to help you set up and schedule
a batch job that records the DEXSUS data for CA MICS. You
will need to set up a regular processing schedule on your VMS
system to record this data on a daily basis.

For all of these VMS data sources you will need to establish
a procedure for transporting the data to your MVS system
where the CA MICS VAX/VMS Analyzer operates. This can be done
through a relatively manual process such as moving tapes from
system to system each day.  If another form of communication
link is available between your VAX and your IBM systems,
however, you may choose to transmit the VMS ACCOUNTING, VMS
MONITOR, and CA MICS DEXSUS data over the link.

Whatever method you employ for getting the VMS data to
CA MICS, be sure to obtain and transport the recording files
in their original binary format and with a record format of
variable (RECFM=VB) because this is the format expected by
the CA MICS VAX/VMS Analyzer input routines.

The following sections discuss:

   1 - Data Collector Operations
   2 - Data Volume Considerations
   3 - Transporting Data from VMS to MVS
   4 - Errors Identified in Measurement Data