Right. However, depending on how complicated your setup is, you may want to refer to the specific resource that lies on node3 rather than "node3" itself (in case you move that special resource to another machine, or setup another machine with another instance of that special resource). If you decide to go with a resource-oriented requirements specification, you would probably not name your resource "NODE3" (as I previously suggested), but something that accurately refers to your resource (i.e. "HAS_MATLAB", "HAS_PROJ1_FPGA1", etc).Try adding custom attributes to the machine's ClassAd. For example, in node3's condor_config file, add these lines:NODE3=TRUE STARTD_EXPRS=NODE3In your job's submit file, add NODE3 to the "Requirements=" line. Condor should automatically try scheduling that job on the only machine with the NODE3 attribute.There is no need to setup special ClassAds for this, just use REQUIREMENTS = ... && Machine == node3.x.y.z or REQUIREMENTS = ... && Name == node3.x.y.z
- Armen -- Armen Babikyan MIT Lincoln Laboratoryarmenb@xxxxxxxxxx . 781-981-1796