Another option, If you have a external scheduling tool like Contol-M,yada, yada...
You can schedule it there so that the job runs every 30 minutes.
I find this the easiest method
Narasimha Kade
Finding answers is simple, all you need to do is come up with the correct questions.
Then you just need a smarter sleeper. I wasn't going to add all the gory details, just put forth the general (very) high level concept.
As an example, I just built one that needs to run over the course of the day and run a series of jobs 'every five minutes'. At the end of each run, regardless of runtime, it sleeps until the next 5 minute mark on the clock. Generally it comes in well under that, but if it does run over then the next 5 minute mark on the clock is the sleep target.
-craig
"You can never have too many knives" -- Logan Nine Fingers
Create a routine. Use the fact that the SLEEP statement has two syntaxes - one that sleeps for a given number of seconds, the other that sleeps until a particular clock time. Being in a routine, it is easy to calculate the next 30 minute point.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Yes, we do. I'm interested in Ray's statement re: two syntaxes... I see no evidence of the ability of being able to sleep until a particular clock time. Where would that be documented?
I went thru some gyrations to compute the next time to sleep to and how many seconds from now that was, hence the interest.
-craig
"You can never have too many knives" -- Logan Nine Fingers
I think the two sleep syntaxes that Ray is referring to is Sleep n where n is the number of seconds and the other one that he mentioned. But i am not sure about the syntax of SLEEP HH:MM. I am trying to test it but no matter what i put in HH or MM , for some reasons it just sleeps for that amount of seconds.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.