RE: PF member current number of increments larger than the max

Jack--

No, it's not a 'troubled' file-- the data is fine. It is a sign that whomever originally created the file didn't know how much data would be stored, and under-estimated the file size.

The problem is that every time the file fills up an 'increment' of records (ie every 100 records you add), the operating system will ask what to do about it. Usually, the option to increment the file and continue is taken. This has happened over 42,000 times!

The cure is to CHGPF and increase the base size of the file, and the size of the increments. Since the file currently has more than 4 million records, the changed size should be at least 5 million. The increment should be more than 100. I recommend the maximum-- 32767. The maximum increments is already 32767, which the file has exceeded by at least 10,000 increments!

CHGPF FILE(LIB/FILE) SIZE(5000000 32767 32767)

You can't change the file while it's busy-- pick a 'quiet time.'

Before you change the file, however-- How many deleted records does the file contain? Would reorganizing the file be a good starting point?


Paul E Musselman
PaulMmn@xxxxxxxxxxxxx

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> On Behalf Of Jack Woehr
Sent: Tuesday, November 06, 2018 2:25 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: PF member current number of increments larger than the max

Excuse the cluelessness and importunity.

DSPFD shows the following:


Member size SIZE
Initial number of records . . . . . . . : 1000
Increment number of records . . . . . . : 100
Maximum number of increments . . . . . : 32767
Current number of increments . . . . . . : 42766
Record capacity . . . . . . . . . . . . . : 4277600
Current number of records . . . . . . . . : 4277600

Is the current number of increments being larger than the max the sign of a
"troubled" file?