RE: PF data space management

Thanks all,

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.

Thanks.
Matt.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[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
released.

No use doing a REORG on this file, as there are no records so you might
as
well CLRPFM. If there was just one record, then it would make sense to
do a
Reorg to recover the space.

Pete

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Matt Laskosky
Sent: Wednesday, March 26, 2008 8:10 AM
To: midrange-l@xxxxxxxxxxxx
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 . . . . . :

Data space size in bytes . . . . . . . : 26353664

Physical file open accesses . . . . . . :
12
Physical file close accesses . . . . . :
12
Write operations . . . . . . . . . . . :
1,673
Update operations . . . . . . . . . . . :

Delete operations . . . . . . . . . . . :

Logical Reads . . . . . . . . . . . . . :

Physical Reads . . . . . . . . . . . . :

Clear operations . . . . . . . . . . . :
1
Data space copy operations . . . . . . :

Reorganize operations . . . . . . . . . :

Access paths builds/rebuilds . . . . . :

Records rejected by key selection . . . :

Records rejected by non-key selection . :

Records rejected by group-by selection. :


How can I manage the data space size?

Thanks.

Matt Laskosky, Consultant
Dynamic Information Services Corporation
IBM Certified Specialist
Ph#: 734-476-5200
Email: Matt@xxxxxxxxxxx