× 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.



On 05-Mar-2014 10:13 -0800, James H. H. Lampert wrote:
<SNIP>>

If I do this,
DSPOBJD OBJ(QSYS/QHST*) OBJTYPE(*FILE) +
OUTPUT(*OUTFILE) OUTFILE(QTEMP/HISTLIST)
to get my list of the extant history log PFs on the system, are the
records in HISTLIST then guaranteed to reflect a chronological
sequence of QHSTxxxxxx files?

The order of the records, collated by the names of the files listed, is not necessarily a chronological ordering.

Or do I need to use a keyed receiver file in order to force
chronological sequence?

The records of the HISTLIST output file would need to be sorted according to the "text" attribute; i.e. the data stored in ODOBTX. I do not recall if that data is conducive to a non-derived key. Or the order of the union of the row data may be desirable instead for collation. But the actual rows of data within the files represents yet another issue for determining truly chronological; they are dependent the system date\time, but are always arrival order. Depending on how the files got to the system, the records from one file with a particular start time could [appear to] bleed into a file of a later start time.

FWiW: An API was delivered in a recent release to process history log data:
<http://pic.dhe.ibm.com/infocenter/iseries/v7r1m0/topic/apis/qmholhst.htm>
_Open List of History Log Messages (QMHOLHST) API_


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.