tofututo

package: tofu

title: tofututo(7)

text:
# tofututo(7)

## NAME
tofututo - a plain stupid tutorial for tofu.

## OBJECT
This tutorial covers the elements to master in order to be able to use tofu in an efficient way. The selected approach tries to be as much concrete, progressive and concise as possible.

## CONTENTS
PRELIMINARY STEPS

THE BASICS

Cook selections

Order your todo

Edit and feed your tasks

When things are got done

Several operations on a single line

TAGGING AND QUEUEING

Getting the right thing to work on now

A todo can hide another one

PLAY WITH MACROS

SEE ALSO

AUTHOR

## PRELIMINARY STEPS
Maybe you've already begun to play with tofu before discovering this tutorial. That's why we first go to create a separate and safe execution environment. Open a new terminal or a new console and type this ($ stands for the prompt, don't type it):

```
$ export TOFURC=/tmp/tofututorc
$ export TOFUDIR=/tmp/tofututo
```

If this one is not already set, specify also your favorite editor (unless vi is your pet):

```
$ export EDITOR=<edit_command>
```

At this point, we're sure to not break anything, so we can feed our dummy todo:

```
$ tofu next="Begin 'In Search of Lost Time'"
$ tofu next="Feed the cat before leaving"
$ tofu next="Clean the mouse"
$ tofu next="Recode getopt() in myproject-demo"
$ tofu next="Write myproject.1 and myproject.5"
$ tofu next="Recall Bob"
$ tofu next="Write the specification of myotherprojectDB"
$ tofu next="Fix the paths in MyProject.pm"
$ tofu next="Report the nasty bugs hidden in tofu"
$ tofu next="Achieve this tutorial"
$ tofu next="A last and pointless task"
```

Right, we're now ready to begin our exploration (notice that here you've already learned how to create new tasks :-). Ladies and Gentlemen, follow the guide...

## THE BASICS
In this section, we will introduce the set of functionnalities commonly needed for a daily use of tofu.

### Cook selections
As you can see if you enter it in your terminal, tofu invoked alone always prints the whole todo list. The first thing we will see is thus how to make more precise selections.

The easiest way to get a set of tasks is to call them by their position in the todo, enter this in your terminal:

```
$ tofu 3 2 5
```

You can also use a negative way, specifying the tasks you want to exclude and getting the others:

```
$ tofu -3 -2 -5
```

But let discover what's happens when we use the both mechanisms:

```
$ tofu 1 2 3 -3 -4 -5
```

As you can see, you get the two first tasks and the five last ones. We can deduce two things from this: 1) the -n (de-)selector is stonger than n, 2) when the selection is made exclusively from n selectors, this one is limited to the tasks selected by this way, but it's not the case when selector with a larger scope (-n means "all but") are introduced.

The first point is easy to understand and just illustrates the fact that tofu always takes the selection the most restrictive it can define. The second is more obscure though, has it any sense to use n with other ones? It has, let use them with the max=amount selector, which limits the amount of tasks selectedi, and the all one, which just call all the tasks in the selection:

```
$ tofu 7 8 9 all max=4
```

It results a selection composed from the first task plus the tasks we've explicitely selected. This shows the role of the n selectors when they are mixed with others: they create exceptions, so that the tasks selected by this way are never removed from the selection unless it's precisely requested.

### Order your todo
With tofu, the tasks are sorted by decreasing order of priority, so change the priority of a tasks is the same as change its position in the todo. The action to perform that is jump=position, try:

```
$ tofu 2 5 6 jump=1
$ tofu
```

tofu first extracts the tasks from the todo and makes a sub-list with them (it means that you could have write 6 5 2, the results would have been the same), then it inserts this one at the requested position in the remaining list. This means that the requested position doesn't refer to the one of the task which is currently at this one, but to the final position of the sub-list in the final todo. Illustration:

```
$ tofu 2 3 5 jump=4
$ tofu
```

You can see that the tasks 2, 3 and 5 are at the good position (fourth) in the current todo, but the task which was at the fourth in the previous todo is now the second one. So, keep in mind that the position are absolutely defined, not relatively to a task. It could seem not very handy at first glance, but in general it's not a problem (it's only unintuitive when the same jump both decreases and increases the priority of selected tasks).

Nevertheless, there are cases were it's handier to place the tasks relatively to another one. This can be achieved with the ride=task action:

```
$ tofu 2 3 8 ride=6
$ tofu
```

In the example above, the selection is inserted before the sixth task (which is now the seventh, due to the eighth which took a place before it). To get the same result with an absolute placing, the selection should have been sent to the fourth position.

### Edit and feed your tasks
Until now, a task has appeared to us as a mere line of text, but tofu does not limit you to this narrow format. Indeed, you have the possibility to append to each task as much further text as you want. This is very useful, for example when you know the algorithm you plan to use to realize a certain functionnality or when there are points you have absolutely to keep in mind when you modifying a certain part of code. Append text is performed with the edit action. Enter this an add some text after the first line:

```
$ tofu 1 edit
```

If, as usual, you type tofu on the command line after your editor's closed, you won't see much changes. This is normal, because default display of tofu tries to be concise. To recover the text you have entered, you have to use another display which is specified through the read action:

```
$ tofu 1 read
$ tofu 1 4 7 read
```

The first command above displays what you've written precedently, the second just aims to show you how tofu display several tasks in this mode. You can note that before each task header is inserted the position of the task, so that you can easily retrieve the ones interesting you in further tofu commands.

### When things are got done
Once you have realized a task in your todo, this one becomes useless. In the world of tofu, the way to process with such tasks is merely to definitively wipe them out. This is made through the delete action:

```
$ tofu 11 delete
```

To avoid precipitate trashing, tofu will always ask to you a confirmation and give you the possibility to read entirely the task a last time before throwing it back to the null dimension. This temperate behaviour also allows to strip a selection of tasks, deleting some and keeping others.

### Several operations on a single line
You've maybe remarked that the command lines we presented until now always put the selectors before the actions. This is merely because you can perform several selection-then-action cycles on the same line. Each time tofu detects a selector after a set of actions, it begins a new cycle. Look at this:

```
$ tofu 1 2 list 2 jump=1 1 2 list
```

As you can see, the two first tasks are primarily listed, then the second is moved to the first position, and endly we get an updated list. Trivial to understand, isn't it? Well, there is although a little subtlety, try this:

```
$ tofu 1 jump=7 list 1 list
```

Do you see the problem? in the second selection, the task should be different, as we have sent the first task to the seventh position, but it shows precisely this one at the seventh position. In fact, this is not a problem, but a solution. As matter of fact, when you begin to write a complex command line you generally know which task is which task, but after one or two jump or/and deletion it can rapidly become tricky to anticipate the position of each one. That's why tofu chooses to always refer to the initial positions in the todo, the only ones you can really know. So when you use n or -n, you can safely do it all along the line, you're sure of the task it will point on.

## TAGGING AND QUEUEING
Select tasks by position is enough to deal with todo containing few tasks, as the one we use in this tutorial. Nevertheless, if you need a todo manager software, it's probably because you expect to have a little more stuff than that. That's why we will see in this section how categorize things and create sub-todo list(s).

### Getting the right thing to work on now
The command to use to add tags is stamp=tags, let's add some on our tasks:

```
$ tofu 2 3 8 stamp=myproject,code
$ tofu 6 stamp=myotherproject,code
$ tofu 8 9 stamp=bug
$ tofu 7 10 stamp=read
$ tofu 1 4 stamp=life,pointless all
```

As you can see, the tags now appear in the digest of the tasks they are put on. This allows to easily retrieve our tasks accoding to the type of things we want to do at the moment. For example, if you want to code:

```
$ tofu wi=code
```

or, on the contrary, if after passing the day to do it, you want to do anything but not debugging nor coding:

```
$ tofu wo=code,bug
```

The new wi=tags and wo=tags we introduced respectively select and reject any task which bears at least one of the specified tags. There are also variants of them that select or reject any task which bears all of the specified tags:

```
$ tofu wil=bug,myproject digest wol=bug,myproject digest wo=read 10
```

As expected, the first cycle above shows you the eighth task while the second prints the ninth. The third cycle merely recalls you the characteristic of the individual selectors (the tenth task bears "read"), which becomes very handy used in conjonction with the tags.

To remove tags, use the erase=tags command:

```
$ tofu 1 4 erase=pointless
```

### A todo can hide another one
Tagging is a mechanism which quitely helps to deal with a large todo list. But it reaches its limits soon. For example, when you work on a project, you really don't care about the rest of your todo list and it's quickly annoying to have to remember to explicitely include or exclude this or this tag in commands. The queue=tag selector aims precisely to resolv such problems:

```
$ tofu queue=myproject
```

It creates a new list with all the tasks bearing the requested tag and masks the others. Moreover, tofu will stay in this queue as long as you don't order a change and automatically add its associated tag to the new tasks, so you can safely keep the nose in your project for hours, you don't risk to mess tasks that are not related. To get back the whole todo, simply request the main queue, which is a reserved item:

```
$ tofu queue=main
```

Note that change queue in the middle of a command line reset the individual selector references, so avoid to use them both or choose your queue in the first cycle:

```
$ tofu queue=read 1 list queue=bug 1 list 1 queue=main list
```

As you can see, each cycle above shows a different task for the same selector.

## PLAY WITH MACROS
To achieve this tutorial, we will say some words about another handy mechanism provided by tofu: the macros. If tofu becomes tour daily todo manager, you will often have to repeat the same operations, and sometimes these one are complex and long to specify. Define macros is then the solution to create shortcuts and new commands. These ones must be written into the configuration file. Edit it:

```
$ $EDITOR $TOFURC
```

