Hello, From my understanding while reading the JSDL Specification V.1.0, a DataStaging element can be created without the optional Target and/or Source elements being specified. For example: <jsdl:DataStaging> <jsdl:FileName>file1.txt</jsdl:FileName> </jsdl:DataStaging> Could you please let me know on the benefits of such element? What is the benefit of a DataStage element that is not Staged-In or Stage-Out on the consuming system, and in general to the end-user? Best regards, -- _________________________________________________ Nicholas Loulloudes High Performance Computing Systems Laboratory (HPCL) University of Cyprus, Nicosia, Cyprus Tel: +357-22892663 Email: loulloudes.n@cs.ucy.ac.cy
Nicholas Loulloudes wrote:
From my understanding while reading the JSDL Specification V.1.0, a DataStaging element can be created without the optional Target and/or Source elements being specified. [...] Could you please let me know on the benefits of such element? What is the benefit of a DataStage element that is not Staged-In or Stage-Out on the consuming system, and in general to the end-user?
You can use it to specify clean-up-on-terminate behaviour too. Donal.
And this explanation is in the JSDL 1.0 errata draft, which you can find at http://forge.gridforum.org/sf/go/doc14115?nav=1 Andreas Donal K. Fellows wrote:
Nicholas Loulloudes wrote:
From my understanding while reading the JSDL Specification V.1.0, a DataStaging element can be created without the optional Target and/or Source elements being specified. [...] Could you please let me know on the benefits of such element? What is the benefit of a DataStage element that is not Staged-In or Stage-Out on the consuming system, and in general to the end-user?
You can use it to specify clean-up-on-terminate behaviour too.
Donal.
participants (3)
-
Andreas Savva -
Donal K. Fellows -
Nicholas Loulloudes