Previous Topic: Assigning Status Privileges Through PreauthorizationNext Topic: Lock Security


Preparing for Derived CCID Processing

When using DERIVED-CCID processing, the CCID(s) associated with a change are determined when the change is made to an entity. The DERIVED CCID processing allows a user to associate changes to one or more CCIDs without the user having to signon to CA Endevor/DB with the CCID(s). To turn on DERIVED CCID processing, the dictionary's and user's security class must specify DE-CCID = Y. If they are not, DERIVED CCID processing is not active. In addition, entities are preauthorized to the derived CCIDs with the DE-CCID flag set to Y.

To accomplish this, you can either use the Online front end or the Batch front end. In Batch, you would use the ADD PREAUTHORIZATION and the MODIFY SECURITY CLASS commands. The Batch commands to set up CCID EDB-QA as a derived CCID for all entities whose name begins with "DEPT" and to assign derived CCID processing for all security classes would be as follows:

ADD PREAUTHORIZATION ENTITY NAME = DEPT*
TO CCID EDB-QA DERIVE CCID = Y.
MOD SECURITY CLASS = * DERIVE CCID = Y.

To accomplish this through the Online front end, perform the following:

  1. Select option 2 on the Pre-authorization Functions menu (2-ADD PREAUTHORIZATIONS). Next, specify the entities to which the CCID EDB-QA is to be preauthorized.

    CA-E/DB nn.n volser PRE-AUTHORIZATION FUNCTIONS mm/dd/yy NDVRU200 USER ===> EDBADMIN DICTNAME ===> SRCNDVR MODE ===> UPDATE OPTION ===> 2 1 - BROWSE PRE-AUTHORIZATIONS 2 - ADD PRE-AUTHORIZATIONS 3 - DELETE PRE-AUTHORIZATIONS 4 - MODIFY PRE-AUTHORIZATIONS ENTITY: (IF OPTIONS 1 - 4 ) NAME ===> DEPT* TYPE ===> VERSION ===> USER ===> (IF OPTIONS 1 - 4 ) CCID ===> EDB-QA (IF OPTIONS 1 - 4 )

    Press ENTER.

    The system responds with a Pre-authorization List screen, which identifies all available entities whose name begins with DEPT. In the following example, all entities (beginning with the characters DEPT) not already preauthorized to CCID EDB-QA have been listed (since the wildcard (*) was specified as part of the ENTITY name qualifier).

  2. Using this screen, you further define the list of entities that are to be preauthorized to this CCID. Select the entities that you wish to preauthorize to the CCID (EDB-QA) by entering any non-blank character to the left of the desired entries. In our example, all entities whose name begins with "DEPT-" have been selected.

    CA-E/DB nn.n volser PRE-AUTHORIZATION LIST mm/dd/yy NDVRU210 USER ===> EDBADMIN DICTNAME ===> SRCNDVR MODE ===> UPDATE ACTION ===> AUTHORIZE USER CCID OUT AUTH DER ENTITY NAME TYP VERS _ N N N DEPTINQ DIA 1 _ N N N DEPTINQ-ENTER PRC 1 _ N N N DEPTINQ-PREMAP PRC 1 _ N N N DEPTMAP LOA 1 _ N N N DEPTMAP MAP 1 s N N N DEPTMAP MOD 1 s N N N DEPTUPD DIA 1 s 001 CCIDS N Y N DEPTUPD-ENTER PRC 1 s 001 CCIDS N Y N DEPTUPD-PREMAP PRC 1 * END *

    Where AUTH is Y, the entity is already preauthorized. Where DER is Y, DERIVE CCID processing is in effect for the preauthorization. Where OUT is Y, the entity is signed-out. The USER and CCID fields indicate the number of USERs and CCIDs to which an entity is preauthorized. In the above example, the last listed entity (DEPTUPD-PREMAP) is preauthorized to one CCID (0001 CCID). For more information, use the Browse Preauthorization function as applied to this entity.

    Note: This screen lists all entities that have not already been preauthorized to CCID EDB-QA. CCID EDB-QA, as specified on the Pre-authorization Functions screen, will reappear on the Pre-authorization Detail screen on the next page.

  3. Press ENTER.

    The system responds with a Pre-authorization Detail screen for each selected entity. A sample detail screen is shown below.

    CA-E/DB nn.n volser PRE-AUTHORIZATION DETAIL mm/dd/yy NDVRM210 USER ===> EDBADMIN DICTNAME ===> SRCNDVR MODE ===> UPDATE ACTION ===> AUTHORIZE *********************** PRE-AUTHORIZATION INFORMATION *********************** DERIVE CCID ===> N SIGNED OUT ===> N PRE-AUTHORIZED ===> N EST. WORK COMPLETION ===> ACT. WORK COMPLETION ===> COMMENT ===> **************************** ENTITY INFORMATION **************************** NAME ===> DEPTUPD VERSION ===> 1 TYPE ===> DIALOG COMMENT ===> **************************** USER INFORMATION **************************** NAME ===> LOCKED ===> SECURITY CLS ===> CURRENT CCID ===> COMMENT ===> **************************** CCID INFORMATION **************************** NAME ===> EDB-QA SECURITY CLASS ===> QA LOCKED ===> N COMMENT ===> EDB PROJECT QA

  4. Within the Pre-authorization Information section of the screen, fill in the appropriate fields to document preauthorization:
  5. Return to the Main Function Menu by pressing CLEAR or PF3.

