LOGCTL command: Modifying file entries in the password table

From m204wiki
Jump to navigation Jump to search


System manager
Adds, deletes, or changes file entries in the password table


LOGCTL {A | D | C} :filename [index]


filename The name of the file entry to be added, deleted, or changed (1 to 8 characters). The file name must be preceded by a colon (:).
index A single character indicating which file entry is being modified, and is either a digit (0-9) or a letter (A-Z); index must be specified if the file has more than one password.



Usage notes

The LOGCTL command adds, deletes, or changes file entries in the password table. If add (A) or change (C) is specified, Model 204 prompts for information as shown below.

The system manager can change any of the following specifications in a file entry:

  • Password
  • Privileges
  • User class
  • Field-level security levels
  • Terminal list

Upon entry of the LOGCTL command, the system responds with a prompt in the following form:


The user response would be in this form:



password As of Model 204 version 7.7, a password can contain up to 127 characters, including blanks and special characters.

Note: Commas in passwords are allowed only when using the LOGONCP command or the $Sir_Login function, but not when using the LOGCTL command. In the case of LOGCTL, comma is the delimiter between arguments.

pppp The two-byte representation of the file privileges. (See the PRIVDEF parameter.)
ccc The procedure user class. (See Procedure security.)
sss The field-level security SELECT level.
rrr The field-level security READ level.
uuu The field-level security UPDATE level.
aaa The field-level security ADD level. (For information on field-level security, see Field-level security.)

When a file entry is being added, the password is required and all other specifications are optional. Model 204 supplies default values of zero.

When a file entry is being changed, all specifications are optional. If the system manager does not supply a specification in the command, the existing specification in the password table is preserved, as described for login user IDs.