McKown, John wrote:
Anybody have a definate response as to whether a STORAGE function can cause the TCB to become z/OS non-dispatchable. I agree that it is not a good idea to do this in CICS.
Work unit non-dispatchability is the key. They are throwing around the term "WAIT" inappropriately. I saw someone post that the interrupt caused by the SVC causes the TCB to be "interrupted". Ay Caramba! So does a page fault. [Sigh!] I posted the following in an attempt to get people back on track:
|In z/OS software development parlance, WAIT is an inappropriate term for |this. GETMAIN/FREEMAIN might be CPU intensive, but they cause absolutely |no implied WAIT. (Contrast with other services e.g., RACROUTE |REQUEST=AUTH where an implied WAIT is likely or inevitable.) | |Tangentially, in a virtual storage environment, /any/ storage reference |can lead to a system-initiated WAIT for your work unit if a page fault |occurs and the needed data is on AUX. But, that's another issue entirely. | |BTW, in z/OS 1.10 or higher, specifying: | |Vsm UseZosV1R9Rules(NO) | |in DIAGxx can speed up GETMAIN/FREEMAIN processing. -- Edward E Jaffe Phoenix Software International, Inc 5200 W Century Blvd, Suite 800 Los Angeles, CA 90045 310-338-0400 x318 edja...@phoenixsoftware.com http://www.phoenixsoftware.com/ ---------------------------------------------------------------------- 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
