|
I fail to see how it is better to "quietly grab" ANYTHING, especially system state or *ALLOBJ authority. Yes, I see the disadvantage of running the entire process with *ALLOBJ. I believe that is the conventional solution (what I call "Generally Accepted 400 Practice", because imnsho, YOU NEED TO ACTUALLY ***KNOW SOMETHING*** of the vendor of ANY software You are loading. Granted the vendor may have a disgruntled employee who intends to wreak havoc... This is definitely a possibility, but a more likely one is that You may have them in Your own shop anyway... Maybe this is something We'll just hafta agree to disagree on, Leif... I dunno...? j | [mailto:midrange-l-admin@midrange.com]On Behalf Of Leif Svalgaard | example: a vendor product needs to have *ALLOBJ for brief periods | (for whatever reason that does not concern us). It is better that he | has a mechanism to quietly grab that authority only when he needs | it and then letting it go when done, rather than run everything with | *ALLOBJ in system state etc all the time. To run "system high" | (as the military jargon goes) is convenient but is an overkill and | can be dangerous as you have too much power and can do | damage (e.g. if there are bugs in your product).
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.