6. DATA SOURCES › 6.1 Data Collection and Transport to CA MICS › 6.1.3 Transporting Data from VMS to MVS

6.1.3 Transporting Data from VMS to MVS

Because CA MICS is run under MVS and the VMS operating system
is a separate entity, the VMS data must be transported to
MVS.  There are numerous ways to get the VMS ACCOUNTING,  VMS
MONITOR, and CA MICS DEXSUS data to MVS. The least desirable
method would be to dump these files to tape on the VAX system
and move them to the MVS system for processing.

You can use FileExchange, a CA software product, to transport
files between your VAX/VMS systems and your MVS systems.

The DECnet/SNA Data Transfer Facility (DTF), a software
product from Compaq Computer Corporation, also allows you to
transmit data from your VMS systems to your MVS system.

Another alternative is FTP between VMS and MVS.  If you
choose this method, be sure to use versions of FTP that
support record structure transfers of binary data in block
mode.  This is required because the logical record structure
presented to the Analyzer must be the same as the original
data records.   In other words, use an FTP that will preserve
the variable length record layout from VMS across to MVS.

For data transfer by tape, there are a number of public
domain tape utility programs for VMS systems that convert VMS
files to MVS variable block format.  These are generally
available through user groups, and are typically classified
as "foreign tape" utility programs.


Data Format Processed by the VAX/VMS Analyzer
---------------------------------------------

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 blocked (RECFM=VB,LRECL=32752,BLKSIZE=32756).  This
is the format expected by the CA MICS VAX/VMS Analyzer input
routines.  Use of a maximum size record length and block size
ensures that data records will not be truncated.