Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Duplicating FDDRL backup volumes with PERCON

Backup MTCs generated by means of FDDRL can be logically copied with the aid of the software product PERCON (see also the “PERCON” manual [11]). Only users with the TSOS privilege can copy FDDRL tapes.

Any PERCON version can be used. When you copy FDDRL files, you can also reset the expiration date to protect the volume from being overwritten.

The internal structure of the backup volumes is not affected. The result of a subsequent restoration run is the same regardless of whether the original backup MTCs or those generated by PERCON are specified in the RELOAD-DISK statement.

Assigning a TASKLIB

FDDRL backup MTCs include certain user labels (UHL, UTL). The special processing routines NDRLEIN and NDRLEOUT are provided in the FDDRL module library (logical name SYSLNK, see also chapter "Scope of supply of FDDRL") to enable the user labels to be transferred correctly to the output volumes when the backup MTCs are copied with the aid of PERCON. This library must be defined as TASKLIB before PERCON is called:

/SET-TASKLIB LIBRARY=SYSLNK.FDDRL.210

If it is certain that only one input volume and one output volume have to be assigned, TASKLIB assignment is not necessary. In this case, the backup MTCs can be copied without processing routines. However, it is always safer to duplicate the backup MTCs with a TASKLIB assignment (as shown in the example below ).

Name of the output file

FDDRL saves a disk to a series of tapes. It produces a tape file whose name begins with the string “FDDRL“. A check is made for this string when the contents of a disk are restored. For this reason the name of the output file specified for copying with PERCON must begin with this string.

See also the description of PERCON in the “PERCON” manual [11].


Example

Converting an FDDRL save from MTC (TAPE-C2) to MTC (TAPE-C4)

/ SET-TASKLIB - 
/     LIBRARY=SYSLNK.FDDRL.210
--(1)
/ IMPORT-FILE -
/    SUPPORT=*TAPE
/       (FILE-NAME=FDDRL.D.DISK01, -
/        VOLUME=(TAP001,TAP002,TAP003), -
/        DEVICE-TYPE=TAPE-C2)
/ ADD-FILE-LINK -
/    LINK-NAME=PCIN, -
/    FILE-NAME=FDDRL.D.DISK01, -
/    ACCESS-METHOD=*BTAM

-+(2)
 |
 |
 |
 |
 |
 |
 |
-+(2)

/ CREATE-FILE -
/    FILE-NAME=PCOUT, -
/    SUPPORT=*TAPE -
/        (VOLUME=(CAS001,CAS002), -
/         DEVICE-TYPE=TAPE-C4))
/ ADD-FILE-LINK -
/    LINK-NAME=PCOUT, -
/    FILE-NAME=FDDRL.D.DISK01.COPY, -
/    ,RETENTION-PERIOD=365
-+(3)
 |
 |
 |
 |
 |
 |
 |
-+(3)
/ START-PERCON --(4)

//ASSIGN-INPUT-FILE -
//   FILE=*TAPE-FILE(NAME=*STD, -
//         LABEL-EXIT=*MODULE -
//         (NDRLEIN,CONTROLLED-LABEL=(HDR,EOV,END))
//ASSIGN-OUTPUT-FILE -
//   FILE=*TAPE-FILE(NAME=*STD, -
//         FILE-ATTRIBUTES=*INPUT-FILE, -
//         LABEL-EXIT=*MODULE -
//         (NAME=NDRLEOUT,CONTROLLED-LABEL=(HDR,EOV,END)))

-+(5)
 |
 |
 |
 |
 |
 |
 |
-+(5)
//END    --(6)

(1)

The object module library (OML) for dynamic loading is assigned as TASKLIB.

(2)

The input file is defined.

(3)

The output file is defined. The output MTCs are to be protected against overwriting for 365 days.

(4)

PERCON is called via START-PERCON.

(5)

PERCON statements are used to assign the input and output files.

(6)

END initiates data transfer.

Notes

  • Once the copying has been successfully completed, the volume entries in MAREN can be adjusted (see chapter "Adjusting volume characteristics of PERCON copies").

  • PERCON copies of FDDRL save entities which used more than one input or output volume per disk or disk set can only be reloaded later if the label exits were activated in the PERCON run (see example).

  • The version of the TASKLIB used should be higher than or equal to the FDDRL version used in DUMP-DISK or DUMP-PUBSET.

  • FDDRL backup MTCs which have been copied in this way can also be reloaded if the number or type of output MTCs differs from the number or type of input MTCs or if the MTCs contain compressed backup data.

  • The name of the output file must begin with “FDDRL.“, otherwise the tapes will not be recognized as FDDRL tapes in the case of RELOAD function.

  • In the copy of a pubset save with multiple disk sets, a uniform name with correctly assigned disk set numbers must be created as a suffix for all the tape sets (see statement, "RELOAD-PUBSET Restore a pubset").