SomeOne write (privately, but now publicly):

>I would be fascinated to know what those who just periodically LISTSPF
>O@;SELEQ=[JOBABORT=FALSE] do to minimize the number of silly aborts they
see
>and how they handle their STDLists for aborted jobs, once they have
examined
>them.

I don't believe there is such a thing as a "silly abort".  If I 
see a job's $STDLIST in the LISTSPF output, I consider it as a 
"bad" thing.

As for what we *do* about it, it depends on what the job was and who 
streamed it.  If it's the invoicing posting job stream, for instance, 
then I immediately print the $STDLIST, troubleshoot it, and fix 
whatever is wrong (can't mess about with the trade receivables, you 
know).  If it's an inquiry-only reporting job and the person has 
tried three times to stream it with invalid input (our online 
system builds job streams on the fly using user input for the 
parameters), then I may walk over to see or phone the person 
and offer some advice on how to get it to run.  *After* I purge 
the $STDLIST.

BTW, $STDLIST's from jobs that have completed successfully are 
deleted after the nightly backup job.  $STDLIST's from aborted 
jobs are retained indefinitely and keep showing up on the LISTSPF 
output until purged manually, which usually happens soon after 
the $STDLIST is read and diagnosed.

Jim Phillips                            Manager of Information Systems
Voice: (330) 527-2124                   Therm-O-Link, Inc.
  Fax: (330) 527-2123                   PO Box 285; 10513 Freedom St.
Email: [log in to unmask]       Garrettsville, Ohio  44231