8. INSTALLATION AND MAINTENANCE › 8.2 Installation › 8.2.2 Installation Instructions and Checklists
8.2.2 Installation Instructions and Checklists
This section contains the remaining four checklists for
installing the VM Data Transfer Program. (Section 8.2.1
contains Checklist 1, Planning for Installation.)
o Checklist 2 addresses the movement of the VM Data
Transfer Program source code from the MVS central site
to the VM system.
o Checklist 3 addresses the installation and generation
of executable code in CMS.
o Checklist 4 addresses the setting of parameters and the
creation of JCL and EXECs for each site.
o Checklist 5 addresses the reassembly of modules in
MVS when the operating system is a pre-MVS/XA system.
*************************************************************
* *
* *
* CA MICS VM DATA TRANSFER PROGRAM *
* *
* Installation Checklist 2 *
* *
* for *
* *
* Moving Source Code from MVS to VM *
* *
* *
*************************************************************
IMPORTANT LICENSE INFORMATION: CA MICS is a site-licensed
product. You must be licensed to install the VM Data
Transfer Program on a VM system remote from your MVS site.
Contact your CA MICS sales office for more information.
___ 1. Edit member sharedprefix.MICS.PARMS(JCLGENUC) so
it reads:
VMTXRDR VMTASML VMTSJCL
___ 2. If you are sending the source code to your VM
system via NJE, add the following lines to
sharedprefix.MICS.PARMS(JCLDEFC):
USERDEF VMTXMODE NJE
USERDEF VMTNODE nodename
USERDEF VMTUSER userid
USERDEF VMTLIST VMT0000I
If you are sending the source code to your VM system
by tape, however, add the following lines to
sharedprefix.MICS.PARMS(JCLDEFC):
USERDEF VMTXMODE TAPE
USERDEF VMTNODE nodename
USERDEF VMTUSER userid
USERDEF VMTLIST VMT0000I
where "nodename" is the name of your VM system as
known to JES, and "userid" is the VM userid where
the VM Data Transfer Program will be installed.
___ 3. Submit sharedprefix.MICS.CNTL(JCLGENUC). Make sure
the job completes with a condition code of zero.
This job will generate those three members named in
step 1 in sharedprefix.MICS.CNTL.
___ 4. If you are sending the source code by tape, edit
sharedprefix.MICS.CNTL(VMTXRDR) and update the
//CMSRDR DD card parameters to meet your
installation's requirements for tape specifications.
___ 5. If you are sending the source code by NJE, you may
have to specify a cards punched limit for the
VMTXRDR job. During the initial transmission of
files from MVS for VM, about 25,000 card images are
written to SYSOUT class B (punch). If your
installation has enforced limits on cards punched,
the limits must be overridden in the VMTXRDR job.
To do this, edit and modify
sharedprefix.MICS.CNTL(VMTXRDR), and specify a card
limit of 25000 on the /*JOBPARM JCL statement.
NOTE: The SYSOUT class parameter at //CMSRDR DD
card in sharedprefix.MICS.CNTL(VMTXRDR) must be a
PUNCH class. The default is set to B. If your
installation has a different PUNCH class, make sure
that the SYSOUT class parameter is updated.
___ 6. Submit sharedprefix.MICS.CNTL(VMTXRDR). Make sure
the job completes with a condition code of zero.
If you choose NJE for sending the source code of the
VM Data Transfer Program, this job will load the
software and transmit it to the destination
specified in step 2. However, if you choose tape as
the medium, this job will load the software and
store it on the tape.
Proceed to the Installation Checklist 3 for
installing the software on the VM system.
*************************************************************
* *
* *
* CA MICS VM DATA TRANSFER PROGRAM *
* *
* Installation Checklist 3 *
* *
* for *
* *
* Installing CMS Resident Code *
* *
* *
*************************************************************
NOTE: The installation process uses the CMS READCARD command
to receive the source code from the virtual reader to the
A-disk of the VM Data Transfer Program's virtual machine.
When this command executes, if any files on the A-disk have
the same name as the files being read, they are replaced
without warning. The VMTXRDR job at the step 6 of the
Checklist 2 produces a list of the names of the files that
are read.
If you are re-installing the VM Data Transfer Program, the
previously customized VMTXMIT parameters will not be lost
during this installation process, neither the local
modifications made to VMTFDEF EXEC, VMTPROF EXEC, and VMTPRFX
EXEC, provided that VMTXED was used when the modifications
were made to the EXECs.
___ 1. Log on to the VM Data Transfer Program's virtual
machine.
___ 2. Load the distributed source files on a CMS minidisk.
If you have sent the source code from your MVS
central site by NJE, make sure that the file
containing the CMS resident code is first in your
CMS reader, and enter the command:
READCARD * * A (NOPROMPT REPLACE
If you are installing the source code from your MVS
central site to your VM system by tape, do the
following:
a) Have the system operator attach a tape drive
to the CMS userid to receive the files as
address 181, and mount the tape previously
created in step 6 of Checklist 2, by the job
VMTXRDR.
b) Make sure there are no class Z files in your
CMS reader, and enter the following
commands:
CP SPOOL PUNCH * CL Z
FILEDEF IN TAP1 SL (RECFM FB BLKSIZE 6160
LRECL 80
FILEDEF OUT PUNCH
MOVEFILE IN OUT
CP SPOOL RDR CL Z
READCARD * * A (NOPROMPT REPLACE
Note: If you get a DMSRDC205W - Reader empty,
reader not ready or empty reader file, do the
following:
Enter - q rdr all
q v 00c (00c reader address)
If the response is RDR 000C CL A NOCONT,
the class is A. The class must be changed to
class B by entering the following command:
sp rdr cl b
___ 3. Generate the executable CMS files. Enter the
command:
VMTFIRST
When you are prompted to continue the generation
process, reply Y.
The generation process should terminate with a
return code of zero.
NOTE: If the generation process terminates
abnormally (with a nonzero return code), correct the
error conditions indicated by the accompanying
messages and restart the process. The generation
process can be restarted with the following command:
VMTGEN ( RESTART
___ 4. Review the documentation for an overview of the VM
Data Transfer Program and the tools used to generate
and maintain it. See Section 7.1 of this guide for
information on the parameters to be set for the next
checklist.
*************************************************************
* *
* *
* CA MICS VM DATA TRANSFER PROGRAM *
* *
* Installation Checklist 4 *
* *
* for *
* *
* Setting VM Data Transfer Program Parameters *
* *
* *
*************************************************************
___ 1. Set the VM Data Transfer parameters with the panels
that are provided when you enter the following
command from CMS:
VMTXMIT PARMS
This command calls the parameter specification
panels and displays the parameters that have been
set or the default parameters if none was set. The
panels are described in Section 7.1 and in the
associated online HELP panels.
NOTE: Even if you do not change any of the default
parameters, the first time you enter the "set
parameters" function, you must use the FILE function
(PF9 key) to exit. This is not required on
subsequent entries.
___ 2. Using the Parameter Selection Menu, specify the
Common Transfer Parameters.
a) Verify or change the parameters for your
installation. Use the HELP panels and Section
7.1.1 of this guide for further information.
Data Transmission Parameters
RSCS Userid name ____________
JES node name ____________
HOLD spool files? ___
Data Source Wait Parameters
Wait for available spool files ? ___
Wait for special messages ? ___
Display messages ? ___
Input spool file class ___
Alternate account data userid ____________
Input disk file mode ___
In case of error, notify ____________
b) Using the PF4 key, create and edit the
Authorization Table for your installation.
c) Using the PF5 key, specify the disposition for
the print file and transmission log for your
installation.
___ 3. Select the Account Data Parameter panel
a) Verify or change the account data parameters
for your installation. Use the HELP panel and
Section 7.1.2 for description of those
parameters.
Transmission mode __________________
Data source __________________
Userid __________________
Virtual address _____
Read password __________________
Linked as _____
Data compression ? ___
Record selection ? ___
Input data archive? ___
Output data duplex? ___
JCL file name __________________
Transfer to userid __________________
b) Using the PF5 key, create and edit the ACCOUNT
JCL file for your installation if you have
specified SPOOL as the transmission mode.
c) Use the PF4 key to create and edit the ACCOUNT
SELECT file for your installation if you have
specified record selection for the Account data.
___ 4. Select the CA VM:Account Data Parameters panel.
a) Verify or change the CA VM:Account data
parameters for your installation. Use the HELP
panel and Section 7.1.3 for the description of
those parameters.
Transmission mode __________________
Data source __________________
Userid __________________
Virtual address _____
Read password __________________
Linked as _____
Data compression ? ___
Record selection ? ___
Input data archive? ___
Output data duplex? ___
JCL file name __________________
Transfer to userid __________________
VM:Account Admin ID __________________
Virt Addr _____
VM:Account Service ID __________________
Virt Addr _____
VM:Account Databas ID __________________
Virt Addr _____
b) If you have specified SPOOL as the transmission
mode, use the PF5 key to create and edit the
CAVMACT JCL file for your installation.
c) If you have specified record selection for
CA VM:Account data, use the PF4 key to create and
edit the CAVMACT SELECT file for your
installation.
___ 5. Select the Monitor Data Parameters panel.
a) Verify or change the VM Monitor data parameters
for your installation. Use HELP panel and
Section 7.1.4 for the description of those
parameters.
Transmission mode __________________
Data source __________________
Userid __________________
Virtual address _____
Read password __________________
Linked as _____
Data compression ? ___
Record selection ? ___
Input data archive? ___
Output data duplex? ___
JCL file name __________________
b) If you have specified SPOOL as the transmission
mode, use the PF5 key to create and edit the
MONXA JCL file for your installation.
c) If you have specified record selection for VM
Monitor data, use the PF4 key to create and edit
the MONXA SELECT file for your installation.
___ 6. Select the Network Data Parameters panel.
a) Verify or change the network data
parameters for your installation. Use the HELP
panel and Section 7.1.5 for the description of
those parameters.
Transmission mode __________________
Data source
Userid __________________
Virtual address _____
Read password __________________
Linked as _____
Data compression ? ___
Record selection ? ___
Input data archive? ___
Output data duplex? ___
JCL file name __________________
b) Using the PF5 key, create and edit the NETDATA
JCL file for your installation if you have
specified SPOOL as the transmission mode.
c) If you have specified record selection for
network data, use the PF4 key to create and edit
the NETDATA SELECT file for your installation.
___ 7. Select the VSE/POWER Data Parameters panel.
a) Verify or change the VSE/POWER data parameters
for your installation. Use the HELP panel and
Section 7.1.6 for the description of those
parameters.
Transmission mode __________________
Data source
Userid __________________
Virtual address _____
Read password __________________
Linked as _____
Data compression ? ___
Record selection ? ___
Input data archive? ___
Output data duplex? ___
JCL file name __________________
b) Using the PF5 key, create and edit the POWER
JCL file for your installation if you have
specified SPOOL as the transmission mode.
c) If you have specified record selection for
VSE/POWER data, use the PF4 key to create and
edit the POWER SELECT file for your
installation.
___ 8. Select the Error Recording Data Parameters panel.
a) Verify or change the Error Recording data
parameters for your installation. Use the HELP
panel and Section 7.1.7 for the description of
those parameters.
Transmission mode __________________
Data source
Userid __________________
Virtual address _____
Read password __________________
Linked as _____
Data compression ? ___
Input data archive? ___
Output data duplex? ___
JCL file name __________________
b) Using the PF5 key, create and edit the ERDS JCL
file for your installation if you have specified
SPOOL as the transmission mode.
___ 9. Create PROFILE XEDIT. The sample XEDIT profile
provided is called VMTPRFX $XEDIT. It contains
support for all file types used by CA MICS in CMS.
To create the XEDIT profile, enter the command
VMTGEN VMTGENU ( GEN VMTPRFX.
The resulting file, VMTPRFX XEDIT, must be renamed
to PROFILE XEDIT using the CMS RENAME command.
___ 10. Modify the VMTFDEF EXEC. This is required if the
input or output data medium is disk or tape, or the
archive or duplex function is activated for any data
source. The prologue of the distributed VMTFDEF
EXEC contains the details for coding the
modifications. Further instructions are available
by entering the command HELP XMIT VMTFDEF or see
Section 10.1 in this guide.
This EXEC must be edited using VMTXED:
VMTXED VMTFDEF
and converted to an EXEC using the command:
VMTGEN VMTGENU (GEN VMTFDEF
___ 11. Modify or create the PROFILE EXEC. The VM Data
Transfer Program is capable of running as a DVM
(disconnected virtual machine). This distributed
sample is called VMTPROF $EXEC. It contains the
code necessary to support VMTXMIT in a DVM. This
EXEC can be edited using VMTXED and converted to an
EXEC using the command:
VMTGEN VMTGENU ( GEN VMTPROF
The resulting EXEC has the name VMTPROF. It may be
renamed to PROFILE EXEC or invoked from an
existing PROFILE EXEC.
*************************************************************
* *
* *
* CA MICS VM DATA TRANSFER PROGRAM *
* *
* Installation Checklist 5 *
* *
* for *
* *
* MVS Resident Code Installation *
* *
* *
*************************************************************
The VM Data Transfer Program modules that run in MVS have
been assembled and link-edited for MVS/XA and MVS/ESA
systems. If you are running in a MVS/XA or above system, the
VM Data Transfer Program is now completely installed.
If your MVS system is not MVS/XA or MVS/ESA, these modules
must be reassembled. See Chapter 7 of the How to Use The
Product Support Program Guide for assembly instructions. The
modules are in sharedprefix.MICS.ASM members VMTRCV, VMTCMP,
and VMTPRT.
___ 1. Using the sample JCL in this step, run VMTMVSLV to
rebuild sharedprefix.MICS.MACLIB(VMTSYSLV).
//VMTMVSLV EXEC PGM=VMTMVSLV
//STEPLIB DD DSN=sharedprefix.MICS.LOAD,DISP=SHR
//MACLIB DD DSN=sharedprefix.MICS.MACLIB(VMTSYSLV),
// DISP=OLD
//*
This job must complete with all condition codes
equal to zero.
___ 2. Edit sharedprefix.MICS.CNTL(VMTASML) and specify
member VMTRCV for assembly as illustrated below:
//VMTASML EXEC MICSASM,COND=(4,LT),
// MEM=VMTRCV,
// ASMPARM='OBJECT,LIST,XREF(SHORT)',
// LNKPARM='MAP,XREF,NORENT,REUS,NCAL,SIZE=(200K,50K)'
//*
Submit sharedprefix.MICS.CNTL(VMTASML).
This job must complete with all condition codes
equal to zero.
___ 3. Edit sharedprefix.MICS.CNTL(VMTASML) and specify
member VMTCMP for assembly as illustrated below:
//VMTASML EXEC MICSASM,COND=(4,LT),
// MEM=VMTCMP,
// ASMPARM='OBJECT,LIST,XREF(SHORT)',
// LNKPARM='MAP,XREF,NORENT,REUS,NCAL,SIZE=(200K,50K)'
//*
Submit sharedprefix.MICS.CNTL(VMTASML).
This job must complete with all condition codes
equal to zero.
___ 4. Edit sharedprefix.MICS.CNTL(VMTASML) and specify
member VMTPRT for assembly as illustrated below:
//VMTASML EXEC MICSASM,COND=(4,LT),
// MEM=VMTPRT,
// ASMPARM='OBJECT,LIST,XREF(SHORT)',
// LNKPARM='MAP,XREF,NORENT,REUS,NCAL,SIZE=(200K,50K)'
//*
Submit sharedprefix.MICS.CNTL(VMTASML).
This job must complete with all condition codes
equal to zero.
