David:

I believe it is a timing issue.

It really would not make a difference if you added a 1 second time delay. The same timing issue might happen again but one second later.

The problem is the code described requires several cpu cycles. Between these cycles anything can happen, including what you describe.  I see no work around unless you want to program in PRIV mode.

You could put a continue before the abort command to make sure the process does not abend.

Olav Kappert


David Powell wrote:

> Seems that pause and jinfo have a slight timing window when they disagree about when a job no longer exists(?).  I have jobs that wait for a specified other job to end, then blow it off after 'x' seconds if it thinks it must be hung.  Normally work just fine, but one time...
>
> :PAUSE 900; JOB=#J5648
> :IF  JINFO('#J5648', "exists")   =   TRUE
> :     TELLOP ABOUT TO TRY TO ABORT #J5648
> :     ABORTJOB #J5648
> ^
> Job does not exist. (CIERR 3042)
> REMAINDER OF JOB FLUSHED.
> CPU sec. = 1.  elapsed min. = 1.  SAT, MAR 1, 2003, 1:03 AM.
>
> Both jobs actually finished within 1 minute, so the 15-minute pause plainly ended when it thought the other job no longer existed.  But then jinfo thought it did still exist, and then abortjob voted that it didn't.  It was in fact logging off normally during all this.
>
> I could easily fix this by adding an extra ':pause 1', it (A) is this a known problem?  (B) any other workarounds?  (C) Any chance of a fix ?
>
> Dave ("starved for ON topic threads, and could the rest of you please remember your 'OT:'? ")
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *