RE: RE: CPI2417 Job message queue for xxxxxx/xxxxxx/xxxx has been wrapped. *** Additional Information ***

"Chuck Lewis" <chuck.lewis@xxxxxxxxxxxxx> wrote:

> Thanks Tom. Yes, now that you mention that I seem to recall other
> instances of this behavior at another job but that was a long time
> ago and it happens so seldomly (thankfully !).
>
> So should I just end QINTER *IMMMED instead of *CNTRLD 300 ?

No, because then you're giving no chance for jobs that can end gracefully
to do so. You will simply be yanking the plug on them. And your job that
does not end at all will almost certainly still not end, so you are
unlikely to improve matters and will be introducing the potential to make
them worse.

What you probably could do is to monitor for CPF1001 (Wait time expired)
[1]. You can then have a routine that runs through the jobs in the
subsystem and attempts to end them explicitly [2]. After 10 minutes if the
subsystem is still active you run through the jobs again and hit them with
ENDJOBABN. If the subsystem still doesn't end I think you're more or less
stymied, and nothing short of an IPL is going to do it.

[1] I'm pretty sure a MONMSG on CPF1001 will be triggered if the subsystem
doesn't end within the time limit [3]. To be absolutely sure you could do a
second ENDSBS monitoring for CPF1054 (No subsystem &1 active) as you do
now. If you don't trigger the MONMSG you can assume the subsystem is still
active.

[2] I think this step may be strictly unnecessary [3] as the ENDSBS should
have had this effect anyway. It can't hurt to try it though.

[3] These things are fairly hard to test as you need (a) a subsystem you
can keep happily ending without being shouted at, and (b) a job which is
guaranteed not to end. (b) should be harder to arrange than (a).

--
Dave...
               _________  ,___o
             __________   _\ <;_        http://www.audax.uk.net
           ___________   (_)/ (_)       http://www.twickenhamcc.co.uk
=======================================================
The opinions expressed in this communication are my own and do not
necessarily reflect those of my employer.


______________________________________________________________________
This message may contain confidential information which may also be legally 
privileged and is intended only for the use of the parties to whom it is 
addressed. If you are not an intended recipient you are hereby notified that 
any disclosure, copying, distribution or use of any information in this e-mail 
is strictly prohibited. If you receive this message in error please notify the 
sender by return e-mail and then destroy it. Further, we make every endeavour 
to keep our network free from viruses. However, you do need to verify that this 
e-mail and any attachments are free of viruses as we can take no responsibility 
for any computer viruses which might be transferred by way of this e-mail. All 
information and attachments remain the property of Stolt Offshore Group and 
should be held as confidential.