John McKown wrote: >Problem: I must restict WALL CLOCK or ELAPSED time, not CPU used time.
We have a solution for this and I'm using it to get alerted when my SMF jobs are taking too long to run. (Robot refusing to mount my tapes. pre-VTS of course...) Ok, I have Control-M and you have CA-Ops (I think). What we do is we schedule a job to run at 02h00 say and then we set an EVENT to be run at say 03h00. That event then checks if a job is still active, if so, I get an SMS and e-mail alert. What you can do in your package is, that when your job starts, you scan with your SYSLOG scraper and search for $HASP373 <jobname> for example. Then you schedule a trigger to be activated one hour or so later. That trigger can then issue a CANCEL command. Clumsy, yes, but that worked. (I played a prank on one of my colleagues on his birthday to cancel his TSO session after 5 minutes since logon... big fun... Bigger fun when after so 4 cancels, I disabled the rule and told *them* the next day the truth... <grin> Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