Macro definitions are set through the macroname(macrobody) syntax. Each command which makes up the body is separated from the others by a period, and members of a tag list by a space. Moreover, the macros can take arguments if you let the arguments of the command which take some empty. Here are some examples (the leading # introduce comments):

```
# a shortcut for the "myproject" queue.
qmyproject(queue=myproject)
amyproject(next=, stamp=myproject code)
# (un-)highlight the tasks you want to work on.
select(stamp=workinprogress, color=1)
reject(erase=workinprogress, color=0)
qselect(queue=workinprogress)
wselect(wi=workinprogress)
# manage the todo in the tofu 2.x fashion
hset(stamp=hot, erase=cool warm, color=3)
wset(stamp=warm, erase=hot cool, color=5)
cset(stamp=cool, erase=warm hot, color=8)
hot(wi=hot)
warm(wi=warm)
cool(wi=cool)
sort(wi=cool, jump=1, wi=warm, jump=1, wi=hot, jump=1, all)
```

Once defined, the macros are used on the command line just like other commands, except that a column (:) is prepended to them:

```
$ tofu :amyproject="Recode the build system"
$ tofu :cset 6 7 :wset 2 3 :hset :sort
$ tofu 2 5 6 :select digest
```

The last examples should have taught you the purpose of the color=n command we introduced in the definition. This one is particuliary useful in macros where they are associated with tags.

## SEE ALSO
tofu(1), tofuup(1)

## AUTHOR
This tutorial written and are maintained by Sébastien Boillod. Bug/typo reports, patches, suggestions, feedbacks and so on are welcome at <sbb at tuxfamily dot org>.

This tutorial manual are published under the terms of the very permissive MIT/X11 license. The text of this one is reproduced at the head of the tofu script.


package: torque-client

title: pbs_job_attributes(7)

summary: pbs job attributes

text:
# pbs_job_attributes(7)

## NAME
pbs_job_attributes - pbs job attributes

## DESCRIPTION
A batch job has the following public attributes shown in the following list. The attributes marked with the section symbol § are required by POSIX 1003.2d: If an attribute is unset, the indicated default value is assumed.

Account_Name §

Used for accounting on some hosts. Format: string; default value: none, not used.

Checkpoint §

If supported by the server implementation and the host operating system, the checkpoint attribute determines when checkpointing will be performed by PBS on behalf of the job. The legal values for checkpoint are described under the qalter and qsub commands. Format: the strings "n", "s", "c", "c=mmmm"; default value: "u", which is unspecified.

depend

The type of inter-job dependencies specified by the job owner. Format: "type:jobid[,jobid...]"; default value: no dependencies.

Error_Path §

The final path name for the file containing the job's standard error stream. See the qsub and qalter command description for more detail. Format: "[hostname:]pathname"; default value: (job_name).e(job_number).

Execution_Time §

The time after which the job may execute. The time is maintained in seconds since Epoch. If this time has not yet been reached, the job will not be scheduled for execution and the job is said to be in wait state. Format: "[[CCwYY]MMDDhhmm[.ss]"; default value: time 0, no delay.

group_list §

A list of group_names@hosts which determines the group under which the job is run on a given host. [internal type: array of strings] When a job is to be placed into execution, the server will select a group name according to the following ordered set of rules:

1.

Select the group name from the list for which the associated host name matches the name of the execution host.

2.

Select the group name which has no associated host name, the wild card name.

3.

Use the login group for the user name under which the job will be run.

Format: "group_name[@host][,group_name[@host]...]".

Hold_Types §

The set of holds currently applied to the job. If the set is not null, the job will not be scheduled for execution and is said to be in the hold state. Note, the hold state takes precedence over the wait state. Format: string made up of the letters 'u', 's', 'o'; default value: no hold.

Job_Name §

The name assigned to the job by the qsub or qalter command. Format: string up to 15 characters, first character must be alphabetic; default value: the base name of the job script or STDIN.

Join_Path §

If the Join_Paths attribute is {TRUE}, then the job's standard error stream will be merged, inter-mixed, with the job's standard output stream and placed in the file determined by the Output_Path attribute. The Error_Path attribute is maintained, but ignored. Format: boolean, values accepted are "True", "TRUE", "true", "Y", "y", "1", "False", "FALSE", "false", "N", "n", "0"; default value: false.

Keep_Files §

If Keep_Files contains the values "o" and/or "e" the corresponding streams of the batch job will be retained on the execution host upon job termination. Keep_Files overrides the Output_Path and Error_Path attributes. Format: "o", "e", "oe" or "eo"; default value: no keep, return files to submission host.

Mail_Points §

Identifies at which state changes the server will send mail about the job. Format: string made up of the letters 'a' for abort, 'b' for beginning, and default value: 'a', send on job abort.

Mail_Users §

The set of users to whom mail may be sent when the job makes certain state changes. Format: "user@host[,user@host]"; default value: job owner only.

Output_Path §

The final path name for the file containing the job's standard output stream. See the qsub and qalter command description for more detail. Format: see error_path, default value: (job_name).o(job_number).

Priority §

The job scheduling priority assigned by the user. Format: "[+|-]nnnnn"; default value: undefined.

Rerunable §

The rerunable flag given by the user. Format: "y" or "n", see Join_Path; default value: y, job is rerunable.

Resource_List §

The list of resources required by the job. The resource list is a set of name=value strings. The meaning of name and value is server dependent. The value also establishes the limit of usage of that resource. If not set, the value for a resource may be determined by a queue or server default established by the administrator. Default value: no usage or no limit depending on specific resource.

Shell_Path_List §

A set of absolute paths of the program to process the job's script file. The list is in the format: "path[@host][,path[@host]...]". If this is null, then the user's login shell on the host of execution will be used. Default value: null, login shell.

stagein

The list of files to be staged in prior to job execution. Format: local_path@remote_host:remote_path

stageout

The list of files to be staged out after job execution. Format: local_path@remote_host:remote_path

User_List §

The list of user@hosts which determines the user name under which the job is run on a given host. [internal type: array of strings] When a job is to be placed into execution, the server will select a user name from the list according to the following ordered set of rules:

1.

Select the user name from the list for which the associated host name matches the name of the execution host.

2.

Select the user name which has no associated host name, the wild card name.

3.

Use the Job_Owner as the user name.

Default value: job owner name.

Variable_List §

This is the list of environment variables passed with the Queue Job batch request. Format: "name=value[,name=value...]".

The following attributes require system, manager, or operator privilege to set. They are visible to clients depending on privilege as noted.

comment

An attribute for displaying comments about the job from the system. Visible to any client. Format: any string; default value: none.

sched_hint

This attribute is present when the job is a member of a synchronous dependency set. It is set when the hold is released on the job. The value is {SYNC_SCHED_HINT_FIRST} (1) when the first job of the set is released for scheduling. This is a hint that may be used by the scheduler to decrease the priority of the job. This keeps a user from attempting to game the scheduler. The attribute is set to {SYNC_SCHED_HINT_OTHER} (2) for all other jobs in the set as they become schedulable. This should be taken as a hint by the scheduler to increase their priority to insure they will run at the same time as the earlier scheduled jobs in the set. [This attribute is viewable only by the batch administrator.] [type: integer]

The following attributes are read-only, they are established by the server and are visible to the client but cannot be set by a client. Certain ones are only visible to privileged clients (those run by the batch administrator).

alt_id

For a few systems, such as Irix 6.x running Array Services, the session id is insufficient to track which processes belong to the job. Where a different identifier is required, it is recorded in this attribute. If set, it will also be recorded in the end-of-job accounting record.

For Irix 6.x running Array Services, the alt_id attribute is set to the Array Session Handle (ASH) assigned to the job.

ctime

The time that the job was created.

etime

The time that the job became eligible to run, i.e. in a queued state while residing in an execution queue.

exec_host

If the job is running, this is set to the name of the host on which the job is executing.

exit_status

The exit status of the job. This is only set on receipt of a job obituary notice from MOM, and probably only useful if the "keep_completed" server attribute is set. Note that negative values are generated internally by PBS to indicate system errors and are listed as the JOB_EXEC_* defines in pbs_job.h. Positive values are returned from the user script and cannot be interpreted by PBS.

egroup

If the job is queued in an execution queue, this attribute is set to the group name under which the job is to be run. [This attribute is available only to the batch administrator.]

euser

If the job is queued in an execution queue, this attribute is set to the user name under which the job is to be run. [This attribute is available only to the batch administrator.]

hashname

The name used as a basename for various files, such as the job file, script file, and the standard output and error of the job. [This attribute is available only to the batch administrator.]

interactive

True if the job is an interactive PBS job. Format: boolean, see Join_Paths; default value: false.

Job_Owner §

The login name on the submitting host of the user who submitted the batch job.

job_state

The state of the job.

E

for exiting, the job has completed execution, with or without errors, and the batch system is doing post-execution clean-up.

H

for Held, one or more holds have been applied to the job.

Q

for Queued, the job resides in a execution or routing queue pending execution or routing. It is not in held or waiting state.

R

for Running, the job resides in a execution queue and has been placed into execution.

S

for Suspend (Job running on Unicos only), the job was executing and has been suspended. The job retains its assigned resources but does not use cpu cycle or walltime.

T

for Transiting, the job is in process of being routed or moved to a new destination.

W

for Waiting, the job is not held but the Execution_Time attribute contains a time which has not yet been reached.

mtime

The time that the job was last modified, changed state, or changed locations.

qtime

The time that the job entered the current queue.

queue

The name of the queue in which the job currently resides.

queue_rank

An ordered, non-sequential number indicating the job's position with in the queue. This is provided as an aid to the scheduler. [This attribute is available to the batch manager only.]

queue_type

An identification of the the type of queue in which the job is currently residing. This is provided as an aid to the scheduler. [This attribute is available to the batch manager only.] Format: The letter E or the letter r.

resources_used §

The amount of resources used by the job. This is provided as part of job status information if the job is running.

server

The name of the server which is currently managing the job.

session_id

If the job is running, this is set to the session id of the first executing task.

substate

A numerical indicator of the substate of the job. The substate is used by the PBS job server internally. The attribute is visible to privileged clients, such as the scheduler. Format: integer.

## SEE ALSO
PBS ERS, qsub(1B), qalter(1B), pbs_resources(7B)


title: pbs_queue_attributes(7)

summary: pbs queue attributes

text:
# pbs_queue_attributes(7)

## NAME
pbs_queue_attributes - pbs queue attributes

## DESCRIPTION
Queue public attributes are alterable on request by a client. The client must be acting for a user with administrator (manager) or operator privilege. Certain attributes require the user to have full administrator privilege before they can be modified. The following attributes apply to both queue types:

acl_group_enable

Attribute which when true directs the server to use the queue group access control list acl_groups . Format: boolean, "TRUE", "True", "true", "Y", "y", "1", "FALSE", "False", "false", "N", "n", "0"; default value: false = disabled.

acl_group_sloppy

Search a job user's secondary groups if the effective group doesn't match the group acl. Warning, this can be very slow and expensive. Format: boolean, "TRUE", "True", "true", "Y", "y", "1", "FALSE", "False", "false", "N", "n", "0"; default value: false = disabled.

acl_groups

List which allows or denies enqueuing of jobs owned by members of the listed groups. The groups in the list are groups on the server host, not submitting hosts. If acl_group_enable is set to true, only groups listed in the acl_groups attribute will be allowed access to the queue. See section 10.1, Authorization, in the PBS External Reference Specification. Format: "[+|-]group_name[,...]"; default value: all groups allowed.

acl_host_enable

Attribute which when true directs the server to use the acl_hosts access list. Format: boolean (see acl_group_enable); default value: disabled.

acl_hosts

List of hosts which may enqueue jobs in the queue. See section 10.1, Authorization, in the PBS External Reference Specification. Format: "[+|-]hostname[...]"; default value: all hosts allowed.

acl_logic_or

Modifies the way acls are applied if both acl_user_enable and acl_group_enable are set to true. If acl_logic_or is true, then user and group acls are logically OR'ed together (a job can pass either the user or group acl lists to be allowed access to the queue). If I acl_logic_or is false, then user and group acls are logically AND'ed together (a job would have to pass both user and group acl lists). Format: boolean (see acl_group_enable and acl_user_enable); default value: disabled.

acl_user_enable

Attribute which when true directs the server to use the the acl_users access list for this queue. Format: boolean (see acl_group_enable); default value: disabled.

acl_users

List of users allowed or denied the ability to enqueue jobs in this queue. See section 10.1, Authorization, in the PBS External Reference Specification. If acl_user_enable is set to true, only users listed in the acl_groups attribute will be allowed access to the queue. Format: "[+|-]user[@host][,...]"; default value: all users allowed.

disallowed_types

List of job "types" (interactive,batch,rerunable,nonrerunable,fault_tolerant,fault_intolerant) that are not allowed in this queue. default value: all types allowed.

enabled

Queue will or will not accept new jobs. When false the queue is disabled and will not accept jobs. Format: boolean (see acl_group_enable); default value: disabled.

from_route_only

When true, this queue will not accept jobs except when being routed by the server from a local routing queue. This is used to force user to submit jobs into a routing queue used to distribute jobs to other queues based on job resource limits. Format: boolean; default value: disabled.

is_transit

When true, jobs will be allowed into this queue that do not fit server resource limitations. This is to allow the jobs to be routed to a server that does have the appropriate resources. Any queue limits are checked.

max_queuable

The maximum number of jobs allowed to reside in the queue at any given time. Format: integer; default value: infinite.

max_user_queuable

The maximum number of jobs owned by a single user that are allowed to reside in the queue at any given time. Format: integer; default value: infinite.

max_running

The maximum number of jobs allowed to be selected from this queue for routing or execution at any given time. For a routing queue, this is enforced, if set, by the server. For an execution queue, this attribute is advisory to the Scheduler, it is not enforced by the server. Format: integer.

Priority

The priority of this queue against other queues of the same type on this server. May affect job selection for execution/routing. Advisory to the Scheduler, not used by the server. Format: integer.

queue_type

The type of the queue: execution or route. Format: "execution", "e", "route", "r". This attribute must be explicitly set.

resources_max

The maximum amount of each resource which can be requested by a single job in this queue. The queue value supersedes any server wide maximum limit. Format: "resources_max.resource_name=value", see qmgr(1B); default value: infinite usage.

resources_min

The minimum amount of each resource which can be requested by a single job in this queue. Format: see resources_max, default value: zero usage.

resources_default

The list of default resource values which are set as limits for a job residing in this queue and for which the job did not specify a limit. Format: "resources_default.resource_name=value", see qmgr(1B); default value: none; if not set, the default limit for a job is determined by the first of the following attributes which is set: server's resources_default, queue's resources_max, server's resources_max. If none of these are set, the job will unlimited resource usage.

started

Jobs may be scheduled for execution from this queue. When false, the queue is considered stopped. Advisory to the Scheduler, not enforced by the server. [default value: false, but depends on scheduler interpretation] Format: boolean (see acl_group_enable).

The following attributes apply only to execution queues:

checkpoint_defaults

Specifies the queues default checkpointing values to be used for a job that does not have any checkpointing specified. Format: string; default value: none.

checkpoint_min

Specifies the minimum interval of cpu time, in minutes, which is allowed between checkpoints of a job. If a user specifies a time less than this value, this value is used instead. Format: integer; default value: no minimum.

resources_available

The list of resource and amounts available to jobs running in this queue. The sum of the resource of each type used by all jobs running from this queue cannot exceed the total amount listed here. Advisory to the Scheduler, not enforced by the server. Format: "resources_available.resource_name=value", see qmgr(1B).

keep_completed

Number of seconds to retain completed jobs in the C state. This overrides the server attribute of the same name. EXPERIMENTAL Format: integer; default value: 0.

kill_delay

The amount of the time delay between the sending of SIGTERM and SIGKILL when a qdel command is issued against a running job. This overrides the server attribute of the same name. Format: integer seconds; default value: 2 seconds.

max_user_run

The maximum number of jobs owned by a single user that are allowed to be running from this queue at one time. This attribute is advisory to the Scheduler, it is not enforced by the server. Format: integer; default value: none.

max_group_run

The maximum number of jobs owned by any users in a single group that are allowed to be running from this queue at one time. This attribute is advisory to the Scheduler, it is not enforced by the server. Format: integer; default value: none.

The following attributes apply only to routing queues:

route_destinations

The list of destinations to which jobs may be routed. [default value: none, should be set to at least one valid destination]

alt_router

If true, an site supplied, alternative job router function is used to determine the destination for routing jobs from this queue. Otherwise, the default, round-robin router is used. Format: boolean (see acl_group_enable); default value: false.

route_held_jobs

If true, jobs with a hold type set may be routed from this queue. If false, held jobs are not to be routed. Format: boolean (see acl_group_enable); default value: false.

route_waiting_jobs

If true, jobs with a future execution_time attribute may be routed from this queue. If false, they are not to be routed. Format: boolean (see acl_group_enable); default value: false.

route_retry_time

Time delay between route retries. Typically used when the network between servers is down. Format: integer seconds; default value: {PBS_NET_RETRY_TIME} (30 seconds).

route_lifetime

The maximum time a job is allowed to exist in a routing queue. If the job cannot be routed in this amount of time, the job is aborted. If unset or set to a value of zero (0), the lifetime is infinite. Format: integer seconds; default infinite.

The following data items are read-only attributes of the queue. They are visible to but cannot be changed by clients.

Items which apply to all types of queues are:

total_jobs

The number of jobs currently residing in the queue.

state_count

The total number of jobs currently residing in the queue in each state.

These read-only attributes only apply to execution queues:

resources_assigned

The total amount of certain types of resources allocated to jobs running from this queue.

## SEE ALSO
the PBS ERS, qmgr(1B), pbs_resources(7B)


title: pbs_resources_aix4(7)

summary: pbs Resources on IBM AIX 4

text:
# pbs_resources_aix4(7)

## NAME
pbs_resources_aix4 - pbs Resources on IBM AIX 4

## DESCRIPTION
This page summarizes the resources supported by PBS for IBM systems running AIX version 4. These resources are specified for jobs by including them in the -l option argument on the qsub or qalter command or in the PBS job script.

## RESOURCES
cput

Maximum amount of CPU time used by all processes in the job. Units: time.

file

The largest size of any single file that may be created by the job. Units: size.

mem

Maximum amount of physical memory (workingset) used by the job. Units: size.

vmem

Maximum amount of virtual memory used by all concurrent processes in the job. Units: size.

nice

The nice value under which the job is to be run. Units: unitary.

pcput

Maximum amount of CPU time used by any single process in the job. Units: time.

pmem

Maximum amount of physical memory (workingset) used by any single process of the job. Units: size.

pvmem

Maximum amount of virtual memory used by any single process in the job. Units: size.

walltime

Maximum amount of real time during which the job can be in the running state. Units: time.

arch

Specifies the administrator defined system architecture requried. This defaults to whatever the PBS_MACH string is set to in "local.mk". Units: string.

host

Name of host on which job should be run. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

nodes

Number and/or type of nodes to be reserved for exclusive use by the job. The value is one or more node_specs joined with the '+' character, "node_spec[+node_spec...]. Each node_spec is an number of nodes required of the type declared in the node_spec and a name or one or more property or properties desired for the nodes. The number, the name, and each property in the node_spec are separated by a colon ':'. If no number is specified, one (1) is assumed. Units: string.

The name of a node is its hostname. The properties of nodes are:

.

ppn=# specifying the number of processors per node requested. Defaults to 1.

.

arbitrary string assigned by the system administrator, please check with your administrator as to the node names and properties available to you.

Examples:

.

To ask for 12 nodes of any type: -l nodes=12

.

To ask for 2 "server" nodes and 14 other nodes (a total of 16): -l nodes=2:server+14

The above consist of two node_specs "2:server" and "14".

.

To ask for (a) 1 node that is a "server" and has a "hippi" interface, (b) 10 nodes that are not servers, and (c) 3 nodes that have a large amount of memory an have hippi:

-l nodes=server:hippi+10:noserver+3:bigmem:hippi

.

To ask for three nodes by name:

-l nodes=b2005+b1803+b1813

.

To ask for 2 processors on each of four nodes:

-l nodes=4:ppn=2

.

To ask for 4 processors on one node:

-l nodes=1:ppn=4

.

To ask for 2 processors on each of two blue nodes and three processors on one red node:

-l nodes=2:blue:ppn=2+red:ppn=3

host

Allows a user to specify the desired execution location. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

other

Allows a user to specify site specific information. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

software

Allows a user to specify software required by the job. This is useful if certain software packages are only available on certain systems in the site. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

## EXAMPLES
qsub -l nodes=15,walltime=2:00:00 script

or in a qsub script as a directive:

\#PBS -l nodes=15,walltime=2:00:00

qsub -l cput=1:00:00,walltime=2:00:00,file=50gb,mem=15mb script

qalter -lcput=30:00,pmem=8mb 123.jobid

or in a qsub script as a directive:

\#PBS -l cput=1:00:00,walltime=2:00:00,file=50gb,mem=15mb

## RESOURCE UNITS
The resource values take the following units:

time

specifies a maximum time period the resource can be used. Time is expressed in seconds as an integer, or in the form:

[[hours:]minutes:]seconds[.milliseconds]

size

specifies the maximum amount in terms of bytes or words. It is expressed in the form integer[suffix] The suffix is a multiplier defined in the following table, The size of a word is the word size on the execution host.

b or w

bytes or words.

kb or kw

Kilo (1024) bytes or words.

mb or mw

Mega (1,048,576) bytes or words.

gb or gw

Giga (1,073,741,824) bytes or words.

unitary

The maximum amount of a resource which is expressed as a simple integer.

## SEE ALSO
the PBS ERS, qsub(1B), qalter(1B), pbs_submit(3B), pbs_alterjob(3B), pbs_statjob(3b) pbs_resources_irix5(7B), pbs_resources_sp2(7B), pbs_resources_sunos4(7B), pbs_resources_unicos8(7B)


title: pbs_resources_aix5(7)

summary: pbs Resources on IBM AIX 5

text:
# pbs_resources_aix5(7)

## NAME
pbs_resources_aix5 - pbs Resources on IBM AIX 5

## DESCRIPTION
This page summarizes the resources supported by PBS for IBM systems running AIX version 5. These resources are specified for jobs by including them in the -l option argument on the qsub or qalter command or in the PBS job script.

## RESOURCES
cput

Maximum amount of CPU time used by all processes in the job. Units: time.

file

The largest size of any single file that may be created by the job. Units: size.

mem

Maximum amount of physical memory (workingset) used by the job. Units: size.

vmem

Maximum amount of virtual memory used by all concurrent processes in the job. Units: size.

nice

The nice value under which the job is to be run. Units: unitary.

pcput

Maximum amount of CPU time used by any single process in the job. Units: time.

pmem

Maximum amount of physical memory (workingset) used by any single process of the job. Units: size.

pvmem

Maximum amount of virtual memory used by any single process in the job. Units: size.

walltime

Maximum amount of real time during which the job can be in the running state. Units: time.

arch

Specifies the administrator defined system architecture requried. This defaults to whatever the PBS_MACH string is set to in "local.mk". Units: string.

host

Name of host on which job should be run. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

nodes

Number and/or type of nodes to be reserved for exclusive use by the job. The value is one or more node_specs joined with the '+' character, "node_spec[+node_spec...]. Each node_spec is an number of nodes required of the type declared in the node_spec and a name or one or more property or properties desired for the nodes. The number, the name, and each property in the node_spec are separated by a colon ':'. If no number is specified, one (1) is assumed. Units: string.

The name of a node is its hostname. The properties of nodes are:

.

ppn=# specifying the number of processors per node requested. Defaults to 1.

.

arbitrary string assigned by the system administrator, please check with your administrator as to the node names and properties available to you.

Examples:

.

To ask for 12 nodes of any type: -l nodes=12

.

To ask for 2 "server" nodes and 14 other nodes (a total of 16): -l nodes=2:server+14

The above consist of two node_specs "2:server" and "14".

.

To ask for (a) 1 node that is a "server" and has a "hippi" interface, (b) 10 nodes that are not servers, and (c) 3 nodes that have a large amount of memory an have hippi:

-l nodes=server:hippi+10:noserver+3:bigmem:hippi

.

To ask for three nodes by name:

-l nodes=b2005+b1803+b1813

.

To ask for 2 processors on each of four nodes:

-l nodes=4:ppn=2

.

To ask for 4 processors on one node:

-l nodes=1:ppn=4

.

To ask for 2 processors on each of two blue nodes and three processors on one red node:

-l nodes=2:blue:ppn=2+red:ppn=3

host

Allows a user to specify the desired execution location. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

other

Allows a user to specify site specific information. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

software

Allows a user to specify software required by the job. This is useful if certain software packages are only available on certain systems in the site. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

## EXAMPLES
qsub -l nodes=15,walltime=2:00:00 script

or in a qsub script as a directive:

\#PBS -l nodes=15,walltime=2:00:00

qsub -l cput=1:00:00,walltime=2:00:00,file=50gb,mem=15mb script

qalter -lcput=30:00,pmem=8mb 123.jobid

or in a qsub script as a directive:

\#PBS -l cput=1:00:00,walltime=2:00:00,file=50gb,mem=15mb

## RESOURCE UNITS
The resource values take the following units:

time

specifies a maximum time period the resource can be used. Time is expressed in seconds as an integer, or in the form:

[[hours:]minutes:]seconds[.milliseconds]

size

specifies the maximum amount in terms of bytes or words. It is expressed in the form integer[suffix] The suffix is a multiplier defined in the following table, The size of a word is the word size on the execution host.

b or w

bytes or words.

kb or kw

Kilo (1024) bytes or words.

mb or mw

Mega (1,048,576) bytes or words.

gb or gw

Giga (1,073,741,824) bytes or words.

unitary

The maximum amount of a resource which is expressed as a simple integer.

## SEE ALSO
the PBS ERS, qsub(1B), qalter(1B), pbs_submit(3B), pbs_alterjob(3B), pbs_statjob(3b) pbs_resources_irix5(7B), pbs_resources_sp2(7B), pbs_resources_sunos4(7B), pbs_resources_unicos8(7B)


title: pbs_resources_darwin(7)

summary: pbs resources on Darwin

text:
# pbs_resources_darwin(7)

## NAME
pbs_resources_darwin - pbs resources on Darwin

## DESCRIPTION
This page summarizes the resources supported by PBS for PC workstations running Darwin. These resources are specified by including them in the -l option argument on the qsub or qalter command or in the PBS job script.

## RESOURCES
cput

Maximum amount of CPU time used by all processes in the job. Units: time.

file

The largest size of any single file that may be created by the job. Units: size.

nice

The nice value under which the job is to be run. Units: unitary.

pcput

Maximum amount of CPU time used by any single process in the job. Units: time.

pmem

Maximum amount of physical memory (workingset) used by any single process of the job. Units: size.

pvmem

Maximum amount of virtual memory used by any single process in the job. Units: size.

vmem

Maximum amount of virtual memory used by all concurrent processes in the job. Units: size.

walltime

Maximum amount of real time during which the job can be in the running state. Units: time.

arch

Specifies the administrator defined system architecture requried. This defaults to whatever the PBS_MACH string is set to in "local.mk". Units: string.

host

Name of host on which job should be run. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

nodes

Number and/or type of nodes to be reserved for exclusive use by the job. The value is one or more node_specs joined with the '+' character, "node_spec[+node_spec...]. Each node_spec is an number of nodes required of the type declared in the node_spec and a name or one or more property or properties desired for the nodes. The number, the name, and each property in the node_spec are separated by a colon ':'. If no number is specified, one (1) is assumed. Units: string.

The name of a node is its hostname. The properties of nodes are:

.

ppn=# specifying the number of processors per node requested. Defaults to 1.

.

arbitrary string assigned by the system administrator, please check with your administrator as to the node names and properties available to you.

Examples:

.

To ask for 12 nodes of any type: -l nodes=12

.

To ask for 2 "server" nodes and 14 other nodes (a total of 16): -l nodes=2:server+14

The above consist of two node_specs "2:server" and "14".

.

To ask for (a) 1 node that is a "server" and has a "hippi" interface, (b) 10 nodes that are not servers, and (c) 3 nodes that have a large amount of memory an have hippi:

-l nodes=server:hippi+10:noserver+3:bigmem:hippi

.

To ask for three nodes by name:

-l nodes=b2005+b1803+b1813

.

To ask for 2 processors on each of four nodes:

-l nodes=4:ppn=2

.

To ask for 4 processors on one node:

-l nodes=1:ppn=4

.

To ask for 2 processors on each of two blue nodes and three processors on one red node:

-l nodes=2:blue:ppn=2+red:ppn=3

host

Allows a user to specify the desired execution location. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

other

Allows a user to specify site specific information. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

software

Allows a user to specify software required by the job. This is useful if certain software packages are only available on certain systems in the site. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

## EXAMPLES
qsub -l nodes=15,walltime=2:00:00 script

or in a qsub script as a directive:

\#PBS -l nodes=15,walltime=2:00:00

qsub -l cput=1:00:00,walltime=2:00:00,file=50gb,mem=15mb script

qalter -lcput=30:00,pmem=8mb 123.jobid

or in a qsub script as a directive:

\#PBS -l cput=1:00:00,walltime=2:00:00,file=50gb,mem=15mb

## RESOURCE UNITS
The resource values take the following units:

time

specifies a maximum time period the resource can be used. Time is expressed in seconds as an integer, or in the form:

[[hours:]minutes:]seconds[.milliseconds]

size

specifies the maximum amount in terms of bytes or words. It is expressed in the form integer[suffix] The suffix is a multiplier defined in the following table, The size of a word is the word size on the execution host.

b or w

bytes or words.

kb or kw

Kilo (1024) bytes or words.

mb or mw

Mega (1,048,576) bytes or words.

gb or gw

Giga (1,073,741,824) bytes or words.

unitary

The maximum amount of a resource which is expressed as a simple integer.

## SEE ALSO
the PBS ERS, qsub(1B), qalter(1B), pbs_submit(3B), pbs_alterjob(3B), pbs_statjob(3b) pbs_resources_aix4(7B), pbs_resources_sp2(7B), pbs_resources_sunos4(7B), pbs_resources_unicos8(7B)


title: pbs_resources_digitalunix(7)

summary: pbs resources on DEC Unix

text:
# pbs_resources_digitalunix(7)

## NAME
pbs_resources_digitalunix - pbs resources on DEC Unix

## DESCRIPTION
This page summarizes the resources supported by PBS for DEC systems running Digital Unix 5. These resources are specified by including them in the -l option argument on the qsub or qalter command or in the PBS job script.

## RESOURCES
cput

Maximum amount of CPU time used by all processes in the job. Units: time.

file

The largest size of any single file that may be created by the job. Units: size.

nice

The nice value under which the job is to be run. Units: unitary.

pcput

Maximum amount of CPU time used by any single process in the job. Units: time.

pvmem

Maximum amount of virtual memory used by any single process in the job. Units: size.

vmem

Maximum amount of virtual memory used by all concurrent processes in the job. Units: size.

walltime

Maximum amount of real time during which the job can be in the running state. Units: time.

arch

Specifies the administrator defined system architecture requried. This defaults to whatever the PBS_MACH string is set to in "local.mk". Units: string.

host

Name of host on which job should be run. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

nodes

Number and/or type of nodes to be reserved for exclusive use by the job. The value is one or more node_specs joined with the '+' character, "node_spec[+node_spec...]. Each node_spec is an number of nodes required of the type declared in the node_spec and a name or one or more property or properties desired for the nodes. The number, the name, and each property in the node_spec are separated by a colon ':'. If no number is specified, one (1) is assumed. Units: string.

The name of a node is its hostname. The properties of nodes are:

.

ppn=# specifying the number of processors per node requested. Defaults to 1.

.

arbitrary string assigned by the system administrator, please check with your administrator as to the node names and properties available to you.

Examples:

.

To ask for 12 nodes of any type: -l nodes=12

.

To ask for 2 "server" nodes and 14 other nodes (a total of 16): -l nodes=2:server+14

The above consist of two node_specs "2:server" and "14".

.

To ask for (a) 1 node that is a "server" and has a "hippi" interface, (b) 10 nodes that are not servers, and (c) 3 nodes that have a large amount of memory an have hippi:

-l nodes=server:hippi+10:noserver+3:bigmem:hippi

.

To ask for three nodes by name:

-l nodes=b2005+b1803+b1813

.

To ask for 2 processors on each of four nodes:

-l nodes=4:ppn=2

.

To ask for 4 processors on one node:

-l nodes=1:ppn=4

.

To ask for 2 processors on each of two blue nodes and three processors on one red node:

-l nodes=2:blue:ppn=2+red:ppn=3

host

Allows a user to specify the desired execution location. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

other

Allows a user to specify site specific information. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

software

Allows a user to specify software required by the job. This is useful if certain software packages are only available on certain systems in the site. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

## EXAMPLES
qsub -l nodes=15,walltime=2:00:00 script

or in a qsub script as a directive:

\#PBS -l nodes=15,walltime=2:00:00

qsub -l cput=1:00:00,walltime=2:00:00,file=50gb,mem=15mb script

qalter -lcput=30:00,pmem=8mb 123.jobid

or in a qsub script as a directive:

\#PBS -l cput=1:00:00,walltime=2:00:00,file=50gb,mem=15mb

## RESOURCE UNITS
The resource values take the following units:

time

specifies a maximum time period the resource can be used. Time is expressed in seconds as an integer, or in the form:

[[hours:]minutes:]seconds[.milliseconds]

size

specifies the maximum amount in terms of bytes or words. It is expressed in the form integer[suffix] The suffix is a multiplier defined in the following table, The size of a word is the word size on the execution host.

b or w

bytes or words.

kb or kw

Kilo (1024) bytes or words.

mb or mw

Mega (1,048,576) bytes or words.

gb or gw

Giga (1,073,741,824) bytes or words.

unitary

The maximum amount of a resource which is expressed as a simple integer.

## SEE ALSO
the PBS ERS, qsub(1B), qalter(1B), pbs_submit(3B), pbs_alterjob(3B), pbs_statjob(3b) pbs_resources_aix4(7B), pbs_resources_sp2(7B), pbs_resources_sunos4(7B), pbs_resources_unicos8(7B)


title: pbs_resources_freebsd(7)

summary: pbs resources on FreeBSD

text:
# pbs_resources_freebsd(7)

## NAME
pbs_resources_freebsd - pbs resources on FreeBSD

## DESCRIPTION
This page summarizes the resources supported by PBS for AMD/Intel/Cyrix workstations running FreeBSD. These resources are specified by including them in the -l option argument on the qsub or qalter command or in the PBS job script.

## RESOURCES
cput

Maximum amount of CPU time used by all processes in the job. Units: time.

file

The largest size of any single file that may be created by the job. Units: size.

nice

The nice value under which the job is to be run. Units: unitary.

pcput

Maximum amount of CPU time used by any single process in the job. Units: time.

pmem

Maximum amount of physical memory (workingset) used by any single process of the job. Units: size.

pvmem

Maximum amount of virtual memory used by any single process in the job. Units: size.

vmem

Maximum amount of virtual memory used by all concurrent processes in the job. Units: size.

walltime

Maximum amount of real time during which the job can be in the running state. Units: time.

arch

Specifies the administrator defined system architecture requried. This defaults to whatever the PBS_MACH string is set to in "local.mk". Units: string.

host

Name of host on which job should be run. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

nodes

Number and/or type of nodes to be reserved for exclusive use by the job. The value is one or more node_specs joined with the '+' character, "node_spec[+node_spec...]. Each node_spec is an number of nodes required of the type declared in the node_spec and a name or one or more property or properties desired for the nodes. The number, the name, and each property in the node_spec are separated by a colon ':'. If no number is specified, one (1) is assumed. Units: string.

The name of a node is its hostname. The properties of nodes are:

.

ppn=# specifying the number of processors per node requested. Defaults to 1.

.

arbitrary string assigned by the system administrator, please check with your administrator as to the node names and properties available to you.

Examples:

.

To ask for 12 nodes of any type: -l nodes=12

.

To ask for 2 "server" nodes and 14 other nodes (a total of 16): -l nodes=2:server+14

The above consist of two node_specs "2:server" and "14".

.

To ask for (a) 1 node that is a "server" and has a "hippi" interface, (b) 10 nodes that are not servers, and (c) 3 nodes that have a large amount of memory an have hippi:

-l nodes=server:hippi+10:noserver+3:bigmem:hippi

.

To ask for three nodes by name:

-l nodes=b2005+b1803+b1813

.

To ask for 2 processors on each of four nodes:

-l nodes=4:ppn=2

.

To ask for 4 processors on one node:

-l nodes=1:ppn=4

.

To ask for 2 processors on each of two blue nodes and three processors on one red node:

-l nodes=2:blue:ppn=2+red:ppn=3

host

Allows a user to specify the desired execution location. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

other

Allows a user to specify site specific information. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

software

Allows a user to specify software required by the job. This is useful if certain software packages are only available on certain systems in the site. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

## EXAMPLES
qsub -l nodes=15,walltime=2:00:00 script

or in a qsub script as a directive:

\#PBS -l nodes=15,walltime=2:00:00

qsub -l cput=1:00:00,walltime=2:00:00,file=50gb,mem=15mb script

qalter -lcput=30:00,pmem=8mb 123.jobid

or in a qsub script as a directive:

\#PBS -l cput=1:00:00,walltime=2:00:00,file=50gb,mem=15

## RESOURCE UNITS
The resource values take the following units:

time

specifies a maximum time period the resource can be used. Time is expressed in seconds as an integer, or in the form:

[[hours:]minutes:]seconds[.milliseconds]

size

specifies the maximum amount in terms of bytes or words. It is expressed in the form integer[suffix] The suffix is a multiplier defined in the following table, The size of a word is the word size on the execution host.

b or w

bytes or words.

kb or kw

Kilo (1024) bytes or words.

mb or mw

Mega (1,048,576) bytes or words.

gb or gw

Giga (1,073,741,824) bytes or words.

unitary

The maximum amount of a resource which is expressed as a simple integer.

## SEE ALSO
the PBS ERS, qsub(1B), qalter(1B), pbs_submit(3B), pbs_alterjob(3B), pbs_statjob(3b) pbs_resources_aix4(7B), pbs_resources_irix5(7B) pbs_resources_sunos4(7B), pbs_resources_unicos8(7B)


title: pbs_resources_fujitsu(7)

summary: pbs resources on Fujitsu UXP/V

text:
# pbs_resources_fujitsu(7)

## NAME
pbs_resources_fujitsu - pbs resources on Fujitsu UXP/V

## DESCRIPTION
This page summarizes the resources supported by PBS for Fujitsu computers running UXP/V. These resources are specified by including them in the -l option argument on the qsub or qalter command or in the PBS job script.

## RESOURCES
cput

Maximum amount of CPU time used by all processes in the job. Units: time.

file

The largest size of any single file that may be created by the job. Units: size.

nice

The nice value under which the job is to be run. Units: unitary.

pcput

Maximum amount of CPU time used by any single process in the job. Units: time.

pvmem

Maximum amount of virtual memory used by any single process in the job. Units: size.

vmem

Maximum amount of virtual memory used by all concurrent processes in the job. Units: size.

walltime

Maximum amount of real time during which the job can be in the running state. Units: time.

arch

Specifies the administrator defined system architecture requried. This defaults to whatever the PBS_MACH string is set to in "local.mk". Units: string.

host

Name of host on which job should be run. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

nodes

Number and/or type of nodes to be reserved for exclusive use by the job. The value is one or more node_specs joined with the '+' character, "node_spec[+node_spec...]. Each node_spec is an number of nodes required of the type declared in the node_spec and a name or one or more property or properties desired for the nodes. The number, the name, and each property in the node_spec are separated by a colon ':'. If no number is specified, one (1) is assumed. Units: string.

The name of a node is its hostname. The properties of nodes are:

.

ppn=# specifying the number of processors per node requested. Defaults to 1.

.

arbitrary string assigned by the system administrator, please check with your administrator as to the node names and properties available to you.

Examples:

.

To ask for 12 nodes of any type: -l nodes=12

.

To ask for 2 "server" nodes and 14 other nodes (a total of 16): -l nodes=2:server+14

The above consist of two node_specs "2:server" and "14".

.

To ask for (a) 1 node that is a "server" and has a "hippi" interface, (b) 10 nodes that are not servers, and (c) 3 nodes that have a large amount of memory an have hippi:

-l nodes=server:hippi+10:noserver+3:bigmem:hippi

.

To ask for three nodes by name:

-l nodes=b2005+b1803+b1813

.

To ask for 2 processors on each of four nodes:

-l nodes=4:ppn=2

.

To ask for 4 processors on one node:

-l nodes=1:ppn=4

.

To ask for 2 processors on each of two blue nodes and three processors on one red node:

-l nodes=2:blue:ppn=2+red:ppn=3

host

Allows a user to specify the desired execution location. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

other

Allows a user to specify site specific information. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

software

Allows a user to specify software required by the job. This is useful if certain software packages are only available on certain systems in the site. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

## EXAMPLES
qsub -l nodes=15,walltime=2:00:00 script

or in a qsub script as a directive:

\#PBS -l nodes=15,walltime=2:00:00

qsub -l cput=1:00:00,walltime=2:00:00,file=50gb,mem=15mb script

qalter -lcput=30:00,pmem=8mb 123.jobid

or in a qsub script as a directive:

\#PBS -l cput=1:00:00,walltime=2:00:00,file=50gb,mem=15mb

## RESOURCE UNITS
The resource values take the following units:

time

specifies a maximum time period the resource can be used. Time is expressed in seconds as an integer, or in the form:

[[hours:]minutes:]seconds[.milliseconds]

size

specifies the maximum amount in terms of bytes or words. It is expressed in the form integer[suffix] The suffix is a multiplier defined in the following table, The size of a word is the word size on the execution host.

b or w

bytes or words.

kb or kw

Kilo (1024) bytes or words.

mb or mw

Mega (1,048,576) bytes or words.

gb or gw

Giga (1,073,741,824) bytes or words.

unitary

The maximum amount of a resource which is expressed as a simple integer.

## SEE ALSO
the PBS ERS, qsub(1B), qalter(1B), pbs_submit(3B), pbs_alterjob(3B), pbs_statjob(3b) pbs_resources_aix4(7B), pbs_resources_sp2(7B), pbs_resources_sunos4(7B), pbs_resources_unicos8(7B)


title: pbs_resources_hpux10(7)

summary: pbs resources on HP UX

text:
# pbs_resources_hpux10(7)

## NAME
pbs_resources_hpux10 - pbs resources on HP UX

## DESCRIPTION
This page summarizes the resources supported by PBS for systems running HP UX version 10.x. These resources are specified by including them in the -l option argument on the qsub or qalter command or in the PBS job script.

## RESOURCES
cput

Maximum amount of CPU time used by all processes in the job. Units: time.

file

The largest size of any single file that may be created by the job. Units: size.

nice

The nice value under which the job is to be run. Units: unitary.

pcput

Maximum amount of CPU time used by any single process in the job. Units: time.

pvmem

Maximum amount of virtual memory used by any single process in the job. Units: size.

vmem

Maximum amount of virtual memory used by all concurrent processes in the job. Units: size.

walltime

Maximum amount of real time during which the job can be in the running state. Units: time.

arch

Specifies the administrator defined system architecture requried. This defaults to whatever the PBS_MACH string is set to in "local.mk". Units: string.

host

Name of host on which job should be run. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

nodes

Number and/or type of nodes to be reserved for exclusive use by the job. The value is one or more node_specs joined with the '+' character, "node_spec[+node_spec...]. Each node_spec is an number of nodes required of the type declared in the node_spec and a name or one or more property or properties desired for the nodes. The number, the name, and each property in the node_spec are separated by a colon ':'. If no number is specified, one (1) is assumed. Units: string.

The name of a node is its hostname. The properties of nodes are:

.

ppn=# specifying the number of processors per node requested. Defaults to 1.

.

arbitrary string assigned by the system administrator, please check with your administrator as to the node names and properties available to you.

Examples:

.

To ask for 12 nodes of any type: -l nodes=12

.

To ask for 2 "server" nodes and 14 other nodes (a total of 16): -l nodes=2:server+14

The above consist of two node_specs "2:server" and "14".

.

To ask for (a) 1 node that is a "server" and has a "hippi" interface, (b) 10 nodes that are not servers, and (c) 3 nodes that have a large amount of memory an have hippi:

-l nodes=server:hippi+10:noserver+3:bigmem:hippi

.

To ask for three nodes by name:

-l nodes=b2005+b1803+b1813

.

To ask for 2 processors on each of four nodes:

-l nodes=4:ppn=2

.

To ask for 4 processors on one node:

-l nodes=1:ppn=4

.

To ask for 2 processors on each of two blue nodes and three processors on one red node:

-l nodes=2:blue:ppn=2+red:ppn=3

host

Allows a user to specify the desired execution location. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

other

Allows a user to specify site specific information. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

software

Allows a user to specify software required by the job. This is useful if certain software packages are only available on certain systems in the site. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

## EXAMPLES
qsub -l nodes=15,walltime=2:00:00 script

or in a qsub script as a directive:

\#PBS -l nodes=15,walltime=2:00:00

qsub -l cput=1:00:00,walltime=2:00:00,file=50gb,mem=15mb script

qalter -lcput=30:00,pmem=8mb 123.jobid

or in a qsub script as a directive:

\#PBS -l cput=1:00:00,walltime=2:00:00,file=50gb,mem=15mb

## RESOURCE UNITS
The resource values take the following units:

time

specifies a maximum time period the resource can be used. Time is expressed in seconds as an integer, or in the form:

[[hours:]minutes:]seconds[.milliseconds]

size

specifies the maximum amount in terms of bytes or words. It is expressed in the form integer[suffix] The suffix is a multiplier defined in the following table, The size of a word is the word size on the execution host.

b or w

bytes or words.

kb or kw

Kilo (1024) bytes or words.

mb or mw

Mega (1,048,576) bytes or words.

gb or gw

Giga (1,073,741,824) bytes or words.

unitary

The maximum amount of a resource which is expressed as a simple integer.

## SEE ALSO
the PBS ERS, qsub(1B), qalter(1B), pbs_submit(3B), pbs_alterjob(3B), pbs_statjob(3b) pbs_resources_aix4(7B), pbs_resources_sp2(7B), pbs_resources_sunos4(7B), pbs_resources_unicos8(7B)


title: pbs_resources_hpux11(7)

summary: pbs resources on HP UX

text:
# pbs_resources_hpux11(7)

## NAME
pbs_resources_hpux11 - pbs resources on HP UX

## DESCRIPTION
This page summarizes the resources supported by PBS for systems running HP UX version 11.x. These resources are specified by including them in the -l option argument on the qsub or qalter command or in the PBS job script.

## RESOURCES
cput

Maximum amount of CPU time used by all processes in the job. Units: time.

file

The largest size of any single file that may be created by the job. Units: size.

nice

The nice value under which the job is to be run. Units: unitary.

pcput

Maximum amount of CPU time used by any single process in the job. Units: time.

pvmem

Maximum amount of virtual memory used by any single process in the job. Units: size.

vmem

Maximum amount of virtual memory used by all concurrent processes in the job. Units: size.

walltime

Maximum amount of real time during which the job can be in the running state. Units: time.

arch

Specifies the administrator defined system architecture requried. This defaults to whatever the PBS_MACH string is set to in "local.mk". Units: string.

host

Name of host on which job should be run. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

nodes

Number and/or type of nodes to be reserved for exclusive use by the job. The value is one or more node_specs joined with the '+' character, "node_spec[+node_spec...]. Each node_spec is an number of nodes required of the type declared in the node_spec and a name or one or more property or properties desired for the nodes. The number, the name, and each property in the node_spec are separated by a colon ':'. If no number is specified, one (1) is assumed. Units: string.

The name of a node is its hostname. The properties of nodes are:

.

ppn=# specifying the number of processors per node requested. Defaults to 1.

.

arbitrary string assigned by the system administrator, please check with your administrator as to the node names and properties available to you.

Examples:

.

To ask for 12 nodes of any type: -l nodes=12

.

To ask for 2 "server" nodes and 14 other nodes (a total of 16): -l nodes=2:server+14

The above consist of two node_specs "2:server" and "14".

.

To ask for (a) 1 node that is a "server" and has a "hippi" interface, (b) 10 nodes that are not servers, and (c) 3 nodes that have a large amount of memory an have hippi:

-l nodes=server:hippi+10:noserver+3:bigmem:hippi

.

To ask for three nodes by name:

-l nodes=b2005+b1803+b1813

.

To ask for 2 processors on each of four nodes:

-l nodes=4:ppn=2

.

To ask for 4 processors on one node:

-l nodes=1:ppn=4

.

To ask for 2 processors on each of two blue nodes and three processors on one red node:

-l nodes=2:blue:ppn=2+red:ppn=3

host

Allows a user to specify the desired execution location. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

other

Allows a user to specify site specific information. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

software

Allows a user to specify software required by the job. This is useful if certain software packages are only available on certain systems in the site. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

## EXAMPLES
qsub -l nodes=15,walltime=2:00:00 script

or in a qsub script as a directive:

\#PBS -l nodes=15,walltime=2:00:00

qsub -l cput=1:00:00,walltime=2:00:00,file=50gb,mem=15mb script

qalter -lcput=30:00,pmem=8mb 123.jobid

or in a qsub script as a directive:

\#PBS -l cput=1:00:00,walltime=2:00:00,file=50gb,mem=15mb

## RESOURCE UNITS
The resource values take the following units:

time

specifies a maximum time period the resource can be used. Time is expressed in seconds as an integer, or in the form:

[[hours:]minutes:]seconds[.milliseconds]

size

specifies the maximum amount in terms of bytes or words. It is expressed in the form integer[suffix] The suffix is a multiplier defined in the following table, The size of a word is the word size on the execution host.

b or w

bytes or words.

kb or kw

Kilo (1024) bytes or words.

mb or mw

Mega (1,048,576) bytes or words.

gb or gw

Giga (1,073,741,824) bytes or words.

unitary

The maximum amount of a resource which is expressed as a simple integer.

## SEE ALSO
the PBS ERS, qsub(1B), qalter(1B), pbs_submit(3B), pbs_alterjob(3B), pbs_statjob(3b) pbs_resources_aix4(7B), pbs_resources_sp2(7B), pbs_resources_sunos4(7B), pbs_resources_unicos8(7B)


title: pbs_resources_irix5(7)

summary: pbs resources on SGI Irix

text:
# pbs_resources_irix5(7)

## NAME
pbs_resources_irix - pbs resources on SGI Irix

## DESCRIPTION
This page summarizes the resources supported by PBS for SGI workstations running IRIX 5. These resources are specified by including them in the -l option argument on the qsub or qalter command or in the PBS job script.

## RESOURCES
cput

Maximum amount of CPU time used by all processes in the job. Units: time.

file

The largest size of any single file that may be created by the job. Units: size.

nice

The nice value under which the job is to be run. Units: unitary.

pcput

Maximum amount of CPU time used by any single process in the job. Units: time.

pmem

Maximum amount of physical memory (workingset) used by any single process of the job. Units: size.

pvmem

Maximum amount of virtual memory used by any single process in the job. Units: size.

vmem

Maximum amount of virtual memory used by all concurrent processes in the job. Units: size.

walltime

Maximum amount of real time during which the job can be in the running state. Units: time.

arch

Specifies the administrator defined system architecture requried. This defaults to whatever the PBS_MACH string is set to in "local.mk". Units: string.

host

Name of host on which job should be run. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

nodes

Number and/or type of nodes to be reserved for exclusive use by the job. The value is one or more node_specs joined with the '+' character, "node_spec[+node_spec...]. Each node_spec is an number of nodes required of the type declared in the node_spec and a name or one or more property or properties desired for the nodes. The number, the name, and each property in the node_spec are separated by a colon ':'. If no number is specified, one (1) is assumed. Units: string.

The name of a node is its hostname. The properties of nodes are:

.

ppn=# specifying the number of processors per node requested. Defaults to 1.

.

arbitrary string assigned by the system administrator, please check with your administrator as to the node names and properties available to you.

Examples:

.

To ask for 12 nodes of any type: -l nodes=12

.

To ask for 2 "server" nodes and 14 other nodes (a total of 16): -l nodes=2:server+14

The above consist of two node_specs "2:server" and "14".

.

To ask for (a) 1 node that is a "server" and has a "hippi" interface, (b) 10 nodes that are not servers, and (c) 3 nodes that have a large amount of memory an have hippi:

-l nodes=server:hippi+10:noserver+3:bigmem:hippi

.

To ask for three nodes by name:

-l nodes=b2005+b1803+b1813

.

To ask for 2 processors on each of four nodes:

-l nodes=4:ppn=2

.

To ask for 4 processors on one node:

-l nodes=1:ppn=4

.

To ask for 2 processors on each of two blue nodes and three processors on one red node:

-l nodes=2:blue:ppn=2+red:ppn=3

host

Allows a user to specify the desired execution location. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

other

Allows a user to specify site specific information. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

software

Allows a user to specify software required by the job. This is useful if certain software packages are only available on certain systems in the site. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

## EXAMPLES
qsub -l nodes=15,walltime=2:00:00 script

or in a qsub script as a directive:

\#PBS -l nodes=15,walltime=2:00:00

qsub -l cput=1:00:00,walltime=2:00:00,file=50gb,mem=15mb script

qalter -lcput=30:00,pmem=8mb 123.jobid

or in a qsub script as a directive:

\#PBS -l cput=1:00:00,walltime=2:00:00,file=50gb,mem=15mb

## RESOURCE UNITS
The resource values take the following units:

time

specifies a maximum time period the resource can be used. Time is expressed in seconds as an integer, or in the form:

[[hours:]minutes:]seconds[.milliseconds]

size

specifies the maximum amount in terms of bytes or words. It is expressed in the form integer[suffix] The suffix is a multiplier defined in the following table, The size of a word is the word size on the execution host.

b or w

bytes or words.

kb or kw

Kilo (1024) bytes or words.

mb or mw

Mega (1,048,576) bytes or words.

gb or gw

Giga (1,073,741,824) bytes or words.

unitary

The maximum amount of a resource which is expressed as a simple integer.

## SEE ALSO
the PBS ERS, qsub(1B), qalter(1B), pbs_submit(3B), pbs_alterjob(3B), pbs_statjob(3b) pbs_resources_aix4(7B), pbs_resources_sp2(7B), pbs_resources_sunos4(7B), pbs_resources_unicos8(7B)


title: pbs_resources_irix6(7)

summary: pbs resources on SGI Irix

text:
# pbs_resources_irix6(7)

## NAME
pbs_resources_irix - pbs resources on SGI Irix

## DESCRIPTION
This page summarizes the resources supported by PBS for SGI workstations running IRIX 6. These resources are specified by including them in the -l option argument on the qsub or qalter command or in the PBS job script.

## RESOURCES
cput

Maximum amount of CPU time used by all processes in the job. Units: time.

file

The largest size of any single file that may be created by the job. Units: size.

ncpus

The number of processors requested. Units: unitary.

cpupercent

The maximum percentage of a cpu which the job used. A value of 100 means 1 cpu. This cannot be set, it is only reported. Units: percent.

nice

The nice value under which the job is to be run. Units: unitary.

nodemask

A bit mask specifying the nodes (a pair of processors) to be associated with this job. This resource is intended for use by PBS to optimize processor allocation and direct use of this field by the job owner is discouraged. Units: bit mask.

pcput

Maximum amount of CPU time used by any single process in the job. Units: time.

pmem

Maximum amount of physical memory (workingset) used by any single process of the job. Units: size.

pvmem

Maximum amount of virtual memory used by any single process in the job. Units: size.

vmem

Maximum amount of virtual memory used by all concurrent processes in the job. Units: size.

walltime

Maximum amount of real time during which the job can be in the running state. Units: time.

arch

Specifies the administrator defined system architecture requried. This defaults to whatever the PBS_MACH string is set to in "local.mk". Units: string.

host

Name of host on which job should be run. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

nodes

Number and/or type of nodes to be reserved for exclusive use by the job. The value is one or more node_specs joined with the '+' character, "node_spec[+node_spec...]. Each node_spec is an number of nodes required of the type declared in the node_spec and a name or one or more property or properties desired for the nodes. The number, the name, and each property in the node_spec are separated by a colon ':'. If no number is specified, one (1) is assumed. Units: string.

The name of a node is its hostname. The properties of nodes are:

.

ppn=# specifying the number of processors per node requested. Defaults to 1.

.

arbitrary string assigned by the system administrator, please check with your administrator as to the node names and properties available to you.

Examples:

.

To ask for 12 nodes of any type: -l nodes=12

.

To ask for 2 "server" nodes and 14 other nodes (a total of 16): -l nodes=2:server+14

The above consist of two node_specs "2:server" and "14".

.

To ask for (a) 1 node that is a "server" and has a "hippi" interface, (b) 10 nodes that are not servers, and (c) 3 nodes that have a large amount of memory an have hippi:

-l nodes=server:hippi+10:noserver+3:bigmem:hippi

.

To ask for three nodes by name:

-l nodes=b2005+b1803+b1813

.

To ask for 2 processors on each of four nodes:

-l nodes=4:ppn=2

.

To ask for 4 processors on one node:

-l nodes=1:ppn=4

.

To ask for 2 processors on each of two blue nodes and three processors on one red node:

-l nodes=2:blue:ppn=2+red:ppn=3

host

Allows a user to specify the desired execution location. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

other

Allows a user to specify site specific information. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

software

Allows a user to specify software required by the job. This is useful if certain software packages are only available on certain systems in the site. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

## EXAMPLES
qsub -l nodes=15,walltime=2:00:00 script

or in a qsub script as a directive:

\#PBS -l nodes=15,walltime=2:00:00

qsub -l cput=1:00:00,walltime=2:00:00,file=50gb,vmem=15mb script

qalter -lcput=30:00,pmem=8mb 123.jobid

or in a qsub script as a directive:

\#PBS -l cput=1:00:00,walltime=2:00:00,file=50gb,mem=15mb

## RESOURCE UNITS
The resource values take the following units:

time

specifies a maximum time period the resource can be used. Time is expressed in seconds as an integer, or in the form:

[[hours:]minutes:]seconds[.milliseconds]

size

specifies the maximum amount in terms of bytes or words. It is expressed in the form integer[suffix] The suffix is a multiplier defined in the following table, The size of a word is the word size on the execution host.

b or w

bytes or words.

kb or kw

Kilo (1024) bytes or words.

mb or mw

Mega (1,048,576) bytes or words.

gb or gw

Giga (1,073,741,824) bytes or words.

unitary

The maximum amount of a resource which is expressed as a simple integer.

## SEE ALSO
the PBS ERS, qsub(1B), qalter(1B), pbs_submit(3B), pbs_alterjob(3B), pbs_statjob(3b) pbs_resources_aix4(7B), pbs_resources_sp2(7B), pbs_resources_sunos4(7B), pbs_resources_unicos8(7B)


title: pbs_resources_irix6array(7)

summary: pbs resources on SGI Irix

text:
# pbs_resources_irix6array(7)

## NAME
pbs_resources_irix - pbs resources on SGI Irix

## DESCRIPTION
This page summarizes the resources supported by PBS for SGI workstations running IRIX 6. These resources are specified by including them in the -l option argument on the qsub or qalter command or in the PBS job script.

## RESOURCES
cput

Maximum amount of CPU time used by all processes in the job. Units: time.

file

The largest size of any single file that may be created by the job. Units: size.

ncpus

The number of processors requested. Units: unitary.

cpupercent

The maximum percentage of a cpu which the job used. A value of 100 means 1 cpu. This cannot be set, it is only reported. Units: percent.

nice

The nice value under which the job is to be run. Units: unitary.

nodemask

A bit mask specifying the nodes (a pair of processors) to be associated with this job. This resource is intended for use by PBS to optimize processor allocation and direct use of this field by the job owner is discouraged. Units: bit mask.

pcput

Maximum amount of CPU time used by any single process in the job. Units: time.

pmem

Maximum amount of physical memory (workingset) used by any single process of the job. Units: size.

pvmem

Maximum amount of virtual memory used by any single process in the job. Units: size.

vmem

Maximum amount of virtual memory used by all concurrent processes in the job. Units: size.

walltime

Maximum amount of real time during which the job can be in the running state. Units: time.

arch

Specifies the administrator defined system architecture requried. This defaults to whatever the PBS_MACH string is set to in "local.mk". Units: string.

host

Name of host on which job should be run. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

nodes

Number and/or type of nodes to be reserved for exclusive use by the job. The value is one or more node_specs joined with the '+' character, "node_spec[+node_spec...]. Each node_spec is an number of nodes required of the type declared in the node_spec and a name or one or more property or properties desired for the nodes. The number, the name, and each property in the node_spec are separated by a colon ':'. If no number is specified, one (1) is assumed. Units: string.

The name of a node is its hostname. The properties of nodes are:

.

ppn=# specifying the number of processors per node requested. Defaults to 1.

.

arbitrary string assigned by the system administrator, please check with your administrator as to the node names and properties available to you.

Examples:

.

To ask for 12 nodes of any type: -l nodes=12

.

To ask for 2 "server" nodes and 14 other nodes (a total of 16): -l nodes=2:server+14

The above consist of two node_specs "2:server" and "14".

.

To ask for (a) 1 node that is a "server" and has a "hippi" interface, (b) 10 nodes that are not servers, and (c) 3 nodes that have a large amount of memory an have hippi:

-l nodes=server:hippi+10:noserver+3:bigmem:hippi

.

To ask for three nodes by name:

-l nodes=b2005+b1803+b1813

.

To ask for 2 processors on each of four nodes:

-l nodes=4:ppn=2

.

To ask for 4 processors on one node:

-l nodes=1:ppn=4

.

To ask for 2 processors on each of two blue nodes and three processors on one red node:

-l nodes=2:blue:ppn=2+red:ppn=3

host

Allows a user to specify the desired execution location. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

other

Allows a user to specify site specific information. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

software

Allows a user to specify software required by the job. This is useful if certain software packages are only available on certain systems in the site. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

## EXAMPLES
qsub -l nodes=15,walltime=2:00:00 script

or in a qsub script as a directive:

\#PBS -l nodes=15,walltime=2:00:00

qsub -l cput=1:00:00,walltime=2:00:00,file=50gb,mem=15mb script

qalter -lcput=30:00,pmem=8mb 123.jobid

or in a qsub script as a directive:

\#PBS -l cput=1:00:00,walltime=2:00:00,file=50gb,mem=15mb

## RESOURCE UNITS
The resource values take the following units:

time

specifies a maximum time period the resource can be used. Time is expressed in seconds as an integer, or in the form:

[[hours:]minutes:]seconds[.milliseconds]

size

specifies the maximum amount in terms of bytes or words. It is expressed in the form integer[suffix] The suffix is a multiplier defined in the following table, The size of a word is the word size on the execution host.

b or w

bytes or words.

kb or kw

Kilo (1024) bytes or words.

mb or mw

Mega (1,048,576) bytes or words.

gb or gw

Giga (1,073,741,824) bytes or words.

unitary

The maximum amount of a resource which is expressed as a simple integer.

## SEE ALSO
the PBS ERS, qsub(1B), qalter(1B), pbs_submit(3B), pbs_alterjob(3B), pbs_statjob(3b) pbs_resources_aix4(7B), pbs_resources_sp2(7B), pbs_resources_sunos4(7B), pbs_resources_unicos8(7B)


title: pbs_resources_linux(7)

summary: pbs resources on Linux

text:
# pbs_resources_linux(7)

## NAME
pbs_resources_linux - pbs resources on Linux

## DESCRIPTION
This page summarizes the resources supported by PBS for PC workstations running Linux. These resources are specified by including them in the -l option argument on the qsub or qalter command or in the PBS job script.

## RESOURCES
cput

Maximum amount of CPU time used by all processes in the job. Units: time.

file

The largest size of any single file that may be created by the job. Units: size.

nice

The nice value under which the job is to be run. Units: unitary.

pcput

Maximum amount of CPU time used by any single process in the job. Units: time.

pmem

Maximum amount of physical memory (workingset) used by any single process of the job. Units: size.

pvmem

Maximum amount of virtual memory used by any single process in the job. Units: size.

vmem

Maximum amount of virtual memory used by all concurrent processes in the job. Units: size.

walltime

Maximum amount of real time during which the job can be in the running state. Units: time.

arch

Specifies the administrator defined system architecture requried. This defaults to whatever the PBS_MACH string is set to in "local.mk". Units: string.

host

Name of host on which job should be run. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

nodes

Number and/or type of nodes to be reserved for exclusive use by the job. The value is one or more node_specs joined with the '+' character, "node_spec[+node_spec...]. Each node_spec is an number of nodes required of the type declared in the node_spec and a name or one or more property or properties desired for the nodes. The number, the name, and each property in the node_spec are separated by a colon ':'. If no number is specified, one (1) is assumed. Units: string.

The name of a node is its hostname. The properties of nodes are:

.

ppn=# specifying the number of processors per node requested. Defaults to 1.

.

arbitrary string assigned by the system administrator, please check with your administrator as to the node names and properties available to you.

Examples:

.

To ask for 12 nodes of any type: -l nodes=12

.

To ask for 2 "server" nodes and 14 other nodes (a total of 16): -l nodes=2:server+14

The above consist of two node_specs "2:server" and "14".

.

To ask for (a) 1 node that is a "server" and has a "hippi" interface, (b) 10 nodes that are not servers, and (c) 3 nodes that have a large amount of memory an have hippi:

-l nodes=server:hippi+10:noserver+3:bigmem:hippi

.

To ask for three nodes by name:

-l nodes=b2005+b1803+b1813

.

To ask for 2 processors on each of four nodes:

-l nodes=4:ppn=2

.

To ask for 4 processors on one node:

-l nodes=1:ppn=4

.

To ask for 2 processors on each of two blue nodes and three processors on one red node:

-l nodes=2:blue:ppn=2+red:ppn=3

host

Allows a user to specify the desired execution location. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

other

Allows a user to specify site specific information. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

software

Allows a user to specify software required by the job. This is useful if certain software packages are only available on certain systems in the site. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

## EXAMPLES
qsub -l nodes=15,walltime=2:00:00 script

or in a qsub script as a directive:

\#PBS -l nodes=15,walltime=2:00:00

qsub -l cput=1:00:00,walltime=2:00:00,file=50gb,mem=15mb script

qalter -lcput=30:00,pmem=8mb 123.jobid

or in a qsub script as a directive:

\#PBS -l cput=1:00:00,walltime=2:00:00,file=50gb,mem=15mb

## RESOURCE UNITS
The resource values take the following units:

time

specifies a maximum time period the resource can be used. Time is expressed in seconds as an integer, or in the form:

[[hours:]minutes:]seconds[.milliseconds]

size

specifies the maximum amount in terms of bytes or words. It is expressed in the form integer[suffix] The suffix is a multiplier defined in the following table, The size of a word is the word size on the execution host.

b or w

bytes or words.

kb or kw

Kilo (1024) bytes or words.

mb or mw

Mega (1,048,576) bytes or words.

gb or gw

Giga (1,073,741,824) bytes or words.

unitary

The maximum amount of a resource which is expressed as a simple integer.

## SEE ALSO
the PBS ERS, qsub(1B), qalter(1B), pbs_submit(3B), pbs_alterjob(3B), pbs_statjob(3b) pbs_resources_aix4(7B), pbs_resources_sp2(7B), pbs_resources_sunos4(7B), pbs_resources_unicos8(7B)


title: pbs_resources_netbsd(7)

summary: pbs resources on NetBSD

text:
# pbs_resources_netbsd(7)

## NAME
pbs_resources_netbsd - pbs resources on NetBSD

## DESCRIPTION
This page summarizes the resources supported by PBS for workstations running NetBSD on various hardware architectures. These resources are specified by including them in the -l option argument on the qsub or qalter command or in the PBS job script.

## RESOURCES
cput

Maximum amount of CPU time used by all processes in the job. Units: time.

file

The largest size of any single file that may be created by the job. Units: size.

nice

The nice value under which the job is to be run. Units: unitary.

pcput

Maximum amount of CPU time used by any single process in the job. Units: time.

pmem

Maximum amount of physical memory (workingset) used by any single process of the job. Units: size.

pvmem

Maximum amount of virtual memory used by any single process in the job. Units: size.

vmem

Maximum amount of virtual memory used by all concurrent processes in the job. Units: size.

walltime

Maximum amount of real time during which the job can be in the running state. Units: time.

arch

Specifies the administrator defined system architecture requried. This defaults to whatever the PBS_MACH string is set to in "local.mk". Units: string.

host

Name of host on which job should be run. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

nodes

Number and/or type of nodes to be reserved for exclusive use by the job. The value is one or more node_specs joined with the '+' character, "node_spec[+node_spec...]. Each node_spec is an number of nodes required of the type declared in the node_spec and a name or one or more property or properties desired for the nodes. The number, the name, and each property in the node_spec are separated by a colon ':'. If no number is specified, one (1) is assumed. Units: string.

The name of a node is its hostname. The properties of nodes are:

.

ppn=# specifying the number of processors per node requested. Defaults to 1.

.

arbitrary string assigned by the system administrator, please check with your administrator as to the node names and properties available to you.

Examples:

.

To ask for 12 nodes of any type: -l nodes=12

.

To ask for 2 "server" nodes and 14 other nodes (a total of 16): -l nodes=2:server+14

The above consist of two node_specs "2:server" and "14".

.

To ask for (a) 1 node that is a "server" and has a "hippi" interface, (b) 10 nodes that are not servers, and (c) 3 nodes that have a large amount of memory an have hippi:

-l nodes=server:hippi+10:noserver+3:bigmem:hippi

.

To ask for three nodes by name:

-l nodes=b2005+b1803+b1813

.

To ask for 2 processors on each of four nodes:

-l nodes=4:ppn=2

.

To ask for 4 processors on one node:

-l nodes=1:ppn=4

.

To ask for 2 processors on each of two blue nodes and three processors on one red node:

-l nodes=2:blue:ppn=2+red:ppn=3

host

Allows a user to specify the desired execution location. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

other

Allows a user to specify site specific information. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

software

Allows a user to specify software required by the job. This is useful if certain software packages are only available on certain systems in the site. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

## EXAMPLES
qsub -l nodes=15,walltime=2:00:00 script

or in a qsub script as a directive:

\#PBS -l nodes=15,walltime=2:00:00

qsub -l cput=1:00:00,walltime=2:00:00,file=50gb,mem=15mb script

qalter -lcput=30:00,pmem=8mb 123.jobid

or in a qsub script as a directive:

\#PBS -l cput=1:00:00,walltime=2:00:00,file=50gb,mem=15

## RESOURCE UNITS
The resource values take the following units:

time

specifies a maximum time period the resource can be used. Time is expressed in seconds as an integer, or in the form:

[[hours:]minutes:]seconds[.milliseconds]

size

specifies the maximum amount in terms of bytes or words. It is expressed in the form integer[suffix] The suffix is a multiplier defined in the following table, The size of a word is the word size on the execution host.

b or w

bytes or words.

kb or kw

Kilo (1024) bytes or words.

mb or mw

Mega (1,048,576) bytes or words.

gb or gw

Giga (1,073,741,824) bytes or words.

unitary

The maximum amount of a resource which is expressed as a simple integer.

## SEE ALSO
the PBS ERS, qsub(1B), qalter(1B), pbs_submit(3B), pbs_alterjob(3B), pbs_statjob(3b) pbs_resources_aix4(7B), pbs_resources_irix5(7B) pbs_resources_sunos4(7B), pbs_resources_unicos8(7B)