Re: Problem with new MONWRITE options

2009-02-17 Thread Rob van der Heij
On Tue, Feb 17, 2009 at 12:05 PM, Rempel, Horst wrote: > The help for HCPMOW6271A tells that, this output file may not be usable. > Makes it sense to collect such files? Two hours worth of raw data is a lot. My guess is that your exec now takes so much time that the user was not back in time to

Re: Problem with new MONWRITE options

2009-02-17 Thread Kris Buelens
I'm pretty convinced that your MOVEAWAY EXEC is too slow. Either work with your old 15 minutes interval; either involve another service machine: MOVEAWAY could - SENDFILE the just closed monitor file to another server the other server uses WAKEUP (RDR to wait for monitor files and FTP it Or - MO

Problem with new MONWRITE options

2009-02-17 Thread Rempel, Horst
Hello, I am running z/VM 5.4.0 and I want to collect monitorrecords using the new monwrite options CLOSE bndy CONFIG EXEC efn. My monitor sample interval is 1 min. For a test I used ' MONWRITE MONDCSS *MONITOR DISK CLOSE 15 CONFIG EXEC MOVEAWAY' Every 15 min the file will be closed and my self