Re: rgzpfm while active

<snip>
Of course, you have to pay somewhere and doing it this way will
generate many, many journal entries presumably depending on how many
deleted records there are. You can easily blow storage space on
journal receivers or if you are a HA shop you can bring your network
and remote apply jobs to their knees.
</snip>

BINGO! We keep our receivers for 77 days and, looking at the following,
can anyone guess why I don't want to add even more journal entries?
% of Size in
Library Owner Disk 1000 bytes
#MXJRN MIMIXOWN 24.45 1551957336.1
QGPL QSYS 4.31 273331470.3
ERPLXF SSA 2.04 129374416.9
...
(Yes, that's 1.5TB for journalling. Yes, that's 10 times + larger than
our main ERP library. Yes 1/4 of our disk is reserved just for
journalling.)

As far as reuse deleted records, well, there was an "oopsie" that added a
few million rows to a table. We have this set to *YES but we don't forsee
reusing this space in a timely manner.

It's not my call as to why we let people stay logged on for days at a
time. It's not seen as a security breach since they all use Windows and
their screen savers are all password protected and kick on in 15 minutes.
Anyway, we have three shifts so someone's going to be on this file
somewhere. So even if I kill a job for someone I know is home, someone
else will be in the file. The alternative is to leave it there until next
month end closing.

We do still have 1.7TB of free space, so it's not like I'm really in a
tight spot quite yet. It's just that all that 'deleted' space is sitting
on our SSD's which are at 98%.


Rob Berendt