I am running on a z/VM 5.1 system and trying to deliver our data to a hobbit server in a client-data format that hobbit will read & process without backend changes. This is a locally configured client.
I am working on the 'file', 'logfile' and 'messages' components of our system. I can get our system log and its status information to hobbit as well as file status information for other files. The unaltered, minimally configured hobbit server shows the msgs and files columns fine, IF there is good data. I am now trying to provide an error condition, where one of the monitored files does not exist. I found some syntax for this error condition by running logfetch on a SLES10 system with a special logfetch.cfg. When I mimic that same syntax in my z/VM client data file, Hobbit still shows the file as green but with 'No Data'. I would like the file to be marked Yellow in the hobbit files display. Must there be a file configuration record in the hobbit server before it will check for the error condition?
Here is the piece from my client data file. [file:/VMSYSU/DFSMS./RMSMASTR.%TODAY] ERROR: No such file or directory [file:/DISKACNT/0191/ACCOUNT.$A111306] type:100000 (file) mode:640 (-rw-r-----) linkcount:1 owner:0 (root) group:3 (sys) size:6880 clock:1163443363 (2006/11/13-13:42:43) atime:1163442621 (2006/11/13-13:30:21) ctime:1163442621 (2006/11/13-13:30:21) mtime:1163442621 (2006/11/13-13:30:21) md5:79d5fe932a2784f2650e17a811fb4a17
/Thomas Kern /301-903-2211