On Wednesday, 02/22/2006 at 07:39 EST, David Boyes <[EMAIL PROTECTED]> wrote: In either case, doesn't it make sense to have IDENTIFY return a default > RSCSid of RSCS (if there is no SYSTEM NETID entry specifying otherwise) > instead of *, since everyone *does* have RSCS these days, and (unless > you know what you're doing and have deliberately changed the id) it's > always installed as userid RSCS? > > It does no harm, and strikes me as something that is in the category of > picking sensible defaults (and in at least one case, a default that > avoids a problem and makes it easier to exploit useful function).
It's been on my mind for some time to get rid of SYSTEM NETID anyway. One or two new SET commands, with defaults of <systemid> and RSCS, and all will be fine. With that thar new-fangled gizmo, SYSPROF EXEC, who needs SYSTEM NETID? Or IDENTIFY (REFRESH? Once RSCS was pre-installed, the solution was evident. We simply haven't had any round tuits to spare. Hey! I know! We'll do installation SYSPROF exits at the same time so you have a place to issue said SET commands! Yeah, that's the ticket! Some day... We've got round tuits on backorder. :-) Alan Altmark z/VM Development IBM Endicott
