David Logan wrote:
I don't understand the reams of discussion about how to handle multiple threads working on a single ECB, or even a single thread spuriously posting an ECB. It isn't what it was designed for.
Ummm. Yes. It is. That how most of z/OS is put together! And, most ISV software too ... including ours Er ... um .. at least that portion that hasn't been converted to enclave SRB mode, eligible for zIIP redirect. SRBs prefer SUSPEND and RESUME.
To me, saying that ECB is a poor design is like saying a bicycle is poor design because you can't use it to reasonably travel the 80 mile round trip to work and back. Just because you can't use it for a purpose you *want* to use it for doesn't mean it's poorly designed. Use it for the purpose it *was* designed for.
IBM invented Pause/Release in OS/390 V2R8, at least in part, to help mitigate the pitfalls of WAIT/POST, especially in cross-memory situations. That speaks volumes.
If you want to do multiple task management, use a locking mechanism more suited to the task, like ENQ/DEQ or a spin lock if you can get away with it.
No. We're talking about queuing requests and retrieving associated responses from a service TCB. The last thing you want to do is single thread that process using ENQ or other serialization mechanism. z/OS and related products would slow to a crawl.!
-- Edward E Jaffe Phoenix Software International, Inc 5200 W Century Blvd, Suite 800 Los Angeles, CA 90045 310-338-0400 x318 [EMAIL PROTECTED] http://www.phoenixsoftware.com/ ---------------------------------------------------------------------- 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
