You assign two account strings to user TAW. The first entry is the default.
MODIFY USER TAW AS ACCOUNT=('$M00ACTB&D&H','$H00FINR&D&H');
When TAW logs on without specifying an account, TAW will default to using the first account. At query execution time, Teradata Database replaces &D with the current date and &H with the current hour.
In another case, you assign two account strings to user DTG. However, the first (default) account string does not specify date or hour expansion:
MODIFY USER DTG AS ACCOUNT = ('$M00accO', '$L00accB&D&H');
When DTG logs in without specifying an account, then the ASE logging does not occur. To initiate them, DTG must type &D&H in the account string either when he logs in or during the session:
- Log in using .logon DTG, mypassword, '$M00accO&D&H'
- Change the account during a session with the following statement: SET SESSION ACCOUNT='$M00accO&D&H'
Because assigning the first account to DTG without ASE variables means ASE logging does not occur by default, Teradata does not recommend listing the account without &D&H in the account string first.
In another case, assume you omit the ASE variables in the two account strings for user AM1:
MODIFY USER AM1 AS ACCOUNT=('$M00accR', '$H00accT');
AM1 cannot invoke the ASE feature at any time. Teradata does not recommend assigning the first account string without the &D&H variables.