It would have helped those of us who only follow IBM-MAIN to have some clue of what the question was.
STORAGE is equivalent to GETMAIN in terms of serialization. For what it's worth, GETMAIN/FREEMAIN can be considered now a beast of the past. STORAGE LINKAGE=SVC is GETMAIN/FREEMAIN (for at least the more common options such as RC / RU); STORAGE LINKAGE=BRANCH is GETMAIN/FREEMAIN with BRANCH=YES. No further changes will be made to the GETMAIN/FREEMAIN macro, instead making changes to the LINKAGE=BRANCH and LINKAGE=SVC (and of course LINKAGE=SYSTEM) paths of STORAGE. Many sub-task managers do not want their threads to do things directly that can "wait" (instead, calling back to the task manager, in effect, to manage that processing). There are a lot of system services that can "wait", if by "wait" one includes getting suspended waiting for a lock, a latch, or an ENQ. I'm not sure if "wait" in this context includes spinning for a lock that is not currently available. If it does, then just about any system service might apply unless it runs throughout in user state and key. A few services get by with CS, CDS, and PLO for serialization; many more need some lock, some latch, and/or some ENQ and thus can "wait" (again, depending on the definition of "wait", suspend locks count and spin locks might or might not count). . Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
