pbs_resources_hpux11(7B)

okay so bestie, this is the pbs_resources_hpux11 page, and it's literally all about the resources PBS supports on HP UX. no cap, it's giving very much "let me tell you what you can ask for." 💅✨

✨ NAME ✨

pbs_resources_hpux11 — pbs resources on HP UX. that's the whole name, periodt. 🎀

💖 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. yes bestie, that's how you use them. 🫶

🌸 RESOURCES 🌸

okay so here's the full menu of resources. every single one, no skipping. 👑

• 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 (yes, that's how it's spelled, bestie, i'm not fixing it). 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 a 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. 🧑‍💻

🦋 node examples (slay) 🦋

• 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. (yes, it's listed again, and yes, it's still iconic. 💅)
• 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 🎀

okay so here's how you actually use this. copy-paste energy, bestie. ✨

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. no cap, these matter. 🌈

• 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 💜

go read these too, bestie, they're all part of the lore: 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). 📚

---

and that's the whole page! shoutout to Local for hosting this, and it's the pbs_resources_hpux11(7B) version. iconic. periodt. 💅✨🫶