Compaq SC RMS - Manuals

List of Tables 10.1 Access Controls Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4 10.2 Accounting Statistics Table . . . . . . . . . . . . . . . . . . . . . . . . . 10-5 10.3 Machine Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6 10.4 Performance S...

10.22 Partitions Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-18 10.23 Projects Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-19 10.24 Resources Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-19 10.25 Servers Table ....

1 Introduction 1.1 Scope of Manual This manual describes the Resource Management System ( RMS ). The manual’s purpose is to provide a technical overview of the RMS system, its functionality and programmable interfaces. It covers the RMS daemons, client applications, the RMS database, the system call...

Related Information Chapter 1 ( Introduction ) explains the layout of the manual and the conventions used to presentinformation Chapter 2 ( Overview of RMS ) overviews the functions of the RMS and introduces its components Chapter 3 ( Parallel Programs Under RMS ) shows how parallel programs are exe...

Conventions 1.4 Related Information The following manuals provide additional information about the RMS from the point of view of either the system administrator or the user: • Compaq AlphaServer SC User Guide • Compaq AlphaServer SC System Administration Guide 1.5 Location of Online Documentation On...

Conventions italic monospace type Italic (slanted) monospace type denotes some meta text. This is usedmost often in command or parameter descriptions to show where atextual value is to be substituted. italic type Italic (slanted) proportional type is used in the text to introduce newterms. It is als...

2 Overview of RMS 2.1 Introduction This chapter describes the role of the Resource Management System ( RMS ). The RMS provides tools for the management and use of a Compaq AlphaServer SC system. To putinto context the functions that RMS performs, a brief overview of the system architecture is given ...

The System Architecture system are also connected to an external LAN . The application nodes, used for running parallel programs, are accessed through the RMS . Figure 2.1: A Network of Nodes Management Network Switch Network Switch Network Control TerminalConcentrator Interactive Nodeswith LAN/FDDI...

The Role of the RMS Figure 2.2: High Availability RMS Configuration RMS Database RMS Host Backup RMS Host The RMS processes run on the node with the name rmshost , which migrates to the backup on fail-over. The database is held on a shared disk, accessible to both theprimary and backup node. 2.3 The...

The Role of the RMS Scheduling deciding when and where to run parallel jobs Audit maintaining an audit trail of system state changes From the user’s point of view, RMS provides tools for: Information querying the resources of the system Execution loading and running parallel programs on a given set ...

RMS Management Functions 2.4 RMS Management Functions The RMS gives the system administrator control over how the resources of a system are assigned to the tasks it must perform. This includes the allocation of resources( Section 2.4.1 ), scheduling policies ( Section 2.4.2 ), access controls and ac...

