mvScan going open

mvScan was originally a tool that I had developed for my use, to document a UniVerse system by iterating through the account and file structures, building impact maps and filling out tables with information culled from the entries found to make it easier for someone to search through their system.

Information such as the relationships between files, programs, subroutines, external functions, SUBR() dictionary calls, translates, includes, common blocks, use of variables, string tables, calling menus and paragraphs. All captured, linked together and available for enquiry or to build documentation, assisted in my case with my autodoc headers and version stamps.

However, and I stress this, it was a tool for my own use.

After various questions in various forums - especially the u2-user list - from people wanting something along these lines to document their systems, I decided to package it up and add it to my product list. But with every system being so different, however adaptable it is (and it is designed to be highly adaptable) I'm always worried whether it has had enough of a real world thrashing for me to feel confident offering it as a packaged product.

So I've decided the best way forward is for me to open it up. That way, people who want to run it on their systems can do so and feed back any updates and changes that result from applying it to their specific structure and code organization.

So watch this space for announcements. If this goes well, there's plenty of other stuff I want to open source.