today during the live session on EVO Marco Fargetta gave an answer to Pelita about Parametric Jobs. We thinks that it could be interesting for all of you to read this public conversation
[10:41:51] Pelita Fajarhati could you please explain the parametric job?
[10:42:00] Marco Fargetta yes
[10:43:00] Pelita Fajarhati i tried the script on the example
[10:44:11] Marco Fargetta yes
[10:44:23] Marco Fargetta the example on wiki or the example on the slide
[10:44:31] Pelita Fajarhati on wiki
[10:44:40] Marco Fargetta I take the same so we can discuss on it
[10:45:46] Marco Fargetta ok
[10:45:49] Pelita Fajarhati i use the script from the solution, .sh and the .jdl files
[10:46:18] Marco Fargetta but the jdl is not on the wiki
[10:46:34] Marco Fargetta ok
[10:46:39] Marco Fargetta i see at the end
[10:46:43] Marco Fargetta so
[10:47:22] Marco Fargetta so you have run the jdl I am sharing
[10:47:31] Marco Fargetta am I right?
[10:48:05] Pelita Fajarhati yes
[10:48:11] Marco Fargetta when you create a parametric job
[10:48:36] Marco Fargetta and write JobType="Parametric";
[10:48:49] Marco Fargetta the WMS will manage your job in a special way
[10:49:04] Marco Fargetta on the WMS the jdl is transformed
[10:49:23] Marco Fargetta in the first case (string parameters)
[10:49:57] Marco Fargetta the tag "Parameter" is deleted from the jdl
[10:50:51] Marco Fargetta and its contents, an array of string, is used to replace the string _PARAM_ inside the JDL
[10:51:14] Marco Fargetta the sobstitution is mode once for each parameter
[10:51:54] Marco Fargetta so the WMS will create a JDL where all _PARAM_ are replaced with "hostname"
[10:52:08] Marco Fargetta once where they are replaced with "date"
[10:52:12] Marco Fargetta and so forth
[10:52:24] Marco Fargetta so
[10:53:04] Marco Fargetta with the same JDL you will generate N jobs, one for parameter in the list of "Parameters"
[10:53:49] Marco Fargetta what these values mean for your job depend on the executable
[10:54:10] Marco Fargetta in this case the "echo_node_properties.sh"
[10:54:49] Marco Fargetta and take care that each generated job will have different name for Input and Output files
[10:55:08] Marco Fargetta (to say the true only output)
[10:55:16] Pelita Fajarhati is that why i see 4 statuses when running glite-wms-job-status?
[10:55:19] Marco Fargetta (my mistake )
[10:55:24] Marco Fargetta yes
[10:55:40] Marco Fargetta you have the Job ID for your job
[10:56:00] Marco Fargetta but for the WMS your job is made by 4 generated jobs
[10:56:08] Marco Fargetta so you will see a global status
[10:56:15] Marco Fargetta and the status for each job
[10:57:14] Marco Fargetta if the string parameter is clear we can move to the integer parameters. Is it clear?
[10:57:30] Marco Fargetta Other trainers would add some words?
[10:59:14] Marco Fargetta (nothing I think mean Ok)
[10:59:24] Marco Fargetta in the second case
[10:59:39] Marco Fargetta we use integer parameters
[11:00:07] Marco Fargetta this means that we ask the WMS to create a loop
[11:00:48] Marco Fargetta for each cicle the WMS will create a Job replacing the string _PARAM_ with an integer number
[11:01:15] Marco Fargetta the first number is the ParameterStart
[11:01:50] Marco Fargetta the next cicles the value will be PreviousValue+ParameterStep
[11:04:20] Marco Fargetta and the cicle will end when the value reach Parameters
[11:05:34] Marco Fargetta so for the job in the wiki
[11:06:13] Marco Fargetta the first cicle _PARAM_ has value 10
[11:06:22] Marco Fargetta the second 20
[11:06:33] Marco Fargetta and so forth until 40
You can find other useful information following the slides published inside the on-line training course ( http://euasiagrid.org/moodle/mod/resour ... .php?id=55 )