1CONDOR_TRANSFORM_ADS(1) HTCondor Manual CONDOR_TRANSFORM_ADS(1)
2
3
4
6 condor_transform_ads - HTCondor Manual
7
8 Transform ClassAds according to specified rules, and output the trans‐
9 formed ClassAds.
10
11
13 condor_transform_ads [-help [rules] ]
14
15 condor_transform_ads -rules rules-file [-in[:<form>] ** *infile*]
16 [-out[:<form>[, nosort]] ** outfile] [<key>=<value> ] [-long ] [-json
17 ] [-xml ] [-verbose ] [-terse ] [-debug ] [-unit-test ] [-testing ]
18 [-convertoldroutes ] [infile1 ...infileN ]
19
20 Note that exactly one rules file, and at least one input file, must be
21 specified. If no output file is specified, output will be written to
22 stdout.
23
25 condor_transform_ads reads ClassAds from a set of input files, trans‐
26 forms them according to rules defined in a rules file, and outputs the
27 resulting transformed ClassAds.
28
29 See
30 https://htcondor-wiki.cs.wisc.edu/index.cgi/wiki?p=TjsAdTransformLanguage
31 for a description of the transform language.
32
34 -help [rules]
35 Display usage information and exit. -help rules displays
36 information about the available transformation rules.
37
38 -rules rules-file
39 Specifies the file containing definitions of the transforma‐
40 tion rules.
41
42 -in[:<form>] infile
43 Specifies an input file containing ClassAd(s) to be trans‐
44 formed. <form>, if specified, is one of:
45
46 · long: traditional long form (default)
47
48 · xml: XML form
49
50 · json: JSON ClassAd form
51
52 · new: "new" ClassAd form without newlines
53
54 · auto: guess format by reading the input
55 If - is specified for infile, input is read from stdin.
56
57
58 -out[:<form>[, nosort] outfile
59 Specifies an output file to receive the transformed Clas‐
60 sAd(s). <form>, if specified, is one of:
61
62 · long: traditional long form (default)
63
64 · xml: XML form
65
66 · json: JSON ClassAd form
67
68 · new: "new" ClassAd form without newlines
69
70 · auto: use the same format as the first input
71 ClassAds are storted by attribute unless nosort is specified.
72
73
74 [<key>=<value> ]
75 Assign key/value pairs before rules file is parsed; can be
76 used to pass arguments to rules. (More detail needed here.)
77
78 -long Use long form for both input and output ClassAd(s). (This is
79 the default.)
80
81 -json Use JSON form for both input and output ClassAd(s).
82
83 -xml Use XML form for both input and output ClassAd(s).
84
85 -verbose
86 Verbose mode, echo transform rules as they are executed.
87
88 -terse Disable the -verbose option.
89
90 -debug More information needed here.
91
92 -unit-test
93 More information needed here.
94
95 -testing
96 More information needed here.
97
98 -convertoldroutes
99 More information needed here.
100
102 condor_transform_ads will exit with a status value of 0 (zero) upon
103 success, and it will exit with the value 1 (one) upon failure.
104
106 Here's a simple example that transforms the given input ClassAds
107 according to the given rules:
108
109 # File: my_input
110 ResidentSetSize = 500
111 DiskUsage = 2500000
112 NumCkpts = 0
113 TransferrErr = false
114 Err = "/dev/null"
115
116 # File: my_rules
117 EVALSET MemoryUsage ( ResidentSetSize / 100 )
118 EVALMACRO WantDisk = ( DiskUsage * 2 )
119 SET RequestDisk ( $(WantDisk) / 1024 )
120 RENAME NumCkpts NumCheckPoints
121 DELETE /(.+)Err/
122
123 # Command:
124 condor_transform_ads -rules my_rules -in my_input
125
126 # Output:
127 DiskUsage = 2500000
128 Err = "/dev/null"
129 MemoryUsage = 5
130 NumCheckPoints = 0
131 RequestDisk = ( 5000000 / 1024 )
132 ResidentSetSize = 500
133
135 HTCondor Team
136
138 1990-2020, Center for High Throughput Computing, Computer Sciences
139 Department, University of Wisconsin-Madison, Madison, WI, US. Licensed
140 under the Apache License, Version 2.0.
141
142
143
144
1458.8 Aug 06, 2020 CONDOR_TRANSFORM_ADS(1)