I'm looking for some field experiences, lessons learned, or actual deployed solutions to the problem of replicating non-CACHE.DAT data in a mirrored Cache environment.
Working with customers on performance reviews, capacity planning and trouble-shooting I am often unpacking and reviewing Caché and Operating System metrics from pButtons.
Prompted by this post about accessing a global at its original location after you have changed a mapping, here's a tip about one specific dropdown in Portal that's sometimes useful.
Prior to 2017.1, whenever I created a new namespace using Portal on Ensemble or HealthShare it was automatically configured to host productions. This used to irritate me, because sometimes I'm setting up a namespace (for example, to host our Deltanji tool) that doesn't need the extra Ensemble baggage.
Sometimes I observe people scrolling manually down to the bottom of the Console Log document when they want to see the most recent messages. So I want to draw attention to the handy link that does the job for you in a single click:
If you deal with multiple instances of Caché / Ensemble / HealthShare and sometimes have to work at the Terminal command prompt, did you know that you can easily add extra information to that prompt which may help prevent you running a command on the wrong instance?
