WAIT processing was rewritten for MVS/XA, and the check for the communications ECB is in the mainline code, not in the FRR. There is no level of IEAVEWAT older than MVS/XA in our code repository, which suggests that WAIT processing was in a different module in MVS/370. I don't know which module that was, so I can't look to see how it worked.
Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp. Poughkeepsie NY >It's also possibly much more overhead than 1 ECB less as the "exception" >which allows waiting on the communications task isn't (wasn't) a short >code path. At least in MVS 3.8 it involved wait getting a program check >trying to validate the communications ECB and wait's FRR deciding no, >that was ok, it's the communications ECB. >So to avoid this extra overhead the task which waits on the communications >ECB should be one which rarely wakes up. >PS: The MVS code may have changed since them... Or not... ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
