FDRPAS and FDRERASE options (panel A.I.4.14)

Panel A.I.4.14 – Set FDRPAS & FDRERASE Options

Set FDRPAS & FDRERASE Options – Panel A.I.4.14

PASPROC

FDRPAS requires that you install a cataloged procedure (PROC) for FDRPAS in an appropriate JES procedure library. This PROC is used when an FDRPAS MONITOR task has to dynamically invoke another MONITOR task to handle the swap of a specific volume. It can also be used in user-created FDRPAS batch jobs and to start FDRPAS started procedures from the console with START(S) commands.

The default procedure name is PASPROC. If you install this procedure with a different name, you must change it here.

The model for this procedure is found in the FDRPAS Installation Control Library (ICL) under member name PASPROC. It looks like:

//PASPROC PROC PROG=FDRPAS,
// LIB=library, <= FDRPAS PROGRAM LIBRARY
// EMAIL=NULLFILE, EMAIL STATEMENT INPUT DATA SET
// IN=NULLFILE, FDRPAS STATEMENT INPUT DATA SET
// OUT='SYSOUT=X', FDRPAS SYSOUT
// D=SHR INPUT DATA SET DISPOSITION
//PAS EXEC PGM=&PROG,REGION=0M
//**************************************************************
//* FDR PLUG AND SWAP *
//**************************************************************
//STEPLIB DD DISP=SHR,DSN=&LIB
//SYSPRINT DD &OUT
//FDRSUMM DD &OUT
//SYSUDUMP DD &OUT
//FDREMAIL DD DSN=&EMAIL,DISP=SHR
//SYSIN DD DSN=&IN,DISP=&D

You must change the value of the LIB parameter to the FDRPAS load library you specified during installation. If SYSOUT class X is not a held class in your system, you may want to change it to a held class.

If you have restricted access to the FDRPAS program library or enabled the FDRPAS ALLCALL security option, you may need to assign an appropriate security user id to started tasks that use PASPROC. Consult the documentation for your security product for details.

PASINDEX

FDRPAS uses the PASINDEX value as the high-level index of data set names it catalogs to create history records for FDRPAS SWAP operations. Only catalog entries are created with this name; FDRPAS does not create any real data sets using this high-level index. This name should be defined in the master catalog of every system on which FDRPAS runs, as an alias of a user catalog into which these FDRPAS catalog entries are placed. If possible, this user catalog should be a shared catalog accessible to every system, but if this is not possible, it can point to different user catalogs on different systems.

The FDRPAS SWAP and MONITOR tasks must have authority to catalog data sets beginning with the PASINDEX into the aliased user catalog. If they do not, the history records are not created but the swaps run successfully.

Do not assign PASINDEX to a user catalog with a lot of activity. Every SWAP and MONITOR task attempts to catalog into that catalog when a swap ends, there are catalog updates from multiple systems in a very short period of time. Depending on the type of catalog sharing and caching in use, this can cause other catalog requests to be delayed and may cause FDRPAS to be delayed. If desired, you can DEFINE a new user catalog for the PASINDEX.

You may change PASINDEX to any valid high-level index.

Here is an example of the IDCAMS input necessary to assign FDRPAS (or whatever value you assign to PASINDEX) as an alias of an existing ICF catalog (the IDCAMS job must be authorized to update the master catalog):

If you do not assign a catalog alias for the PASINDEX, a diagnostic message FDR247 is generated when FDRPAS tries to catalog the history record, although this is not considered an error and does not cause a non-zero return code. However, if you wish to avoid the message, change PASINDEX to “#BYPASS” (customers outside the US: replace the # character with whatever character generates hex value X'7B').

NONRESPONDING

This option controls whether replies are allowed to be specified at the console for the FDRW68 message “FDRPAS MONITOR FAILED TO RESPOND”. The valid values are:

MSG

Allows all replies.

FAIL

Allows no replies.

RETRY

Allows replies of “RETRY” or “NO”.

Default: RETRY.

CHKTARGNO

This option controls whether CHECKTARGET=NO is accepted on an FDRERASE main statement.

NO

Does not accept CHECKTARGET=NO that allows you to erase volumes that are not empty or that have a valid volume label (such as the source DASD of a successful FDRPAS swap). This can be used to ensure that volumes containing data that you need are not inadvertently erased. If you specify the CHECKTARGET=NO option, it results in message FDR302 REASON=I when CHKTARGNO is set to NO.

YES

Accepts CHECKTARGET=NO that allows you to erase any volume, even though it contains data sets and valid volume label.

Default: YES.

If you set CHKTARGNO to NO, and you plan to use FDRERASE to erase your data from DR DASD after a Disaster Recovery test (or a real disaster), you need to reset the option to YES and specify CHECKTARGET=NO to do so, since those DASD volumes will not be empty.