There are several command files for setting up the data
structures described in ACCOUNT.DOC, which should be read
(or at least skimmed) first. The command file assumes you
will be in the same UIC as the system accounting data,
which is usually [1,6]. If you are not, then you should
either move these files to [1,6], or edit the file
ACCOUNT.BKP and where there are domain definitions such as
"DEFINE DOMAIN xxx USING xxx-REC ON ACCOUNT.DOM;",
ACCOUNT.DOM is the name of the file containing the data,
and you may insert a UIC designation before it, such as
[1,6]ACCOUNT.DOM. I find it better to keep the commands in
[1,6], and let only the system manager have access to them.
If your site has one dictionary for everyone, I also
reccomend you create a seperate one for just this purpose:
you can do this with the Datatrieve CREATE DICTIONARY
command, or by using the RMS DEF utility and the supplied
QUERY.DEF file with the command DEF @QUERY.DEF which will
create an empty dictinary in the UIC you are in at the
time.

Once you have decided where the data will be, enter
Datatrieve, and at the prompt "DTR>" enter the command 
@ACCOUNT.BKP
which will create all of the definitions and procedures
described in the document for system accounting. The first
time you do this, you will get the message
'"xxx" has not been defined in the dictionary'
these messages may be ignored. As you may wish to modify
these reports, I suggest you keep ACCOUNT.BKP around to
restore the data structures in case of accident.

Because indexed files cannot be put on magnetic tape with
FLX, the data for the CODES domain is distributed in a
sequential file CODES.SEQ: to convert the data, in
Datatrieve enter the command @CODES, and a temporary domain
CODES-SEQ will be created to read and convert the data.
This domain may be deleted when done.

The file ACCOUNT.CMD is a command file to read the
accumulated system account data and convert it to the form
expected by Datatrieve. It replaces the data previously
obtained with this command file. ACCOUNT.BAT is the same
thing in batch form. REPORTS.CMD is invoked from Datatrieve
to obtain a complete set of reports: you may want to edit
this to include only those reports you want.

To create the structures described in the document for
processing the console log file, use the file CONSOLE.BKP
in the same manner as ACCOUNT.BKP given above. This file
also expects you to be in the same UIC as the data, which
in this case is [1,4], but may be changed in the same
manner as given above. The file CONSOLE.DEF is described in
the document, and is used to create a file which will hold
data extracted from the console log using the RMS
utilities. You can convert the data with the command file
CONSOLE.CMD, which will ask for the name of the data file
(CNV cannot read the log file while COT is writing to it),
and will create the temporary file, and invoke Datatrieve
to use the CONVERT.CMD file for the final conversion.
When this is done, the comain C will contain the formatted
data ready for reporting as described in the document. The
procedure BATCH will produce the report shown.

Comments and suggestions are welcomed, and should be
directed to:

Bart Z. Lederman
I.T.T. World Communications
67 Broad St.
New York, N.Y. 10004-2464

(212) 607-2657 8:00 A.M. - 4:00 P.M. Eastern time.