Changes between Version 32 and Version 33 of Tutorial/DataMgt

Timestamp:

Sep 26, 2010, 4:31:25 PM (14 years ago)

Author:

/C=FR/O=CNRS/OU=UMR8607/CN=Charles Loomis/emailAddress=loomis@…

Comment:

--

Tutorial/DataMgt

@@ -76 +76 @@
 == Access Data on the Grid from a Job ==
 
-In the job description, this is possible to describe the data available on the grid that the job need to access. Data files can be identified by a LFN, a GUID or a SURL. This description is taken into account by WMS to select the appropriate site: a CE will be selected only if one the file replica is on one of the ''close SE'' for the CE (this is a configuration information for each CE). Then the job can retrieve the list of files provided, the replicas used... with command `glite-brokerinfo` (available only on WNs).
+In the job description, it is possible to describe the data available on the grid that the job needs to access. Data files can be identified by a LFN, a GUID or a SURL. This description is taken into account by WMS to select the appropriate site: a CE will be selected only if one the file replica is on one of the ''close SE'' for the CE (this is a configuration information for each CE). Then the job can retrieve the list of files provided, the replicas used, etc. with command `glite-brokerinfo` (available only on WNs).
 
 To specify the grid files the job needs access to, it is necessary to add the following two lines to the JDL:
@@ -84 +84 @@
 }}}
 
-`DataAccessProtocol` is a list of transfer/access protocol that the job will use to access the data. The protocols in the example are the most common but other possibilities are `xroot`, `dcap`, and `https`. There is no default and this clause is required if `InputData` is present.
+`DataAccessProtocol` is a list of transfer/access protocol that the job will use to access the data. The protocols in the example are the most common but other possibilities are `xroot`, `dcap`, and `https`. There is no default and this attribute is required if `InputData` is present.
 
 File names specified in `InputData` can be LFN, GUID or SURL. The standard syntax is used with the corresponding prefix `lfn:`, `guid:` or `srm:`. See [wiki:Tutorial/DataMgt#MainDataManagementCommands above].
@@ -104 +104 @@
  1. Modify one of your existing JDL file and add clauses described above with reference to a file you created with `lcg-cr` commands.
  1. Use `glite-wms-job-list-match` command to display the list of sites which can execute the job. Compare with the list without the `InputData` clause.
- 1. Execute the job after adding `glite-brokerinfo closeSEs` and `glite-brokerinfo getInputData` commands to check the information passed to the job.
-
+ 1. Execute the job after adding `glite-brokerinfo getCloseSEs` and `glite-brokerinfo getInputData` commands to check the information passed to the job.
+ 1. Create a second file on a different SE and require both files in your job description.  What does `glite-wms-job-list-match` return in this case?
 
 == GFAL ==