Re: Object quantity limit for QPGMR access

Time to circle the wagons. I have had this problem at MULTIPLE accounts. The
limit is not an exact number, but rather dependent upon the space of a table
associated with the user profile.

In the first case, the system generated a large number of files in QTEMP. Each
file would consume space with the authority information. the gotcha was that
when the job went away, the file went away. BUT THE SPACE IN THE TABLE DID NOT!
It was unusable. There was an APAR on this problem, but the solution was UGLY.
At that time, the only way to reclaim the space in the table was to deliberately
CRASH the AS/400. Yup, hit the EPO. During IPL from an abnormal termination, the
space would be rebuilt, reclaiming all of the lost space.

I do not know if this has been corrected. At the time, IBM felt, rightfully so,
that there were not enough accounts experiencing the error, to warrant a more
elegant  solution.

We are currently exeperiencing the same situation in an environment where we are
scanning documents to optical. Each document is an object, so we must create
many profiles, as the profiles quickly run out of space, even though we archive
the documents offline to an optical jukebox. (Running under OS/2 for you Warp
fans)

The other gotch is the 324,000 object limit in a library. QDOC contains all
directiories, subdirectories, and objects for the QDLS file system. At 324,000
or so objects, you get nasty messages about the integrity of backup/restore. We
have alleviated it temporarily by creating a QDOC0002 in ASP 2,  but soon will
need to create QDOC0003 and ASP3.

With Multi Terabyte machines, and Data warehousing such hot topics, maybe IBM
needs to examine these limits, and what it will take to raise the bar.  They
need to do it quick before the NT bigots in the shop I am at find out!!
PLEASE!!.
Bob Larkin

Betsy Moore wrote:

> This command returns a list of about 2000 objects.  Using service tools, we
> can see the #of owned object entries, the #of private authorities, and the #
> of private authorities for other users of QPGMR objects.  In total, this
> exceeds the 1,048,000 authorities allowed.
>
> We have multiple member files owned by QPGMR with a great number of multiple
> members.  Apparently, when you have an object owned by QPGMR and other users
> are granted private authority to that object, each of those user/object
> combos counts as a hit toward QPGMR access to the object.
>
> Al Barsa, Jr. wrote:
>
> > At 01:08 PM 5/21/99 -0400, you wrote:
> > >>>>
> >
> > > We have a problem this morning with QPGMR needing to own or have
> > > explicit access to more than 1,048,000 objects which is the system
> > > limit.  Determining the owned objects is not a problem.  Does anyone
> > > know how to list the objects to which QPGMR has explicit authority but
> > > does not own?
>
> >
> > DSPUSRPRF USRPRF(QPGMR) TYPE(*OBJAUT)
> >
> > Al
>
>
>   Betsy Moore <betsy.e.moore@lmco.com>

begin:          vcard
fn:             Bob Larkin
n:              Larkin;Bob
org:            <A HREF="HTTP://web.wt.net/~blarkin/">Larkin Computer Consulting</A>
adr:            <A HREF="http://web.wt.net/~blarkin/">Bob and Diana's Page</A>;;;Houston;TX;<A HREF="http://web.wt.net/~blarkin/">;United States
email;internet: blarkin@wt.net
title:          Systems Consultant
x-mozilla-cpt:  ;4104
x-mozilla-html: FALSE
version:        2.1
end:            vcard