Re: Locking everybody out of an application database library

[Luis Rodriguez <luisro58@xxxxxxxxx>]

James,

Does your master serve job run with a specific user, different from the rest
of your users? If so, you could (temporarily) change your library's auth.
list, excluding the rest of your users (assuming, of course, that nobody has
*ALLOBJ authority...)

Regards,

Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries


On Wed, Dec 30, 2009 at 1:26 PM, James H. H. Lampert <
jamesl@xxxxxxxxxxxxxxxxx> wrote:

> Here's the situation:
>
> We have an application database library. In addition to our application,
> it may also, depending on the customer, have customer-specific
> inbound-data propagation programs (triggers, periodic update programs,
> maybe even exit programs, or any combination thereof) accessing it.
>
> The library itself is on the library list of our application's master
> server job (which does nothing but spawn off child-server jobs whenever
> a client connects).
>
> Now, we want to do an update to that library, adding fields to one or
> more of the files, with a CL program. We're holding the master server
> job, and checking for any child-server jobs before we start, in order to
> keep our application out.
>
> But any ideas on what we could put an *EXCL lock on, that would lock out
> any of the inbound data-propagation without forcing us to kill the
> master server job outright?
>
> --
> JHHL
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.