OK, that recent thread may have been my fault, so I'll clarify. I had
posted some examples of detecting that a job was running, and invited
feedback. I had misrepresented the approach using SHOWJOB and SHOWPROC,
the problem being that SHOWPROC seems to ignore the HPJOBNAME, so cannot
be used for HPUSER.HPACCOUNT pairs that can have other jobs or sessions
running under them, and SHOWJOB does not set CIERROR when there are NO
SUCH JOB(S). So while SHOWPROC is not useless, it's usefulness is very
constrained. Bummer. The other approach was to send the output to a
file, then test the file for length, which does work, but involves I/O.

I was less than gracious to those who suggested issuing a TELL to the
job, which at least can be counted on to produce the testable There was
no session found that matched this ID. (CIWARN 1619) if there is no such
job, and "HPJOBNAME, HPUSER.HPACCOUNT" not interactive.  Message not
sent to job. (CIWARN 1627) if there is such a job. Of course, this
assumes that no one would be signed on with the same values as a job
runs under.

>----------
>From:  Bruce Conrad[SMTP:[log in to unmask]]
>Sent:  Monday, December 22, 1997 6:19 PM
>To:    [log in to unmask]
>Subject:       [HP3000-L] Abortjob + Maestro question
>
>     Once in a while, (I'll leave out the details) a job is streamed on our
>     system that we would like to automatically abort, so that it doesn't
>     run (the job limits are high, so it doesn't automatically log on).
>
>     I'm trying to setup a daily job to :
>     MPEX
>     showjob job=jobname,job.account
>     if cierror=0
>     ABORTJOB  Jobname,Job.Account;NOVERIFY
>     endif
>     exit
>
>     However, if there is no job to abort, the JOB itself will abort. I
>     want it to check first, and not do an abortjob if there isn't anything
>     to abort. got it? :) There was a recent thread which covered this
>     subject, since that's where I got some of the ideas; but it's not
>     working for me .