Using the pipe Jonathan gave me -- I was able to figure out that there actually was no 2nd day's worth of data in the monitor file ... but I think you're right - you really want that initial config info at the start of the file.
I had the same question about the report builder.. it's probably possible - but they really want keep things in daily files. <shrug> Thanks for the responses! I got enough info from Jonathan's pipe to figure out what datestamp I was looking for, and that got me far enough in this case. Thanks, Jonathan! Scott On Thu, Feb 11, 2010 at 1:59 PM, Kris Buelens <kris.buel...@gmail.com>wrote: > I don't think it is that easy: when MONWRITE is started it includes > "configuration" information in the monitor file, if you split it up, the > second file won't have this information. > But, why do you need to split it up? Can't you tell your "report builder" > to limit its reports to a given timespan? > > 2010/2/11 Quay, Jonathan (IHG) <jonathan.q...@ihg.com> > > Quick and dirty… figure out midnight on the 2nd day. e.g… Pipe literal >> 2010-02-10 00:00:00.000000 | dateconv isodate todabs | spec 1-* c2x 1 and >> then either browse for it in the file or feed it in to a comparison against >> the timestamp in the monitor records. >> >> >> ------------------------------ >> >> *From:* The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] *On >> Behalf Of *Scott Rohling >> *Sent:* Thursday, February 11, 2010 10:54 AM >> >> *To:* IBMVM@LISTSERV.UARK.EDU >> *Subject:* Separating monitor records by date >> >> >> >> We have a daily monitor file from MONWRITE that ended up with 2 days worth >> of monitor records. Is anyone aware of a utility, or pipe incantation, or >> anything else that could be used to separate the file into 2 daily files? >> >> Thanks for any tips you can give - >> >> Scott >> > > > > -- > Kris Buelens, > IBM Belgium, VM customer support >
