RE: MIDRANGE-L Digest, Vol 7, Issue 249

DSPLOG does use all the QHST* files. For example, if I do a
WRKOBJ QHST*
my oldest has a change date/time of
01/01/08 02:01:15

So, if I do a
DSPLOG PERIOD((0100 010108) (0115 010108)) OUTPUT(*PRINT)
I'll see entries from it.
Now, if I delete that file and do the
DSPLOG PERIOD((0100 010108) (0115 010108)) OUTPUT(*PRINT)
the printout simply says
"(No messages available)"

I can even break the sequence.
Object Type Library Attribute Text
QHST08001B *FILE QSYS PF 10801010201131080101063222
QHST08001C *FILE QSYS PF 10801010632221080101070418
QHST08001D *FILE QSYS PF 10801010704181080101073635
...
DLTF QHST08001C
DSPFD QHST08001B
DSPOBJD OBJ(QHST08001B) OBJTYPE(*FILE) DETAIL(*FULL)
Change date/time . . . . . . . . . . : 01/01/08 06:32:47
DSPLOG PERIOD((0600 010108) (0615 010108)) OUTPUT(*PRINT)
and there's the appropriate entries.

However, if your goal is to print off JUST the contents of QHST08001B when
it's past it's prime, then delete it, that would be a little trickier to
automate the exact begin and end. My arguement is: "Why are spool files
and/or printed output in favor of QHST* files?" Heck, just check the
date/time, save the QHST* file itself off to tape or CD, store that and go
from there. Your only counter arguments remain:
- PITA to restore.
- format of QHST* file may change with a release upgrade.

Rob Berendt