This section shows you how to use RA on CLUSTER systems.
Data collection
There are two daily collection procedures that run every night. The first, ACC_DAY_UPDATE_nodename.COM, only runs on nodes where you are collecting disk data. The second, ACC_SUMMARY_nodename.COM, runs on every node. When you run RA_COM:AUTOSUBMIT.COM on each node, you are allowed to submit one or both of these procedures.
Since ACC_DAY_UPDATE_nodename.COM collects disk information, it should only run on node(s) that are collecting disk information. Unless there are some disk drives which are node-specific, you should pick one node to collect all disk information for all the disks in the DISKNAMES.nodename file. Be careful to avoid collecting multiple sets of data for the same drive on more than one node. When you run AUTOSUBMIT.COM, it will ask you if you want this node to collect disk information. If you answer "Y", ACC_DAY_UPDATE_nodename.COM will be submitted.
ACC_SUMMARY_nodename.COM extracts the OpenVMS accounting information and generates the daily reports. This command procedure should run on each node of your cluster for which you want to generate reports.
RA accounting summary file
RA keeps resource usage information in a monthly accounting summary file called RA_DAT:nodename_ACCOUNTNG.month. The file extension is the month, in the standard OpenVMS abbreviated format ("JAN" for January).
You can specify multiple accounting files in the Accounting File List. This allows you to charge different rates for the different nodes. You can also merge several accounting files from different nodes into a single file to generate consolidated reports. The /multiple qualifier which was added with Version 5.2 will cause RA to scan all the files in the Accounting File List to generate a summary file for multiple nodes and/or months. Prior to this the only way to create a summary file for multiple nodes or months was to use the DCL APPEND command to create a single data file before summarizing it; this meant RA only charged for one cpu class.
Client file
T he RA installation procedure creates the RA_DAT:CLIENT.DAT file from the user authorization file. This file contains one record for each OpenVMS username and stores charge rates for that user.
If your cluster has a common SYSUAF.DAT, you can easily combine data to generate reports.
If your cluster has a separate SYSUAF.DAT for each node, install RA on each node or create a separate data directory for each node and use the create_client_file.com procedure to create a client file on each node..
If a username is not found in the CLIENT.DAT file, RA uses the charge rates from the DEFAULT account in the file. You can create a consolidated client file by adding users using the RA Client File Maintenance function or you can merge the client files from all systems using the SORT/MERGE utility. For example, the command:
$ SORT/KEY=(POSITION:9,SIZE:12)/KEY=(POSITION:1,SIZE:8)/NODUPLICATE- client_file_1,client_file_2 master_client_file/OVERLAY
will merge two client files into a master_client file.
For more information on the client file, refer to the section "Files you need to use RA". For more information on the SORT command, refer to the OpenVMS Sort/Merge Utility Manual.
SYSTARTUP and SYLOGIN command procedures
The RA installation procedure creates 2 files, RA_SETUP.COM and RA_ADD_SYLOGIN.COM, and copies these files to the SYS$MANAGER directory. It also copies 2 programs to SYS$SYSTEM; ACC_RECORD_TERMINAL.EXE and ACC_SET_PROJECT.EXE.
If you plan to charge for connect time at different baud rates or use project accounting, these files should be placed in the SYS$MANAGER and SYS$SYSTEM directories for each node. See the section "RA and the OpenVMS accounting utility" for information on the effect these programs have on the OpenVMS accounting file.
RA_SETUP.COM installs the images ACC_RECORD_TERMINAL.EXE and
ACC_SET_PROJECT.EXE with CMKRNL and PHYS_IO privilege, using the install utility. Be sure to execute it in each node's specific SYSTARTUP_V5 command procedure.
RA_ADD_SYLOGIN.COM executes the programs necessary to record the terminal speed and to initiate project accounting. Be sure to execute it in each node's specific SYLOGIN command procedure.
Using RA on a CLUSTER
You can use RA to track resources on clusters. You specify the locations of the accounting files for each node in an Accounting File List. RA reads and summarizes all the files into a single summary data file so you can generate one invoice for your entire cluster.
Using project accounting
You can analyze resource usage by project. To start a project, users enter the command:
 |
$ PROJECT project_name |
RA verifies that the project exists and the user is allowed to access it then charges all resource usage to that project until a new project is defined or the user logs out. You can create new projects and specify which users are allowed to access them. Optionally, RA can be configured to accept any project name and not verify it against a list.
Easy to use
RA is easy to set up and use. It comes with a tutorial, a menu/form interface, on-line HELP, extensive error messages and a comprehensive user guide and reference manual.
Field-proven
RA is analyzing resources and charging users at almost 100 sites in North America. It's solidly engineered, rigorously tested and fully field-proven by system managers like yourself.
Fully supported
With an annual support agreement, you'll always have someone to call if you have any problems with RA. For a single low annual fee, you get unlimited TOLL-FREE telephone support from our experienced software developers, yearly software updates and a subscription to our SYS$UPDATE newsletter packed with tips showing you how to use Saiga Systems' products like RA to do more with less on your system. Our support lines are open Monday to Friday from 8 a.m. to 5 p.m. Mountain Standard Time except normal business holidays. The second page of this manual includes our telephone numbers, e-mail addresses, web page URL and ftp address.