|
> From: rob@xxxxxxxxx > > Why not just call an API that changes the library list? Are you asking "as opposed to calling a CL program"? If so, my response is that CL programs are really easy to write and call. Not everything needs to be turned into a call to an API; there are certain things that CL does really well, and environment maintenance is one of them. With the QLICHGLL API, you have to pass values for current library and product library 1 and 2, as well as the array of libraries and a binary count. Even if you're just passing *SAME, it's a point of error, whereas with the CHGLIBL command, you need only change the library list. Not only that, it opens the door to expansion down the road. What if he also wanted to change priority and timeslice? Or output queue? Multiple API calls might be fine, but an environment setting CL program might be just as nice. And since this is a one-time call, the overhead of a CL program is not prohibitive. Joe
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.