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 - MOVEAWAY issues an SMSG to the other server the other server uses WAKEUP (SMSG and LINKs to MONWRITE to come and get the monitor data file and FT it (the SMSG would include the fn and ft of the file to FTP The last method would be the fastest, but, if the other server would be gone, monitor files from that period would not be FTPed; wtih the intermediate SENDFILE, those files would be waiting in the server's reader and FTP would be done when the server is started.
As a model for the server code: get my RxServer package from the VM download lib, follow the instructions to create a VMUTIL from RXSERVER README, change the genberated VMUTIL EXEC: add some REXX lines in subroutine RDR_EVENT: for the first alternative of GOT_A_SMSG: for the second alternative 2009/2/17 Rempel, Horst <hrem...@bgchemie.de> > 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 selfwritten MOVEAWAY exec > starts. > This exec will copy the file with a new name (it is better to sort) and the > pack option (to save some diskspace), > erase unneeded or older files and ftp the up to date file to a pc. After > that monwrite will continue with the next file. > > This works fine with 15 min interval. > But now I have increased the time interval to 120 min and I see very often > the following messages. > ! > ftp return code is --> > 0 > MOVEAWAY EXEC ends with RC= > 0 > HCPMOW6272I Now recording in file D021709 T110046 > A1 > HCPMOW6267I MONITOR WRITER CONNECTION TO *MONITOR > ENDED > HCPMOW6265A MONITOR WRITER CONNECTED TO > *MONITOR > HCPMOW6269E MACRO IUCV REPLY *MONITOR FAILED WITH RETURN CODE > 9 > HCPMOW6271A WARNING: OUTPUT FILE DOES NOT CONTAIN INITIAL SAMPLE > CONFIGURATION RECORDS > > The help for HCPMOW6271A tells that, this output file may not be usable. > Makes it sense to collect such files? > > It seems to be a timing problem. But I want to collect monitorrecords > without the need for human intervention. > Is anybody using these new monwrite options and so kind to share his > experience ? > > kind regards, mit freundlichen Grüßen, > > Horst Rempel > Berufsgenossenschaft > *http://www.bgchemie.de*<http://www.bgchemie.de> > der chemischen Industrie e-mail hrem...@bgchemie.de > Kurfürstenanlage 62 > 69115 Heidelberg > Germany > > -- Kris Buelens, IBM Belgium, VM customer support
