VMT Checklist 3.3 - Maintenance Installation Using FTP

Install maintenance to the VM Transfer program using FTP.
micsrm140
If you have not previously used FTP to install maintenance, execute the entire checklist, else skip steps 1 through 4 and start with step 5.
  1. Make a copy or rename your existing VMTXRDR JCL member to retain the JCL used to transmit using your current transport mode.
  2. Add or update the following lines in sharedprefix.MICS.PARMS(JCLDEFC):
    USERDEF VMTXMODE FTP USERDEF VMTNODE hostname USERDEF VMTUSER userid USERDEF VMTLIST VMT0000I USERDEF VMTTCP TCPIP.DATA configuration file data set name USERDEF VMTNETRC NO or NETRC.DATA file data set name
    where "hostname" is the remote host name of your VM system as known to FTP, and "userid" is the VM userid where the VM Data Transfer Program will be installed.
    The VMTNETRC value indicates whether or not the IBM NETRC facility is used to supply the remote userid and password.
    • When this value is set to NO, update the generated VMTXRDR JCL's first SYSIN statement, replacing 'PASSWORD' with your userid's password.
    • When specifying a NETRC data set name, the VMTXRDR JCL is generated with a NETRC DD statement and the SYSIN userid/password statement is not generated - the NETRC facility supplies the userid and password as defined for the remote host name in your NETRC file.
    The VMTNETRC value indicates whether or not the IBM NETRC facility is used to supply the FTP userid and password. If set to NO, you must update the generated VMTXRDR JCL to supply the target FTP userid and password. If you specify a data set name, the JCL is generated with a NETRC DD statement and the NETRC facility will supply the userid and password as specified for the FTP host name in the NETRC file.
    If you do not know the name of the TCPIP.DATA configuration file, contact the systems programmer, or within MICS Workstation Facility (MWF), you can issue the command 'MWFLISTA' to list the 'Data Set Allocations', and do a find on the DDNAME SYSTCPD to get the configuration file name.
  3. Edit sharedprefix.MICS.PARMS(JCLGENUC) so that it contains the following:
    VMTXRDR
    Submit the job in sharedprefix.MICS.CNTL(JCLGENUC). Ensure that there are no error messages in MICSLOG or SYSTSPRT, that the MICSLOG contains the normal termination message, BAS10999I, and that the job completes with a condition code of zero.
  4. Edit sharedprefix.MICS.CNTL(VMTXRDR) and update the //CMSRDR DD parameters to meet your installation's requirements for DISK specifications. If the NETRC parameter is set to NO, update the 'MICSSUP PASSWORD' statement, providing the password for the VM/CMS userid you are transmitting to.
    Do not change the file type @MAINT in the put statement because the product change will not install properly on VM.
    If you have previously implemented FTP for maintenance installation, start here.
  5. Install the product change in the MVS central site libraries using PSP Online.
  6. Edit sharedprefix.MICS.CNTL(VMTXRDR):
    1. Change the SENDLIST DDname so it references the maintenance to be sent to the VM system:
      //SENDLIST DD DISP=SHR, // DSN=sharedprefix.MICS.HOLD.PARMS(fix_ref)
      where "fix_ref" is the name of the maintenance transmission control file.
      This control file has a name consisting of the change number suffixed with the letter I. e.g., Product change VMT6005 has a control file named VMT6005I.
    2. Update:
      //CMSRDR DD DISP=(,CATLG), // DCB=(LRECL=80,BLKSIZE=6160,RECFM=FB), // DSN=HLQ.VMTnnnn.MAINT, <--CHANGE AS // UNIT=SYSDA, // VOL=SER=12345, // SPACE=(TRK,(45,15),RLSE)
      FTP control cards:
      PUT 'HLQ.VMTnnnn.MAINT' VMTnnnn.@MAINT
      where "VMTnnnn" is the product change number of the maintenance to be sent.
      For example, Product change VMT6005:
      DSN=HLQ.VMT6005.MAINT PUT 'HLQ.VMT6005.MAINT' VMT6005.@MAINT
      Do not change the file type @MAINT in the put statement because the product change will not install properly on VM.
  7. Submit sharedprefix.MICS.CNTL(VMTXRDR). This job must complete with a return code of zero. Review the SASLOG to ensure all members that are selected in VMTXRDR have been found.
  8. Log on to the CMS userid that is to receive the maintenance.
  9. If the job submitted in step 4 transferred the maintenance by NJE or FTP enter the command:
    VMTMNT RDR
    The VMTMNT utility initiates all steps that are required to load the product change onto the VM Data Transfer Program minidisk and make the product change operational.