If you are using the CA‑Panvalet lock facility, it is necessary to unlock members being replaced in the move job before they are removed. If you are running version 14.1 of CA‑Panvalet, the PAN#1 program is used to unlock members; if you are running a higher version, the PAN#2 program is used (lock does not apply to earlier versions of CA‑Panvalet). You must specify the version of CA‑Panvalet you are running by setting the $G$PV_VERSION user keyword in either the APJMLEAD or APJMPANV model. If you do not specify anything, the default is version 14.2, which is satisfactory for either version 14.2 or 14.3 of CA‑Panvalet.
If you are generating REXX style move JCL, the REXX procedure examines the CA‑Panvalet library and automatically performs an unlock of any locked members. If you are generating the standard move JCL, you must specify to the model whether or not there might be any locked members. Additional job steps can be generated to unlock these members. The $G$PV_LOCK user keyword can be set to either Y or N to designate a system‑wide default. Specify this keyword in either the APJMLEAD or APJMPANV model. If it is not specified, it defaults to N, meaning no unlocks are performed. Override this in any Library Code by specifying the LOCK user keyword in the model specifications before including the APJMPANV model.
Sample Model Specifications, standard JCL and Protection Files:
PF_PAYROLLT = 'PAYROLL.TEST.PANBKUP'
PF_PAYROLLQ = 'PAYROLL.QA.PANBKUP'
PF_PAYROLLP = 'PAYROLL.PROD.PANBKUP'
PF_TMSPARM = 'DCB=BLKSIZE=32000'
INCLUDE APJMPANV
Sample Model Specifications, REXX JCL and Protection Files:
PF_PAYROLLT = 'PAYROLL.TEST.PANBKUP'
PF_PAYROLLQ = 'PAYROLL.QA.PANBKUP'
PF_PAYROLLP = 'PAYROLL.PROD.PANBKUP'
TMSPARM = 'BLKSIZE(32000)'
INCLUDE APJMPANV
Sample Model Specifications, standard or REXX JCL with no Protection Files:
INCLUDE APJMPANV
|
Copyright © 2004 CA.
All rights reserved.
|
|