|
Another possibility is to execute the cl command: DSPJOBLOG OUTPUT(*OUTFILE) OUTFILE(QTEMP/joblogfile) This creates a formatted file of all the messages in the joblog. If you have the actual escape message then read back from the end of file to the first match. The info you need should be there. If you don't know the message ID, you may have to make some educated choices (not "guesses", were professionals!) as to which message records are relevant. Rick Weber | TЯU International -----Original Message----- From: Paul Morgan [mailto:pmorgan@xxxxxxxxxxxxxx] Sent: Thursday, October 20, 2005 10:33 AM To: rpg400-l@xxxxxxxxxxxx Subject: Re: Finding where an escape message came from Antoine, I'm not positive about any of this but I'd suggest: If you call the API a second time with the *ESCAPE message type you might get the original escape message (they get retrieved in LIFO order). Another possibility is to get the Message Key of the CEE9901 message. Try retrieving a second message with *PRV Message Type and that Message Key to retrieve the message just before the CEE9901 message. Hopefully that's the original escape message sent from the other program. You might also have to play with the call stack entry to get to the original escape message. Paul
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.