The CMS-level Data Set Protection option is installed in the CMS nucleus as directed by an optional task which is invoked after CP and the server have been built. CMS-level protection functions in a more traditional way by providing security calls during normal data set open processing in CMS’s DOS and OS simulation routines. If CA Top Secret fails the request, the open is not completed, and the user’s program is not able to read or write records to the file.
Because of the design of VM and CMS, however, it is not always necessary to use the simulation routines to access a data set. A more experienced user may, for example, write a program to perform physical I/O (PIOCS) to the device and access the desired information without going through normal system access methods. If, on the other hand, your users are locked into protected applications, this method may be more appropriate. Consider these points, as well as the sensitivity of the data involved, in your selection. If you need absolute data security, you may want to choose CP-level Data Set Protection.
|
Copyright © 2009 CA.
All rights reserved.
|
|