The idb.txt contents impact groov but not PAC Control (which uses the .idb binary file).
By tags, do you mean non-I/O tags?
I'm hoping you could use tables to save yourself a lot of variables and redundant code, as I mentioned in this post.
For example, let's say those 30-40 tags per drive might be:
nOnFlag, nVoltageLevel, nSerialNumber, etc. (just making this up) and you're thinking you'd add:
nOnFlag1, nOnFlag2... nOnFlag100; nVoltageLevel1, nVoltageLevel2, etc.
If instead you changed each of these 30-40 tags into a table (where each element/index would correspond to a particular drive), when you'd instead have:
ntOnFlags, ntVoltageLevels, ntSerialNumbers and your tags would be in the 30-40 range instead of the 3,000 - 4,000 range. Much easier to manage. Also easier to expand when you go from today's 100 drives to tomorrow's 10,000 drives.
Do you see what I'm saying here?