FDRPAS SWAP task examples
These are examples of SWAP operations, where the volumes involved are moved to the new DASD devices specified by the SWAPUNIT= operand. The examples first show performing the task by using the ISPF panels. This is followed by a comparable JCL example that can be found in the JCL library installed with FDRPAS. The member names are PA31021x. We recommend you to use the ISPF panels to generate the FDRPAS JCL and control cards.
See FDRPAS ISPF Interface for detailed information on using and submitting jobs using the ISPF panels.
Example - swap a group of volumes on multiple systems
In this example, the volumes in SMS storage group “PROD9” are swapped to offline units in the 21C* range. To perform that, type “prod9” in the “SMS Storage Group” field and press Enter.
COMMAND ===> Menu Panel: 1 of 3 |
The information for the devices in SMS storage group PROD9 are displayed. From this panel, type the target mask “21c*” in the “Swap to Offline Unit” field to generate the offline units for the displayed volumes.
Menu Panel: 1 of 3 |
The source and target devices are verified on the executing system and additional source volume information is displayed. If no discrepancies are found with the source and target volumes, “INACTIVE” is displayed in the “Status” field.
Menu Panel: 1 of 3 |
Once all the information is entered, Use the “SIMSWAP job” option on the “Menu” drop-down list to generate the job and control cards to perform the SIMSWAP.
FDRPAS pull-down menu
Active SWAP job CLear entries COnfirm SWAPDUMP job RESEt status Message CONFIRM job SUspend MONITOR job REsume SIMSWAP job ABORT SIMSWAPMON job Options AUTOSWAP job HIstory HYPERSWAP job SOrt Place the cursor next to the command to execute and press enter. Press PF3 to exit. Press PF1 for the Help tutorials. |
Pressing Enter displays the generated JCL and control statements that can be modified if needed. Type “submit” on the TSO command line to submit this for execution. The options that are generated are the values from the FDRPAS Options panel (see FDRPAS ISPF Interface).
SIMSWAP generated JCL and control statements
Command ===> submit |
The output from this SIMSWAP run includes the CPU serial numbers and the number of systems that need to have MONITOR tasks running.
… |
FDR233 CPU WITH (SERIAL# 026E0D2096) IS ATTACHED TO VOL=IDPLB3 - EMC 2105F20 TO IBM 2107921 |
FDR233 CPU WITH (SERIAL# 016E0D2096) IS ATTACHED TO VOL=IDPLB3 - EMC 2105F20 TO IBM 2107921 |
FDR233 CPU WITH (SERIAL# 096E0D2096) IS ATTACHED TO VOL=IDPLB3 - EMC 2105F20 TO IBM 2107921 |
FDRW66 SWAP OF VOL=IDPLB3 TO UNIT=21C3 NEEDS TO BE STARTED ON 3 SYSTEMS |
… |
The CPU serial numbers from the SIMSWAP output is needed to create the JCL for the MONITOR tasks. Use the FDRPAS Options panel (go to the pull-down MENU and select “Options”) to type the CPU serial numbers and the JCL necessary to route jobs on the other LPARs.
FDRPAS options panel (A.P.OPTIONS) – Enter CPUID and routing JCL
More: - + |
The Options panel allows specification of up to 12 MONITOR tasks. If you need to add more than 12 MONITOR tasks, they can be added manually after the JCL is generated.
Use the “SIMSWAPMON job” option from the FDRPAS pull-down MENU to generate the JCL and control statements needed to run the SIMSWAPMON job. Type “submit” on the TSO command line to submit this for execution.
SIMSWAPMON generated JCL and control statements
Command ===> submit |
The output from this SIMSWAPMON run shows that CHECKSOURCE=YES was specified “CPK320I” as well as the acknowledgment of the MONITOR tasks from the other LPARs FDR233. It also shows that the job completed successfully FDR 999 and is ready for the actual SWAP job to be run.
FDR303 CARD IMAGE -- SIMSWAPMON TYPE=FULL, |
FDR303 CARD IMAGE -- CONFIRMSWAP=NO, |
FDR303 CARD IMAGE -- CONFMESS=NO, |
FDR303 CARD IMAGE -- LOGMESS=YES, |
FDR303 CARD IMAGE -- PACEDELAY=0, |
FDR303 CARD IMAGE -- SWAPDELAY=15, |
FDR303 CARD IMAGE -- CHECKSOURCE=YES, |
FDR303 CARD IMAGE -- CHECKTARGET=YES, |
FDR303 CARD IMAGE -- LARGERSIZE=OK, |
FDR303 CARD IMAGE -- PACING=STATIC, |
FDR303 CARD IMAGE -- MAXTASKS=1, |
FDR303 CARD IMAGE -- MAXACTIVESWAPS=NO, |
FDR303 CARD IMAGE -- WTOR=YES |
FDR303 CARD IMAGE -- MOUNT VOL=IDPLB8,SWAPUNIT=21C8 |
FDR303 CARD IMAGE -- MOUNT VOL=IDPLB7,SWAPUNIT=21C7 |
FDR303 CARD IMAGE -- MOUNT VOL=IDPLB6,SWAPUNIT=21C6 |
FDR303 CARD IMAGE -- MOUNT VOL=IDPLB5,SWAPUNIT=21C5 |
FDR303 CARD IMAGE -- MOUNT VOL=IDPLB4,SWAPUNIT=21C4 |
FDR303 CARD IMAGE -- MOUNT VOL=IDPLB3,SWAPUNIT=21C3 |
FDR183 FDR SUBMITTED FDRPAS MONITOR JOBNAME=PASMONU FOR CPUID=0912342818 |
FDR183 FDR SUBMITTED FDRPAS MONITOR JOBNAME=PASMONV FOR CPUID=0112342818 |
FDR256 --- REPORT FROM SYSPRIN1 --- |
CPK320I COMPAKTOR OPTIONS IN EFFECT -- CHECKSOURCE-------------IDPLB8 |
CPK529I INDEXED VTOC EXISTS ON VOLUME=IDPLB8 |
VOLUME SUMMARY --- DEVICE TYPE ................................. 3390-3 |
NO. OF TRACKS ............................... 50085 |
NO. OF CYLINDERS ............................ 3339 |
NO. OF ALLOCATED TRACKS ..................... 48834 |
PERCENTAGE OF VOLUME IN USE ................. 98 |
CPK600I COMPAKTOR SUCCESSFULLY COMPLETED CHECKSOURCE RUN ------ VOLUME=IDPLB8 |
FDR233 CPUB (SERIAL# 0212342818) ACKNOWLEDGES THE SWAP OF VOL=IDPLB8 - HTC 2107900 TO HTC 2107900 |
FDR233 CPUC (SERIAL# 0112342818) ACKNOWLEDGES THE SWAP OF VOL=IDPLB8 AND HAS JOINED IN SWAP OF UNIT=8068 TO 21C8 |
FDR233 CPUA (SERIAL# 0912342818) ACKNOWLEDGES THE SWAP OF VOL=IDPLB8 AND HAS JOINED IN SWAP OF UNIT=8068 TO 21C8 |
FDRW66 SIMSWAP VOL=IDPLB8 TO UNIT=21C8 COMPLETED 3 SYSTEMS (CPUB CPUC CPUA) |
… |
FDR999 FDR SUCCESSFULLY COMPLETED |
This listing shows that two MONITOR tasks were started by FDRPAS. Also, since CHECKSOURCE=YES was specified, it shows the COMPAKTOR stats from the volume plus the VTOC and VVDS had no errors. The last part of the messages show the systems that participate in the swap.
After running and verifying that the SIMSWAPMON job completed with no errors, return to the FDRPAS ISPF panels and generate the SWAP job that performs the actual movement of the data. The JCL that is generated looks similar to the SIMSWAPMON JCL. When everything is ready, type “submit” on the TSO command like to submit the JCL.
SWAP generated JCL and control statements
Command ===> submit |
Simulate a swap example
Execute a simulated swap (SIMSWAP statement) to validate the parameters being used for the real SWAP. No MONITOR tasks are required. This displays all of the LPARs with access to the source volumes on DASD subsystems where FDRPAS can identify the attached LPARs.
//STEPLIB DD DISP=SHR,DSN=fdrpas.loadlib
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
SIMSWAP TYPE=FULL,MAXTASKS=3,LARGERSIZE=OK
MOUNT VOL=DATA22,SWAPUNIT=07C3
MOUNT VOL=PROD12,SWAPUNIT=425C
/*
Simulate a SWAP with Monitor Tasks Example
Execute a simulated swap with monitor checking (SIMSWAPMON statement) to validate the parameters being used for the real SWAP. MONITOR tasks are required for all LPARs in the sysplex. In this example, one LPAR is a z/VM system requiring an EXCLUDE CPUID= statement to exclude that LPAR. If you are licensed for FDRPASVM (see FDRPASVM) an EXCLUDE statement is not necessary for supported z/VM systems and the z/VM system does not need to be quiesced.
//SIMSWAPM EXEC PGM=FDRPAS,REGION=0M//STEPLIB DD DISP=SHR,DSN=fdrpas.loadlib//FDRSUMM DD SYSOUT=*//SYSPRINT DD SYSOUT=*//SYSIN DD * SIMSWAPMON TYPE=FULL,MAXTASKS=10,LARGERSIZE=OK,CHECKSOURCE=YES EXCLUDE CPUID=0220F72828 EXCLUDE z/VM LPAR MOUNT VOL=MV4324,SWAPUNIT=99A1 MOUNT VOL=MV4287,SWAPUNIT=99A2 MOUNT VOL=MV4445,SWAPUNIT=99A3/*//PASJOB DD DATA,DLM=ZZ//*CPUID=0320E72828//T#PASSW_ JOB jobcard
/*JOBPARM SYSAFF=____//*//* EXECUTE FDRPAS MONITOR//FDRPAS EXEC PGM=FDRPAS,REGION=0M//STEPLIB DD DISP=SHR,DSN=fdrpas.loadlib//SYSPRINT DD SYSOUT=*//SYSUDUMP DD SYSOUT=*//SYSIN DD * MONITOR TYPE=SWAP MOUNT SWAPUNIT=99A1 MOUNT SWAPUNIT=99A2 MOUNT SWAPUNIT=99A3/*//*CPUID=0120E72828//T#PASSW_ JOB jobcard
/*JOBPARM SYSAFF=____//*//* EXECUTE FDRPAS MONITOR//FDRPAS EXEC PGM=FDRPAS,REGION=0M//STEPLIB DD DISP=SHR,DSN=fdrpas.loadlib//SYSPRINT DD SYSOUT=*//SYSUDUMP DD SYSOUT=*//SYSIN DD * MONITOR TYPE=SWAP MOUNT SWAPUNIT=99A1 MOUNT SWAPUNIT=99A2 MOUNT SWAPUNIT=99A3/*//*CPUID=0220E72828//T#PASSW_ JOB jobcard
/*JOBPARM SYSAFF=____//*//* EXECUTE FDRPAS MONITOR//FDRPAS EXEC PGM=FDRPAS,REGION=0M//STEPLIB DD DISP=SHR,DSN=fdrpas.loadlib//SYSPRINT DD SYSOUT=*//SYSUDUMP DD SYSOUT=*//SYSIN DD * MONITOR TYPE=SWAP MOUNT SWAPUNIT=99A1 MOUNT SWAPUNIT=99A2 MOUNT SWAPUNIT=99A3/*
ZZ
Example - Swap a volume on multiple systems
A volume accessible to multiple system images is swapped to a new device. FDRPAS determines the number of systems that have access to the volume. Prior to running this job, you must start FDRPAS MONITOR tasks on each of the systems, to monitor the target device (see MONITOR SWAP Examples). The target device must be offline on all systems.
//SWAP EXEC PGM=FDRPAS,REGION=0M//STEPLIB DD DISP=SHR,DSN=fdrpas.loadlib//SYSPRINT DD SYSOUT=*//FDRSUMM DD SYSOUT=*//SYSUDUMP DD SYSOUT=*//SYSIN DD * SWAP TYPE=FULL MOUNT VOL=DATA22,SWAPUNIT=07C3/*
A partial output from the swap step looks similar to:
FDR241 FDRPAS SUCCESSFULLY COMPLETED SWAP OF VOL=DATA22 TO UNIT=07C3 ON CPUB |
FDR241 FDRPAS SUCCESSFULLY COMPLETED SWAP OF VOL=DATA22 TO UNIT=07C3 ON CPUA |
FDR241 FDRPAS SUCCESSFULLY COMPLETED SWAP OF VOL=DATA22 TO UNIT=07C3 ON CPUC |
FDR007 ENDING TIME OF FULL VOL SWAP -- 16.31.56 -- UNIT=3390-3 ,IN=D#DATA22,OUTPUT=TAPE1 |
FDR122 OPERATION STATISTICS FOR 3390 VOLUME..................DATA22 |
FDR122 CYLINDERS ON VOLUME..............3,339 |
FDR122 DATASETS PROCESSED.................234 |
FDR122 BYTES READ FROM DASD.......237,893,477 |
FDR122 DASD TRACKS SWAPPED..............4,986 |
FDR122 UPDATED TRACKS RECOPIED..........2,639 |
FDR122 DASD EXCPS.........................381 |
FDR122 TARGET DASD EXCPS..................450 |
FDR122 CPU TIME (SECONDS)...............0.522 |
FDR122 ELAPSED TIME (MINUTES).............2.5 |
FDR122 SWAP TIME..........................2.5 |
FDR999 FDR SUCCESSFULLY COMPLETED |
DASD TRACKS SWAPPED
DASD TRACKS SWAPPED is the total number of tracks that had to be copied during the swap, including tracks that were copied more than once because of updates during the swap.
UPDATED TRACKS RECOPIED is the number of tracks that had to be copied more than once because they were updated during the swap.
Example - Swap several volumes on a single system concurrently
Several volumes on adjacent z/OS addresses on a single system image2 are swapped to new devices on adjacent addresses (1AAx) in the new DASD subsystem. The volumes must not be accessible by any other system image. The target devices must be offline to all systems. All five volumes are swapped concurrently.
//SWAP EXEC PGM=FDRPAS,REGION=0M//STEPLIB DD DISP=SHR,DSN=fdrpas.loadlib//SYSPRINT DD SYSOUT=*//FDRSUMM DD SYSOUT=*//SYSUDUMP DD SYSOUT=*//SYSIN DD * SWAP TYPE=FULL,MAXTASKS=5,CHECKTARGET=YES MOUNT VOL=TSO001,SWAPUNIT=1AA* MOUNT VOL=TSO002,SWAPUNIT=1AA* MOUNT VOL=TSO003,SWAPUNIT=1AA* MOUNT VOL=TSO004,SWAPUNIT=1AA* MOUNT VOL=TSO005,SWAPUNIT=1AA*/*
Example - SWAP a volume on a single system setting source volume serial
A volume on a single system image<Superscript>1 is swapped to a new device. The volume must not be accessible by any other system image. The target device must be offline to all systems. At the completion of the SWAP, give the source device a volume serial number of “ZZ” followed by the 4-digit device number (unit address). Give the volume label an invalid ID of FDR3 so that the volume cannot be brought online.
//SWAP EXEC PGM=FDRPAS,REGION=0M//STEPLIB DD DISP=SHR,DSN=fdrpas.loadlib//SYSPRINT DD SYSOUT=*//FDRSUMM DD SYSOUT=*//SYSUDUMP DD SYSOUT=*//SYSIN DD * SWAP TYPE=FULL,CHECKTARGET=YES MOUNT VOL=WORK55,SWAPUNIT=374C,CHANGEVOL=ZZ&UUU/*
Example - SWAP a volume on a single system setting source volume serial and copying the volume label
A volume on a single system image<Superscript>1 is swapped to a new device. The volume must not be accessible by any other system image. The target device must be offline to all systems. At the completion of the SWAP, give the source device a volume serial number of “XX” followed by the 4-digit device number (unit address). Copy the ID of the volume label from the target device. If the volume label of the target device has a valid ID of VOL1 before the SWAP, then the source device will have a valid volume label with a unique volume serial number, and will be able to be brought online after the SWAP.
//SWAP EXEC PGM=FDRPAS,REGION=0M//STEPLIB DD DISP=SHR,DSN=fdrpas.loadlib//SYSPRINT DD SYSOUT=*//FDRSUMM DD SYSOUT=*//SYSUDUMP DD SYSOUT=*//SYSIN DD * SWAP TYPE=FULL,LABEL=SWAP,CHECKTARGET=YES MOUNT VOL=WORK55,SWAPUNIT=374C,CHANGEVOL=XX&UUU/*
Example - SIMULATE a SWAP, and generate and submit monitor tasks
(1) Execute a simulated swap, and (2) generate and submit the MONITOR tasks for the other LPARs to validate the parameters you use for the real SWAP. The PASPROC procedure is used to ensure all the tasks use the same JCL and to reduce the number of JCL statements needed. The DURATION= operand is not coded since we want these MONITOR tasks to dynamically build the table to be used by the actual SWAP task that is submitted later.
We recommend using the ISPF panels to generate the SIMSWAPMON job with the PASJOB DD statements.
If the PASJOB DD statement contains a //*CPUID= referring to the LPAR that the SWAP task is executing, that MONITOR task is not submitted to that LPAR since the SWAP task performs the monitoring. In this way, a single job can be created that can be submitted on any of the LPARS without requiring any change.
//PASSWAPM EXEC PASPROC//PAS.SYSIN DD * SIMSWAPMON TYPE=FULL,MAXTASKS=16,LARGERSIZE=OK MOUNT VOL=HI17CC,SWAPUNIT=17CA MOUNT VOL=HI17C2,SWAPUNIT=17C1/*//PASJOB DD DATA,DLM=$$//*CPUID=0912342818//PASMONA JOB …/*ROUTE XEQ JESCPUA//MONITORA EXEC PASPROC//PAS.SYSIN DD * MONITOR TYPE=SWAP,DYNMON=YES/*//*CPUID=0212342818//PASMONB JOB …/*ROUTE XEQ JESCPUB//MONITORB EXEC PASPROC//PAS.SYSIN DD * MONITOR TYPE=SWAP,DYNMON=YES/*//*CPUID=0112342818//PASMONC JOB …/*ROUTE XEQ JESCPUC//MONITORC EXEC PASPROC//PAS.SYSIN DD * MONITOR TYPE=SWAP,DYNMON=YES/*$$
SIMSWAPMON sample output from the previous example
The following are examples of the output from the SWAP task and one of the MONITOR tasks. A MONITOR task was missing from one of the LPARs and is reflected in the output messages in the SWAP task.
The SYSPRINT output from the SWAP task looks similar to:
FDR001 FDR PLUG AND SWAP - FDRPAS VER. x.x/xx - INNOVATION DATA PROCESSING DATE=yyyy.ddd PAGE 1 |
FDR303 CARD IMAGE -- SIMSWAPMON TYPE=FULL,MAXTASKS=16,LARGERSIZE=OK |
FDR303 CARD IMAGE -- MOUNT VOL=HI17CC,SWAPUNIT=17CA |
FDR303 CARD IMAGE -- MOUNT VOL=HI17C2,SWAPUNIT=17C1 |
FDR183 FDR SUBMITTED FDRPAS MONITOR JOBNAME=PASMONA FOR CPUID=0912342818 |
FDR183 FDR SUBMITTED FDRPAS MONITOR JOBNAME=PASMONC FOR CPUID=0112342818 |
FDR256 --- REPORT FROM SYSPRIN1 --- |
FDR234** SWAP ERROR ON VOL=HI17CC - UNIT=17CA REASON=M - CPU (SERIAL#=0512342818) FAILED TO RESPOND IN PHASE 1 |
FDR234** SWAP ERROR ON VOL=HI17CC - UNIT=17CA REASON=Q - SWAP OPERATION CANCELLED NONRESPONDING=FAIL |
FDR998** FDRPAS COMPLETED WITH ERRORS VOL=HI17CC |
FDR256 --- REPORT FROM SYSPRIN2 --- |
FDR234** SWAP ERROR ON VOL=HI17C2 - UNIT=17C1 REASON=M - CPU (SERIAL#=0512342818) FAILED TO RESPOND IN PHASE 1 |
FDR234** SWAP ERROR ON VOL=HI17C2 - UNIT=17C1 REASON=Q - SWAP OPERATION CANCELLED NONRESPONDING=FAIL |
FDR998** FDRPAS COMPLETED WITH ERRORS VOL=HI17C2 |
FDR998** FDR COMPLETED WITH ERRORS |
The SYSPRINn DD statement output from the SWAP task looks similar to:
FDR001 FDR PLUG AND SWAP - FDRPAS VER. x.x/xx - INNOVATION DATA PROCESSING DATE=yyyy.ddd PAGE 1 |
FDR234** SWAP ERROR ON VOL=HI17CC - UNIT=17CA REASON=M - CPU (SERIAL#=0512342818) FAILED TO RESPOND IN PHASE 1 |
FDR234** SWAP ERROR ON VOL=HI17CC - UNIT=17CA REASON=Q - SWAP OPERATION CANCELLED NONRESPONDING=FAIL |
The SYSPRINT output from one of the MONITOR tasks looks similar to:
FDR001 FDR PLUG AND SWAP - FDRPAS VER. x.x/xx - INNOVATION DATA PROCESSING DATE=yyyy.ddd PAGE 1 |
FDR303 CARD IMAGE -- MONITOR TYPE=SWAP,DYNMON=YES |
FDR235 FDRPAS ON CPU SERIAL# 0112342818 IS MONITORING DYNAMICALLY |
FDR235 FDRPAS ON CPU SERIAL# 0112342818 IS MONITORING 17C1 |
FDR235 FDRPAS ON CPU SERIAL# 0112342818 IS MONITORING 17CA |
FDR238 FDRPAS STARTED MONITOR JOIN TASK FOR UNIT=17C1 |
FDR238 FDRPAS STARTED MONITOR JOIN TASK FOR UNIT=17CA |
FDR238 FDRPAS ENDED MONITOR JOIN TASK FOR UNIT=17CA |
FDR238 FDRPAS ENDED MONITOR JOIN TASK FOR UNIT=17C1 |
FDR238 FDRPAS STARTED MONITOR JOIN TASK FOR UNIT=17C1 |
FDR238 FDRPAS STARTED MONITOR JOIN TASK FOR UNIT=17CA |
FDR238 FDRPAS ENDED MONITOR JOIN TASK FOR UNIT=17C1 |
FDR238 FDRPAS ENDED MONITOR JOIN TASK FOR UNIT=17CA |
The SYSPRTnn DD statement output from one of the MONITOR tasks looks similar to:
FDR001 FDR PLUG AND SWAP - FDRPAS VER. x.x/xx - INNOVATION DATA PROCESSING DATE=yyyy.ddd PAGE 1 |
FDR303 CARD IMAGE -- MOUNT SU=17C1 ,,=17 PARM ENTRY |
FDR235 FDRPAS ON CPU SERIAL# 0112342818 IS MONITORING THE FOLLOWING 1 UNITS: |
FDR235 17C1 |
FDR233 CPUC (SERIAL# 0112342818) ACKNOWLEDGES THE SWAP OF VOL=HI17C2 AND HAS JOINED IN SWAP OF UNIT=17C2 TO 17C1 |
FDR999 FDR SUCCESSFULLY COMPLETED |
FDR001 FDR PLUG AND SWAP - FDRPAS VER. x.x/xx - INNOVATION DATA PROCESSING DATE=2010.270 PAGE 1 |
FDR303 CARD IMAGE -- MOUNT SU=17C1 ,,=17 PARM ENTRY |
FDR235 FDRPAS ON CPU SERIAL# 0112342818 IS MONITORING THE FOLLOWING 1 UNITS: |
FDR235 17C1 |
FDR999 FDR SUCCESSFULLY COMPLETED |