8. INSTALLATION AND MAINTENANCE › 8.2 Installation › 8.2.1 Planning for Installation
8.2.1 Planning for Installation
*************************************************************
* *
* CA MICS VM DATA TRANSFER PROGRAM *
* *
* Installation Checklist 1 *
* *
* for *
* *
* Planning for Installation *
* *
* *
*************************************************************
Gather the relevant information to assess each of the items
discussed below.
VM USERID
You must determine whether to use an existing VM userid or
create a new one for installing and operating the VM Data
Transfer Program.
Installation of the CMS-resident portion of the CA MICS VM
Data Transfer Program requires a nonprivileged VM userid,
running CMS, with at least 1200 4K blocks of DASD (for
example, 8 cylinders of 3380 or 3390) and 4 MB of storage.
The following is a sample definition of the VM Data Transfer
Program userid:
USER MICSVMT password 4M G
ACCOUNT MICSVMT distcode
IPL CMS PARM AUTOCR
CONSOLE 009 3215 T
MDISK 191 3390 nnn 008 volser MR rpass wpass
SPOOL 00C 2540R *
SPOOL 00D 2540P B
SPOOL 00E 1403 A
LINK MAINT 190 190 RR
LINK MAINT 19E 19E RR
___ 1. Define a VM userid, name __________________.
If this is a new userid, the minidisk must be
formatted using the CMS FORMAT command
FORMAT 191 A
See the CMS Command and Macro Reference for details
about this command.
INSTALLATION SITE
___ 2. Determine where the source code resides.
Before installing the VM Data Transfer Program, you
must decide whether its source code will be
installed in VM from MVS from tape or NJE.
___ a. The MVS central site via tape, or
___ b. The MVS central site via NJE
If you select this option, obtain the VM
system NJE node name (the name by which the
central-site JES recognizes RSCS on the VM
system in which the VM Data Transfer Program
will be installed).
VM system node name (RSCS node name) ________
DATA TRANSFER MEDIUM
___ 3. Decide how VM data will be transferred.
____ a. Transfer data by tape
____ b. Transfer data by NJE
____ RSCS userid _________________________
This parameter identifies the virtual
machine initially receiving the job created
by VMTXMIT. This virtual machine is
ordinarily the one which runs RSCS on your
system, but it may be any other userid on
your system.
____ JES node name ________________________
This parameter identifies the JES2 or JES3
node of the MVS system receiving the data.
This is the name by which RSCS "knows" the
MVS system.
DATA SOURCES
___ 4. Place a check next to each data source that will be
transferred by the VM Data Transfer Program.
___ VM Account data
___ CA VM:Account data
___ VM Monitor data
___ VM Network data
___ VSE/POWER data
___ Error Recording data
INPUT DATA MEDIUM
When the VM Data Transfer Program is running, it reads data
from the VM Spool, disk, or tape. You must determine the
input medium used by the input data that will be processed.
___ 5. Place a check next to those that will be read from
disk or tape.
___ VM Account data
___ CA VM:Account data
___ VM Monitor data
___ VM Network data
___ VSE/POWER data
___ Error Recording data
___ 6. Place a check next to those that will be read from
VM Spool.
___ VM Account data
___ CA VM:Account data
Place a Y (yes) next to each data source for which
you want to hold processed files.
___ VM Account data
___ CA VM:Account data
This parameter allows the VM Data Transfer Program
to purge reader files once they have been processed.
A reader file is purged only when this parameter is
specified as Y and there are no errors detected in
CMS.
IMPORTANT NOTE: Only errors in CMS are detected.
Job execution in MVS occurs after a file is purged.
If the purge option is used and the job abends or
fails to execute due to a JCL error, the data is
lost.
RECORD SELECTION
Record selection enables you to selectively transfer data.
___ 7. Place a Y (yes) next to each data source for which
you will invoke record selection.
___ VM Account data
___ CA VM:Account data
___ VM Monitor data
___ VM Network data
___ VSE/POWER data
DATA COMPRESSION
Data compression is used to reduce the volume of data that is
sent through your NJE network.
___ 8. Place a Y (yes) next to each data source for which
you will compress data.
___ VM Account data
___ CA VM:Account data
___ VM Monitor data
___ VM Network data
___ VSE/POWER data
___ Error Recording data
SECURITY CONSIDERATIONS
Consider your installation's security requirements when
creating JCL to run the VM Data Transfer Program. Many MVS
systems use security packages that have exacting requirements
for job names, data set names, system access via NJE, etc.
In TSO, the job submission mechanism usually provides the
correct security information for a job. This automatic
feature is not available in CMS; therefore, these information
requirements must be met manually. If your installation
already sends jobs from VM to run on MVS, most of these
issues have probably been addressed. Your Security
Administrator can provide specific guidance in this area.
TAILORING EXECS IN CMS
You must tailor the following CMS EXECs to your
installation's specifications. The installation instructions
indicate the steps required to generate these files.
o VMTPROF EXEC is a CMS PROFILE for running the VM
Data Transfer Program in a Disconnected Virtual
Machine (DVM) without manual intervention.
o VMTPRFX XEDIT is an XEDIT PROFILE that supports all
files used by the VM Data Transfer Program.
o Use the VMTFDEF EXEC if any one of the following
conditions are true.
a) The input data is located at disk or tape. This
EXEC must be modified to define the input data at
the datatype.INPUT section.
b) The output data medium is disk or tape. This EXEC
must be modified to establish the output data
definition at the datatype.OUTPUT section.
c) Request that a copy of the input data file is to
be saved on disk or tape. This EXEC must be
modified to establish the archive definition at
the datatype.ARCHIVE section.
d) Request that a copy of the output data file is to
be saved on disk or tape. This EXEC must be
modified to establish the back up file definition
at the datatype.DUPLEX section.
Note: If any of the above involves tapes, VMTFDEF
EXEC should be modified to acquire a tape drive and
request a tape mount. The sample EXEC distributed
with the VM Data Transfer Program illustrates this.
VMTFDEF EXEC may be expanded to interface with a tape
management system.
