|
boothm@ibm.net wrote: <snip> > The only way that the job can now > be closed is by calling the program again and turning on LR in it. If > you don't do it in your program then the call stack will when a program > higher in the stack receives an LR instruction. AFAIK even if the caller has on LR the called program stays active. You must either call it with an option to seton LR, perform a RCLRSC (Reclaim Resources) or sign off. I've never worried about it too much, since I want the program in the users PAG. Variable reset is controlled by the caller via a call/feedback parameter. If a program is called so infrequently that I don't want it hanging around it returns with LR on. +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.