Modeling Facility › Sample Models › Turnover Move Models › CA-PFF Moves

CA-PFF Moves

Model Name: APJMPFF

Usage: Daily Processing Cycle.

Purpose: Move members of CA‑PFF libraries as part of the daily processing cycle (APJJ5310-APJJ5320).

Members of the APTMDLO PDS:

• $OUTDD = APTMDLO
• $OUTMEM =
  • <$OUTPFX>A—backup to destination2 protection file
  • <$OUTPFX>B—transfer from destination1 to destination2
  • <$OUTPFX>C—backup to destination1 protection file
  • <$OUTPFX>D—transfer from original to destination1 (purge included if desired)
  • <$OUTPFX>—contains JCL
• $OUTPOST = <$OUTPFX>#

Note: This is the output member name of the modeling statement $OUTPOST=<$OUTPFX>. The # is not coded on the modeling statement, It is automatically added when the model is processed.

User keywords passed to the model:

ALIAS

Specifies how CA‑PFF is to process aliases on a PDS. Valid values are Y and N.

LIBTYPE

Specifies the type of PDS being processed. This model validates the value for the correct content. Valid values are ",", SOURCE, EXEC, and OBJECT.

Specify each of these parameters in the Library Code definition for every Library Code that uses the model. For example, use the following specification:

ALIAS='N'; LIBTYPE= ''; INCLUDE APJMPFF

Output: Several members are built in the model output library, APTMDLO. These members contain control statements that govern the members' movement for one step of the complete move procedure. The MOVEJCL member is the driver which includes the customized JCL in the <$OUTPFX> member on APTMDLO. That member does the actual move.

Processing Overview:

Moves are done in several stages depending on the number of library levels, the following is true for all:

• First, all members whose Library Codes require the use of a Backup Library are moved from the destination1 library to the destination2 or Backup Library.
• Second, members are moved between the originating library and the destination1 or target library. The following are possible moves:
  • From a lower level to a higher target level
  • From the current level to its backout library
• Third, all members that must be deleted (according to Library Code definitions) are deleted. This step is part of the copy/purge step.

The same model (APJMPFF) is used to process CA‑PFF moves with protection files and without them. Protection files must be specified in the library code specification before the model is included in order to alert CA‑PanAPT to their existence. To use a protection file for any CA‑PFF type move, set the variable PF_DDN to the data set name of the protection file, excluding the GDG generation reference at the end of the name. Substitute DDN with the ddname of the library this protection file is for. For example, if you want to use a protection file name, PAYROLL.PROD.PFFBKUP for library PAYROLL.PROD.PFFLIB and the ddname for the latter is PFF$P$P, designate the following in the library code specification:

PF_PFF$P$P='PAYROLL.PROD.PFFBKUP;
 ALIAS='N'; LIBTYPE= ''; INCLUDE APJMPFF