GRAM5 still supports the RSL attribute "stdout". The notice, you mentioned, concerns sending output to another machine than a job is executed on. When a user decided to stage out output, GRAM2/GRAM4 streamed output incrementally. Now, in GRAM5, output is sent after the job is terminated. But still, the same like with GRAM2/GRAM4, the output file is written down on the disk and you can check the output file periodically. However, you can see differences between individual clusters. In fact, a lot depends on how local resource manager (PBS, Torque, SGE etc.) is configured and how the GRAM job manager script is modified by an admin of a cluster.
Regards, Lukasz On Mar 25, 2010, at 9:10 PM, cinyoung hur wrote: > Hello, > > I'm Hur, and new to GT5. > > I attached one of removed features in GT5. > > I would like to know that GRAM of GT5 does not support application's output > to file during its execution? > > > > With gram4, I used to submit a job that streams output to files and checked > the files periodically > > to find out job is doing well. > > > > Is there way to check process of job except status of job(e.g. running, > complete, etc.)? > > > > Removed > Features(http://www.globus.org/toolkit/docs/5.0/5.0.0/execution/gram5/rn/#gram5RN) > > The GRAM5 service no longer streams output and error during job execution; > instead this data is send after the job terminates > > > Regards, > Cinyoung Hur
