Roger Cope wrote: > I'm porting a DSM system to Cache (5.0.8 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.
Yes, you should plan to keep them separate forever. > 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? I think so. What you said sounds backward. I think your System Global mapping for each application namespace should point to the new "MGR" database that you created. Thus you should be in your new "MGR" namespace mapping ^% back to %SYS, not the other way around.
