• Subject: Objects per user
  • From: Rob Berendt <rob@xxxxxxxxx>
  • Date: Thu, 9 Jul 1998 13:12:37 -0500

We are getting a MCH2804 message on one of our AS/400's.  We checked the user 
profile, (a group profile), and it is set to *NOMAX on disk.  However IBM is 
leading me to believe that the problem is not in the total size of the objects, 
but in the number of the objects.  Also factoring, (although I am not exactly 
sure on how the factor works), in the number of user profiles using that group 
profile.  There is a theoretical limit of around 1,000,000 objects that can be 
owned by anyone.  This group profile owns between 200,000 and 300,000 objects.  
There are 112 users associated with the group profile, only 24 of them have 
signed on this month.

The funny thing is, is that I think this factor is limited by the number of 
active users and not total users.  We had someone sign off and others stopped 
getting this message.  This message appeared on many commands:  CPYFRMQRYF, 

I've done no testing to see if the number of sessions per user matters.

IBM has reported this problem occurring in multiple levels of the operating 

Has anyone else seen this problem?  Most likely to occur in a shop where one 
group profile owns many many objects, or, in a shop where a group profile owns 
many objects and there are many users in that shop on the system at the same 
time using the same group profile.
| 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 thread ...


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

This mailing list archive is Copyright 1997-2019 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].