If Signon CCIDs are used, these are the CCIDs under which you are processing. Displayed initially as the CCIDs for the user shown above, as of the last successful CA Endevor/DB Signon (if any) for a given dictionary, or blanks (if not). If the CCIDs entered differ from those stored for the user in the CCDB, the CCDB is updated to reflect the new values.
The CCIDs specified stay in effect for a given dictionary until they are changed using the CA Endevor/DB User and User Change History Facility (described in Chapter 8), or until you Signon with a different CCID.
If the Derived CCID option is in effect for the user, CCIDs are dynamically assigned through the use of preauthorizations and these CCID fields are not used.
Note: If you specify NOCCID, it will clear the list of current CCIDs for the user.
In addition, Derived CCID processing enables users to switch from one CCID to another without having to sign on under the different CCIDs. Without Derived CCIDs, for example, if a unique CCID is established for every change for every DIALOG, programmers would be issuing CA Endevor/DB signons on a frequent basis. To circumvent this problem, the CA Endevor/DB administrator can predefine the relationships between CCIDs and dictionary entities, and the programmers can run in "DERIVED CCID" mode. When doing so, they only signon to CA Endevor/DB to specify their userid. The CCID to which a given change is attributed will be determined by the presence of a PREAUTHORIZATION junction.
|
Copyright © 2013 CA.
All rights reserved.
|
|