Previous Topic: Using ACF INSERT to Create LogonidsNext Topic: Using ACF CHANGE to Change the PASSWORD Field


Using ACF CHANGE to Change User Information

You can change logonid information with the ACF CHANGE subcommand. If you have the correct privileges (specified in the SCPLIST field of your logonid record), you can change other logonid records. The syntax for the ACF CHANGE subcommand is:


        {*             }
        {logonid       }
CHange  {Like(lidmask) }  field,...,field
        {Uid(uidmask)  }  IF(field,...,field)
*

Tells CA ACF2 for VM to use the last logonid you referenced. Your logonid is the default when you first enter the ACF command. CA ACF2 for VM uses it until you enter another logonid.

logonid

Tells CA ACF2 for VM which logonid record to change.

Like(lidmask)

Tells CA ACF2 for VM which group of logonid records to change. These logonid records match the mask you provide.

Uid(uidmask)

Tells CA ACF2 for VM to change the logonids that match the UID you specified.

field,...,field

Tells CA ACF2 for VM which fields to change, specified by their field names. For a list of valid field names, see the “About the Loginid Record” chapter.

IF(field,...,field)

Tells CA ACF2 for VM to change logonids that have the privileges that you list in parentheses. For example, CHANGE IF(SECURITY,ACCOUNT) changes all users with the SECURITY and ACCOUNT privileges. To change logonid records without a specific bit field, prefix the field name with NO.

You can specify only the bit fields of the logonid record as defined by CA ACF2 for VM or your site. For information about CA ACF2 for VM defined fields, see the “About the Loginid Record” chapter.

You can also specify the IF parameter with the LID or UID parameter.

The LIKE parameter lets you change a group of logonid records at one time if they match the specified mask. Using the UID operand and mask changes all logonid records with UIDs that match the mask. Your ability to change logonid records can be scoped.

To illustrate the CHANGE subcommand, we will first list Ann Smith's (TLCAMS) logonid record:

ACF

list TLCAMS

TLCAMS AAPMGRGUSER09 ANN SMITH EXT.458 PRIVILEGES ACCOUNT SCPLIST(ACCTMGR) ACCESS ACC‑CNT(0) ACC‑DATE(0) ACC‑TIME(0) PASSWORD PSWD‑TOD(01/04/98‑12:01) STATISTICS UPD‑TOD(01/04/98‑12:01) RESTRICTIONS PREFIX(TLCAMS)

The account manager wants to change Ann's logonid record to remove the ACCOUNT privilege and add the AUDIT privilege. Ann will have the AUDIT privilege and can display the logonid records and access rules of other users.

ACF

change TLCAMS audit noaccount

TLCAMS AAPMGRGUSER09 ANN SMITH EXT.458 PRIVILEGES AUDIT SCPLIST(ACCTMGR) ACCESS ACC‑CNT(0) ACC‑DATE(0) ACC‑TIME(0) PASSWORD PSWD‑TOD(01/04/98‑12:01) STATISTICS UPD‑TOD(01/04/98‑12:01) RESTRICTIONS PREFIX(TLCAMS)

The AUDIT privilege appears in the Privileges section of this logonid record and the account manager has removed the ACCOUNT attribute in the Privileges section. The AUDIT and ACCOUNT fields are bit or attribute fields of the logonid record. To add an attribute field, enter the field name in the CHANGE or INSERT subcommand (as AUDIT in the previous example). To remove an attribute field, enter the prefix NO and the field name (as in NOACCOUNT).

To add fields that have a value, enter the field name followed by the value of the field in parentheses, such as SCPLIST(ACCTMGR). To delete fields that have a value, enter the field name followed by left and right parentheses, such as SCPLIST(). The only exception to this rule is a change made to the PASSWORD field, explained in the next section.

The account manager issued this CHANGE subcommand done under the default of SET VERBOSE. If he had entered the SET TERSE subcommand before changing this logonid record, CA ACF2 for VM would have replied:

Logonid TLCAMS changed