RE: joblog outq management (was AW: Hiding spoolfiles from outq x)

What we added to the error processing is the command "DSPJOBLOG
OUTPUT(*PRINT)" if an error hit our general trap routine.  Also include a
DMPJOB and SNDNETMSG to your IS programming staff to include the
job/user/number.  Now you got all the info trapped to work with.  The user
never gets those annoying CPF messages and your programmers get the
necessary info to find/re-create/fix the error.

Christopher K. Bipes      mailto:ChrisB@Cross-Check.com
Operations & Network Mgr  mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.                  http://www.cross-check.com
6119 State Farm Drive     Phone: 707 586-0551 x 1102
Rohnert Park CA  94928    Fax: 707 586-1884

-----Original Message-----
From: MacWheel99@aol.com [mailto:MacWheel99@aol.com]
Sent: Wednesday, July 25, 2001 10:32 AM
To: MIDRANGE-L@midrange.com
Subject: Re: joblog outq management (was AW: Hiding spoolfiles from outq
x)


Now that David says the archives are up again, you should try to access them

because there has been a lot of discussion of related topics, but let me 
address the desired job log topic since we have been into this where I work.

We have applications that try to do their own error resolution.
Ideally we want errors recovered in a graceful way that will not burden the 
end users with having to be MIS experts to cope with error messages.
This means that IBM 400 OS does not recognize as a problem worthy of a job 
log, a problem that the application saw but perhaps did not handle as 
gracefully as we MIS would desire, so we need to give the task a human 
helping hand to ensure the generation of a joblog.
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---