The GT.M side of it is simple: it's trivially easy to export the routines and database from GT.M: use ^%RO to export the routines and mupip extract to export the globals (remember to use the ZWR format). The routines are exported in a MUMPS standard format that all MUMPS implementations handle. A simple 2 line M program can import the exported global variables into any standard MUMPS implementation.
However, I don't know what it takes to reconfigure VistA once it is imported into Cache - at least ^ZTMGRSET I would guess, but you may also have to play with things like the NULL device. Also, any shell scripts would need to be recreated (e.g., presumably the way to deploy a CPRS GUI server under Cache is not the same as for GT.M). Cache on Windows would presumably be more work than Cache on Linux. -- Bhaskar On Mon, 2006-01-09 at 10:36 -0600, Marc Krawitz wrote: > Once I get a gtm-based VistA installation configured to my > satisfaction, is it possible to move the entire installation to a > Cache-based system? Or do I need to start over? > > Thanks, > > Marc > ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Hardhats-members mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hardhats-members
