Barbara, Sounds like you have some battle scars there :-)
Back in the day when I was a sysprog, we used to define catch-alls in both RACF and WLM definitions so that when we installed new software that required STCs we used to deliberately make them drop thru unless the install doc was specific. The catch-alls gave the STC no real RACF access to speak of (or any OMVS segment) and placed the STC in STCLO. When problems arose that were due to RACF/WLM/whatever omissions, then we went back and bashed the ISV (or IBM) over the head with the doc. Likewise any issues with the new STC requiring other STCs like OMVS and TCPIP - the software should either support the ability to recognise that the parents are AWOL and wait/retry or it should be written in bold in the install doc. A "resource-owning" ASID should quite happily live with the default catch-alls. Rob Scott Developer Rocket Software 275 Grove Street * Newton, MA 02466-2272 * USA Tel: +1.617.614.2305 Email: rsc...@rs.com Web: www.rocketsoftware.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Barbara Nitz Sent: 29 September 2009 13:45 To: IBM-MAIN@bama.ua.edu Subject: Re: Ownership of PC routines >>"however some of the giant brains in some customer sites will still >>wail and gnash their teeth at you." >> > It is astonishing how often this happens - as if asking for a started > task is somehow akin to demanding the first-born child. Chris may have refered to the fact that this is an address space that 'just' sits there and owns a PC and does who-knows-what-we-don't-know to the system, especially when it crashes. On the other hand, an address space that just sists there and does nothing always is suspicious. Not to mention that it causes problems when you least expect them. Have you ever thought what needs to be done to get a new address space established? RACF definitions, WLM definitions (and don't scream about bad performance if you forget to tell me that it *should* run in SYSSTC!), Automation definitions, not to mention that this needs to get done on test, development and in production .... And then go and try to get the answers to 'which service class should this run in?' or 'What are the parents of this address space?' (in other words: Which address spaces does this thing need to run successfully?) out of whoever has to install a new address space! In some cases they don't know and the docs don't mention this, either. Yes, getting me to establish a new address space (especially one that appears to sit around around and does nothing or - worse - that has feet in OMVS) is worse than stealing my firstborn! :-) Best regards, Barbara ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
