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

Someone needs to teach SQL about bad programs!

Paul E Musselman
PaulMmn@xxxxxxxxxxxxx

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

Anything but *nomax is not allowed for SQL DDL tables.

-Matt

On Nov 6, 2018, at 2:54 PM, Musselman, Paul <pmusselman@xxxxxxxxxxxxxxxx> wrote:

Booth--

~eeeeewwwww~ *NOMAX!

In this case, I'd probably set the size at 10,000,000 records to start with. That's double the existing size.

I cringe when I hear *NOMAX-- I have visions of a program running away one night and filling all available storage (almost said 'disk space') until the OS says "I give up" and shuts down the system.

"Oh, but the programs that touch that file have been running for -years- without problems!"

*sigh*

Paul E Musselman
PaulMmn@xxxxxxxxxxxxx

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

I am curious; why aren't you recommending *NOMAX?

On 11/6/2018 2:36 PM, Musselman, Paul wrote:
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

--
Booth Martin
www.martinvt.com
(870)576-9371
(802)461-5349

Brain fried -- core dumped