I have tried copying the file to QTEMP which changes the data space
size. So I know I can reduce the data space size. Also, based on the
suggestion below I added 1 record to the file and performed a file reorg
which has reduced the file size to 12,288; so, getting the file size
down is possible in probably many different ways.
This file was originally created as an output from interactive SQL.
Anyone happen to know where the interactive SQL session pulls the
default from to create a PF? Originally, the file size attributes were
MAXMBRS(*NOMAX) and SIZE(*NOMAX); so, if as Mike Cunningham suggested
the Allocate Storage parameter defaulted to *YES this may explain how
the file initially was size to 26MB.
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Massiello
Sent: Wednesday, March 26, 2008 8:27 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: PF data space management
Did the file at one time contain records and then you deleted all the
records? If you delete ALL the records it doesn't recover the space, it
stays out there. If you CLRPFM then all storage that was used is
No use doing a REORG on this file, as there are no records so you might
well CLRPFM. If there was just one record, then it would make sense to
Reorg to recover the space.
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Matt Laskosky
Sent: Wednesday, March 26, 2008 8:10 AM
Subject: PF data space management
I have a PF with zero records and a size of 26,353,664; WOW zero records
and a file size of 26MB.
The physical file description attributes the file size to the "Data
Space Size", see below.
Data Space Activity Statistics . . . . . :
This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact