Hi...
I don't consider my script as something I want to give away yet. This is mainly because I am fidling around with it still. I don't find any spare time to end it and pack it down for somebody else to use.
If I slip it away, it will just produce a lot of noise for me
Anyway some details about my script:
* it's written in python
* some tools to access ARS is done in perl (ARS-perl)
* using tk-widgets so there is a nice gui
* configuration, selections of forms to dump, progress is all in gui
* underlying tool is runmacro
A clip from the log shows the dumping of a single form. The parameters to the runmacro.exe tool is visible (the password is however masked in the log-output).
=======> START FORM Group
Dumping form Group
8 record(s) found in the form
C:\buffer\wbin\ars51\servers\ar03\runmacro.exe -f "Group" -x "ar6c" -U "Demo" -t "arx" -o "c:\data\dump\dump_2004-1-20_13-36-29\Group" -P "**********" 2>&1
Action Request System Runmacro.exe Version 5.1
Remedy, a BMC Software company. Copyright (c) 1991-2003 BMC Software, Inc. All rights reserved.
Accessing server - ar6c ...
Processing form - Group ...
Processing complete with total matches of 8 record(s).
Server - ar6c access complete with total matches of 8 record(s).
8 record(s) reported by the runmacro-tool
8 record(s) found in the exported file
=======> END FORM Group
It's not difficult to make something that works. It just a consideration of how fancy you want it. At the moment I have given priority to the fancy stuff (GUI) instead of the stability.
So at the moment status is:
* some bad errors can be triggered if the GUI is not used correctly
* to many tools have to be installed (perl, ARS-perl, python, tk)
* it's not intuitive to use, so it has to be documented (not fun yet for this tool)
* consider putting in some threads to avoid lock-up of application during dump of forms with lots of data.
If I am able to complete this someday, I probably make it public.
_________________________
------
Quick