A small detail about using CPUID rather than SYSTEMID which would have mattered to me in a previous incarnation ...
The CPUID in question is the VIRTUAL CPUID. Once upon a time I was required to provide the capability to flip between default RSCS's with a user command. That is, sometimes you'd specify to reach another system via RSCS-1 but at other times you'd say to reach it via RSCS-2 and, having specified it, expect commands such as SENDFILE to behave accordingly. I implemented this capability by having two entries in SYSTEM NETID and issuing SET (virtual) CPUID commands inside the CMS machines to flip between RSCS targets. (This is simplified - there are a few flaming hoops involved if you want to try if for yourself.) My point is that the current criterion (cpuid) is dynamically variable whereas the proposed criterion (SYSTEMID) is fixed. Once upon a time this would have been an issue for me. Nowadays, for me, the convenience and simplicity of SYSTEMID would win hands-down - but it DOES imply a tradeof f and, if implemented, may irritate one or two remaining eccentrics such as I used to be. Regards Jeff
