Previous Topic: Lock SecurityNext Topic: The Browse Option


Introduction

In addition to preauthorizing users and CCIDs, security measures can be taken one step further using a level of control called lock. The lock function is used to prevent use of an CA Endevor/DB userid or CCID, and/or to prevent a dictionary from being updated. Lock is a temporary condition; when you want to allow access again, you simply unlock the entity.

You can lock:

This chapter provides a step-by-step approach to locking and unlocking users, CCIDs, and the dictionary.

Lock processing begins when you select option 3 from the Main Function Menu:

CA-E/DB nn.n volser MAIN FUNCTION MENU mm/dd/yy NDVRU000 USER ===> EDBADMIN DICTNAME ===> SRCNDVR MODE ===> UPDATE OPTION ===> 3 1 - SIGNIN/SIGNOUT FUNCTIONS 2 - AUTHORIZATION FUNCTIONS 3 - LOCK FUNCTIONS 4 - ENTITY AND ENTITY CHANGE HISTORY 5 - CCID AND CCID CHANGE HISTORY 6 - STATUS AND STATUS ASSOCIATIONS 7 - USER AND USER CHANGE HISTORY 8 - DICTIONARY AND DICTIONARY HISTORY 9 - MANAGEMENT GROUPS AND CCIDS 10 - ENDEVOR/DB CONTROL FUNCTIONS 11 - ENDEVOR/DB SIGNON FUNCTION 12 - RETURN TO IDMS/DC

The system returns the Lock/Unlock Functions menu below:

CA-E/DB nn.n volser LOCK/UNLOCK FUNCTIONS mm/dd/yy NDVRU300 USER ===> EDBADMIN DICTNAME ===> SRCNDVR MODE ===> UPDATE OPTION ===> 1 - BROWSE LOCKED USERS 2 - LOCK USERS 3 - UNLOCK USERS 4 - BROWSE LOCKED CCIDS 5 - LOCK CCIDS 6 - UNLOCK CCIDS 7 - BROWSE LOCKED DICTIONARIES 8 - LOCK DICTIONARIES 9 - UNLOCK DICTIONARIES USER ===> (IF OPTIONS 1, 2, 3 ) CCID ===> (IF OPTIONS 4, 5, 6 ) DICTIONARY ===> SRCNDVR (IF OPTIONS 7, 8, 9 )

The remainder of this chapter discusses the three options and related procedures used in LOCK processing. Read the section(s) appropriate to your needs.