|
Booth: In the example I gave, each job that started ==within that subsystem== would have the system portion of the library list amended by having the SYSLIBLE() entry placed at the top of the list. (Hmmm... I wonder what happens if the job is then routed elsewhere...) BTW, it wasn't to say that Mike was wrong, but simply to note that the system portion may be amended without CHGSYSLIBL. (Of course, there's nothing to stop someone from only running a single job in a particular subsystem.) Tom Liotta On Mon, 03 December 2001, "Booth Martin" wrote: > When you change the System Library List, don't you change it System wide? > For everyone that signs on from then on? Not just for the duration of your > job, or for your job's users? > -------Original Message------- > Mike: > Note that there are additional ways to amend the system portion of a library > list although AFAIK none are as specific as a direct CHGSYSLIBL executed > within the job. One example is through the SYSLIBLE() attribute of a > subsystem description which is perhaps most commonly used to add a language > library for jobs in that subsystem. > Tom Liotta > On Mon, 03 December 2001, Mike.Collins@syan.co.uk wrote: > > The question related to the System Library List, not the User Library List > > > which unless something has changed since V4R4 of the operating system > > cannot be specified on a job description, and can only be amended via > > CHGSYSLIBL if you wish to amend it for an individual job. Unless I am > > misunderstanding the question of course. -- Tom Liotta The PowerTech Group, Inc. 19426 68th Avenue South Kent, WA 98032 Phone 253-872-7788 Fax 253-872-7904 http://www.400Security.com ___________________________________________________ The ALL NEW CS2000 from CompuServe Better! Faster! More Powerful! 250 FREE hours! Sign-on Now! http://www.compuserve.com/trycsrv/cs2000/webmail/
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.