|
Dan There were any number of reasons, why OCL checked the name of the current library. I suspect, it dates back to a time before the /36, when individual libraries and files were `kept on removable disk packs, on the System 3 line of machines... If the application is split between separate libraries, then an examination of the OCL might reveal that some programs in the OCL stream are kept in another library. If all programs are in the same library on the 36EE or M36, then I suspect the PAUSE OCL is really redundant, and in effect, slowing down the whole process. If separate libraries are utilised for the stream, then the SLIB procedure is probably used. Ken Shields Oshawa systems group Works 81, Oshawa Ontario
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.