[drmaa-wg] making a custom file path for output

Rajic, Hrabri hrabri.rajic at intel.com
Tue Apr 5 10:21:22 CDT 2005


Andreas,

I would suggest we approach the question as two issues:

1) what are the global placeholders in DRMAA
2) in which (string typed) job attributes the placeholders could be used


Here are few questions that go with the above:

How is JDSL handling placeholders - nice to know?
Do all major DRM systems support placeholders well?
Do we need a new error code indicating failure in resolving a
placeholder?  Any other errors needed?

    -Hrabri
 

>-----Original Message-----
>From: owner-drmaa-wg at ggf.org [mailto:owner-drmaa-wg at ggf.org] On Behalf
Of
>Andreas Haas
>Sent: Tuesday, April 05, 2005 7:37 AM
>To: Tim Harsch
>Cc: DRMAA Working Group
>Subject: Re: [drmaa-wg] making a custom file path for output
>
>Hi Tim,
>
>I fully agree there is a need for this. Please see
>
>   http://forge.gridforum.org/tracker/?aid=805
>
>I raised it's priority to P2. I believe that issue must
>be solved with resubitted DRMAA spec.
>
>Regards,
>Andreas
>
>
>On Mon, 4 Apr 2005, Tim Harsch wrote:
>
>> I'm sorry I wasn't clear.  I guess the heart of my question is:  How
can
>> create an arbitrarty template for the file and path name?
Specifically
>what
>> constant tells the DRM to insert job id into that filename template.
>>
>> Said in Perl psuedo form:
>>
>> drmaa_set_attribute( $jt,
>>         $DRMAA_OUTPUT_PATH +  ":/tmp/my_job_output.$DRMAA_JOB_ID.out"
);
>>
>> # with that code job outputs look like
>> /tmp/my_job_output.1.out
>> /tmp/my_job_output.2.out
>> /tmp/my_job_output.3.out
>>
>> # without that code job outputs look like
>> /home/harsch/script_name.o1
>> /home/harsch/script_name.o2
>> /home/harsch/script_name.o3
>>
>> Is there a DRMAA_JOB_ID constant?
>>
>> ----- Original Message -----
>> From: "Rajic, Hrabri" <hrabri.rajic at intel.com>
>> To: "DRMAA Working Group" <drmaa-wg at gridforum.org>
>> Sent: Monday, April 04, 2005 12:02 PM
>> Subject: RE: [drmaa-wg] making a custom file path for output
>>
>>
>> There is a simple solution, provided it works for you:
>> to rely on the shell to supply the home directory path instead of
DRMAA.
>>
>>     -Hrabri
>>
>>
>> >-----Original Message-----
>> >From: owner-drmaa-wg at ggf.org [mailto:owner-drmaa-wg at ggf.org] On
Behalf
>> Of
>> >Tim Harsch
>> >Sent: Monday, April 04, 2005 1:19 PM
>> >To: DRMAA Working Group
>> >Subject: [drmaa-wg] making a custom file path for output
>> >
>> >Hi all,
>> >    I have a requirement for the app I'm writing ( using
>> Schedule::DRMAAc )
>> >which I'm trying to implement.
>> >
>> >Normally the output files from jobs go to home directory and are of
the
>> >form
>> ><jobname>.o<jobid>
>> >
>> >I want to move the jobs to a subdir in /tmp, but retain the <jobid>
in
>> the
>> >filename.  I tried this:
>> >
>> >    ( $job_error, $diagnosis ) = drmaa_set_attribute( $jt,
>> >        $DRMAA_OUTPUT_PATH,
>> >        ":" . $tmpdir . '/' .
>> >        __PACKAGE__ .  '.' .
>> >       $DRMAA_PLACEHOLDER_INCR .
>> >        ".out" );
>> >
>> >... but PLACEHOLDER is only for parametric jobs, I've been scanning
the
>> >docs
>> >and have not found a placeholder for job id.  Any ideas on how I
could
>> >accomplish this task?
>> >
>> >A similar task would be to move the job output path without changing
>> the
>> >filename format at all.  How could I do that?
>>
>>





More information about the drmaa-wg mailing list