Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!uwm.edu!zaphod.mps.ohio-state.edu!usc!snorkelwacker!apple!agate!ucbvax!DB0ADW11.BITNET!RZA31LH From: RZA31LH@DB0ADW11.BITNET (Lutz Hamann) Newsgroups: comp.lang.asm370 Subject: Re: HNDEXT macro Message-ID: <9008311022.AA27434@ucbvax.Berkeley.EDU> Date: 31 Aug 90 10:22:51 GMT References: Sender: daemon@ucbvax.BERKELEY.EDU Reply-To: IBM 370 Assembly Programming Discussion List Distribution: inet Organization: The Internet Lines: 25 X-Unparsable-Date: Thu, 30 Aug 90 16:50:10 MEZ On Thu, 30 Aug 90 09:36:59 LCL Stelios Fragakis said: >On SC24-5284-0 (CMS Macros and Functios References) page 73, note 7 says: > >7. It is your responsibility to issue a HNDEXT CLR in the application that > issued a HNDEXT SET,address. Under certain environments, no > cleanup is performed by DMSINT after the execution of the program. > For instance, when you terminate the programm using 'HX'. On our computer the interrupt-handling routine is in this case still active (but we have an early release of VM/SP, may be not 100% compatible with the IBM-Original). >My question is whats the "certain" enviroment mentioned above. I want to be >able to keep the HNDEXT active for a while (say 4 minutes) after the program >has terminated. Any danger on that ? > It depends on what you will do in this 4 minutes or where the interrupt- handling routine was loaded. If it was nearby address x'20000', than better do nothing (no xedit, no call of user-programs). If it is a nucleus extention, it should work (if the extention was not dropped). Bye Lutz P.S. Question please only through the list (we're not yet in the BITEARN NODES)