Thanks. I forgot about that one. It is covered in Chapter 22 on Exits in the Auth Assembler Guide. This would also be classified as a branch entry intercept.
-----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Gerhard Postpischil Sent: Tuesday, April 09, 2013 9:15 PM To: [email protected] Subject: Re: Use of the TRAPx Instructions On 4/9/2013 7:03 PM, Kenneth Wilkerson wrote: > So now specifically to asynchronous exits. There are 3 ways to > schedule asynchronous exits that I know of, by STIMER(M), by SCHEDIRB > and by the old, SCHEDXIT. If there are other ways, please let me know. There is at least one other - see the CIRB macro. Before HASP, operators on an OS/360 system had to issue an explicit START RDR command to read a job stream. I had a parameterized facility (define command, alter, delete by unit) that caused an unsolicited interrupt to a defined device to trigger the appropriate command, thus obviating the need for the operator to start the reader. For MVS I have a version with more flexibility - I can set an ATI in designated UCBs, and issue any command in response to an interrupt. This is handy for activating CRT terminals on a different floor (not all are defined to VTAM). The MVS version does not use CIRB, nor does it use the Master Scheduler; instead it calls CVT0EF00 directly to schedule an IRB and IQE. Gerhard Postpischil Bradford, Vermont ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
