Testing and implementing CA Disk functions that make use of a data set's last used date (for example, archival), or perhaps its last modified date (for example, special backup option), requires some special consideration if the CA Disk SVC (or MVS SU 60) has not been installed long enough to have these fields properly updated on all data sets.
The first option is to simply wait an appropriate period before implementing a dependent function. The second is to use the DSCB Update Utility (see the DSCB Update Utility section) to initialize these fields to an appropriate starting value. The third is to use the following sysparms for testing, and then follow either option one or two.
Sysparms DSCBLUSD and DSCBLMOD normally provide the decimal offset into the format-1 DSCB where the last used and last modified dates are being recorded. For testing, however, you specify them with an offset of either the creation date (decimal offset 53) or the expiration date (decimal offset 56). For your test purposes, these values cause CA Disk to treat the creation date (or expiration date) as the last used and last modified dates as well. In the example here, the sysparms have been specified with the offset of the creation date:
DSCBLUSD053 DSCBLMOD053
Note: Be sure to remove these entries after the CA Disk SVC or SU 60 has been active long enough to have recorded proper values. Be sure that you do not have these testing values set if you execute the DSCB Update Utility to initialize the fields.
If a local modification to OPEN is already being used to record either or both of these fields in the DSCB, the sysparm entries can be used to direct CA Disk to the fields maintained by your own local modification. See the descriptions of these system parameters in the Systems Guide.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|