Installing

Review the following operational considerations prior to starting an FDRPASVM migration.

Operational considerations

The following high-level considerations are extremely important:

•  All source and target DASD must be accessible to the z/VM systems running the monitor, and the z/OS system running the main swap task.

• The CALCDASD EXEC with the ‘(ALL’ parameter should be run on all z/VM systems before installing FDRPASVM. The report output must be sent toBMC Support.

•  Any z/VM system that has page or spool volumes swapped must have a minimum of two of each. z/VM is installed with only one of each. See Add Additional Page and Spool Volumes for an example of adding these types of volumes. Also, the MAXTASKS=1 option should be set in the z/OS JCL job. See Migrate the CP-Owned Volumes for details.
• If you have upgraded to a new level of FDRPASVM, you must run the DIAGRELO EXEC to reload the user-defined DIAGNOSE. See Load the Updated User Diagnose.
• If you are migrating from smaller to larger 3390 volumes, the LARGERSIZE=OK operand must be used in the z/OS main SWAP job. The cylinder allocation table on the target volumes will be rewritten so that all remaining cylinders are PERM cylinders. 

• FDRPASVM supports all volumes that can be mounted on a z/OS system. There are special considerations if volumes do not have a valid/dummy VTOC. If you are not sure if the volumes have a valid/dummy VTOC, refer to 

  FDRPAS

  z/VM and Linux on IBM Z considerations in the FDRPAS documentation, run the FDREPORT job documented to identify volumes that do not have a valid/dummy VTOC. If any valid/dummy VTOC are found, follow the special instructions. (FDREPORT is part of FDRABR, and can be licensed directly.)
  

  • A volume is considered to contain a dummy VTOC, when it is formatted with CPFMTXA utility or ICKDSF with the CPVOL keyword.
  • A volume with a dummy VTOC is copied in its entirety.
  • In general, we recommend all z/VM and Linux for Systemz volumes use the following select statement in their JCL:
    SELECT FROM(CYL=0),TO(CYL=65519)
    This ensures that the volumes are copied in their entirety.

•  If your installation has EAV volumes, CYL=65519 must be increased to included the size of the largest volume in your installation.
• If migrating a non-SSI z/VM system, update the HMC with the IPL address and any other location where the real device address is stored.
• During the migration of a z/VM SSI system, the SSI PDR (Persistent Data Record) is dynamically migrated, when the PDR volume is moved. IBM APAR VM65712 is not required.
• If migrating a z/VM SSI, run the FDRPAS MONITOR on all members of the SSI cluster. After the volumes are swapped, update the PDVOL value in both the IPL parameters and the Stand-Alone Program Loader (SAPL). See Prepare for the Next IPL.
  
• When migrating a z/VM system, consider moving volumes in this order:

1. 
   
   1. All page and spool volumes sequentially
   2. Remaining CP-owned volumes in parallel (Update the HMC immediately after the 'SYSRES' volume is moved. For z/VM 6.2 and above, run the SALIPL command immediately after the 'PDVOL' volume is moved.)
   3. PERM volumes in parallel, up to 100 at a time

See Migrating an Entire z/VM System for details.

• For FDRPASVM to migrate volumes, PAV/HYPERPAV must be set off. If you do not have PAV/HYPERPAV minidisks defined in the Linux virtual machines, the SET CU command turns off PAV. 
• If migrating Linux systems from smaller to larger volumes, and minidisks are defined using the “END” keyword, modify the user directory entries to specify the exact ending cylinder. For example, if moving from 3390-9s to 3390-27s, and there are minidisk statements with “1 END”, update all user directory entries with “1 10016”. This way, the Linux disks remain the same size, and the remaining space is available for other minidisks.
• Only run one monitor job per z/OS system. While it is possible to run more than one, it is not recommended.
• Migrating devices with duplicate volume serial numbers. Although z/OS does not allow devices with duplicate volume serial numbers to come online, it is perfectly normal to have such devices on z/VM. If you are planning to migrate such volumes, you need to bring online to z/OS the device that you want to move and FDRPASVM will pick the corresponding device. This feature requires that devices on both systems have matching unit addresses.
• Migrating devices with minidisks defined as DEVNO. As IBM recommends in CP Planning and Administration, defining minidisks with DEVNO should be avoided except for cases that are duplicate volume serial numbers on multiple devices or when the guest controls the duplexing. Migration of such devices are only supported if the unit address of such devices match the z/OS unit address. After a successful swap of such volumes, the CP directory must immediately be updated to reflect the new addresses and placed online.
• If you have z/VM DASD volumes under the control of z/OS Geographically Dispersed Parallel Sysplex (GDPS). 
• It may be possible that there are volumes to be migrated that have a z/OS VTOC. If so, it is recommended to add a SELECT statement after the MOUNT statement in all SWAP tasks. See Determining the Type and Amount of DASD Being Migrated.
• Review Special Considerations.

FDRPASVM installation - upgrade checklist

All of the steps in the checklist for the FDRPAS z/OS main SWAP task in FDRPAS Checklist must be performed in addition to the checklist items in this section to ensure proper operation of the main SWAP task and the FDRPASVM monitor.

New installations

Start with Create the FDRMAINT Virtual Machine described in the subsequent sections.

Existing installations

Skip to Upgrading an Existing Installation if performing an upgrade.

To install FDRPASVM, perform the following tasks:

• Create the FDRMAINT Virtual Machine
• Create the FDRPASVM Virtual Machine
• Load the FDRPASVM Software to the FDRMAINT Minidisks

Create the FDRMAINT Virtual Machine

The FDRMAINT virtual machine must be created with three minidisks.

• The 191 minidisk is for the product envelope file and other files.
• The 691 minidisk contains the files for the FDRPAS CMS command. It should be linked by the users that need to use the FDRPAS CMS command.
• The 692 minidisk contains the files used to run the FDRPASVM service machine.

To add the FDRMAINT virtual machine, perform the following steps:

• Log on to your z/VM system as MAINT, or another virtual machine with sufficient privileges.

• Create the directory entry similar to the following example; text in italics should be replaced with values for your environment. In this example, IBM DirMaint is configured, so the FDRMAINT DIRECT file is created. If you are not using a directory maintenance product, you should add the entry to the bottom of the USER DIRECT file. If you are using a different directory maintenance product, perform the appropriate steps to create the new virtual machine.

  ==> x fdrmaint direct
  USER FDRMAINT password 64M 128M ABG
  INCLUDE IBMDFLT
  IPL CMS PARM AUTOCR
  IUCV ALLOW
  MACH ESA
  OPTION DEVMAINT
  LINK MAINT 0193 0193 RR
  MDISK 0191 3390 start 100 volser MR rpass wpass mpass
  MDISK 0691 3390 start 005 volser MR rpass wpass mpass
  MDISK 0692 3390 start 010 volser MR rpass wpass mpass

• Create the new virtual machine. In this example, IBM DirMaint is configured, with the DIRM ADD command. If you are using a different directory maintenance product or none at all, add the virtual machine accordingly.

  ==> dirm add fdrmaint
  PUN FILE 0111 SENT TO DIRMAINT RDR AS 0204 RECS 0017 CPY 001 0 NOHOLD NOKEEP
  DVHXMT1191I Your ADD request has been sent for processing to DIRMAINT at
  DVHXMT1191I VMLAB63A.
  …
  DVHREQ2289I Your ADD request for FDRMAINT at * has completed; with RC
  DVHREQ2289I = 0.
  Log on to the new FDRMAINT virtual machine and watch for errors:
  LOGON FDRMAINT
  z/VM Version 6 Release 3.0, Service Level 1302 (64-bit),
  …

• If you see DMSACP112S messages, it probably means the new disks have not been formatted. Format these disks as needed. An example of formatting the 191, 691, and 692 disks as file modes A, B, and C follows.

  ==> format 191 a
  DMSFOR603R FORMAT will erase all files on disk A(191). Do you wish to continue?
  Enter 1 (YES) or 0 (NO).
  1
  DMSFOR605R Enter disk label:
  psm191
  DMSFOR733I Formatting disk A
  DMSFOR732I 100 cylinders formatted on A(191)
  ==> format 691 b
  …
  DMSFOR733I Formatting disk B
  DMSFOR732I 5 cylinders formatted on B(691)
  ==> format 692 c
  …
  DMSFOR733I Formatting disk B
  DMSFOR732I 10 cylinders formatted on C(692)

• Create a PROFILE EXEC that spools the console, access the 691 disk as file mode B, and the 692 disk as C. Following is a sample.

  /*****************************/
  /* FDRMAINT PROFILE EXEC */
  /*****************************/
  ADDRESS COMMAND
  'CP SET PF12 RETRIEVE' /* set command retrieve */
  'CP SPOOL CONSOLE * START' /* spool the console */
  'ACCESS 691 B' /* access the FDRPAS command */
  'ACCESS 692 C' /* access the product code */
• Log off of FDRMAINT.

The FDRMAINT virtual machine should now be defined and configured.

Create the FDRPASVM Virtual Machine

The FDRPASVM service machine runs the SWAP monitors for the devices specified with the FDRPAS CMS command. All z/VM command classes are required to ensure proper control of the DASD devices being swapped.

The service machine should usually be automatically logged on at system IPL, but it can also be started manually when required to monitor FDRPAS swaps.

A user-defined z/VM diagnose is required by the service machine to perform functions that can only be done within the z/VM CP Nucleus. This diagnose is dynamically loaded with the CPXLOAD command. The user diagnose can be loaded at any time before starting the service machine. If desired, the user diagnose can be disabled and then unloaded with the CPXUNLOAD command after exiting the service machine.

If you are not in an SSI environment, create the FDRPASVM virtual machine as follows, where text in italics should be replaced with values for your environment:

• Log on to MAINT, or another virtual machine with sufficient privileges.

• In this example, IBM DirMaint is configured, so the FDRPASVM DIRECT file is created.

  USER FDRPASVM password 512M 1024M ABCDEFG
  INCLUDE IBMDFLT
  IPL CMS
  IUCV ALLOW
  MACH ESA
  OPTION CHPIDV OFF
  LINK MAINT 0193 0193 RR
  LINK FDRMAINT 0692 0692 RR
  MDISK 0191 3390 start 100 volser MR rpass wpass mpass

• Create the virtual machine. In this example, DirMaint is running so the command is DIRM ADD. If you are using a different directory maintenance product or none at all, add the virtual machine accordingly.

  ==> dirm add fdrpasvm
  DVHREQ2289I Your ADD request for FDRPASVM at * has completed; with RC
  DVHREQ2289I = 0.

  Important

  If running a z/VM Single System Image (SSI) environment, the steps are different.

• If running an SSI environment, create this virtual machine as an IDENTITY (not a USER) so that it can be logged on to all members of the SSI at the same time.

Create the FDRPASVM IDENTITY with no directory maintenance product

If you are not using a directory maintenance product, the IDENTITY and SUBCONFIGs can be added at the same time. The following example shows the entry for a two-member SSI with the member systems being SSI63A and SSI63B. The new IDENTITY and two SUBCONFIGs being created.

• Add the following to the bottom of the USER DIRECT file.

  ==> x user direct c
  …
  IDENTITY FDRPASVM password 512M 1024M ABCDEFG
  INCLUDE IBMDFLT
  BUILD ON SSI63A USING SUBCONFIG FDRPAS-1
  BUILD ON SSI63B USING SUBCONFIG FDRPAS-2
  IPL CMS
  IUCV ALLOW
  MACH ESA
  OPTION CHPIDV OFF
  LINK MAINT 0193 0193 RR
  LINK FDRMAINT 0692 0692 RR
  SUBCONFIG FDRPAS-1
  MDISK 0191 3390 2636 100 VM189A MR rpass wpass mpass
  SUBCONFIG FDRPAS-2
  MDISK 0191 3390 2736 100 VM189A MR rpass wpass mpass

•  Bring the changes online with the DIRECTXA command.

  ==> directxa user
  …

Create the FDRPASVM IDENTITY with a directory maintenance product

If you are not using a directory maintenance product, the IDENTITY and SUBCONFIGs are added in multiple steps.

• First create the input file for the IDENTITY, then one file for each member.

  ==> x fdrpasvm direct
  IDENTITY FDRPASVM password 512M 1024M ABCDEFG
  INCLUDE IBMDFLT
  IPL CMS
  IUCV ALLOW
  MACH ESA
  OPTION CHPIDV OFF
  LINK MAINT 0193 0193 RR
  LINK FDRMAINT 0692 0692 RR

• Create the input files for each SUBCONFIG. In this example, there are two.

  ==> x fdrpas-1 direct
  SUBCONFIG FDRPAS-1
  MDISK 0191 3390 start 100 volser MR rpass wpass mpass
  ==> x fdrpas-2 direct
  SUBCONFIG FDRPAS-2
  MDISK 0191 3390 start 100 volser MR rpass wpass mpass

• Add the IDENTITY with the DIRM ADD command.

  ==> dirm add fdrpasvm
  PUN FILE 0053 SENT TO DIRMAINT RDR AS 0121 RECS 0015 CPY 001 0 NOHOLD NOKEEP
  DVHXMT1191I Your ADD request has been sent for processing to DIRMAINT at
  DVHXMT1191I SSI63A.
  …
  DVHREQ2289I Your ADD request for FDRPASVM at * has completed; with RC
  DVHREQ2289I = 0.

• Add the SUBCONFIGs with the BUILD ON clause.

  ==> dirm add fdrpas-1 build on ssi63a in fdrpasvm
  PUN FILE 0054 SENT TO DIRMAINT RDR AS 0137 RECS 0011 CPY 001 0 NOHOLD NOKEEP
  DVHXMT1191I Your ADD request has been sent for processing to DIRMAINT at
  DVHXMT1191I SSI63A.
  …
  DVHREQ2289I Your ADD request for FDRPAS-1 at * has completed; with RC
  DVHREQ2289I = 0.
  ==> dirm add fdrpas-2 build on ssi63b in fdrpasvm
  PUN FILE 0055 SENT TO DIRMAINT RDR AS 0149 RECS 0011 CPY 001 0 NOHOLD NOKEEP
  DVHXMT1191I Your ADD request has been sent for processing to DIRMAINT at
  DVHXMT1191I SSI63A.
  …
  DVHREQ2289I Your ADD request for FDRPAS-2 at * has completed; with RC
  DVHREQ2289I = 0.

  Important

  End of z/VM Single System Image (SSI) differences.

• Log on to the new FDRPASVM virtual machine, again watching for error messages.

  LOGON FDRPASVM
  z/VM Version 6 Release 3.0, Service Level 1302 (64-bit),
  …

• If you see a DMSACP112S error message, it again means the disk has not been formatted for CMS files. Following is an example of formatting the 191 disk as file mode A:

  ==> format 191 a
  DMSFOR603R FORMAT will erase all files on disk A(191). Do you wish to continue?
  Enter 1 (YES) or 0 (NO).
  1
  DMSFOR605R Enter disk label:
  pvm191
  DMSFOR733I Formatting disk A
  DMSFOR732I 100 cylinders formatted on A(191)
•  Log off of FDRPASVM.
• Log on to FDRPASVMon all members of the cluster and repeat the previous steps to format the 100 disk on each member.

The FDRPASVM virtual machine is now created. Later, a PROFILE EXEC will be added to the FDRPASVMvirtual machine.

Limiting privilege classes

In the previous examples, the virtual machine FDRMAINT is given ABG privilege classes, and FDRPASVM is given all privilege classes. If this is not acceptable, a user-defined privilege class can be created. For example, to create a new privilege class P that permits the commands necessary for FDRPASVM to function, the following sample REXX EXEC is shown.

The new privilege class can be queried with the following command. For example, to query the CPACCESS command.

The FDRMAINT and FDRPASVM virtual machines now only need classes G and P on the USER statement in the user directory. In addition, the FDRPASVM code must be patched in order to allow it to load the user defined diagnose as described in Customizing-after-installation.

Load the FDRPASVM Software to the FDRMAINT Minidisks

The FDRPASVM software is distributed in an envelope file created by the VMFPLCD command. This file should be copied to the FDRMAINT A disk as FDRPAS DISTPIPE. The envelope file contains two files that are also envelope files. One file is used to load the FDRPASVM service machine minidisk, and the other is used to load the FDRPAS CMS command minidisk.

You should also have obtained the EXTRFDRP EXEC to make unwinding the envelope files easier. If you do not have it, you can still install the FDRPASVM; you will just need to type more commands.

There are different methods that can be used to copy the software to z/VM. The following is an example using FTP from a DOS Window to copy the FDRPASVM code to z/VM. In this example, the z/VM TCP/IP address is 192.168.1.20. The EXTRFDRP EXEC is uploaded in ASCII, and the software is uploaded in binary.

To load the FDRPASVM software to the proper minidisks, perform the following steps:

1. Log on as FDRMAINT.
2. Run the EXTRFDRP exec to extract the files from the envelope (DISTPIPE) file.

3. Query the CMS disks. Assuming the new PROFILE EXEC ran successfully, the 191, 691, and 692 disks should be accessed read/write as file modes A, B, and C.

   ==> q disk
   LABEL VDEV M STAT CYL TYPE BLKSZ FILES BLKS USED-(%) BLKS LEFT BLK TOTAL
   PSM191 191 A R/W 100 3390 4096 2 8-01 17992 18000
   PSM691 691 B R/W 5 3390 4096 0 7-01 893 900
   PSM692 692 C R/W 10 3390 4096 0 7-00 1793 1800
   MNT190 190 S R/O 207 3390 4096 696 18085-49 19175 37260
   MNT19E 19E Y/S R/O 500 3390 4096 1124 30404-34 59596 90000

   Important

   If you have already copied the EXTRFDRP EXEC, you can skip the next section. If you do not have it, you can also copy it from Sample REXX EXEC to Extract FDRPASVM Distribution File.

Extract the FDRPASVM code without the EXTRFDRP EXEC

To extract the FDRPASVM code without using the EXTRFDRP EXEC, perform the following steps:

1. Use the PIPE command to convert the distribution file back to CMS format.

   ==> pipe < fdrpas distpipe a | deblock cms | > fdrpas dist a

   This creates the file FDRPAS DIST on your A disk.

2. Use the VMFPLCD command twice, first with the reset (RST) operand then with the load operand to restore the envelope file.

   ==> vmfplcd rst env= fdrpas dist a
   ==> vmfplcd load * * a (eod date
   Loading ... Format LRECL Records Date Time
   FDRPASB DIST A1 V 8120 964 08/25/14 10:27:43
   End-Of-Group OR End-Of-Disk
   FDRPASC DIST A1 V 65535 1002 08/25/14 10:27:46
   End-Of-Group OR End-Of-Disk
   End-Of-Group OR End-Of-Disk

   Important

   When entering the VMFPLCD commands, a space is required after ENV=. If you want to run the above commands from an EXEC, specify EXEC VMFPLCD instead of VMFPLCD. (VMFPLCD fails if it is not called with EXEC.)

3.  Verify that two DIST files were unloaded with the FILELIST command.

   ==> filel
   FDRMAINT FILELIST A0 V 169 Trunc=169 Size=5 Line=1 Col=1 Alt=24
   Cmd  Filename Filetype Fm Format Lrecl Records Blocks    Date   Time
    FDRPAS   DIST     A1 V     65535 1970 50     8/25/14 11:19:01
    FDRPAS   DISTPIPE A1 V     8192 26     50   8/25/14 11:15:57
    FDRPASC  DIST     A1 V     65535 1002 35  8/25/14 10:27:46
    FDRPASB  DIST     A1 V     8120 964 15  8/25/14 10:27:43

4. Invoke two VMFPLCD commands to reset and load the envelope file for the B minidisk.

   ==> vmfplcd rst env= fdrpasb dist a
   ==> vmfplcd load * * b (eod date
   Loading ...       Format  LRECL  Records     Date     Time
   FDRPAS    EXEC   B1 V      25 8       08/18/14 12:05:07
   FDRPAS    MODULE B1 V      8120 4       08/20/14 10:29:47
   PASUPA    TEXT   B1 F      80 43       07/17/14 10:19:26
   PASUSY    TEXT   B1 F      80 3       07/17/14 10:19:25
   CALCDASD  EXEC   B1 V      73 901    08/25/14 07:14:45
   End-Of-Group OR End-Of-Disk
   End-Of-Group OR End-Of-Disk

5. Invoke two VMFPLCD commands to reset and load the envelope file for the C minidisk.

   ==> vmfplcd rst env= fdrpasc dist a
   ==> vmfplcd load * * c (eod date
   Loading ... Format    LRECL    Records   Date   Time
   DIAGLOAD EXEC   C1      V            95 82 10/15/13 16:09:35
   DIAGRELO EXEC   C1      V            76    113 10/30/13 08:49:28
   FDRDGN54 RULES  C1      F            80  3 09/25/13 03:25:54
   FDRDGN54 TEXT   C1      F            80   150 08/20/14 10:29:38
   FDRDGN62 RULES  C1      F            80  3 10/03/13 19:53:03
   FDRDGN62 TEXT   C1      F            80   152 08/20/14 10:29:42
   FDRDGN63 RULES  C1      F            80  3 01/14/14 08:43:38
   FDRDGN63 TEXT   C1      F            80    152 08/20/14 10:29:46
   FDRPASOP MODULE C1      V            80  3 08/20/14 10:29:47
   FDRPASXT TEXT   C1      F            80    309 07/28/14 15:52:33
   IUCSM EXEC      C1      V            41    15 03/21/13 04:09:41
   PASIUCSM MODULE C1      V         65535  5 08/20/14 10:29:49
   End-Of-Group OR End-Of-Disk
   End-Of-Group OR End-Of-Disk
6. Log off of FDRMAINT.

FDRPASVM is now installed.

Extract the FDRPASVM Code Using the EXTRFDRP EXEC

If you have a copy of the EXTRFDRP EXEC, you can extract the FDRPASVM code with less typing.

1. Run the EXTRFDRP EXEC. It expects the file FDRPAS DISTPIPE to be on a read/write A disk.

   ==> extrfdrp
   Deblocking FDRPAS DISTPIPE A file ...
   Loading main envelope file on A disk ...
   Loading ... Format LRECL Records Date  Time
   FDRPASB DIST  A1 V  8368    1603 12/15/14 11:24:46
   End-Of-Group OR End-Of-Disk
   FDRPASC DIST      A1 V 65535    1916 12/15/14 11:24:46
   End-Of-Group OR End-Of-Disk
   End-Of-Group OR End-Of-Disk
   Loading envelope file for FDRMAINT 691 disk (B) ...
   Loading ... Format LRECL Records Date  Time
   CALCDASD EXEC   B1  V    75    1208   12/01/14 13:33:38
   FDRPAS EXEC   B1  V    25   8 08/18/14 12:05:07
   FDRPAS MODULE   B1  V  8368   4 12/15/14 10:42:45
   PASUPA TEXT   B1  F    80   43 12/15/14 10:41:06
   PASUSY TEXT   B1  F   80   3 12/15/14 10:41:06
   PROFILE FDRPASVM  B1  F    80  17 12/15/14 11:06:14
   PROFILE FDRMAINT  B1  F    80   8 11/24/14 10:03:33
   QLABEL EXEC   B1  V    75 304 12/01/14 13:33:34
   End-Of-Group OR End-Of-Disk
   End-Of-Group OR End-Of-Disk
   Loading envelope file for FDRMAINT 692 disk (C) ...
   Loading ... Format LRECL Records Date Time
   …
   Successfully extracted FDRPAS DISTPIPE A

   FDRPASVM is now installed.

Sample REXX EXEC to extract FDRPASVM distribution file

You can copy the following sample EXTRFDRP EXEC to make unwinding the FDRPAS DISTPIPE file if you do not have a copy of it: