• Subject: RE: Error Message List
  • From: Buck Calabro <mcalabro@xxxxxxxxxxxx>
  • Date: Tue, 9 Nov 1999 08:43:47 -0500

If you're trying to diagnose an error well after the fact, look at the
QSYSOPR and QSYSMSG message queues as well as DSPLOG QHST.  Not a perfect
substitution for the S/36 history, but I can't imagine logging every CL
command from every one of my programs for every user in one place.  It'd be

Buck Calabro
Aptis; Albany, NY

> -----Original Message-----
> From: End of the Trail 
> Sent: Monday, November 08, 1999 11:33 PM
> To:   MIDRANGE-L@midrange.com
> Subject:      Re: Error Message List
> That is one thing I miss from the S36, the history file.  One place to go,
> to find out who, what, when.  I did not have to guess who, find their job
> log, scan to find the error and start over if I had the wrong who.
> Eurrat
> -----Original Message-----
> From: Buck Calabro <mcalabro@commsoft.net>
> To: MIDRANGE-L@midrange.com <MIDRANGE-L@midrange.com>
> Date: Monday, November 08, 1999 2:13 PM
> Subject: RE: Error Message List
> >Jeff,
> ><sound of Obi-Wan Kenobi's ghostly voice in the background> "Use the job
> >log, Jeff!"
| 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

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].