As I recall from a former life, a package called MICS used the raw data files. It was the reason for the hourly closing of the files - it was both a disk capacity (we were on 3380-A04s) and a turnaround time problem. By closing the files hourly and transmitting them immediately, I reduced the DASD requirement and was able to get the last hour's data across in time for the daily reports to be run before the end of the next day's prime shift.
Regards, Richard Schuh -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Gribbin, EDS Sent: Wednesday, March 29, 2006 11:42 PM To: [email protected] Subject: Re: zVM 5.2 ESAMAP and MXG Thanks Mike - that makes it more likely, "something silly" at this end. = Yes, I meant the HISTORY file (we actually ship the, "daily" HISTORY file= that ESAMAP builds from the HISTORY file created by ESAWRITE - the one = with the date as the filetype). We use NETDATA to pack the file and ship = it via RSCS rather than go via tape but otherwise we're doing similar things. Our ESAWRITE / ESAMAP (as shown in the header of the HISTORY records) is = at 3.5.2.5 and our MXG is at 23.05. I'd be interested in knowing your ESAWRITE / ESAMAP level. Suggest we now take this off-list as it looks like a, "minority interest = topic" and I'll post a conclusion once one's achieved. Regards Jeff
