Specifies quantities of the consumable resources "consumed" by each task of a job step. The resources may be machine resources or floating resources. The syntax is:
resources=name(count) name(count) ... name(count)
where name(count) is an administrator-defined name and count, or could also be ConsumableCpus(count), ConsumableMemory(count units), or ConsumableVirtualMemory(count units). ConsumableMemory and ConsumableVirtualMemory are the only two consumable resources that can be specified with both a count and units. The count for each specified resource must be an integer greater than or equal to zero, with three exceptions: ConsumableCpus, and ConsumableMemory must be specified with a value which is greater than zero, and ConsumableVirtualMemory must be specified with a value greater than 0, and greater than or equal to the image_size. If the count is not valid, then LoadLeveler will issue an error message, and will not submit the job. The allowable units are those normally used with LoadLeveler data limits:
b bytes w words kb kilobytes (2** 10 bytes) kw kilowords (2** 10 words) mb megabytes (2** 20 bytes) mw megawords (2**20 words) gb gigabytes (2** 30 bytes) gw gigawords (2** 30 words)ConsumableMemory and ConsumableVirtualMemory values are stored in mb (megabytes) and rounded up. Therefore, the smallest amount of ConsumableMemory or ConsumableVirtualMemory which you can request is one megabyte. If no units are specified, then megabytes are assumed. However, image_size units are in kilobytes. Resources defined here that are not in the SCHEDULE_BY_RESOURCES list in the global configuration file will not affect the scheduling of the job. If the resources keyword is not specified in the job step, then the default_resources (if any) defined in the administration file for the class will be used for each task of the job step.