|
|
|
This section shows you how to specify the database unit level
JCL parameters required to install the CA MICS Analyzer
Option for VM/CMS. This product processes the following
types of input:
o VM Monitor data is stored by an application program (for
example, MONWRITE) as either a CMS disk file or tape file
o CP account data is stored as a CMS disk file
These files must be transported to the z/OS system that runs
CA MICS. The VM Data Transfer Program is available to assist
you in moving the data from your VM system to your z/OS
system.
The input DD statements, which define the VM data files area,
are supplied in the INPUTVMC member of the prefix.MICS.PARMS
library and referenced by the MON, ACT, VMACCT, and COMMON
statements of VMCOPS. A worksheet for preparing the INPUTVMC
member is provided in Figure 7-5.
It is likely that you will have data from multiple systems as
input to the VM tracking update process. To provide for
account data from multiple systems, supply one DD statement
per system using the ddnames specified in VMCOPS. To
provide for monitor data from multiple systems, supply one DD
statement per system using the ddnames specified in VMCOPS
or provide the single ddname specified on the COMMON
statement in VMCOPS, and concatenate the data sets.
For example, in the JCL below, the unit will process CP
account data from SYS1 and SYS2; and VM monitor data from
SYS1, SYS2, and SYS3. The monitor data from SYS2 and SYS3
will be brought in using a single ddname, specified in
VMCOPS. In addition, VM monitor data will be brought in from
a fourth system, SYS4. The DD statements will read as
follows:
//VMCACT01 DD DISP=SHR,DSN=VM.SYS1.ACCOUNT.DATA
//VMCACT02 DD DISP=SHR,DSN=VM.SYS2.ACCOUNT.DATA
//VMCMON01 DD DISP=SHR,DSN=VM.SYS1.MONITOR.DATA
//VMCMONXX DD DISP=SHR,DSN=VM.SYS2.MONITOR.DATA
// DD DISP=SHR,DSN=VM.SYS3.MONITOR.DATA
//VMCMXAXX DD DISP=SHR,DSN=VM.SYS4.MONITOR.DATA
Note: Due to the text substitution process used by
JCLGEN to produce //*, /*, and & in the
JCL produced by JCLGEN, the following symbols
must be used:
//@ produces //*
/@ produces /*
? produces &
DCB PARAMETERS
DCB record description parameters are required only when data
is provided to the DAY080 step by unlabeled tape.
VM monitor data has LRECL=4092 and RECFM=VB. If the tape is
created by the VM monitor, you should specify BLKSIZE=4096.
Otherwise, you should use the blocksize used by the creating
program. If this cannot be determined, you can use a
BLKSIZE=32756.
VM monitor data decomposed by the CA MICS VM Data Transfer
Program has LRECL=8188 and RECFM VB.
CP account data and CA VM:Account data is not normally
brought into CA MICS by tape. If an unlabeled tape is used,
the LRECL for CP account is 80 and the LRECL for CA
VM:Account data is 240. You should use the blocking
information specified by the creating program for each data
source.
PROVIDING DATA TO CA MICS
Getting the data to be processed each day into the CP account
and VM monitor data sets you specify is an operational
responsibility of the CA MICS System Administrator. The
preferred methods are by use of the VM Data Transfer Program
or some similar facility, or by standard label tape.
Guidelines are provided for transporting the VM data files to
z/OS in the chapter named Processing.
You must use the CA MICS VM Data Transfer Program to
decompose the data from MONWRITE format to CA MICS readable
format if you want to process VM Monitor data in CA MICS.
+--------------------------------------------------------------------------+ | INSTALLATION PREPARATION WORKSHEET: User Inserted JCL Definitions | | | | PARMS Library Member is INPUTVMC | | Reference Section: 7.6, CA MICS VM Component Guide | +--------------------------------------------------------------------------+ | | | This definition is required to specify the DD statement for VMC data | | that will be read by the DAILY CA MICS job. | | | | //@ | | //@ WARNING: ALWAYS MAKE CHANGES IN PARMS(INPUTVMC) AND NOT | | //@ &CNTL(DAILY). | | //@ CHANGES MADE TO &CNTL(DAILY) | | //@ WILL BE GONE WHEN DAILY REGENERATED BY JCLGEN. | | //@ | | //@ SPECIFY THE INPUT MONITOR AND ACCOUNT DATASETS FOR ALL | | //@ SYSTEMS | | //@ | | //@ ACCOUNT DATA | | //VMCACT01 DD DISP=SHR,DCB=BUFNO=3,DSN =_____________________ | | //VMCACT02 DD DISP=SHR,DCB=BUFNO=3,DSN =_____________________ | | //VMCACT03 DD DISP=SHR,DCB=BUFNO=3,DSN =_____________________ | | //@ VM MONITOR DATA | | //VMCMXA01 DD DISP=SHR,DCB=BUFNO=3,DSN =_____________________ | | //@ MONITOR DATA (COMMON DD OPTION) | | //MONXA DD DISP=SHR,DCB=BUFNO=3,DSN =_____________________ | | // DD DISP=SHR,DCB=BUFNO=3,DSN =_____________________ | | //@ VM:ACCOUNT DATA | | //VMCACCT1 DD DISP=SHR,DCB=BUFNO=3,DSN =_____________________ | | | +--------------------------------------------------------------------------+
Figure 7-5. INPUTVMC JCL Definition Worksheet
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |