SWAP, SWAPDUMP, SIMSWAP, SIMSWAPMON statements

Additional large scale SWAP operands

Additional operands for Large Scale swaps:

SWAP statement

This statement initiates an FDRPAS SWAP task to move a volume to a new DASD device. It must be the first statement in the input; only one SWAP statement is allowed per execution. SWAP must be followed by one or more MOUNT statements to identify the online volumes to be swapped and may optionally be followed by one or more EXCLUDE statements to exclude certain systems that do not have a source volume online.

If multiple MOUNT statements are specified, by default FDRPAS processes them serially (one at a time). However, you can request that this SWAP task process multiple volumes concurrently, up to 100 at a time, by specifying the MAXTASKS= operand. To swap more than 100 volumes concurrently, you must start multiple SWAP tasks.

A RACROUTE call is issued to verify that the user has READ authority to resource “FDRPAS.SWAP” in the FACILITY class, if that resource is protected. If “FDRPAS.SWAP” is not protected, the operation continues.

If you have security checking enabled (see ALLCALL), SWAP checks that the user has ALTER authority to the source volume under the DASDVOL security class. If the user does not have DASDVOL authority, the operation fails. If the volume is not protected by DASDVOL, FDRPAS checks that the user has ALTER authority in the DATASET class to every data set on the volume; if any data set is not authorized the operation fails.

SWAPDUMP statement

SWAPDUMP is similar to SWAP, except that the volume is not swapped to the target device. It is used to create a point-in-time copy of the source volume on the target device that can then be backed up with FDRINSTANT. All rules and considerations of SWAP also apply to SWAPDUMP. Contact BMC Support if processing a large number of volumes to go over GENSWAP.

Start the SWAPDUMP operation far enough ahead of the time you plan to do the backup so that FDRPAS can copy the data and synchronize the volumes. If you specify CONFIRMSPLIT=YES, FDRPAS then continues to keep the volumes synchronized until you “confirm” the operation and create the frozen point-in-time copy, at that time you can submit the FDRINSTANT backup jobs.

MAXTASKS= is especially useful for SWAPDUMP when there is the need to create point-in-time backups of a large number of DASD volumes all at the same point-in-time. MAXTASKS= allows the SWAPDUMP of up to 100 DASD volumes in a single swap job or started task, so that the number of jobs or tasks required to synchronize all of those volumes is small.

A RACROUTE call is issued to verify that the user has READ authority to resource FDRPAS.SWAPDUMP in the FACILITY class, if that resource is protected. If FDRPAS.SWAPDUMP is not protected, the operation is allowed.

SIMSWAP statement

SIMSWAP performs a simulation of a SWAP operation. The SIMSWAP statement accepts all of the operands and statements of a SWAP operation but it does not actually perform a swap. The SIMSWAP statement does not require MONITOR tasks on other systems; if MONITOR tasks are running they do not participate.

SIMSWAP has these uses:

• It validates all of the operands that appear on the SWAP statement.
• It validates the online volumes and offline target devices specified on the MOUNT statements on the system where the SIMSWAP is executed. This identifies errors such as the target device does not exist or is not offline, or is the wrong type or size.
• For DASD volumes in subsystems where FDRPAS can determine the systems with access to the source volume, it displays all of the identified systems, including their CPU IDs, in FDR233 messages. You can verify that all of the systems you expect have access, and that there are no unexpected systems with access.

SIMSWAPMON statement

SIMSWAPMON performs a simulation of a SWAP operation and provides additional processing above that performed by SIMSWAP by communicating with the MONITOR tasks. The SIMSWAPMON statement accepts all of the operands and statements of a SWAP operation so they can be used for the actual SWAP operation after running the SIMSWAPMON. The SIMSWAPMON does not perform the SWAP. SIMSWAPMON requires and verifies that MONITOR tasks are running on all the other systems.

SIMSWAPMON has these uses:

• It validates all of the operands that appear on the SWAP statement.
• It validates the source volumes and target devices specified on the MOUNT statements on the system where SIMSWAPMON is executed as well as all the systems where MONITOR tasks are running. This identifies errors such as the target device does not exist, or is the wrong type or size.
• It displays all the systems that respond and that join in the swap operation. It also displays all the systems that did not join (ERROR) or did not need to join (OK). Non-responding systems where MONITOR tasks are not running are also displayed.
• It can check the integrity of the VTOC and VVDS on the source volume (CHECKSOURCE=YES), and whether the target device is empty of data sets (CHECKTARGET=YES).
• It is recommended to always run SIMSWAPMON before running any dynamic processing to allow SIMSWAPMON to populate the MONITOR tasks (if needed).

The time needed to validate the devices depends on how the devices are specified or discovered in the MONITOR tasks. This is the time that it takes for the SWAP task to discover the status of a non-responding device. For example,

• It takes approximately 5-10 seconds when the MONITOR tasks have MOUNT statements with the appropriate SWAPUNITs.
• It takes approximately 30-40 seconds when the MONITOR task dynamically adds the SWAPUNIT.
• It takes approximately 120 seconds when one or more MONITOR tasks are not running or cannot dynamically add the SWAPUNIT.

Certain situations cannot be identified until the actual SWAP is attempted. These include having a duplicate source volume specified or having duplicate SWAPUNITs specified.

SWAP, SWAPDUMP, SIMSWAP, and SIMSWAPMON statement operands

TYPE=FULL

Must be specified on the SWAP, SWAPDUMP, SIMSWAP, or SIMSWAPMON statement.

ALLOWPAV=

APV=

The ALLOWPAV= operand controls the status of the Parallel Access Volume (PAV) aliases during the SWAP operation. This operand specifies whether the Parallel Access Volume (PAV) aliases for the source volume are disabled at the start of the SWAP operation or at the time when the actual SWAP of the volume occurs. (The PAV aliases for the target volume are always disabled at the start of the SWAP operation.)

NO

Indicates that the Parallel Access Volume (PAV) aliases for the source volume are disabled at the start of the SWAP operation and re-enabled after the SWAP operation completes.

YES

For SWAP, indicates that the Parallel Access Volume (PAV) aliases for the source volume stay enabled during the initial copy phase and are disabled during the time the actual SWAP of the volume occurs. This reduces the amount of time that PAV aliases are not available. For SWAPDUMP, indicates that the PAV aliases for the source volume stay enabled during the entire operation.

Default: NO.

ALLOWZHPF=

NO

At the beginning of a SWAP, FDRPAS temporarily disables zHPF only on the source volume(s) being swapped; FDRPAS turns zHPF back on at the end of the SWAP.

YES

FDRPAS allows zHPF Transport Control Word (TCW) commands and does not disable zHPF for the SWAP process.

Default: NO.

BUFNO=

nn

Specifies the number of I/O buffers that FDRPAS uses while copying data from the source volume to the target device, from 2 to 32. It should be an even number and is rounded up if odd. FDRPAS divides this buffer set in half, in order to overlap input and output I/Os. With BUFNO=32, FDRPAS reads and writes up to 15 tracks per I/O; with lesser values, it does half of the BUFNO= value in tracks per I/O. A smaller BUFNO= value reduces the elapsed time of each I/O, and thus reduces the impact of each I/O on your I/O system, but it increases the number of I/Os required to copy the data, and thus increases the total time to do the swap.

We do not recommend specifying BUFNO= unless the length of the FDRPAS I/Os are causing problems. For example, certain hardware channel extenders may experience errors on extremely long I/O chains, causing the swap to fail. Reducing BUFNO= may allow the swap to work. If many FDRPAS swaps are running concurrently, the length of each individual FDRPAS I/O may impact overall system performance; reducing BUFNO= may decrease this impact (see also PACEDELAY=).

Default: 32.

CANCELPROT=

CP=

NO

A CANCEL(C) command causes immediate termination of the SWAP task.

YES

FDRPAS protects this SWAP task against accidental cancellation. If a CANCEL(C) command is issued, it is treated like a STOP(P) command. Message FDR267 is issued and the task lets active swaps complete before terminating. You can issue a second CANCEL(C) command to force immediate termination.

Default: NO.

CHECKSOURCE=

FDRPAS checks the integrity of the VTOC and VVDS. It is recommended that a CHECKSOURCE=YES be run at least once before running the actual swap to check the source volumes for errors

NO

The source volume is not checked for structural errors in the VTOC and VVDS.

YES

During the SIMSWAP or SIMSWAPMON process, FDRPAS checks the source volume for structural errors in the VTOC and VVDS. This operand is ignored on SWAP and SWAPDUMP operations.

Default: NO. CHECKSOURCE=YES is recommended for SIMSWAPMON jobs.

CHECKTARGET=

CKT=

NO

The target volume is not checked. The target volume is overlaid regardless of its current contents.

YES

FDRPAS checks the target device before beginning a SWAP or SWAPDUMP operation to ensure that the target is empty. The operation is terminated if the target contains any data sets other than a VTOC, VTOC index (SYS1.VTOCIX.volser), or VVDS (SYS1.VVDS.Vvolser). Also, volumes initialized by z/VM, with a dummy VTOC in cylinder 0 track 0, are bypassed. DASD volumes that do not contain a valid volume label (such as those that have never been used since they were delivered or defined) are also accepted; this includes volumes that were the source volumes of successful FDRPAS swaps.

Default: NO. CHECKTARGET=YES is recommended for SIMSWAPMON jobs.

CONFIRMSPLIT=

CONFIRMSWAP=

NO

FDRPAS completes the operation as soon as the source and target devices are in synchronization, without waiting for any confirmation. CONFIRMSWAP=NO is recommended for a SWAP operation unless you have a need to swap a set of volumes at the same time.

YES

FDRPAS does not complete the swap or dump of this volume until you confirm that you are ready to do so. The operation continues through Phases 1 through 4 (see SWAP Phases) and then waits, copying updated tracks as required, until you confirm that the operation is to be completed, by using the FDRPAS ISPF panels (see FDRPAS ISPF Interface) or a MONITOR TYPE=CONFIRMSWAP or CONFIRMSPLIT job (see MONITOR CONFIRM Statement). With SWAPDUMP, CONFIRMSPLIT=YES can be used to continue updating the duplicate volume until you are ready to create the point-in-time backup.

Default: NO.

CONFIRMSPLIT=YES and CONFIRMSWAP=YES do not result in any console message or WTOR when the volumes are ready for the swap or split to complete. You can only tell when the volumes are in this state by using the FDRPAS ISPF panels, and you can confirm the operation only by using the ISPF panels or the MONITOR TYPE=CONFIRMSWAP or CONFIRMSPLIT statement.

CONFMESS=

CM=

YES

Before beginning the swap, FDRPAS requests confirmation via FDRW01 message that must be replied to before the swap can start. The FDRW01 can be issued as a WTOR to the system operator (see WTOR=) or you can reply to this message from the FDRPAS ISPF panels.

NO

Suppresses the WTOR and begins the swap immediately.

Default: NO.

CPYVOLID=

CPY=

COPYVOLID=

Specifies whether the volume label of the target DASD volume in a SWAPDUMP or the source volume of a SWAP should be marked valid. Normally, it is marked as invalid, so that the volume cannot come online and cause problems because it has a duplicate volume serial.

YES

The volume label of the target volume of a SWAPDUMP or the source volume of a SWAP is set to “VOL1” so that it can be brought online.

Default: The volume label of the target volume of a SWAPDUMP or the source volume of a SWAP is set to “FDR3” so that it cannot be brought online.

EMSG=

EMAILMSG=

When the FDR e-mail notification facility has been invoked by including an FDREMAIL DD statement in the FDRPAS execution JCL, EMSG= is used to modify the conditions when an e-mail is sent. The parameter is a list of 3-digit FDR message numbers in parenthesis, and may also include the keyword “OK”. The parenthesis can be omitted if only one parameter is specified. Examples:

EMSG=123
EMSG=(123,456)
EMSG=(OK,123,456,789)
EMSG=OK

OK

E-mail notifications are sent for successful SWAP and SWAPDUMP operations as well as failures. Note that this generates a separate e-mail for every DASD volume processed by FDRPAS, which could result in many messages.

nnn

E-mailed messages include message FDRnnn (if it is issued). FDRPAS has a fixed set of such messages (FDR302, FDR316, FDR319, FDR234, and FDR997), EMSG=nnn adds to the list. Note that EMSG=999 generates a single message for the whole FDRPAS step if the FDR999 (successful) message is issued; separate messages for failed swaps are still sent.

Default: E-mail notifications are sent only for SWAP and SWAPDUMP failures.

KEEPACTIVE=

REPEAT

After processing each volume, SWAPDUMP does not remove the I/O intercepts, but leaves them installed to continue to monitor updates. On remote operations and large scale synchronized migrations, it is expected that KEEPACTIVE=REPEAT will be specified, so that all of the SWAPDUMPs can be completed in a synchronized manner. After processing all of the volumes specified by MOUNT commands, SWAPDUMP does not terminate, but waits for 30 seconds and then process all of the volumes again. The first cycle through all of the volumes is the initial copy cycle, and may take a long time if there are many volumes. Later cycles only recopy updated tracks, and are much shorter. The process continues until a MODIFY jobname,KEEPACTIVE=DONE console command is issued. This command may be issued manually when the installation is ready to complete the migration, or it may be issued automatically by a MONITOR TYPE=KEEPACTIVE job. When KEEPACTIVE=DONE is issued, SWAPDUMP terminates the current cycle after the copy of the currently active volumes, performs one final cycle, and completes the operation for all of the volumes.

NO

FDRPAS completes the operation for each source volume as soon as the source and target devices are in synchronization, without waiting for any confirmation.

KEEPACTIVE=NO can be used as a cleanup function if a KEEPACTIVE=REPEAT operation is terminated by a failure or by a STOP(P) or CANCEL(C) command, leaving the I/O intercepts installed, and for some reason it is not desired to resume the operation. With KEEPACTIVE=NO, FDRPAS performs one cycle through all of the volumes, completes the operation, and deinstalls the I/O intercepts.

Default: NO.

LABEL=

NOSWAP

On a SWAP process, the volume serial of the source volume is unchanged (unless CHANGEVOL= is specified on the MOUNT command), and the volume label identifier of the source volume is set to a special FDRPAS designation so that the volume cannot be brought online. On a SWAPDUMP process, the volume serial of the target volume is copied from the source volume, and the volume label identifier of the target volume is set to a special FDRPAS designation so that the volume cannot be brought online.

SWAP

On a SWAP process, the volume labels of the target and source volumes are interchanged. On a SWAPDUMP process, the volume label of the target volume is retained.

• For a successful SWAP process:
  • If the target volume had a valid volume label before the SWAP process, that volume label is copied to the source volume. A valid volume label is a label that contains “VOL1” or “RSV1” in the volume label identifier field. “RSV1” indicates that the volume was initialized by the ICKDSF INIT command with the RESERVED operand. As a result, the volume serial of the source volume is copied from the target volume, unless CHANGEVOL= is specified.
  • The target volume label is copied from the source volume.
• For a successful SWAPDUMP process:
  • The source volume label is unchanged.
  • If the target volume had a valid volume label before the SWAPDUMP process, that volume label is retained.

Default: NOSWAP.

LARGERSIZE=

LS=

NO

The output device must have the same number of data cylinders as the source volume.

OK

The target device may have more data cylinders than the source volume. LARGERSIZE=OK allows you to swap from one model of a DASD volume to a larger model. For example, you can swap from a 3390-3 (3339 cylinders) to a 3390-9 (10017 cylinders). The volume size is updated in the VTOC and VTOCIX (if active), as well as all in-storage tables, when the devices are swapped. However, there is a small chance that the Indexed VTOC may be disabled during the swap; if so; you can use the FDRPAS SWAPBUILDIX utility function (see SWAPBUILDIX and EXPANDVTOC Statement) to rebuild it even while the volume is in use on multiple systems. If the target device is larger than the source, you receive an FDRW66 message with the “OVERRIDE OF WARNINGS” text. FDRPAS invokes ICKDSF to update the volume size.

The conditions where the VTOCIX may be disabled during the swap are:

• FDRPAS calls ICKDSF BUILDIX to rebuild the Indexed VTOC and perform a VIB build (SVC 139). If during the VIB build a data set is allocated, extended, or scratched and the timing is just right, then in some vary rare circumstances the Indexed VTOC may become disabled.
• Since ICKDSF performs a VIB build, we do not expect the Indexed VTOC to become disabled in a sysplex. If volumes are swapped that are not part of the sysplex, then in some rare circumstances the Indexed VTOC could still become disabled.

Default: NO.

LARGESWAP=

nnnnn

Specifies a value slightly larger than the number of volumes being swapped, from 2000 to 16000. The purpose of this operand is to reduce the below-the-line CSA requirements. This operand should only be used on a SWAP or SWAPDUMP of more than 2000 volumes. For example, for 5000 volumes, specify LARGESWAP=6000. When LARGESWAP= specifies a value larger than the number of volumes being swapped, the requirement for below-the-line CSA is no more than 400 KB.

• LARGESWAP= needs to be specified on all of the SWAP and MONITOR tasks running in the same time period.
• This option should only be used with Large Scale Swaps specifying KEEPACTIVE=REPEAT, CONFIRMSPLIT=, or CONFIRMSWAP=.

LOGMESS=

LM=

NO

No SYSLOG/console messages are written.

YES

Messages are written to SYSLOG (and usually to an operator console) documenting that the swap is occurring, and has completed.

Default: YES for the SWAP statement and NO for the SWAPDUMP statement.

MAXACTIVESWAPS=

MAS=

NO

The total number of active SWAP or SWAPDUMP tasks, in multiple FDRPAS jobs, is not limited or controlled. If you submit multiple FDRPAS jobs, each of them may be actively copying data for multiple DASD volumes (up to the MAXTASKS= limit in each job). Many such jobs may overload DASD channels and system common storage. In this case, We recommend that you submit a few such jobs at one time, and submit new jobs as each old job finishes.

YES

FDRPAS limits the number of SWAP or SWAPDUMP tasks in multiple FDRPAS jobs that can be in the initial “Phase 3 pass 1" copy phase, where the tracks identified by FDRPAS as “in-use” are copied. The limit is equal to the value of MAXTASKS= (see MAXTASKS=) or the number of MOUNT statements (whichever is less). If you submit multiple FDRPAS jobs, FDRPAS limits the number of volumes that can be in “pass 1" across all of those jobs to the value specified by MAXTASKS=. This allows you to submit many FDRPAS jobs while limiting the number of volumes that are actively copying data. Beyond “pass 1", FDRPAS periodically copies updated tracks that are a much smaller load on the system.

MAXACTIVESWAPS=YES is especially useful when CONFIRMSWAP=YES or CONFIRMSPLIT=YES is specified, since this usually implies many volumes are in “confirm” state before the operation is finally confirmed and terminated. This allows you to submit the FDRPAS jobs for all those volumes at once knowing that no more than 64 are ever in “pass 1”.

Default: NO.

MAXCARDS=

nnnn

Specifies the maximum number of MOUNT statements that can be present in this FDRPAS step, from 1 to 9999.

Default: 250.

MAXTASKS=

MT=

nnn

Specifies the maximum number of volumes that can be processed concurrently by this SWAP task; from 1 to 100 (from 32 to 100 for SIMSWAPMON). You must follow the SWAP statement with multiple MOUNT statements, specifying the volumes to be processed. If the number of MOUNT statements exceeds the MAXTASKS= specification, FDRPAS starts the indicated number of swaps; as each one finishes another one is started, until all MOUNT statements have been processed. The FDRPAS ISPF panels can be used to terminate active swaps individually.

In order to separate the messages from these swaps, the messages are written to SYSPRINx DD statements (“x” is 1-9, 0, and A-V in that order, depending on MAXTASKS=). If you have not provided these DD statements in the SWAP task JCL, they are dynamically allocated as SYSOUT=*. At the termination of each swap subtask, most of its messages are also written to SYSPRINT so that all FDRPAS messages are in one place.

Default: SIMSWAPMON defaults to its minimum MAXTASKS= value of 32, but a value up to 100 may be specified. For SIMSWAP, SWAP, and SWAPDUMP, the default is that only one volume is processed at a time. If multiple MOUNT statements are provided, they are processed serially. All messages are written only to SYSPRINT. The MAXACTIVESWAPS= operand can be used to coordinate the total number of active SWAP jobs when multiple concurrent SWAP jobs are running.

NONRESPONDING=

If a non-responding system is detected during initialization (usually due to a system where no FDRPAS MONITOR is running), then NONRESPONDING= controls how FDRPAS responds.

FAIL

The swap fails immediately, as if (“NO”) was replied to message FDRW68.

MSG

Message FDRW68 is issued, allowing the user to override the error (“YES”), terminate the swap (“NO”), or retry the missing systems (“RETRY”). See Phase 1: Initialization for details.

RETRY

Message FDRW68 is issued, allowing the user only to terminate the swap (“NO”) or retry the missing systems (“RETRY”). See Phase 1: Initialization for details.

Default: RETRY, unless a different default has been set for the global option NONRESPONDING, as described in FDRPAS and FDRERASE Options (Panel A.I.4.14).

NORA=

nn

Specifies the number of restart areas that are created from 17 to 48.

Default: 17.

NOTIFYERR=

userid

Specifies a TSO user ID. Error messages from FDRPAS are sent to that user ID using the SEND command, for immediate notification of problems in FDRPAS execution. If the TSO user is logged on to the same LPAR as the FDRPAS SWAP task, the messages appear as soon as the user presses Enter. On another LPAR, the user must use the LISTBC command to view them, or they are displayed when the user next logs on.

Default: No TSO notification.

PACEDELAY=

PD=

nnnnn

Specifies the number of hundredths of a second (1-32767) that FDRPAS waits between WRITE I/Os on the target device, in order to minimize the impact of the background copy operation on other applications (each copy I/O copies up to 15 tracks of source data). In most cases, a value between 1 and 20 should be sufficient. PACEDELAY can be dynamically modified for a specific volume from the FDRPAS ISPF panels, see FDRPAS ISPF Interface. If PACING=DYNAMIC is also specified, the PACEDELAY= value is used as the initial pacing delay, and FDRPAS adjusts it dynamically.

Default: 0 (no pacing delay).

PACING=

DYNAMIC

FDRPAS uses an algorithm to gauge the impact of its I/O's on I/O queue length and I/O delay for other tasks on the source volume. Every 15 seconds FDRPAS may adjust the PACEDELAY= value in use depending on recent results. If PACEDELAY= is also specified, that is used as the initial value; otherwise FDRPAS determines the initial value when the swap starts. If possible, run the swap on the system with the highest level of update activity for the volume when dynamic pacing is used.

STATIC

Static I/O pacing is used for FDRPAS I/O. If PACEDELAY= is also specified, FDRPAS inserts the indicated time delay between each write to the target device. The PACEDELAY value can be displayed and interactively modified from the FDRPAS ISPF panels.

Default: STATIC. If PACEDELAY=0 is specified or defaulted, no I/O pacing is done (unless modified from the ISPF panel during the swap).

PAGE=

DRAIN

Allows swapping a volume that contains an active local page data set. This keyword instructs FDRPAS to internally issue z/OS PAGEDEL and PAGEADD commands.

NO

Attempts to SWAP a volume that contains an active local page data set result in an FDR234 error message with REASON=P.

Default: NO.

PRINT=

PR=

ALL

Requests additional printout from the SWAP task, including a list of all data sets on the source volume, and a detailed list of the tracks copied in each phase.

PRTDEFAULTS

If specified, the PRTDEFAULTS operand lists the defaults for various operands that affect FDRPAS operation. If overriding operands are present before the PRTDEFAULTS operand, it displays those overrides. Overriding operands that follow the PRTDEFAULTS operand are not displayed.

SRVCLASS=

Allows you to override the service class assigned to the SWAP job by Workload Manager (WLM).

classname

The desired service class.

HIGHEST>

(Note the 8th character is a “greater than” sign.) Set the service class to the same class as the address space with the highest dispatching priority in the system that is X'F8' (248) or less, and that has a single performance period.

NULL

Do not change the service class assigned by WLM.

If SRVCLASS= is not specified, the default for MONITOR is as follows:

• If the service class assigned by WLM gives a dispatching priority of X'F0'(240) or higher, MONITOR does not change it.
• If the service class assigned by WLM gives a dispatching priority lower than X'F0' (240):
  • Set the service class to PRDBATHI.
  • If class PRDBATHI is not defined, take the action described for SRVCLASS=HIGHEST>.

STGADMIN

If specified, FDRPAS checks to see if the user ID under which it is running is authorized to security class FACILITY profile name STGADMIN.ADR.STGADMIN.DUMP. If so, all security checks are bypassed for all FDRPAS operations, including system allocation and catalog functions. Using STGADMIN allows FDRPAS to move all DASD volumes without needing any additional security.

Default: FDRPAS does normal security checks including system allocation and catalog security. The user id under which FDRPAS runs is authorized to move any data set, but has no authority to those data sets outside of FDRPAS. The security system overhead may be significant if many data sets are involved.

STOPAFTER=

mmmmm

Specifies a number of minutes, from 1 to 65535. This operand should only be used with KEEPACTIVE=REPEAT. If FDRPAS has not completed the initial copy pass of all of the volumes specified by MOUNT commands within this time period, then it will not begin new volumes within this cycle, but bypasses them with message FDR266. The volumes that are currently in progress will continue. When they complete, FDRPAS starts over from the beginning of the list of volumes. Since the earlier volumes have now completed the initial copy pass, they should complete much more quickly, allowing FDRPAS to reach the end of the list within the STOPAFTER period. It is also possible for STOPAFTER to take effect after the initial copy pass if update activity is very high.

The purpose is to limit the amount of memory needed for track update tables for earlier volumes.

Values higher than about 2800 are liable to cause failures, since there is a limit of 48 hours for how long a volume can go without a new pass being started.

If KEEPACTIVE=REPEAT and STOPAFTER= are both specified, STOPAFTER= must be specified after KEEPACTIVE=REPEAT to be honored.

Default: 1440 (24 hours).

SWAPDELAY=

SWD=

nnn

Specifies the interval in seconds (1-255) that FDRPAS waits between checks to see if all the system images have indicated that they are ready to swap the volume. FDRPAS makes this check up to 30 times; if all expected systems have not joined in the swap by the 30th check, FDRPAS terminates the swap. This may indicate that an FDRPAS MONITOR task was not monitoring the target volume on every system. The value specified should be three or more times the value specified for SWAPDELAY= on the MONITOR statement in the MONITOR task.

Default: 15 seconds (the default on the MONITOR statement is five seconds). The default should be adequate unless you have a large number of systems that participate in the swap process; in that case more time may be required for all systems to join.

SWAPID=

This operand is required (except under GENSWAP) when more than one SWAPDUMP or SIMSWAPMON job using just in time monitors is to run at the same time. FDRPAS uses the SWAPID value to relate each SWAPDUMP or SIMSWAPMON job to its associated monitors. Without SWAPID, a SWAPDUMP or SIMSWAPMON job does not submit a just in time monitor to an LPAR where a monitor is already running. With SWAPID, the SWAPDUMP or SIMSWAPMON job submits the just in time monitor to an LPAR unless a monitor with a matching SWAPID is already running there.

nnn

Specifies a number from 1 to 255. Do not use 64; if 64 is specified, it is treated as 65. Each SWAPDUMP or SIMSWAPMON job that is to run at the same time must specify a different value.

Default: None. SWAPID is not needed when only one SWAPDUMP or SIMSWAPMON job runs at a time.

SWAPIOERR=

RETRY

An I/O error on the target device while copying tracks causes the swap to stop the copy and retry the I/O error every five seconds until it is successful or until the swap is terminated (by the ABORT command on the FDRPAS ISPF panels or a console CANCEL(C) command). SWAPIOERR=RETRY allows a swap to recover and continue when the target device has an error that can be corrected. It is intended for use when the target device is connected over a channel extender; if the remote link is interrupted and later recovered, FDRPAS automatically waits for the repair and continue.
When the first such I/O error occurs, FDRPAS puts a non-scrollable message FDR210 on the console to document that it is in the retry loop. IBM I/O error messages are suppressed for the retry I/Os so they appear only for the original error. Message FDR210 appears again when the error is successfully corrected.

NORETRY

An I/O error on the target device while copying tracks immediately terminates the swap. If the I/O error is later corrected, the swap must be restarted.

Default: NORETRY.

TRKTAB=

Do not specify TRKTAB=OLD unless recommended by INNOVATION.

The track table is an area in ECSA (common memory above the 16 MB line) where FDRPAS keeps a record of tracks that have been updated since the beginning of the run or since the end of the previous copy or update pass. The track table for a given volume is fully or partially obtained the first time the volume is updated after the beginning of a run or after the end of the previous copy or update pass, and is freed at the end of each copy or update pass.

NEW

The track table is a variable size that depends on update activity. Only 4 KB is obtained at a time.

OLD

The track table is a fixed size of 1 KB plus 2 times the number of data cylinders on the volume. When the volume is updated, the full size of the track table is obtained. This may be very large, especially for EAVs.

If KEEPACTIVE=REPEAT and TRKTAB= are both specified, TRKTAB= must be specified after KEEPACTIVE=REPEAT to be honored.

Default: With KEEPACTIVE=REPEAT, the default is TRKTAB=NEW; otherwise the default is TRKTAB=OLD.

VOLSORT=

NO

FDRPAS selects the source volumes in the reverse order that the UCBs appear on the UCB chain, which usually means descending order by device number.

YES

Causes FDRPAS to sort the source volumes by the last digit of the device number (unit address). In most installations, this has the effect of spreading out the SWAP tasks across the LCUs.

Default: NO. FDRPAS selects the source volumes in the reverse order that the UCBs appear on the UCB chain.

WTOR=

NO

The FDRW01 and FDRW68 messages are issued as WTO messages, not WTOR messages, so that the operator cannot reply to them. The MSG option of the FDRPAS ISPF panels must be used to reply to these messages (see FDRPAS ISPF Interface). WTOR=NO may be appropriate when the system operator is not involved in the FDRPAS swaps, so that inappropriate responses are not made by the operator.

YES

Certain FDRPAS messages requiring a response are issued as WTOR messages so that the system operator can reply to the messages. These messages currently include FDRW01, issued only if CONFMESS=YES is specified, and FDRW68, issued for various error conditions. Replies to these messages can be made by the system operator, or by the MSG option of the FDRPAS ISPF panels.

Default: YES.