1
00:00:00,000 --> 00:00:05,000


2
00:00:12,600 --> 00:00:17,100
We start by checking our credential

3
00:00:26,100 --> 00:00:31,800
We have to delegate this credential to the broker we want to use

4
00:00:48,000 --> 00:00:53,100
We choose a handle or ID for the credential: demo

5
00:01:00,500 --> 00:01:05,600
Let us see the job we are going to submit

6
00:01:06,700 --> 00:01:10,100
It is similar to job 2 of the ngtest command

7
00:01:17,500 --> 00:01:22,700
Submit requires a delegationID

8
00:01:24,100 --> 00:01:27,600
The VO I want to represent

9
00:01:28,100 --> 00:01:32,500
A job description and a broker

10
00:01:37,900 --> 00:01:44,200
We see the job translated to JDL and successfully submitted

11
00:01:55,800 --> 00:02:03,800
Let us check the status of the job

12
00:02:08,300 --> 00:02:14,300
We use gLite tools to prove that the job is available on EGEE

13
00:02:22,400 --> 00:02:27,300
The job has finished. Now we need the output

14
00:02:39,800 --> 00:02:44,900
ngwmget needs the jobid and the broker the job was submitted to

15
00:03:16,800 --> 00:03:22,000
The job was succesfully executed

16
00:03:30,300 --> 00:03:34,700
We start by submitting the "hello world" job again

17
00:03:44,200 --> 00:03:49,900
ngwmcancel requires jobid and broker just like ngwmget

18
00:04:11,100 --> 00:04:16,400
Let us check that the job was cancelled on gLite

19
00:04:43,500 --> 00:04:48,700
This job requires input from nordugrid storage servers

20
00:04:51,900 --> 00:04:57,400
and it will output to a storage server as well

21
00:05:01,000 --> 00:05:07,800
This example job is very simple. It adds a comment to the data

22
00:05:10,300 --> 00:05:25,900
But the job could just as easily have been a real physics job

23
00:05:40,900 --> 00:05:44,800
We check that the input file is available

24
00:05:47,700 --> 00:05:55,900
and that the output is not there already

25
00:06:08,300 --> 00:06:11,700
We submit the job

26
00:06:13,800 --> 00:06:19,700
We see that the output is more complex

27
00:06:20,000 --> 00:06:25,000
This is because the job has to transfer the executable to gLite

28
00:06:42,400 --> 00:06:45,500
The job is running on a EGEE CE in poland

29
00:07:03,600 --> 00:07:08,300
and, it is done

30
00:07:10,000 --> 00:07:16,000
Let us get the output

31
00:07:35,700 --> 00:07:40,000
stdout and stderr was transfered successfully

32
00:07:51,000 --> 00:07:55,700
and the output is available on the NG storage server

33
00:08:28,100 --> 00:08:33,600
The data has been successfully transformed