× 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.






Bruce,
It's a good idea to issue (as you do) regularly a WRKJRNRCV *ALL/*ALL on
every system: you can find gems like your 154 receivers on one journal
very likely.
In this specific case, the system IS managing your receivers, it just don't
delete them automatically !
Your library DIRSRV looks like a SQL COLLECTION.  The parameters used by
SQL to create the QSQJRN journal are MNGRCV(*SYSTEM) DLTRCV(*NO): so you
can have a bunch of receivers left behind (specially if you are IPL'ing
often).  I would avoid to change to DLTRCV(*YES), if you need to save the
receiver before deleting it. If you don't care saving them, delete all the
old receivers, and issue the following command :
CHGJRN  JRN(DIRSRV/QSQJRN)  JRNRCV(*GEN)  DLTRCV(*YES)  Et voilà !
BTW, in V5R3, the default for the CRTJRN  CL command is also
MNGRCV(*SYSTEM) instead of *USER in the older releases: it's a significant
change.

Side question : has your DIRSRV library something to do with LDAP ?  In
this case - I mean if you are using LDAP - you will find myriads of *USRSPC
objects in library QDIRSRV2.   You can also consider a periodic cleanup of
them.

HTH

Bonne réception/Best regards
Richard THEIS
  iSeries Education, France



As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.