• Aucun résultat trouvé

CREATING AN ACCOUNT DATA BASE

Dans le document 'is respons~ble (Page 114-119)

SUPERIOR DIRECTORY FULL

CHANGE 10: 00 WEEKENDS ,MONDAY CHANGE 12:00 TUESDAY,THURSDAY,SAT

6.3 CREATING AN ACCOUNT DATA BASE

Sections 6.3.1 through 6.3.3 describe how to use your selected accounting scheme and create the necessary files for your data base.

Specifically, these sections include how to enter accounting data into files, how to run the account generator program (ACTGEN) to create the data base, and what to do if an error occurs.

6.3.1 Entering Accounting Data into Files

Base and subaccount files are created using a text editor. The format below shows the combination of entries you can make in accounting files using the CREATE command. Each file you or a project administrator creates can contain one or more accounts. Each account can point to one subaccount file, where additional account information is stored pertaining to that account. Following the format is a summary of the valid commands in an account file.

6-6

CREATING ACCOUNTS

GROUP (ON STRUCTURE) dev:fUSER:user group number

GROUP (ON STRUCTURE) dev:/DIRECTORY:directory group number

<ESC> immediately following the USER entry. For example:

USER/EXPIRES:10-JAN-86, name1, name2, name3, name4

This format specifies that none of the users in the list can use the

CREATING ACCOUNTS

Table 6-1: Summary of Account Data File Commands

Command Description

ACCOUNT Specifies the name of the account that you or a project administrator wish to assign.

/SUBACCOUNT:

/CLASS:n

Note: The ACCOUNT command must be the first entry in an account data file because all subsequent entries up to the next ACCOUNT entry are modifiers.

Modifies the ACCOUNT command. It includes the specification of the file where additional data for the account can be found.

Note: The ACCOUNT command accepts only one /SUBACCOUNT:modifier.

Example: One of your accounting files contains the following commands.

ACCOUNT CORRECT-DATA/SUBACCOUNT:

<GERHARD>ACCT.TXT

ACCOUNT UNIONBANK/SUBACCOUNT:

<WARRINER>ACCTG.TXT

ACTGEN looks in <GERHARD>ACCT.TXT ·for more account data for the account CORRECT-DATA, and it looks in <WARRlNER>ACCTG.TXT for more data for account UNIONBANK.

Modifies the ACCOUNT command and is used in conjunction with the class scheduler. It specifies the scheduling class that is valid for this account. For example,

ACCOUNT CHEM-207/CLASS:3

6-8

Command

/ALLOW:n,n

CREATING ACCOUNTS

Description

means that class 3 is valid when using the account CHEM-207. ACTGEN places this . information in the system's accounting data base for use by the class scheduling routines. Use the /CLASS:n switch only if you have selected to specify class scheduling by account. (Refer to Section 10.1 for a complete description of using the class scheduler by account.)

When a user gives an account that does not have a valid class associated with it, the system uses the default class, class O. If the account has a class associated with it, that class is used. The percentage of CPU time that classes can receive is defined in the n-CONFIG.CMD file.

To use class scheduling by account, you must have:

o made the appropriate entries in the n-CONFIG.CMD file.

o updated your ACCOm~TS.CMD file (and subaccount files) to specify the classes that are associated with each account.

o run ACTGEN with the INSTALL command to update the ACCOUNTS-TABLE.BIN file.

o given the ENABLE CLASS-SCHEDULER command to OPR or brought the system down and back up again to start class scheduling.

Modifies the ACCOUNT command and is used in conjunction with the class scheduler. It allows you to delegate the assigning of classes to subaccounts by project administrators. It specifies the class or classes that can be used by subaccounts of this account. For example,

ACCOUNT CHEM/SUBACCOUNT:<ABC>MORE.TXT-/CLASS:2/ALLOW:l,3

Command

USER

*

CREATING ACCOUNTS

Description

means the CHEM account is in class 2, and that subaccounts created under CHEM can be in either class 1 or class 3. If no /ALLOW switch is given, the administrator is not restricted to using certain classes and, therefore, can give the subaccounts any class. For example, the administrator can give them the same class as the superior directory. The /ALLOW switch is useful when you want the superior account to be in perhaps a higher percentage class than its inferior accounts. Remember that if the administrator does not give a /CLASS switch to the subaccount, users who log into or change to this subaccount will be in class

o.

Specifies one user or the list of users who are allowed to use this account.

Specifies that an account is valid for all users on a system. The * is a special argument to the USER command.

Example: One instance when you might use * is if you have not established an accounting scheme but would like to allow users to log into the system. You could set up one account and use the * to indicate that all users can use that account.

You could also use the * as follows:

ACCOUNT MATH-101 USER: MATH.*

This means that all users with a user name beginning with MATH can use the MATH-101 account. For example, the users assigned the user names MATH. SMITH, MATH. JONES, and MATH.BROWN can all use this account.

6-10

Command project administration. This command also prevents users from being charged for file storage in files-only directories.

Note: The DIRECTORY command also accepts a for account CORRECT-DATA.UNIONBANK.FUND has the entry:

Dans le document 'is respons~ble (Page 114-119)