RMS Management Functions The RMS scheduler allocates contiguous ranges of nodes with a given number of CPU s per node 1 . Where possible each resource request is met by allocating a single range of nodes. If this is not possible, an unconstrained request (those that only specify thenumber of CPUs re...

3 Parallel Programs Under RMS 3.1 Introduction RMS provides users with tools for running parallel programs and monitoring their execution, as described in Chapter 5 ( RMS Commands ) . Users can determine what resources are available to them and request allocation of the CPU s and memory required to ...

Resource Requests 3.2 Resource Requests Having logged into the system, a user makes a request for the resources needed to run aparallel program by using the RMS commands prun (see Page 5-11 ) or allocate (see Page 5-3 ). When using the prun command, the request can specify details such as the follow...

Loading and Running Programs The resource request is sent to the Partition Manager, pmanager (described in Section 4.4 ). The Partition Manager performs access checks (described in Chapter 6 ( Access Control, Usage Limits and Accounting ) ) and then allocates CPU s according to the policies establis...

Loading and Running Programs processes, removing any core files if requested (see Page 5-11 ) and then deallocating the CPU s. The application processes are run from the user’s current working directory with thecurrent limits and group rights. The data and stack size limits may be reduced if RMS has...

Loading and Running Programs Sometimes, it is desirable for a user to be granted more control over the use of aresource. For instance, the user may want to run several jobs concurrently or use thesame nodes for a sequence of jobs. This functionality is supported by the command allocate (see Page 5-3...

4 RMS Daemons 4.1 Introduction This chapter describes the role of the RMS daemons. There are daemons that run on the rmshost node providing services for the system as a whole: msqld Manages the database (see Section 4.2 ). mmanager Monitors the health of the machine as a whole (see Section 4.3 ). pm...

The Machine Manager 4.1.1 Startup RMS is started as each node executes the initialization script /sbin/init.d/rms with the start argument on startup. This starts the rmsmhd daemon which, in turn, starts the other daemons on that node. The daemons can also be started, stopped and reloaded individuall...

The Partition Manager 4.3 The Machine Manager The Machine Manager, mmanager , is responsible for detecting and reporting changes in the state of each node in the system. It records the current state of each node and anychanges in state in the database. When a node is functioning correctly, rmsd , a ...

The Transaction Log Manager Configuration information about each partition is held in the partitions table (see Section 10.2.16 ). The information is indexed by the name of the partition together with the name of the active configuration. 4.5 The Switch Network Manager The Switch Network Manager, sw...

The Process Manager Each entry in the services table specifies which command to run, who can run it and on which host. 4.6.1 Interaction with the Database The Transaction Log Manager maintains the transactions table (see Section 10.2.23 ). It consults the services table (see Section 10.2.20 ) in ord...

The RMS Daemon 4.8 The Process Manager The Process Manager, rmsmhd , is responsible for starting and stopping the other RMS daemons. It runs on each node and is responsible for managing the other daemons thatrun on its node. It starts them as the node boots, stops them as the node halts and startsor...

allocate(1) NAME allocate – Reserves access to CPU s SYNOPSIS allocate [-hIv] [-B base] [-C CPUs] [-N nodes | all] [-n CPUs] [-p partition] [-P project] [-R request] [script [args ...]] OPTIONS -B base Specifies the number of the base node (the first node to use) in thepartition. Numbering within th...

allocate(1) immediate=0 | 1 With a value of 1, this specifies that the requestshould fail if it cannot be met immediately (this isthe same as the -I option). hwbcast=0 | 1 With a value of 1, this specifies a contiguous rangeof nodes and constrains the scheduler to queue therequest until a contiguous...

allocate(1) can be used with hwbcast set to 1 to ensure that the range of nodes allocated is contiguous. Before allocating resources, the Partition Manager checks the resource limits imposedon the current project. The project can be specified explicitly with the -P option. This overrides the value o...

allocate(1) RMS_TIMELIMIT Specifies the execution time limit in seconds. The program will besignaled either after this time has elapsed or after any time limitimposed by the system has elapsed. The shorter of the two time limitsis used. RMS_DEBUG Specifies whether to execute in verbose mode and disp...

allocate(1) argument, it is interpreted as -I and the user is warned that this feature should not be used anymore. SEE ALSO prun , rinfo RMS Commands 5-7

nodestatus(1) NAME nodestatus – Gets or sets the status or run level of each node SYNOPSIS nodestatus [-bhr] [status] OPTIONS -b Operate in the background. -h Display the list of options. -r Get/set run level. DESCRIPTION The nodestatus command is used to update status information in the RMS databas...

msqladmin(1) NAME msqladmin – Perform administrative operations on the mSQL database server SYNOPSIS msqladmin [-q] [-f confFile] [-h host] command OPTIONS -f confFile Specify a non-default configuration file to be loaded. The defaultaction is to load the standard configuration file located in /var/...

prun(1) -n procs Specifies the number of processes required. The -n and -N options can be combined to control how processes are distributed over nodes.If neither is specified, prun starts one process. -O Allows resources to be over-committed. Set this flag to run more thanone process per CPU . -P pr...

prun(1) DESCRIPTION The prun program executes multiple copies of the specified program on a partition. prun automatically requests resources for the program unless it is executed from a shell that already has resources allocated to it. (See Page 5-3 ). The way in which processes are allocated to CPU...

rcontrol(1) NAME rcontrol – Controls use of system resources SYNOPSIS rcontrol command [args ...] [-ehs] [-r level] [command args ...] OPTIONS -e Exit on the first error. -h Display the list of options. -r level Set reporting level. -s Stop and print warning on error. command is specified as follows...

rcontrol(1) set attribute [=] name val [=] value exit help [all | command] show object [=] name object may be one of: nodes , configuration , partition . DESCRIPTION rcontrol is used to manage the following: nodes, partitions and configurations; servers; users and their resource requests, projects a...

rcontrol(1) # rcontrol configure in nodes = ’atlas[1-3]’ # rcontrol configure in nodes ’atlas[1-3]’ Creating and Removing Nodes To create a new node description, use rcontrol with the create command and the argument node followed by the hostname of the node. Additional attribute-value pairs specify ...

rcontrol(1) The timelimit attribute specifies the maximum time in seconds for which CPU s can be allocated on the partition. On expiry of the time limit, jobs will be sent the signal SIGXCPU . If they have not exited within a grace period, they will be killed. The grace period for a site is defined ...

rcontrol(1) start command, the server argument and the name of the server. The command rinfo (with the -s flag) can be used to show the status of the RMS servers. To instruct an RMS server to change its reporting level, use the reload command and the server argument with the name of the server. In a...

rcontrol(1) # rcontrol set resource = 32 priority = 25 # rcontrol set batchid = 48 priority = 40 rcontrol can also be used to suspend, kill or resume jobs identified by their attributes. The attributes that can be specified are: partition , project , status and user . Attributes of the same name are...

rcontrol(1) Note that a user can be in more than one project in which case the value would be acomma-separated list: # rcontrol set user = frank projects = parallax,science To create an access control called, for example, science , in the par1 partition, use rcontrol with the create command followed...

rcontrol(1) The attribute cpu-poll-stats-interval specifies the interval between successive polls for gathering node statistics. The interval is specified in seconds and must be inthe range 0 to 86400 (1 day). The attribute rms-keep-core determines whether core files are deleted or saved. By default...

rcontrol(1) # rcontrol kill resource = 2212 2213 # rcontrol kill batchid = 44 45 To instruct a Partition Manager to reread the user , projects and access_controls tables: # rcontrol reload partition = par1 To enable debug reporting from the RMS scheduler for the partition called par1 : # rcontrol re...

rinfo(1) NAME rinfo – Displays resource usage and availability information for parallel jobs SYNOPSIS rinfo [-chjlmnpqr] [-L [partition] [statistic]] [-s daemon [hostname] | all] [-t node | name] OPTIONS -c List the configuration names. -h Display the list of options. -j List current jobs. -l Give m...

rinfo(1) EXAMPLES When used with the -q flag, rinfo prints information on the user’s projects, CPU usage limits, memory limits and priorities. $ rinfo -q PARTITION CLASS NAME CPUS MEMLIMIT PRIORITY parallel project default 0/8 100 0 parallel project divisionA 16/64 none 1 In this example, the access...

rmsbuild(1) NAME rmsbuild – Creates and populates an RMS database SYNOPSIS rmsbuild [-dhv] [-I list] [-m machine] [-n nodes | -N list] [-p ports] [-t type] OPTIONS -d Create a demonstration database. -h Display the list of options. -I list Specifies the names of any interactive nodes. -m machine Spe...

rmsbuild(1) Detailed information about each node (number of CPU s, amount of memory and so on) is added later by rmsd as it starts on each node. The machine name is specified with the -m option. Machines should be given a short name that does not end a digit. Node names are generated by appending a ...

rmsctl(1) NAME rmsctl – Stops, starts or shows the status of the RMS system. SYNOPSIS rmsctl [-aehv] [start | stop | restart | show ] OPTIONS -a Show all servers, when used with the show command. -e Only show errors, when used with the show command. -h Display the list of options. -v Verbose operati...

rmsctl(1) RMS service stopped on atlas0 RMS service stopped on atlas3 RMS service stopped on atlas2 RMS service stopped on atlasms To start the RMS system, use rmsctl as follows: # rmsctl stop RMS service started on atlas0 RMS service started on atlas1 RMS service started on atlasms RMS service star...

rmsexec(1) freemem Free memory in megabytes. users Lowest number of users. By default, usercpu is used as the statistic. Statistics can be used on their own, in which case a node is chosen that is lightly loaded according to this statistic, or you canspecify a threshold using statistic < value or...

rmsquery(1) NAME rmsquery – Submits SQL queries to the RMS database SYNOPSIS rmsquery [-huv] [-d name] [-m machine] [SQLquery ] OPTIONS -d name Select database by name. -h Display the list of options. -m machine Select database by machine name. -u Print dates as seconds since January 1st 1970. The d...

rmsquery(1) The source is provided in /usr/opt/rms/src . Details of the SQL language can be found on the Quadrics support page http://www.quadrics.com/web/support . EXAMPLES An example follows of a select statement that results in a list of the names of all of the nodes in the machine. Note that the...

rmstbladm(1) DESCRIPTION The command rmstbladm is used to administer the RMS database. It creates the tables and their default entries. It can be used to back up individual tables (or the wholedatabase) to a text file, to restore tables from file or to force the recreation of tables.Unless a specifi...

6 Access Control, Usage Limits and Accounting 6.1 Introduction RMS access controls and usage limits operate on a per-user or per-project basis (a project is a list of named users). Each partition may have its own controls. This mechanismallows system administrators to control the way in which the re...

Access Controls control records. When submitting requests for CPU s, users can select any project of which they are a member (by setting the RMS_PROJECT environment variable or by using the -P flag when executing prun or allocate ). RMS rejects requests to use projects that do not exist or requests ...

Access Controls The access controls for individual users must set lower limits than those of the projectsof which they are a member. That is to say, they must have a lower priority, smallernumber of CPU s, smaller memory limit and so on than the access control record for the project. Where a memory ...

How Access Controls are Applied parallel priority = 5 rcontrol create access_control = default class = project partition = \ parallel priority = 0 memlimit = 256 name class partition priority maxcpus memlimit design project parallel 5 Null Null default project parallel 0 Null 256 Requests submitted ...

How Access Controls are Applied allocated has its memory limits set to this value. A process with more than one CPU allocated has proportionately higher memory limits. The RMS_MEMLIMIT environment variable can be used to reduce the memory limit set by the system, but not to raise it. By default, the...

Accounting 1. No CPU usage limits are set on jobs run by the root user. 2. If the user has an access control record for the partition, the CPU usage limit is determined by the maxcpus field in this record. 3. The access control record for the user’s current project determines the CPU usage limit. 4....

Accounting Accounting records are updated periodically until the CPU s are deallocated. The running flag is set to 0 at this point. The atime statistic is summed over all CPU s allocated to the resource request. The utime and stime statistics are accumulated over all processes in all jobs running on...

7 RMS Scheduling 7.1 Introduction The Partition Manager (see Section 4.4 ) is responsible for scheduling resource requests and enforcing usage limits. This chapter describes the RMS scheduling policies and explains how the Partition Manager responds to resource requests. 7.2 Scheduling Policies The ...

Scheduling Constraints together. That is to say, all of the processes in a program are eitherrunning or suspended at the same time. Gang scheduling is required for tightly coupled parallel programswhich communicate frequently. It becomes increasingly important asthe rate of interprocess communicatio...

What Happens When a Request is Received Time Limit Jobs are normally run to completion or until they are preempted by a higher priorityrequest. Each partition may have a time limit associated with it which restricts theamount of time the Partition Manager may allow for a parallel job. On expiry of t...

What Happens When a Request is Received immediate The request should fail rather than block if resources are notavailable immediately. Note The RMS scheduler attempts to allocate CPU s on a contiguous range of nodes. If a contiguous range of nodes is not available then requests that explicitly speci...

What Happens When a Request is Received 7.4.1 Memory Limits If memory limits are enabled (by setting the memlimit attribute of a partition or access control) then a request is only allocated CPU s on nodes that have sufficient memory available. RMS enforces memory limits by setting the data and stac...

8 Event Handling 8.1 Introduction RMS includes a general mechanism for posting, waiting on and handling events. This functionality is provided by the Event Manager, eventmgr (see Section 4.7 ). Events are specified by RMS class, name, type and description. class The class of object generating the ev...

Introduction $ rmsquery -v "select * from events order by ctime" id name class type ctime handled description --------------------------------------------------------------- 20 atlas0 node status 05/04/01 15:53:02 1 running 21 atlas0 node status 05/05/01 11:27:29 1 not responding 8.1.1 Posti...

Event Handling ::: matches node:atlas0:status Note that the class, name, type and description must all be specified when postingevents but one or more of the class, name and type can be null when waiting on events. 8.2 Event Handling Event handler scripts are specified in the event_handlers table. T...

List of Events Generated program=‘basename $0‘ id=$1 class=$2 name=$3 type=$4 description=$5 # # format event description message # message() { echo "‘date ’+%h %e %X’‘ OSF1 event $id $type $class $name $description" } # # log the event # message >> /var/rms/adm/log/event.log # # execu...

List of Events Generated submitted transaction submitted started transaction being executed complete transaction completed successfully failed transaction failed to execute error transaction completed but there were errors In the case of a transaction completing with errors (a link error test orboun...

9 Setting up RMS 9.1 Introduction This chapter describes how to set up RMS and carry out routine operations. The information is organized as follows: • Planning the installation (see Section 9.2 ). • Starting RMS and configuring the system (see Section 9.3 ). • Carrying out day-to-day operations and...

Setting up RMS for this command to work correctly. This should have been enabled as part of theinstallation. # rmsctl start Configure all of the nodes into the machine using rcontrol . # rcontrol configure in ’atlas[0-63]’ Use rinfo with the -n option to check the status of the nodes. The output sho...

Day-to-Day Operation Note In the current release, any requests that are suspended when a partition isstopped must be resumed manually if the partition is restarted. 9.4 Day-to-Day Operation Once the system is up and running, give some thought to automating some routine orday-to-day operations: • Per...

Day-to-Day Operation 9.4.3 Summarizing Accounting Data Accounting records accumulate in the RMS database as each job is run. By default, they are not processed as each site has its own requirements in this respect. A simpleexample script to produce a summary of resource usage is included in the rele...

Day-to-Day Operation instructing the table administration program, rmstbladm , to remove old entries. Before running rmstbladm , archive any data you want to keep as described in Section 9.4.4 . Remove old entries as follows: # rmstbladm -c rmstbladm clears out all entries that are older than a spec...

Local Customization of RMS # rcontrol configure in node=atlas2 3. Restart the partition: # rcontrol start partition=parallel This brings the partition back up to its full complement of nodes. 9.5 Local Customization of RMS RMS can be customized to suit local operating patterns in a variety of ways. ...

Log Files crashed. A site-specific variant might copy core files from the local temporary directoryto a global file system for subsequent analysis. To create a site-specific core file analysis script, copy the default script /opt/rms/etc/core_analysis to /usr/local/rms/etc and modify it as required....

Log Files 9.6 Log Files The RMS daemons output reports to log files in the directory /var/rms/adm/log . The amount of detail is controlled for each daemon by setting a reporting level. By default,the reporting level is set to 0. The reporting level is a bitmap that turns on different reports. Values...

10 The RMS Database 10.1 Introduction This chapter describes the tables which make up the RMS database. Each machine has its own database, called rms_ machine , where machine is the name of the machine. This allows a single database server to support multiple machines. The database contains tables s...

Introduction x-y This denotes a range of possible integer values. text This denotes a character string of arbitrary length. • Fields of type text can be selected by the field name but the text entry cannot be matched. If the text is a list of items, for example, a list of node names, the items in th...

Introduction Operational State The following tables hold details of the current state of the machine. events records changes to the state of the machine event handlers lists the handlers used to act on events attributes holds site-specific attribute-value pairs fields specifies how objects and attri...

Listing of Tables transaction outputs contains output from requests posted to the transaction log request types describes output formats in the transaction outputs table statistics lists the performance statistics available in the current release services describes the services available and who can...

Listing of Tables The memint field is set to 0 in AlphaServer SC Version 2.0. The number of entries in the accounting statistics table can grow rapidly. The tableshould be cleared periodically of old entries as described in Section 9.4.3 . 10.2.3 The Attributes Table The attributes table shown in Ta...

Listing of Tables entries, if called with the -c option (see Page 5-44 ). Note that the accounting statistics table is not cleared out (see Section 10.2.2 ). Table 10.4: Performance Statistics Attributes Attribute Default Description node-statistics cpu statistics collected per node cpu-stats-poll- ...

Listing of Tables 10.2.5 The Elites Table The elites table shown in Table 10.8 , contains one entry for each switch in the network. Its entries are created and maintained by the Switch Network Manager, swmgr (see Section 4.5 ). Table 10.8: Elites Table Field Type Description name char(8) Elite name,...

Listing of Tables attributes table (see Section 10.2.3 ) must be set to cpu . This is the default setting. The interval at which the nodes are sampled for CPU statistics is controlled by the attribute cpu-stats-poll-interval in the attributes table; the default is to sample every 2 minutes. The node...

A Compaq AlphaServer SC Interconnect Terms A.1 Introduction RMS includes support for programs that use Compaq AlphaServer SC Interconnect. This appendix provides an introduction to Compaq AlphaServer SC Interconnect, definingterms used elsewhere in this manual. Before an application process can use ...

Introduction Figure A.1: A 2-Stage, 16-Node, Switch Network Plane 0 Plane 3 Top Switches Level 1 Level 2 Level 0 Uplinks Network Adapters Net id 0 Net id 15 The level is the index of the stage, starting with 0 at the top. Note that in a 2-stage switch network the Elans are at level 2. Each component...

Link Errors network, data can be broadcast directly to a contiguous range of processors: data isrouted up to a node in the tree from which all processors can be reached; then the data isrouted down to all switch outputs in the broadcast range on the way down. Data can berecombined as it travels thro...

B RMS Status Values B.1 Overview This appendix lists the various states that RMS objects can enter. State information is stored in the status field of the RMS table for the object in question. For example, the current state of a partition is held in the partitions table (see Section 10.2.16 ). and t...

Link Status Values B.2 Generic Status Values There are three generic status values: ok This state means that an object is functioning correctly as far as therelevant RMS daemon can tell. error This state means that one or more errors have been detected. Adescription of the problem will be found in t...

Module Status Values B.4 Link Status Values Each switch (see Appendix A ( Compaq AlphaServer SC Interconnect Terms ) ) has an entry in the elites table. Each switch has eight links and the state of each of these links is recorded in the linkstate field of the elites table. The field holds eight char...

Node Status Values node has more than one instance of each type of temperature sensor, the maximum oftheir values is recorded. Temperature information is recorded as a list of attribute-value pairs, for example: ambient=15 cpu=40 psu=20 Note that not all node types support all types of thermistor re...

Resource Status Values The current UNIX run level of a node is held in the nodes table in the runlevel field. This field is updated by the nodestatus program as the run level changes. The valid strings are shown together with their meaning in Table B.5 . Table B.5: Run Level Status Values Status Des...

Transaction Status Values jobs using the CPU s complete. While CPU s are allocated, the valid resource status strings are as shown in Table B.7 . Table B.7: Resource Status Values Status Description blocked CPU s cannot be allocated because of a usage limit queued insufficient CPU s free for the req...

C RMS Kernel Module C.1 Introduction The RMS kernel module supports the operation of RMS on each node in a system. It provides functions that bind together the set of processes that make up a program oneach node, allowing RMS to apply scheduling, signal delivery and statistics gathering operations t...

System Call Interface and the Elan hardware context numbers to be used. typedef struct elan_capability { ELAN_USERKEY UserKey; /* User defined protection */ int Version; /* Version number */ short Type; /* Type */ short Generation; /* Generation number */ int LowContext; /* low context number in blo...

rms_setcorepath(3) NAME rms_setcorepath, rms_getcorepath – Set, get the path for application core files SYNOPSIS cc [ flag ... ] file ... -lrmscall [ library ... ] #include <rms/rmscall.h> int rms_setcorepath(caddr_t path); int rms_getcorepath(pid_t pid, caddr_t path, int maxlen); PARAMETERS p...

rms_prgcreate(3) NAME rms_prgcreate, rms_prgdestroy – Create, destroy program descriptions SYNOPSIS cc [ flag ... ] file ... -lrmscall [ library ... ] #include <rms/rmscall.h> int rms_prgcreate(int id, uid_t uid, int cpus); int rms_prgdestroy(int id); PARAMETERS id Program identifier. uid Owne...

rms_prgcreate(3) EINVAL Program identifier is in use or the number of CPU s is invalid. ECHILD Processes belonging to this program are still running. EEXIST Program identifier does not exist. SEE ALSO rms_getprgid(3) RMS Kernel Module C-5

rms_prgids(3) NAME rms_prgids, rms_prginfo, rms_getprgid – Get information on a program or programs SYNOPSIS cc [ flag ... ] file ... -lrmscall [ library ... ] #include <rms/rmscall.h> int rms_prgids(int maxids, int *ids, int *nids); int rms_prginfo(int id, int maxids, pid_t *pids, int nids); ...

rms_prgids(3) EINVAL Count of number of array elements is invalid. EFAULT Array address is invalid. ENOMEM Insufficient kernel memory to perform this operation. ESRCH Process or program does not exist. SEE ALSO rms_prgcreate(3) RMS Kernel Module C-7

rms_prgsuspend(3) NAME rms_prgsuspend, rms_prgresume, rms_prgsignal – Suspend or resume the processes in a program, deliver a signal to all processes in a program SYNOPSIS cc [ flag ... ] file ... -lrmscall [ library ... ] #include <rms/rmscall.h> int rms_prgsuspend(int id); int rms_prgresume(...

rms_prgsuspend(3) EACCESS Caller is not permitted to perform this operation. ESRCH No such program identifier. EINVAL Invalid signal number. SEE ALSO rms_prgcreate(3) RMS Kernel Module C-9

rms_prgaddcap(3) NAME rms_prgaddcap, rms_setcap – Associate Elan capabilities with a program or process SYNOPSIS cc [ flag ... ] file ... -lrmscall [ library ... ] #include <rms/rmscall.h> int rms_prgaddcap(int id, int index, ELAN_CAPABILITY *cap); int rms_setcap(int index, int context); PARAM...

rms_prgaddcap(3) EACCESS Caller is not permitted to perform this operation. ENOMEM There was insufficient memory to perform this operation. ESRCH Program does not exist. EFAULT Capability has invalid address. EINVAL Invalid context number ( rms_setcap() only). SEE ALSO rms_ncaps(3) RMS Kernel Module...

rms_ncaps(3) NAME rms_ncaps, rms_getcap – Return information on the Elan capabilities allocated to a process in a parallel program SYNOPSIS cc [ flag ... ] file ... -lrmscall [ library ... ] #include <rms/rmscall.h> int rms_ncaps(int *ncaps); int rms_getcap(int index, ELAN_CAPABILITY *cap); PA...

rms_prggetstats(3) NAME rms_prggetstats – Return resource usage information for a program SYNOPSIS cc [ flag ... ] file ... -lrmscall [ library ... ] #include <rms/rmscall.h> int rms_prggetstats(int id, prgstats_t *stats); PARAMETERS id Program identifier. stats Pointer to a program statistics...

rms_prggetstats(3) The elapsed time statistic etime is the time in millisecs since the program was created. The allocated time statistic atime is the time in millisecs for which CPU s have been allocated multiplied by the number of CPU s allocated. The utime and etime statistics are summed over the ...

D RMS Application Interface D.1 Introduction The RMS application interface is provided so that external scheduling modules can make inquiries about the availability of resources, allocate and deallocate CPU s and perform job control operations. The application interface is provided as a dynamic libr...

rms_allocateResource(3) NAME rms_allocateResource, rms_deallocateResource – Allocate or deallocate a resource SYNOPSIS cc [ flag ... ] file ... -lrmsapi -lrms [ library ... ] #include <rms/rmsapi.h> int rms_allocateResource(char *partition, int cpus, int baseNode, int nodes, uid_t uid, char *p...

rms_allocateResource(3) rid ID of the resource to deallocate. DESCRIPTION rms_allocateResource() allocates CPU s from a named partition. If partition is NULL , the default partition is used, otherwise the named partition must exist. You can optionally specify the base node and the number of nodes (a...

rms_run(3) NAME rms_run – Run a program on an allocated resource SYNOPSIS cc [ flag ... ] file ... -lrmsapi -lrms [ library ... ] #include <rms/rmsapi.h> int rms_run(int rid, char *cmd, char **args, char *jobFlags); PARAMETERS rid Resource id. cmd Command to execute. args Arguments for the com...

rms_run(3) SEE ALSO rms_allocateResource(3) , RMS Application Interface D-5

rms_suspendResource(3) NAME rms_suspendResource, rms_resumeResource, rms_killResource – Job control operations on allocated resources SYNOPSIS cc [ flag ... ] file ... -lrmsapi -lrms [ library ... ] #include <rms/rmsapi.h> int rms_suspendResource(int rid); int rms_resumeResource(int rid); int ...

rms_defaultPartition(3) NAME rms_defaultPartition, rms_numCpus, rms_numNodes, rms_freeCpus – Provide information on RMS partitions SYNOPSIS cc [ flag ... ] file ... -lrmsapi -lrms [ library ... ] #include <rms/rmsapi.h> char *rms_defaultPartition(); int rms_numCpus(char *partition); int rms_nu...

E Accounting Summary Script E.1 Introduction This appendix describes the example accounting summary script included in /usr/opt/rms/examples/scripts/accounting_summary and referred to in Section 9.4.3 . • Section E.2 describes the command line interface. • Section E.3 shows a sample of output from t...

Listing of the Script -p Sort the records by project name and then by user name. This is thedefault. -M Show time in minutes rather than seconds. -H Show time in hours rather than seconds. days Show statistics for the specified number of days. By default, statisticsare shown for the previous day onl...

Listing of the Script E.4 Listing of the Script #!/bin/sh ####################################################################### # # accounting_summary # ####################################################################### usage() { echo "Usage : $sname [ -u -p -d [ -M | -H ] ] [ days ]"...

Listing of the Script # # parse the options # while [ $# -gt 0 ]; do option=‘echo $1 | sed "s/ˆ-//"‘ if [ "$option" = "$1" ]; then break fi if [ "$option" = "p" ]; then primary="project" elif [ "$option" = "u" ]; then primary="user&...

Listing of the Script starttime=‘expr $now - $daysecs‘ if [ "$primary" = "project" ]; then primarytitle="Project" secondarytitle="User" querystr="select \ acctstats.project,resources.username, \ acctstats.atime,acctstats.utime, acctstats.stime \ from resources,acc...

Listing of the Script printf ("\t %-8.8s ", secondary) } } function printdashes() { printf ("---------------------------------------------------------------------\ ----\n") } function printvals(vals, i) { for (i=1; i<=nvalues; i++) { if (hours == 1 || minutes == 1) { printf ("...

Listing of the Script printf ("Name Name Secs Secs Secs Sessions\n") } } printdashes() } primary = $1 secondary = $2 for (i=1; i<=nvalues; i++) { values[i] = 0 primvalues[i] = 0 } recs = 0 primrecs = 0 printprim = 1 } else { if ($2 != secondary) { printsortfields() printvals(values) print...

Listing of the Script printf (" %6d\n", primrecs) printdashes() printf ("Grand Total ") printvals(grandvalues) printf (" %6d\n", grandrecs) printdashes() }’ primtitle="$primarytitle" sectitle="$secondarytitle" machine=$machine \ days=$days hours=$hours minutes...

Glossary Abbreviations API Application Program Interface — specification of interface to softwarepackage (library). CFS Cluster File System — the file system for Tru64 UNIX clusters. CGI Common Gateway Interface — a standard method for generating HTML pages dynamically from an application so that a ...

HTML HyperText Markup Language — a generic markup language,comprising a set of tags, that enables structured documents to bedelivered over the World Wide Web and viewed by a browser. HTTP HyperText Transfer Protocol — a communications protocol commonlyused between a Web server and a Web browser toge...

Shmem A one-sided (put/get) inter-process communication interface used onhigh-performance parallel systems. SMP Symmetric MultiProcessor — a computer whose main memory isshared by more than one processor. SNMP Simple Network Management Protocol — a protocol used to monitorand control devices on the ...

Flit A communications cycle unit of information. HTTP cookies Cookies provide a general mechanism that HTTP server-side connections use to store and to retrieve information on the client sideof the connection. main memory The memory normally associated with the main processor, that is tosay, memory ...

slice A local copy of a global object. switch network The network constructed from the Elan cards and Elite cards. thread An independent sequence of execution. Every host process has atleast one thread. virtual memory A feature provided by the operating system, in conjunction with the MMU , that pro...

Index A access controls CPU usage, 6-5 , 7-2 memory limits, 6-4 , 7-3 , 7-5 priority, 6-5 , 7-2 records, 6-2 system services, 2-5 table, 10-4 accounting record, 2-10 , 6-1 , 6-6 statistics, 10-4 allocate, 5-3 application node, 2-1 attributes cpu-poll-stats-interval, 5-29 default-priority, 5-29 grace...