× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: message MCH2804 'Tried to go larger than storage limit for object QPGMR'
  • From: Bob Larkin <blarkin@xxxxxx>
  • Date: Thu, 12 Jun 1997 21:42:11 -0700
  • Organization: Larkin Computer Consulting

karl Liss wrote:
> 
> Anyone run into this?
> 
> We are receiving message MCH2804 'Tried to go larger than storage limit
> for object QPGMR'  on our model 310 running V3R2M0.  This message occurs
> whenever a user performs a function that attempts to create an object.
> The creation fails.
> 
> Our 310 is a development, not production, machine.  It has about 60G of
> dasd.  Most of the 150 usrprfs have a group profile of QPGMR with the
> group profile becoming the owner of any new objects created.  This was
> designed to avoid the nightmare of managing objects owned by 150
> different people.  All users typically need access to the objects
> created by the other users.  Additionally, the objects created are
> commonly restored to AS/400s owned by our clients.  Since QPGMR exists
> on all AS/400s we don't have to worry about object ownership converting
> to QDFTOWN at restore time.
> 
> Depending upon who we talk to at IBM we're told the message either has
> something to do with reaching a maximum number of entries in a usrprf
> table or reaching a maximum size for the usrprf object QPGMR.  They
> say we've reached an architectural limit of the operating system and
> no fix is planned.  Only solution offered is to change ownership of
> some objects to another user profile.
> 
> Any ideas?  How do the really large shops cope with this?  We'd like to
> keep our object management relatively simple.
Check the user profile, and make sure storage is set to *NOMAX.
This could also be related to an internal table that stores authority
information. Doc is at work, but as I reacall, the problem is as
follows:
Object authority is stored in a table in the owner's user profile space.
As number of objects grows, and/or number of authorities grows, this
space becomes consumed.

Now for the good part. As authorities are deleted or objects deleted,
the entries in the table are NOT reusable. The ONLY way (according to
IBM) to fix this is to "CRASH" the AS/400. During an IPL from an
abnormal shutdown, the space is rebuilt, allowing for more entries to be
added.

HTH 
-- 
Bob Larkin
Larkin Computer Consulting
blarkin@wt.net
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.