• Subject: Re: Pulling messages from the joblog
  • From: LAN400GEEK <LAN400GEEK@xxxxxxx>
  • Date: Tue, 13 Jan 1998 17:07:28 EST
  • Organization: AOL (http://www.aol.com)

Ed, I looked for the CL I had used to do a very similar process to what you
are describing here, but I could not find it.  Anyway, the program executed a
DSPJOBLOG for the job to an output file (*OUTFILE) and read position 56 (the
beginning position of the MSGID) and processed from there.  You could write a
Query or an SQL after retrieving the current time, etc. from the job to define
which messages to show and/or print.  I had a Query that printed a hardcopy of
the entire formatted output file for the joblog (sorted by message time,
message type, and message id) and it was easy to read as well as nice
documentation for the auditors.  You can also get the name and library of the
message file as well as the sending program (which sounds like it would meet
your needs).  Good luck!!

-Reid Collier

In a message dated 98-01-13 06:15:31 EST, Ed wrote:

<< 1.  Execute a command in a CL/C/RPG program.
 2.  The command puts messages in the joblog.
 3.  The command finishes executing, and the joblog messages need to be
 examined for specific message ID-s for auditing purposes.  I need to spin
 backwards through the joblog, until I find the command executed in step 1.
 How do I fetch these messages?  I'm not really familiar with this kind of
 message handling, so any help would be appreciated.
 Thanks! >>
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@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].