I'm porting a DSM system to Cache (5.08 and I have very little Cache experience at this stage). Because this is a simple port and we wish to migrate to Cache style software at a later date I wish to keep the ported system completely separate from any IS installed or future cache code and data.
I thought that the best way of doing this was to build the database as a self contained set of files and namespaces. The system contains some '%' system globals and routines and for completeness I wanted to use mapping to map the CACHESYS globals and routines to the new namespaces. This seems to work for globals I create (and map) in CACHESYS (e.g. ^%TEST) but I have failed to successfully map the installed IS ones across (e.g. ^% utility). Am I making life difficult for myself? There are very few IS globals and routines in CACHESYS these days - do people simply mingle their own system globals in there when doing traditional M stuff?
