DataStaging

Element Information

Model

FileName , FilesystemName{0,1} , CreationFlag , DeleteOnTermination{0,1} , Source{0,1} , Target{0,1} , ANY element from ANY namespace OTHER than 'http://schemas.ggf.org/jsdl/2005/11/jsdl'

Children: CreationFlag, DeleteOnTermination, FileName, FilesystemName, Source, Target

Attributes

QName	Type	Fixed	Default	Use	Inheritable	Annotation
name	xsd:NCName			optional
Wildcard: ANY attribute from ANY namespace OTHER than 'http://schemas.ggf.org/jsdl/2005/11/jsdl'

Used By

Complex Type

JobDescription_Type

Source

<xsd:element name="DataStaging" type="jsdl:DataStaging_Type"/>

Sample

< jsdl:JobDescription xmlns:jsdl = "http://schemas.ggf.org/jsdl/2005/11/jsdl" xmlns:jsdl-posix = "http://schemas.ggf.org/jsdl/2005/11/jsdl-posix" >

[...]

< jsdl:JobIdentification>

< jsdl:JobName>

My Gnuplot invocation

</ jsdl:JobName>

< jsdl:Description>

Simple application invocation: User wants to run the application 'gnuplot' to produce a plotted graphical file based on some data shipped in from elsewhere(perhaps as part of a workflow). A front-end application will then build into an animation of spinning data. Front-end application knows URL for data file which must be staged-in. Front-end application wants to stage in a control file that it specifies directly which directs gnuplot to produce the output files. In case of error, messages should be produced on stderr (also to be staged on completion) and no images are to be transferred.

</ jsdl:Description>

</ jsdl:JobIdentification>

< jsdl:Application>

< jsdl:ApplicationName>

gnuplot

</ jsdl:ApplicationName>

< jsdl-posix:POSIXApplication>

< jsdl-posix:Executable>

/usr/local/bin/gnuplot

</ jsdl-posix:Executable>

< jsdl-posix:Argument>

control.txt