Signon and Set Options Commands › SIGNON › Purpose

Purpose

The assigned userid identifies you to CA Endevor/DB, enabling the product to access security restrictions for that user. It also determines whether you are allowed to do batch processing. In CA Endevor/DB Batch, you can process under one signon ID at a time. If specified, it must be the first statement in the batch run. If you want to process under two different userids, you must submit two batch jobs.

When you enter a SIGNON command, you perform three functions:

• You identify the CCDB to be accessed (DICTNAME).
• You identify yourself (your userid).
• You identify the CCID(s) under which you are working.

The security rules that determine what functions you will be allowed to perform are determined by all three pieces of information. (Refer to the Security Class Maintenance chapter of the CA Endevor/DB for CA IDMS Administrator Guide for more information on security rules.) If any of the functions that you perform require change logging, then the change log entries are marked with the userid/CCID information.

CA Endevor/DB "remembers" the CCIDs that you specify from one CA Endevor/DB Online or CA Endevor/DB Batch session to the next. If you are working under the same CCID(s) as in your last session, you can omit the CCID clause in this command.

All CA IDMS processing runs under an assigned CA IDMS/DC userid. In the case of:

• CA IDMS/DC logon, the userid is taken from the VTAM login.
• Batch processing, the userid is taken from the originating interactive session (TSO, CICS), or from the batch job (JOB card USER parameter).

The purpose of the CA IDMS/DC SIGNON task is no longer to establish an CA IDMS/DC userid, but to switch userids - all CA IDMS/DC processing is now done under a specific userid.

When CA Endevor/DB is used to monitor dictionary changes by any of these means, it will automatically determine the userid, and attribute the dictionary changes to that userid. It determines your userid at the instant of your first dictionary update, and "remembers" it for as long as you are connected to CA IDMS. Thus, you can execute CA IDMS dictionary utilities (ADSC, etc.), and the dictionary updates will automatically be attributed to your userid.

While the automatic usage of your DC userid is often useful, there are several situations where it is not appropriate:

• If your site requires the use of CA Endevor/DB passwords.
• If you need to switch from working under one (set of) CCID(s) to another.
• If you change DC userids after making changes to a dictionary.

For the preceding cases, you use the SIGNON command to specify your userid.