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

... but you still can execute an CHGPF on a SQL Table to set the maximum of
rows!

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"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)


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> On Behalf Of Tyler, Matt
Sent: Dienstag, 6. November 2018 23:02
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
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.midrange.co
m_mailman_listinfo_midrange-2Dl&d=DwICAg&c=2S-2xx8Cum_thMfWs-kOOHQTwol
PvSZ4PFLhr1wDDGs&r=wgq2KO1Tl8HswJht2RKpmz7qvL2YDU_M-VhnRH6r43I&m=ABPi6
bl4NpyuCcMM48iF8RG6HllOSvu_lzN4aHLZ8-k&s=ECwb7Pi0mwowvc0cRSf-4g5jqG5sV
9IM2SJIcBaNSio&e= or email: MIDRANGE-L-request@xxxxxxxxxxxx Before
posting, please take a moment to review the archives at

https://urldefense.proofpoint.com/v2/url?u=https-3A__archive.midrange.com_mi
drange-2Dl&d=DwICAg&c=2S-2xx8Cum_thMfWs-kOOHQTwolPvSZ4PFLhr1wDDGs&r=wgq2KO1T
l8HswJht2RKpmz7qvL2YDU_M-VhnRH6r43I&m=ABPi6bl4NpyuCcMM48iF8RG6HllOSvu_lzN4aH
LZ8-k&s=qMg1OeI51GJ5tGZnkCQTfjvpWjHb4xOtmRDrhdXoDHU&e=.

Please contact support@xxxxxxxxxxxx for any subscription related

questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link:
https://urldefense.proofpoint.com/v2/url?u=https-3A__amazon.midrange.c
om&d=DwICAg&c=2S-2xx8Cum_thMfWs-kOOHQTwolPvSZ4PFLhr1wDDGs&r=wgq2KO1Tl8
HswJht2RKpmz7qvL2YDU_M-VhnRH6r43I&m=ABPi6bl4NpyuCcMM48iF8RG6HllOSvu_lz
N4aHLZ8-k&s=RRYFCSBiFl2b1NNVUM0W5mubvsyNYt1YvH5ZsarwSiI&e=

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com