Model APJMPANV is used to process CA‑Panvalet moves. It can generate two different styles of move JCL; one being a series of CA‑Panvalet job steps, the other being a single step move using REXX. The REXX style of move is for compatibility with release 1.3 of CA‑PanAPT. There is no benefit to using this style of move any more unless you are having trouble keeping your number of job steps for a move below the JES maximum of 255, or if you are having GDG problems (described later).
The $G$PV_REXX user keyword is used to specify whether the model generates REXX move JCL (a value of Y) or standard move JCL (a value of N). The default is to generate standard move JCL. If used, set this keyword set in either the APJMLEAD model or the APJMPANV model, not in your Library Code model specifications.
This model uses user keywords to specify whether members are saved on protection files prior to being deleted or replaced. To use a protection file for any CA‑Panvalet library defined in your Library Code, set the keyword 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 named PAYROLL.PROD.PANBKUP for library PAYROLL.PROD.PANLIB and the ddname for PAYROLL.PROD.PANLIB is PAYROLLP, designate the following in your model specifications before including the APJMPANV model:
PF_PAYROLLP = 'PAYROLL.PROD.PANBKUP'
The model also inspects other user keywords to determine what unit the protection file is on, and any other parms that should be specified on the DD statements.
User keyword $G$PV_PFUNIT is used to specify the unit. If not specified, this defaults to TAPE. If used, set this keyword in either the APJMLEAD model or the APJMPANV model, not in your Library Code model specifications. Override the unit for any Library Code by designating the PV_PFUNIT user keyword in its model specifications before including the APJMPANV model.
You can specify miscellaneous DCB information to be used when creating protection files. For the standard move JCL, place this information on a continuation line of the output DD statement. For the REXX move JCL, embed this information within an APTALLOC command to allocate the protection file. APTALLOC is virtually identical to the TSO ALLOCATE command, but is set up to allocate GDG data sets. Typical information you might want to specify are expiration dates or retention periods.
Because the format of the miscellaneous DCB information is different for the standard move JCL than for the REXX move JCL, different user keywords are used to specify the information. This way your Library Codes can be set up to work either way. For the standard move JCL, you can set a default for your Library Code using the PF_TMSPARM user keyword, and override it for a specific protection file using the PF_DDN_TMSPARM user keyword. Substitute DDN with the ddname of the library this protection file is for.
For example, to set a retention period of 30 days for output protection files, you would specify the following:
PF_TMSPARM = 'RETPD=30'
For REXX style move JCL, specify the DCB information using the TMSPARM user variable. There are no means to override it for a specific protection file. For a block size of 32000, specify the following:
TMSPARM = 'BLKSIZE(32000)'
|
Copyright © 2004 CA.
All rights reserved.
|
|