DSXchange

Thanks Ken.

alright. I guess I am confused. I did a search for Batch::UTILSetDefaultParameters and this is what I found. If Update = "Y" Then Open "DS_JOBS" TO F.JOBS Then Read prototypenbr from F.JOBS,PrototypeJob Then PROTOFILE = "DS_JOB":prototypenbr Open PROTOFILE TO F.PROTO Th...

Can you please tell me how to run this "UTILSetDefaultParameters.bat"

Thanks Craig.

Is there a utility that can do this for defining subroutines too?

My lucky day. :D

Thanks Ken

Did you mean Kenneth Bland, Craig?

For some reason, whatever personal message that I send through DSxchange stays forever in my outbox rather than the sentbox. I guess I will just have to hope that he sees this.

Hi All,

I have a project which contains 'n' number of jobs. I want to add a job parameter to each of the jobs with the value as $PROJDEF. Is there a simpler way of doing this rather than modifying the jobs one by one.

Your time is appreciated.

Thanks Ray.

and thanks for the tip Craig. I will try to that outside of the jobs.

I am marking this topic as resolved.

I cant thank you guys enough.

Thanks Shane. Works like a charm.

Only thing is it doesnt write anything if the job is stopped.

Though I couldnt read the content, I understood what you meant. It is always returning me DSJS.RUNNING as the job is still running. I understand that it shouldnt be a after-job subroutine.

About time I got a membership.

My bad. I was thinking that each DSJS.<<status>> gives a different return integer.

I should be actually manipulating this inside the routine itself instead of worrying about the integer written to the log.

Will let you guys know if I am successful.

Thanks Shane. That was exactly what I was looking for. I did three different runs where one finished, one aborted and one stopped. The log file had code "0" all the three times. Following is the code I used Status = DSGetJobInfo (DSJ.ME, DSJ.JOBSTATUS) Am I missing something or is there a ...

Thanks Craig. I will check the help files for that. Meanwhile, is there a way that I can get the "Control" statement which says "Job X Finished" or "Job X aborted" by editing the existing code above.

To add to the above details, the routine truncates lot of data to "(...)" in the file just like the way it it seen in the director log. Is there a way I can get the full details instead of "(...)"

Hi All, Following is the code I use to write the log to a target directory. I got this code from one of the posts in dsxchange. This writes the log summary for the particular job from where it is called. It writes the exact same log as in Director except the last line of type "Control". Ca...