Rich,
I'd be interested to see why the application needs that many MEMBERS in the
file...perhaps some redesign could put that into one file and make life
easier... I recall an application years ago that did a lot of member useage
that was a royal pig...we redesigned it to use a single file and performance
was nicer...but that was a LONG time ago...
As for the file deletion, not understanding a lot of your other parameters
there, and presuming that you need to run this procedure a lot, why not
stick the file in QTEMP??? That would allow not only multiple concurrent
runs, but would take care of any object coexistence conflict
issues...wouldn't address the time duration issues though...
Eh, just some random thoughts...
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rich Loeber
Sent: Thursday, February 21, 2008 1:44 PM
To: Midrange Systems Technical Discussion
Subject: File w/Large Number of Members
Hello list,
I'm working with an application that has a work file that builds up a
large number of members while the application is running. It takes
several hours to complete. I even bumped into IBM's restriction of no
more than 32,767 members in a physical file with this one.
I'm have a minor issue with deleting the work file when I'm all done.
When the file has 30,000+ members in it, it can take more than an hour
for a DLTF to run. Has anyone ever run across this before? Are there
any tricks out there to speed up the file deletion process?
Rich Loeber
Kisco Information Systems
http://www.kisco.com
midrange.com
