LIB/CCF Model System › Suggested Procedure for Emergency Changes

Suggested Procedure for Emergency Changes

We recommend that your site set up a procedure for emergency changes.

Define an application called EMERGENCY (or use a name of your own choosing). Designate your key operations authority as manager of this application, as the programmer reporting to himself, and define that person’s user ID as the emergency key. You can then use the EMERGENCY application for opening and closing emergency change requests to provide a record of such changes.

To designate a user key as the emergency key, perform the following steps:

1. In the System Profile Table (12.0), assign the keyword EMERID (for TSO and VM/ESA) or EMERKEY (for CA Roscoe and AllFusion CA‑Vollie) to a user ID.
2. In the User Definition Table (12.1), authorize that user ID to the EMERGENCY application. Define a Chain Group that contains a chain for every production master file that the EMERGENCY application can use. It might suffice to define only one test emergency master file for all of the production master files. However, if duplicate member names exist on the various production master files, an attempt to logout a member that is already logged out into the emergency test master file fails. Additionally, if your site uses QA libraries, you must decide whether you want to define them in the emergency chains.
3. In the Managers Definition Table (12.2), designate the emergency user ID as the manager of the EMERGENCY application with the emergency Chain Group.
4. In the Programmer Definition Table (12.3), designate the emergency user ID as a programmer and as a manager of itself.

You can define more than one emergency application and more than one user ID or key as an emergency key, if necessary. Whoever is defined as having the emergency user ID is automatically granted:

• Multiple logout privileges (regardless of the ALLOWMULT specification in Option 12.0). Multiple logout privileges let the emergency ID log out a member that was already logged out. (See the following section for information of multiple logouts.)
• Control group privileges, which let the emergency ID process login and link-edit requests.

The emergency ID can then open an emergency change request, assign the change request to himself, log out the member, fix it, log it in, do the link, and close the change request.