|=DELETE /<regex>/=|Delete attributes matching =<regex>=|
|=EVALMACRO <key> <expr>=|Evaluate =<expr>= and then insert it as a transform macro value|
-Optionally, a transform rule set can end with an iteration command
-
-=TRANSFORM [<N>] [<vars>] [in <list> {quote:|} from <file> {quote:|} matching <pattern>]=
-
In the above commands =<attr>= must be a valid attribute name and =<expr>= a valid {quote: ClassAd}
expression or literal. The various $() macros will be expanded in =<expr>=, =<newattr>= or
=<newattrs>= before they are parsed as {quote: ClassAd} expressions or attribute names.
@@ -32,6 +28,10 @@
When a =COPY=,=RENAME= or =DELETE= with =<regex>= is used, regex capture groups are substituted in
=<newattrs>= after $() expansion. \0 will expand to the entire match, \1 to the first capture, etc.
+Optionally, a transform rule set can end with an iteration command
+
+=TRANSFORM [<N>] [<vars>] [in <list> {quote:|} from <file> {quote:|} matching <pattern>]=
+
A =TRANSFORM= command must be the last command in the rules file. It takes the same options as the
=QUEUE= statement from a HTCONDOR submit file. There is an implicit =TRANSFORM 1= at the end of a rules file
that has no explicit =TRANSFORM= command.
