Re: [HTCondor-users] Access to renamed DAG node names

["R. Kent Wenger" <wenger@xxxxxxxxxxx>]

On Mon, 12 Jan 2015, Brian Candler wrote:

> Thank you. I missed $(JOB) in "DAGMan Applications" - probably because this 
> special macro can only be expanded in a VARS statement.
>
> Incidentally, quotes are needed:
> VARS NodeA nodename="$(JOB)"

Oops, sorry about forgetting the quotes...

> >  you're saying that for failed nodes you'd like to see the values of 
> output and error put directly into the JOBSTATE.LOG or NODE_STATUS files, so 
> you could find them without having to look at the submit file?
>
> Not quite; I'm saying that if a particular node fails, I want to be able to 
> read and display its associated output and error files (without having to 
> parse the DAG file to locate the submit file, then parse the submit file, 
> then expand all the nested macros and VARS)
>
> I hadn't thought of putting output/error into the JOBSTATE.LOG or NODE_STATUS 
> files; I am just planning to stick to a convention that I use <nodename>.out 
> and <nodename>.err as the names of the files, so that they are trivial to 
> find given the nodename.

Yes, if you adopt that naming convention it should be pretty easy to find 
the right file(s).

> My difficulty was in finding a way to set the input and output attributes in 
> the submit file to the right nodename, in the presence of dagman's node name 
> munging - and you've given me the answer to that now.

Okay, great!

Kent