Hi Sergio, Glad you found this interesting. In general, I've replicated most of the system checks performed by FoxWatch for 51 and Solaris Mesh workstations. The script runs on one of our off platform Windows servers and telnets to each of our Ethernet connected DCS workstations to run checks on those stations. Access to the windows server is more tightly controlled than access to our DCS workstations, so I haven't addressed the insecure telnetting from the windows server to the I/A workstations. From some of those stations the script connects across the local nodebus via rlogin to run the same checks on workstations not connected to our corporate network. Please note, I haven't made the telnetting portion of the script particularly robust. This runs every Saturday at my plant - if it fails it's normally because a workstation somewhere in the plant has some kind of problem. If I don't receive my Saturday morning report I log in and check the log files to see where the script stopped and then go troubleshoot the I/A workstation it was on when it stopped. If the script was more robust I might not realize I had a problem in the plant until Monday morning, so I'm considering the lack of robustness as a feature rather than a problem. The XML file I sent you is a summary report. I'll attach the detailed report and a copy of the script that I've slightly sanitized for passwords and email addresses. I'm copying this back in to the list, I know the attachments will bounce. If anyone else on the list is interested, I'm happy to send copies of the summary xml report, the detailed txt report and the Perl script. Regards, Kevin On Wed, Nov 17, 2010 at 10:39 PM, Sergio Gonzalez < sgonzale16@xxxxxxxxxxxxxxxxx> wrote: > Thanks Kevin > This file looks so interesting, may I have a copy of the script so I could > do the report I need? > > Talking about this file attached, what does it do? do you have auxiliar > scripts to do all that job? > > regards > > > On Tue, Nov 16, 2010 at 10:16 PM, Kevin Fitzgerrell <fitzgerrell@xxxxxxxxx > > wrote: > >> Hi Sergio, >> >> The script you use needs to generate the xml formatting for the document >> to wrap around your data. The resulting file will be quite a bit larger >> than a .csv file would be, but since the script does all the work it's not >> that big an issue. The report I wanted was a simple table. I use Perl for >> the parsing and report generation language, but it could be done in just >> about anything, including a shell or awk script on a workstation. >> >> I've attached a copy of the table I generate. If you open it with excel >> you'll see the finished result. If you open it with notepad, you'll see the >> data as prepared by the script. The header information is just coded in to >> my script and written directly. The individual cell formatting is appended >> to each chunk of data I want in a table's cell. >> >> Regards, >> >> Kevin >> On Wed, Nov 17, 2010 at 11:10 AM, Sergio Gonzalez < >> sgonzale16@xxxxxxxxxxxxxxxxx> wrote: >> >>> Thanks Kevin! >>> I csv would ne ok but a xml would be awsome! >>> How do you do it? >>> >>> Regards! >>> >>> >>> -----Original Message----- >>> From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] >>> On Behalf Of Kevin Fitzgerrell >>> Sent: Tuesday, November 16, 2010 6:18 PM >>> To: foxboro@xxxxxxxxxxxxx >>> Subject: Re: [foxboro] Daily Excel report trough email >>> >>> And if you want more formatting than a CSV file, generating an XML file >>> that Excel can open is also very straightforward. I do this for some >>> summary reports that use tables. >>> Cheers, >>> >>> Kevin >>> >> >> > _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave