If you change your journal as follows, the receivers are automatically deleted as soon as they will be detached.
QSYS/CHGJRN JRN(YourJrnLib/QSQJRN)
TEXT('COLLECTION - created by SQL')
MSGQ(*LIBL/QSYSOPR)
JRNRCYCNT(*SYSDFT)
MNGRCVDLY(10)
DLTRCV(*YES)
DLTRCVDLY(10)
Mit freundlichen Grüßen / Best regards
Birgitta Hauser
Modernization – Education – Consulting on IBM i
Database and Software Architect
IBM Champion since 2020
"Shoot for the moon, even if you miss, you'll land among the stars." (Les Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them and keeping them!"
"Train people well enough so they can leave, treat them well enough so they don't want to. " (Richard Branson)
"Learning is experience … everything else is only information!" (Albert Einstein)
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Patrik Schindler
Sent: Sunday, 17 August 2025 00:02
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Disk space issues with not automatically deleted journal receivers
Hello,
when developers create databases and tables through SQL, journaling is automatically set up, and set to mngrcv(*system), which is good. But the journal is not set to delete detached receivers by default. This in turn slowly but steadily eats up disk space.
Is there a way to tell the SQL CREATE command to set dltrcv(*yes) right from the start?
Secondary issue: When I try to run chgjrn dltrcv(*yes), I'm faced with CPF70E3, "Only attached receivers allowed in receiver directory". The second level text says, I should run wrkjrna and press the function key to work with the receiver directory. The screen offers only F17=Show attributes of connected receivers. Also, said screen looks very different on 7.3, compared to V4R5 — which I'm pretty much used to.
I have no better idea what to do but use wrklib option 12 for every SQL created library, and delete all but the highest numbered receivers. This makes me lose receivers which haven't been saved (by the automatic daily savchgobj), yet.
What would be the proper way to deal with this situation? Thanks!
:wq! PoC
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
As an Amazon Associate we earn from qualifying purchases.