My_condor_submit: example 1

# Specify the name of the executable to run
Executable = gulp

# Specify where the executable should get stdin from and put stdout to
GlobusRSL = (stdin=andalusite.dat)(stdout=andalusite.out)

# Specify an SRB collection to get the relevant executable from
pathToExe = /home/codes.eminerals/gulp/

# Specify a metadata dataset to create all metadata within
RDatasetId = 55

# Specify a directory to get files from, put
# files to and relate to metadata created below
Sdir = /home/user01.eminerals/gulpminerals/
Sget = *
Sput = *

# Creates and names a metadata data object
Rdesc = "Gulp output from andalusite at ambient conditions"
# Specify metadata to get from files with Agent-x - get environment
# and default metadata only
AgentXDefault = andalusite.xml
GetEnvMetadata = True

The first three lines give information about the executable (name and location within the SRB) and the standard GlobusRSL command. The three lines with names beginning with S provide the interaction with the SRB. The Sdir line passes the name of the SRB collection containing the files, and the Sput * and Sget * lines instruct MCS to download and upload all files. The lines beginning with R concern the interaction with the metadata database through the RCommands. The identification number of the relevant metadata dataset into which data objects are to be stored is passed by the RDatasetID parameter. The Rdesc command creates a data object with the specified name. Its associated URL within the SRB will be automatically created by MCS.