> Note that we're not using the info settings on the IOC.
We're simply (mis-)using the familiar syntax for storing some related info in the *.db file.
Might as well have used "#info(..." to turn it into a magic comment that's ignored by the database yet used by our tool, which is a python script that parses the database files for "record(xx, THE_NAME)" and then an optional "info(archive...)", from which
it creates the archive configuration file.
The script won't handle macros in the database files and doesn't promise to handle all possible database files, but it's been helpful for this purpose.
I wonder if leveraging the function makeAutosaveFileFromDbInfo from the autosave module is used, one may not have to worry about macro substitution.
We can have additional information inserted in the info field to indicate various modes of archiving, group names and the group enable parameters.
This function's source code can be customised to extract info relevant to the CSS arcihver as a .req file. This info can be further converted to XML format.
OR
ofcourse we can do so independently by having a aSub record fetching the info records after iocInit
Kuldeep
