|
Why wouldn't you use different job descriptions for each the English and Sweedish users? There's no need to have english libraries in a library list for the sweedish. Bradley V. Stone Taylor Corporation - OASIS Programmer/Analyst bvstone@taylorcorp.com > -----Original Message----- > From: Denis Robitaille [SMTP:DRobitaille@cascades.com] > Sent: Friday, November 27, 1998 12:25 PM > To: MIDRANGE-L@midrange.com > Subject: Re: LIBL limitation of 25 libraries > > > > Denis Robitaille > Cascades inc. > Tel: 819-363-5187 > DRobitaille@cascades.com > > >>> Rob Marssdorf <Rob@cascade400.com> 11/27 11:52 am >>> > >Can the job stream be broken up into multiple runs - say one for North > >America, another for Europe? Sounds like both could run at the same time > >that way. > > It is. In fact this setup allows us to run both english and sweddish on > the same machine. The english users have the APP*ENG libraries in theire > librairy list and the sweed users have the APP*SWE libraries in their. > That is why we need 2 library per applications. > > >If not, I think that if the processing program were to explicitly > override > >the files for each application to the appropriate library at run time, > you > >could bypass the library list issue - you're not doing an ADDLIBLE, > you're > >just pointing the file to the library location with the OVRDBF. > > We would have to override message files, display files, printer files, > panel group(for help), menus. I'am not even sure if all those are > overidable. Also, this can add a lot of codes to ALL programs (Ex: clp pgm > A call rpg pgm B that call rpg pgm C ... then all override must be coded > in pgm A, maintenance hell). Also, when you explicitly use a library name, > this makes things harder in test mode (you can not use the library list to > access test object). > > Overriding data files would save 2 entries and put my maximun number of > application to 11 > > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@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 > +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@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-2025 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.