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

[vhamberg@xxxxxxxxxxx]

Rob

I'm curious - which files are multiformat logicals? The QHST* files are definitely physical files.

As for printing reports that look like the DSPLOG output, you CAN process the QHST* files using the information in the links I provided earlier. The records in QHST are multiple records per message in the log, but they are just message IDs and message data - you can use - or have to use - RTVMSG to get the full text. You also have to read at least 3 records to get everything.

Now yes a multiformat logical might be possible - or format id stuff in I-specs - to collate all the related stuff together. It's actually pretty cool, and some of the important message do NOT show up in DSPLOG output of any kind - I mean, the messages do, but not all the information there - in particular, CPF1124 and CPF1164 - the latter has all kinds of runtime metrics for the job.

Later
Vern

 -------------- Original message ----------------------
From: rob@xxxxxxxxx
> I think it would be quite rough for IBM to change the format of that file. 
>  It's an internally defined multiformat logical.  So your basic SQL script 
> kiddie would have a tough time with it.  Then again, some of the dates 
> appear to be stored as 7 digits so perhaps it did undergo a conversion at 
> one time.
>
> Rob Berendt
> -- 
> Group Dekko Services, LLC
> Dept 01.073
> PO Box 2000
> Dock 108
> 6928N 400E
> Kendallville, IN 46755
> http://www.dekko.com
>
>
>
>
>
> rob@xxxxxxxxx 
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> 01/31/2008 01:53 PM
> Please respond to
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
>
>
> To
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> cc
>
> Subject
> 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
> -- 
> Group Dekko Services, LLC
> Dept 01.073
> PO Box 2000
> Dock 108
> 6928N 400E
> Kendallville, IN 46755
> http://www.dekko.com
>
>
>
>
>
> "Haberman, Patty" <phaberman@xxxxxxx> 
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> 01/31/2008 12:46 PM
> Please respond to
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
>
>
> To
> <midrange-l@xxxxxxxxxxxx>
> cc
>
> Subject
> RE: MIDRANGE-L Digest, Vol 7, Issue 249
>
>
>
>
>
>
> Thanks for the response Gord.  But what I was looking for was to be able
> to print the QHST* files that are saved from the message queue in the
> same format as DSPLOG does for the QHST message queue.
>
>
> ------------------------------
>
> message: 9
> date: Thu, 31 Jan 2008 10:19:29 -0500
> from: Gord Hutchinson <gordm1@xxxxxxxxxxxxxxx>
> subject: Re: Printing QHST* files
>
> > On Thu, 31 Jan 2008 06:54:37 -0800, "Haberman, Patty"
> <phaberman@xxxxxxx> wrote:
>
> > I have yet to convince my employer to purchase TAATOOLs to be able to
> > use their command for selecting and printing the history log from the
> > QHST* files.  Does anyone have a utility or method for printing out the
> > history log from the QHST* files?
> >
> >
> >
> > TIA
>
> DSPLOG OUTPUT(*PRINT)
>
> I run this every day just after midnight for the previous day and
> convert
> the print to a PDF file for historical/auditor requirements.
>
>
> Gord
> -- 
> Gord Hutchinson
> Database Administrator, IT
> TST Overland Express
> ghutchinson@xxxxxxxxxxxxxxx
> 905-212-6330
> fax: 905-602-8895