Note: To preauthorize the same entities to another CCID, follow the same procedure as above. Entities may be preauthorized to single or multiple CCIDs.

Now that you've built the preauthorization list for the CCID EDB-QA, you need to modify the security descriptors for the dictionary descriptor and the users who will be using DERIVED CCID processing. To do this:

  1. Select option 10 (ENDEVOR/DB CONTROL FUNCTIONS) 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 ===> 10 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

  2. Press ENTER.

    The system responds with the CA-ENDEVOR/DB SYSTEM CONTROL FUNCTIONS screen.

  3. Select option 5 (MODIFY SECURITY DESCRIPTORS).

    CA-E/DB nn.n volser CA-ENDEVOR/DB SYSTEM CONTROL FUNCTIONS mm/dd/yy NDVRUA00 USER ===> EDBADMIN DICTNAME ===> SRCNDVR MODE ===> UPDATE OPTION ===> 5 1 - BROWSE CCDB DESCRIPTOR RECORD 2 - MODIFY CCDB DESCRIPTOR RECORD 3 - BROWSE SECURITY DESCRIPTORS 4 - ADD A SECURITY DESCRIPTOR 5 - MODIFY SECURITY DESCRIPTORS 6 - DELETE SECURITY DESCRIPTORS 7 - BROWSE MONITOR DICT STAT BLOCKS 8 - MODIFY MONITOR DICT STAT BLOCKS SECURITY CLASS ===> (IF OPTIONS 3, 4, 5, 6 ) DICTNAME ===> SRCNDVR (IF OPTIONS 7, 8 )

  4. Press ENTER.

    The system then provides a list of all the Security Classes in the database on the SECURITY CLASS LIST screen.

  5. This action changes all security classes to use derived CCID processing. Select all items on the list by typing any non-blank character to the left of each Security Class entry. This lets you "zoom in" on each Security Class in order to set security flags as needed.

    CA-E/DB nn.n volser SECURITY CLASS LIST mm/dd/yy NDVRUA10 USER ===> EDBADMIN DICTNAME ===> SRCNDVR MODE ===> UPDATE ACTION ===> MODIFY SECURITY CLASS COMMENT s DEFAULT-SECURITY SECURITY CLASS FOR RESTRICTED CAPABILITIES s QA SECURITY CLASS FOR QUALITY ASSURRANCE s DEVELOPMENT SECURITY CLASS FOR DEVELOPMENT s SUPPORT SECURITY CLASS FOR TECHNICAL SUPPORT s NDVR-DDA DICTIONARY ADMINISTRATION CAPABILITIES s NDVR-GLOBAL UNIVERSAL ENDEVOR/DB AND DICTIONARY CAPABILITIES ** END **

  6. Press ENTER.

    The system responds with a SECURITY CLASS DETAIL screen for each Security Class selected on the above list.

  7. On the Security Class Detail screen, enter a Y in the DE-CCID field. This will enable DERIVED CCID processing for users and the dictionary descriptors, which have these security classes.

    CA-E/DB nn.n volser SECURITY CLASS DETAIL mm/dd/yy NDVRMA10 USER ===> EDBADMIN DICTNAME ===> SRCNDVR MODE ===> UPDATE ACTION ===> MODIFY ************************** SECURITY CLASS INFORMATION *********************** NAME ===> DEFAULT-SECURITY COMMENT ===> SECURITY CLASS FOR RESTRICTED CAPABILITIES MENU 1 2 3 4 5 6 7 8 9 MENU 1 2 3 4 5 6 7 8 CONTROL: Y N Y N N N Y N SIGNOUT: Y Y Y LOCK: N N N N N N N N N AUTH: Y Y Y N CCID: Y Y Y Y Y Y Y Y Y ENTITY: Y Y Y Y Y Y STATUS: Y Y Y Y Y Y Y Y USER: Y Y Y Y Y Y Y Y M-GRP: Y Y Y Y Y Y Y Y DICT: Y N N Y N N SIGNIN: Y SO-CCID: N SO-USER: Y NO-USER: N NO-CCID: N NO-AUTH: N LIM-AUT: N NM-MODE: Y ARCHIVE: Y MIGRATE: Y DE-CCID: Y BATCH: N ENTITY: SCH DMC FIL TAS SUB USE DES REC SYS APO SET DIA APP ELE QFI PRC TAB FUN MODS: N N N N N Y Y Y Y Y Y Y Y Y Y Y Y Y A-OPT: N N N N N N N N N N N N N N N N N N ENTITY: MOD PHY CLA ATT MAP LOG LIN MSG LOA LR PRO CCD DIC EUS CCI MGR STA SEC MODS: Y N Y Y Y N N N N N Y Y Y Y Y Y Y Y A-OPT: N N N N N N N N N N N N N N N N N N

Note: If the security class for the dictionary descriptor (NDVR-GLOBAL) does not specify DERIVED CCID processing (DE-CCID = Y), DERIVED CCID processing will not be active even if a user's security class in that dictionary specified CCID processing.

By pressing ENTER after each detail screen as it appears, you are building a group of security classes which specify derived CCID processing. Press PF3 to cancel your MODIFY SECURITY CLASS request.