× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Everything in the history log is already in physical files - names start with QHST - there can be multiple records for each message. There is actually more data there than you get in the *PRINT output, or even displaying.

The Work Management documentation and the CL Programming documentation both have information on the layout of the records in the QHST* physical files. It is not difficult to work with, just a little tedious.

I would scan the QHST* files for a certain date range, perhaps - the text description of the files has that range, I believe. Read through them, finding the seq# 1 record that has this message ID. Then find the remaining records for the message and combine the contents into a long-enough character variable.

TAA Tools also has some analysis tools for the history log - not sure if anything would help you there.

HTH
Vern

On 7/7/2011 2:08 PM, fbocch2595@xxxxxxx wrote:
Hi Folks, I'm trying to get the client info from the history log, specifically the client IP address for the usrprf in the log msg CPIAD09. DSPLOG doesn't have the option for outfile so I'm wondering if anyone has a quick way to create a report for DSPLOG that will create a report of the IP addresses from the log? If anyone has code to share on this plz send it along.
Thanks, Frank








As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

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.