Serious users of VTAM exits (e.g. session managers) run authorized and set their LUs fastpath. VTAM responds by using SRB intead of IRB.
Old memory, but no protection was in place to handle same exit running multiple times. May have had something to do that sends and receives were executed on multiple tasks. There is a field passed to VTAM which she returns (correlator field?) used to handle parallelism. Woe betide the programmer who does not have all code rent. I remember a case where one of our exits was non-rent. The fix was labeled "any abend anywhere any time any symptom". It was necessary to have each correlator value be assigned to run on only one task. IBM Mainframe Assembler List <[email protected]> wrote on 06/01/2011 08:49:04 AM: > From: Chris Mason <[email protected]> > >> no asynchronous exit routine can interrupt another asynchronous exit > >> routine > > Perhaps VTAM does something special, but in general this is not true. > http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/f1a1d930/2.5.4 > Unless VTAM development is lying through its collective teeth, there's no > "perhaps" about it. > Chris Mason ----------------------------------------- The information contained in this communication (including any attachments hereto) is confidential and is intended solely for the personal and confidential use of the individual or entity to whom it is addressed. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this communication in error and that any review, dissemination, copying, or unauthorized use of this information, or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. Thank you
