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

Tom Liotta <qsrvbas@xxxxxxxxxxxx> wrote:

> As Dave said, by using *IMMED, you lose the opportunity for jobs to
> end gracefully, at least for jobs that have benn coded to detect the
> shutdown condition. I pretty much _never_ use *IMMED unless I already
> know there are no active jobs.

Which begs the question: if you know there are no active jobs why use
*IMMED? The default of *CNTRLD *NOLIMIT should have exactly the same
effect. It's a safeguard because if the subsystem doesn't end you know
you've got a job running in it. To me *IMMED is something you use only when
you explicitly want to pull the plug on any active jobs in the subsystem:
as you said, almost never on a subsystem running production jobs.

> (And I'd still like to see something authoritative so I don't have to
> rely on years of experience for this answer.)

As I said before it's tricky to test even if you can dedicate a machine for
the purpose as you need to have a job that reliably refuses to end. I also
suspect that minor details might be inconsistent from release to release,
and maybe even depending on the precise reason the job doesn't end.

--
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.