|
Reading all QHST* files wouldn't reliably give you all available entries somewhere in the past. The problem was something like QHST itself is a form of message queue, not a physical file. Only messages that had been copied to the QHST* files would be available for reading through those files. It's been a while, but IIRC, it was necessary to execute a DSPLOG command first. This somehow caused the *MSGQ to be flushed to the files. Does anybody know if this is still true? Tom Liotta midrange-l-request@xxxxxxxxxxxx wrote: > 6. Re: Analysing DSPLOG to CFG (Pete Massiello) > >date: Sun, 11 Dec 2005 21:54:07 -0500 (EST) > > You can do this by reading all the qhst* files that exists in QSYS. > >Pete > >---------------------------- Original Message ---------------------------- > >> I am not as skilled as you guys on spectrum of topics, because I am a jack >> of all trades, jedi master of only some, so like to work with various >> capabilities for multiple applications to get more familiar with what can >> be done. I have an idea for a potential solution to multiple challenges, >> but I an unsure of all the pieces. I do most of my programming nowadays >> in >> RPG/400 with embedded SQL, and occasionally Query/400 work files (because >> speed of implementation is lightning fast compared to other approaches). >> >> I'd like to read current DSPLOG info into a program, obtain selected >> messages, extract security and performance tracking info:
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.
midrange.com
