|
Thanks for all the help. This seems to be what is happening - it is a Unix converted piece of software leaving user space objects for EVERY transmission in QUSRSYS. ----- Original Message ----- From: "Jim Franz" <franz400@xxxxxxxxxxxx> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> Sent: Tuesday, September 30, 2003 8:47 PM Subject: Re: Object information repository > If not the QUSRSYS/QP0Z* user space objects, I have had a similar problem > (several > years ago) with one of the major edi packages leaving a user space object > after every single transmission, times many thousands a day, every day..... > At V5r1, max objects in a lib is 360,000 (from knowledgebase) > jim > ----- Original Message ----- > From: <bdietz@xxxxxx> > To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> > Sent: Tuesday, September 30, 2003 9:07 PM > Subject: Re: Object information repository > > > > > > > > > > > > I have noticed the same thing. I am v5r2. Here is some thing from V5R1. > > It appears that the APAR says it will be fixed in a future version. V5R2 > > does not seem to be that version. > > > > I usually just run this every once in a while DLTUSRSPC > > USRSPC(QUSRSYS/QP0Z*) > > > > > > > http://www-912.ibm.com/n_dir/nas4apar.NSF/1be1a5b61b213a6c86256c23007048f4/20d7b3701fdaf71086256ba1003d1b89?OpenDocument&Highlight=0,QTOCTCPIP > > > > > > ------------------------- > > Bryan Dietz > > 3X Corporation > > 614-410-9205 > > > > > > At 01:07 PM 9/30/2003 -0500, you wrote: > > >I am getting a CPD2120 - Cannot add new objects to library QUSRSYS. It > > seems > > >that QUSRSYS is filling up with *USRSPC objects. Has anyone experienced > > >this, and how was it fixed? > > > > > >Thanks, > > >Trevor > > > > _______________________________________________ > > 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. > > > > > > > _______________________________________________ > 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. >
As an Amazon Associate we earn from qualifying purchases.
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.