|
Al, >The reason to use a persistent library (as opposed to QTEMP) is that a real >library lasts from job to job. QTEMP is unique to any job, but insures >that you control your own QTEMP. > >My suggestion would be to create a persistent library (e.g.:$$TEMP), and >then have the start-up program clear it on each IPL. > >The one difference between my solution, and the use of QRPLOBJ (which I >also object to) is that my solution is not persistent across achieving a >restricted state of OS/400 (without some relatively complex coding), but I >suspect for most purposes, this is persistent enough. Besides authority considerations, what objections do you have to using QRPLOBJ? -mark * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 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 MAJORDOMO@midrange.com and specify * * 'unsubscribe MIDRANGE-L' in the body of your message. 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.