data_limit, file_limit, core_limit, stack_limit, rss_limit: 64-bit integer values may be assigned to these limits. Fractional specifications are allowed and will be converted to 64-bit integer values. Unit specifications are accepted. In LoadLeveler 2.2, the units may be one of the following: b, w, kb, kw, mb, mw, gb, gw. In LoadLeveler 3.1, the unit specifications may also include tb (terabyte: 2**40 bytes), tw (teraword: 2**42 bytes), pb (petabyte: 2**50 bytes), pw (petaword: 2**52 bytes), eb (exabyte: 2**60 bytes), ew (exaword: 2**62 bytes).
Examples:
data_limit = 25.5tb,8.25gb file_limit = 1.2eb,8pb
| Note: | In LoadLeveler 3.1, the hard and soft time limits associated with the keywords cpu_limit, job_cpu_limit, wall_clock_limit, ckpt_time_limit remain 32-bit integers. If a value beyond the range of an int32_t data type is assigned to one of these limits, it will be truncated to either INT32_MAX (2147483647) or INT32_MIN (-2147483648). |
resources: Consumable resources associated with the resources keyword may be assigned 64-bit integer values. Fractional specifications are not allowed. Unit specifications are valid only when specifying the values of the predefined ConsumableMemory and ConsumableVirtualMemory resources.
Examples:
resources = spice2g6(123456789012) ConsumableMemory(10 gb) resources = ConsumableVirtualMemory(15 pb) db2_license(1)
requirements, preferences: 64-bit integer values may be associated with the LoadLeveler variables "Memory" and "Disk" in the expressions assigned to these keywords. Fractional and unit specifications are not allowed.
Examples:
requirements = (Arch == "R6000") && (Disk > 500000000) && (Memory > 6000000000) preferences = (Disk > 6000000000) && (Memory > 9000000000)
image_size: 64-bit integer values may be assigned to this keyword. Fractional and unit specifications are not allowed. The default unit of image_size is kb.
Example:
image_size = 12345678901
| Note: | LoadLeveler and NQS job command keywords: If your LoadLeveler cluster interacts with an NQS system, some mappings of keywords and values may occur as information is transferred between the two systems. 64-bit integer values in a LoadLeveler job command file will be mapped to 64-bit integer values in an NQS script. 64-bit integer values in an NQS script may be truncated when mapped to a LoadLeveler Job Command file. Truncation occurs when the corresponding LoadLeveler keywords support only 32-bit integers. |