1CONDOR_TRANSFORM_ADS(1)         HTCondor Manual        CONDOR_TRANSFORM_ADS(1)
2
3
4

NAME

6       condor_transform_ads - HTCondor Manual
7
8       Transform  ClassAds according to specified rules, and output the trans‐
9       formed ClassAds.
10
11

SYNOPSIS

13       condor_transform_ads [-help [rules] ]
14
15       condor_transform_ads  [-rules  rules-file]  [-jobtransforms  name-list]
16       [-jobroute  route-name]  [-in[:<form>]   **  *infile*]  [-out[:<form>[,
17       nosort]]  ** outfile] [<key>=<value> ] [-long ] [-json ] [-xml ] [-ver‐
18       bose ] [-terse ] [-debug ] [-unit-test ] [-testing ] [-convertoldroutes
19       ] [infile1 ...infileN ]
20
21       Note that one or more transforms must be specified in  the  form  of  a
22       rules  file  or a JOB_TRANSFORM_ or JOB_ROUTER_ROUTE_ name and at least
23       one input file must be specified. Transforms will be applied in the or‐
24       der  they  are given on the command line.  If a rules file has a TRANS‐
25       FORM statement with arguments it must be the last rules  file.   If  no
26       output file is specified, output will be written to stdout.
27

DESCRIPTION

29       condor_transform_ads  reads  ClassAds from a set of input files, trans‐
30       forms them according to rules defined in a rules  files  or  read  from
31       configuration, and outputs the resulting transformed ClassAds.
32
33       See  the  classads/transforms:Classad Transforms section for a descrip‐
34       tion of the transform language.
35

OPTIONS

37          -help [rules]
38                 Display usage information and exit. -help rules displays  in‐
39                 formation about the available transformation rules.
40
41          -rules rules-file
42                 Specifies  the file containing definitions of the transforma‐
43                 tion rules,  or  configuration  that  declares  a  JOB_TRANS‐
44                 FORM_<name>  or JOB_ROUTER_ROUTE_<name> variable for use in a
45                 subsequent -jobtransforms <name> or  -jobroute  <name>  argu‐
46                 ment.
47
48          -jobtransforms name-list
49                 A  comma-separated  list of more transform names.  The trans‐
50                 form rules will be read from a previous  rules  file  or  the
51                 configured JOB_TRANSFORM_<name> values
52
53          -jobroute name
54                 A  job route.  The transform rules will be read from a previ‐
55                 ous rules file or the configured JOB_ROUTER_ROUTE_<name> val‐
56                 ues
57
58          -in[:<form>] infile
59                 Specifies  an  input  file containing ClassAd(s) to be trans‐
60                 formed.  <form>, if specified, is one of:
61
62long: traditional long form (default)
63
64xml: XML form
65
66json: JSON ClassAd form
67
68new: "new" ClassAd form without newlines
69
70auto: guess format by reading the input
71                 If - is specified for infile, input is read from stdin.
72
73
74          -out[:<form>[, nosort] outfile
75                 Specifies an output file to  receive  the  transformed  Clas‐
76                 sAd(s).  <form>, if specified, is one of:
77
78long: traditional long form (default)
79
80xml: XML form
81
82json: JSON ClassAd form
83
84new: "new" ClassAd form without newlines
85
86auto: use the same format as the first input
87                 ClassAds are storted by attribute unless nosort is specified.
88
89
90          [<key>=<value> ]
91                 Assign  key/value  pairs  before rules file is parsed; can be
92                 used to pass arguments to rules. (More detail needed here.)
93
94          -long  Use long form for both input and output ClassAd(s). (This  is
95                 the default.)
96
97          -json  Use JSON form for both input and output ClassAd(s).
98
99          -xml   Use XML form for both input and output ClassAd(s).
100
101          -verbose
102                 Verbose  mode, echo to stderr the transform names as they are
103                 applied and individual transform rules as they are executed.
104
105          -terse Disable the -verbose option.
106
107          -debug Causes debugging information to be sent to stderr,  based  on
108                 the value of the configuration variable TOOL_DEBUG.
109

EXIT STATUS

111       condor_transform_ads  will  exit  with  a status value of 0 (zero) upon
112       success, and it will exit with the value 1 (one) upon failure.
113

EXAMPLES

115       Here's a simple example that transforms the given  input  ClassAds  ac‐
116       cording to the given rules:
117
118          # File: my_input
119          ResidentSetSize = 500
120          DiskUsage = 2500000
121          NumCkpts = 0
122          TransferrErr = false
123          Err = "/dev/null"
124
125          # File: my_rules
126          EVALSET MemoryUsage ( ResidentSetSize / 100 )
127          EVALMACRO WantDisk = ( DiskUsage * 2 )
128          SET RequestDisk ( $(WantDisk) / 1024 )
129          RENAME NumCkpts NumCheckPoints
130          DELETE /(.+)Err/
131
132          # Command:
133          condor_transform_ads -rules my_rules -in my_input
134
135          # Output:
136          DiskUsage = 2500000
137          Err = "/dev/null"
138          MemoryUsage = 5
139          NumCheckPoints = 0
140          RequestDisk = ( 5000000 / 1024 )
141          ResidentSetSize = 500
142

AUTHOR

144       HTCondor Team
145
147       1990-2023,  Center for High Throughput Computing, Computer Sciences De‐
148       partment, University of Wisconsin-Madison, Madison,  WI,  US.  Licensed
149       under the Apache License, Version 2.0.
150
151
152
153
154                                 Oct 02, 2023          CONDOR_TRANSFORM_ADS(1)
Impressum