Marc's Place

1 RENAME

Changes the user name of the SYSUAF record (and, if specified, the corresponding identifier) while retaining the characteristics of the old record. Format RENAME oldusername newusername 2 Parameters oldusername Specifies the current user name in the SYSUAF. newusername Specifies the new name for the user. It can contain 1 to 12 alphanumeric characters and underscores. Although dollar signs are permitted, they are usually reserved for system names. 2 Qualifiers /GENERATE_PASSWORD /GENERATE_PASSWORD[=keyword] /NOGENERATE_PASSWORD (default) Invokes the password generator to create user passwords. Generated passwords can consist of 1 to 10 characters. Specify one of the following keywords: BOTH Generate primary and secondary passwords. CURRENT Do whatever the DEFAULT account does (for example, generate primary, secondary, both, or no passwords). This is the default keyword. PRIMARY Generate primary password only. SECONDARY Generate secondary password only. When you modify a password, the new password expires automatically; it is valid only once (unless you specify /NOPWDEXPIRED). On login, users are forced to change their passwords (unless you specify /FLAGS=DISFORCE_PWD_CHANGE). Note that the /GENERATE_PASSWORD and /PASSWORD qualifiers are mutually exclusive. /MODIFY_IDENTIFIER /MODIFY_IDENTIFIER (default) /NOMODIFY_IDENTIFIER Specifies whether the identifier associated with the user is to be modified in the rights database. This qualifier applies only when you modify the UIC or user name in the UAF record. By default, the associated identifiers are modified. /PASSWORD /PASSWORD=(password1[,password2]) /NOPASSWORD Specifies up to two passwords for login. Passwords can be from 0 to 32 characters in length and can include alphanumeric characters, dollar signs, and underscores. Avoid using the word password as the actual password. Use the /PASSWORD qualifier as follows: o To set only the first password and clear the second, specify /PASSWORD=password. o To set both the first and second password, specify /PASSWORD=(password1, password2). o To change the first password without affecting the second, specify /PASSWORD=(password, ""). o To change the second password without affecting the first, specify /PASSWORD=("", password). o To set both passwords to null, specify /NOPASSWORD. When you modify a password, the new password expires automatically; it is valid only once (unless you specify /NOPWDEXPIRED). On login, the user is forced to change the password (unless you specify /FLAGS=DISFORCE_PWD_CHANGE). Note that the /GENERATE_PASSWORD and /PASSWORD qualifiers are mutually exclusive. When you create a new UAF record with the RENAME command, you must specify a password. 2 Examples 1.UAF> RENAME HAWKES KRAMERDOVE/PASSWORD=MARANNKRA %UAF-I-PRACREN, proxies to HAWKES renamed %UAF-I-RENMSG, user record renamed %UAF-I-RDBMDFYMSG, identifier HAWKES modified The command in this example changes the name of the account Hawkes to Kramerdove, modifies the user name identifier for the account, and renames all proxies to the account. 2.UAF> RENAME HAWKES KRAMERDOVE %UAF-I-PRACREN, proxies to HAWKES renamed %UAF-I-RENMSG, user record renamed %UAF-W-DEFPWD, Warning: copied or renamed records must receive new password %UAF-I-RDBMDFYMSG, identifier HAWKES modified This example shows the warning message that the system displays if you fail to specify a new password with the RENAME command. 2 /IDENTIFIER Renames an identifier in the rights database. Format RENAME/IDENTIFIER current-id-name new-id-name 3 Parameters current-id-name Specifies the name of an identifier to be renamed. new-id-name Specifies the new name for the identifier. 3 Example UAF> RENAME/IDENTIFIER Q1SALES Q2SALES %UAF-I-RDBMDFYMSG, identifier Q1SALES modified The command in this example renames the identifier Q1SALES to Q2SALES.

© 1997- Marc Vos (and others)   -   Privacy Statement   -    Contact Me

On this website, Google Analytics is used to track visitor statistics. These are anonymised data about the number of visitors, which pages they visit on this site, from which regions they visit, which web browsers they use, etc.. You will also see non-personalised ads via Google AdSense. Cookies from Paddle or Paypal are placed when you click on a 'Buy now!' or 'Donate!' button, and possible cookies from Disqus when you use that system to comment on one or more blogposts.
Privacy Statement