RE: [Possible SPAM-O365] Access Path Size

All of our ERP physical files are NOT keyed. All access is done via various keyed logical files.

I was just hoping there was a better way to identify only those files currently approaching the 4GB limit.

So I created this (I only used this over 1 library)

-- Create Physical File attributes Workfile
CL: DSPFD FILE(ASTDTA/*ALL) TYPE(*ATR) OUTPUT(*OUTFILE) FILEATR(*PF) OUTFILE(HHPLIB/PHYSFILES);

-- Physical File Size Workfile
CL: DSPFD FILE(ASTDTA/*ALL) TYPE(*MBR) OUTPUT(*OUTFILE) OUTFILE(HHPLIB/PHYSMBRS);

-- Find All Files over 3GB with Access Path Size *MAX4GB by joining them
SELECT PHFILE, PHLIB, PHAPSZ, MBDSSZ as BYTES, (MBDSSZ/1073741824) as GIGABYTES
FROM PHYSFILES
JOIN PHYSMBRS ON MBFILE=PHFILE
WHERE (MBDSSZ/1073741824) > 3
AND PHAPSZ='0'

This was a weird experience... even after changing the file, we still exhibited the issue. I'm assuming because the access path (via the logical files) wasn't yet rebuilt. I did RGZPFM over the file to fix it.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rob Berendt
Sent: Friday, March 18, 2022 8:10 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: [Possible SPAM-O365] Access Path Size

Are you physical files keyed? Because if they are not then ACCESS_PATH_SIZE will be null, along with many other fields dealing with keys.
Try this and notice the difference once you hit the NO
select *
from qsys2.sysfiles
where system_table_schema ='ROB'
order by access_path_keyed desc, system_table_name;

Rob Berendt