HTCondorWiki: Using Condor Annex On Chtc

 You will also need to modify the =requirements= line.  The modification has two goals: first, to prevent your jobs from running anywhere other than CHTC or your annex; and second, to allow your job to run on either CHTC or your annex.  To accomplish the first goal, add the following clause to the =requirements= line, changing "MyFirstAnnex" to the name of your annex, if different:
 
 {verbatim}
-(AnnexName =?= "MyFirstAnnex" || IsCHTC)
+(AnnexName == "MyFirstAnnex" || TARGET.PoolName == "CHTC")
 {endverbatim}
 
 If the phrase "add the following clause" didn't make a lot of sense to you, the new =requirements= line should like the following, except replacing the text =<old-requirements>= with everything to the right of the equals sign in the original requirements line.
 
 {verbatim}
-requirements = (<old-requirements>) && (AnnexName =?= "MyFirstAnnex" || IsCHTC)
+requirements = (<old-requirements>) && (AnnexName =?= "MyFirstAnnex" || TARGET.PoolName == "CHTC")
 {endverbatim}
 
 As mentioned above, the default operating system for resources acquired by =condor_annex= does not advertise =OpSysMajorVer=, but is "like" EL6.  If the old requirements do not mention =OpSysMajorVer=, add the following clause to the =requirements= line:
@@ -214,9 +214,30 @@
 OpSysMajorVer =?= 6
 {endverbatim}
 
+If that's _not_ how the old requirements use =OpSysMajorVer=, ask a research computing facilitator for help.
+
 {subsection: 4.2 Modify an Idle Job}
 
-Instructions for using =condor_qedit= to follow.
+If you want a job that's already in the queue to run on your AWS resources, you can use the =condor_qedit= command to make changes much like the ones you would if you were changing a submit file.  However, to make sure your job doesn't flock to someplace you don't want it to go, you'll need to modify the =requirements= before you set =MayUseAWS= and =WantFlocking=.
+
+For these examples, we'll assume your job's ID is 100234.5.
+
+You can run =condor_q 100234.5 -af:r requirements= to examine a queued job's requirements.  When making a change, copy-and-paste the whole thing and sandwich it between single quotes (='=), as in the example below.
+
+{term}
+$ condor_q 100234.5 -af:r requirements
+(TARGET.PoolName == "CHTC") && (Target.OpSysMajorVer == 6) || (Target.OpSysMajorVer == 7)) && (OpSysName =!= "Debian") && (TARGET.Arch == "X86_64") && (TARGET.OpSys == "LINUX") && (TARGET.Disk >= RequestDisk) && (TARGET.Memory >= RequestMemory) && (TARGET.HasFileTransfer)
+$ condor_qedit 100234.5 requirements '(TARGET.AnnexName == MyFirstAnnex || TARGET.PoolName == "CHTC") && (Target.OpSysMajorVer =?= 6 || (Target.OpSysMajorVer =?= 7) ) && (OpSysName =!= "Debian") && (TARGET.Arch == "X86_64") && (TARGET.OpSys == "LINUX") && (TARGET.Disk >= RequestDisk) && (TARGET.Memory >= RequestMemory) && (TARGET.HasFileTransfer)'
+{endterm}
+
+Execute the following commands to set =MayUseAWS= and =WantFlocking= as required.  (Note that when editing a job in the queue, these attribute names are _not_ preceded by a plus ('=+=') sign.)  A reminder: this means these jobs will flock!  For now, you shouldn't use =condor_annex= if you don't want your jobs flocking.
+
+{term}
+$ condor_qedit 100234.5 MayUseAWS TRUE
+Set attribute "MayUseAWS" for 1 matching jobs.
+$ condor_qedit 100234.5 WantFlocking TRUE
+Set attribute "WantFlocking" for 1 matching jobs.
+{endterm}
 
 {section: 5 Cleaning Up (Optional)}