...
Since a job requirement can include a number of operator characters, any reference to a property or resource that includes an operator should be quoted so the interpreter can differentiate between the literal character and the operator.
Example
$ qbsub --requirements "host.kernel_version eq '2.6.17-1.2142_FC4smp'"
...
Here are some examples of job requirements that include property expressions:
% qbsub --requirements "host.os eq linux" ls % qbsub --requirements "host.name eq host01" ls % qbsub --requirements "host.flag.remove_logs host.group has host05" ls % qbsub --requirements "(host.os == 'winnt') and host.processor_speed >= 100" ls
Resource operands
are slightly different and include those defined by your administrator host.
...
Here is an example of a job requirement that uses a host resource expression:
% qbsub --requirements "host.processors.total > 10" ls
Job operands
The possible operands for a job.type are:
...
Here are examples of job requirements that use job resource expressions:
% qbsub --requirements "job.type in host.jobtypes" ls
% qbsub --requirements "job.user eq host.name" ls
Requirements Expressions - Advanced
...
Examples
More advanced uses of the requirements expression allow Qube! users to route a job to a specific host and also conversely restrict a job from a host.
...