Dataset protection ensures that a dataset currently in use by a MUF or DBUTLTY cannot be used in a contrary way by another DBUTLTY or MUF. It ensures that a dataset being created by DBUTLTY cannot be used by a MUF or other DBUTLTY until the creation process completes.
Dataset protection is provided in two layers.
ENQ is provided to protect datasets within CA Datacom processing for Version 14.0 and later releases.
It uses the z/OS Global Resource Serialization (GRS) facility to ENQ across the systems to ensure a dataset can be used for the intended purpose.
With this layer of protection, any protection of the CXX, LXX, or FXX lasts for the entire job step. Any protection for database data sets for the index or data areas lasts just for the specific DBUTLTY function having the requirement. The temporary condition is valid if the datasets are dynamically allocated, and not provided as JCL DD statements.
DISPOLD is provided to protect datasets within CA Datacom processing for all releases and also outside CA Datacom processing. It provides similar protection to Layer 1.
With this layer of protection, any protection of the CXX, LXX, or FXX, lasts for the entire job step. Any protection for database datasets for the index or data areas lasts just for the specific DBUTLTY function having the requirement. An exception exists if the specific dataset name protected is referenced in a subsequent step of the job. The protection is extended by the operating system to include the remainder of the step where acquired through all the succeeding steps and through the step where it is last specified. Layer 2 is very important protection but it can be disabled in individual JCL streams or completely as an option in the DBSIDPR member being used.
For more information, see the CA Datacom/DB Database and System Administration Guide.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|