LIB/CCF relies on the management code (MCD) feature of CA Librarian or CA Librarian’s external security interface to provide master file security. This feature allows the assignment of a management code (or MCD) to a master file and a security status (either TEST, PROD0, PROD1 or PROD2) to individual members on the master file. The assignment of the MCD to the master file must be done with a batch CA Librarian job for z/OS and OS/390 or VSE/ESA initialized master files, or with the LIB/CMS LIBMAST command for VM/ESA initialized master files. For details on assigning an MCD and the various security statuses, see the Security Administration Guide.
Once your LIB/CCF master files are assigned an MCD, you must tell LIB/CCF what the MCD base code for each file is and what the status for members in each file should be. For CA Roscoe, VM/ESA, and TSO, use the Library Chain Definition Facility (or LCDF, Option 12.11). For CA Vollie, use the Production Master File Table (Option 12.6), the History Master File Table (Option 12.7) and the Master File Information Table (Option 12.10). Once the MCD is assigned to the master file and the MCD base code and member status are specified to LIB/CCF, LIB/CCF maintains this information and generates the correct MCD and status whenever they are required for member processing.
Your production source master file should be security protected, with a status of PROD1 or PROD2 for the production members. We also recommend that you have security protection for the test master files. You should specify the LOCK status or security status given to a test member on a test master file when the login function is performed as PROD1 or PROD2. In this way, you lock the test member from further changes when it is logged in. The member on the test master remains in TEST status until it is logged in. The status is changed when the login function is requested.
|
Copyright © 2010 CA.
All rights reserved.
|
|