Ioctl is probably a much faster way to check, but why not create the files
as part of some other monthly process (12 months in advance even), checking
anything a billion times for a onetime event seems a waste of cpu cycles.

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of
Simon Verona
Sent: Monday, September 28, 2009 8:00 AM
To: [email protected]
Subject: Dynamically created Distributed files

I have a transaction file which can get very large, and has the potential to
blow through the 2gb file size limit (we are using jBase 3.4.10 on Windows
platforms).

The item id of  the records in the file is [Internal Date].nn   eg 
15274.1 15274.2 etc.

As such, I thought that I could split the file up into a distributed 
file with part files in the format TRANSACTION.FILE.MM.YY   where MM is 
the calendar month, and  YY is the calendar year and Part file numbers of
MMYY

Writing the algorithm for filing and retrieving the records is pretty 
straightforward (just an OCONV(INT(ID),'DM') and OCONV(INT(ID),'D2Y').   
However, for each new month as the first record is written I will need to
pre-create the data file before trying to retrieve any data from it.  

I'm therefore considering the best way of verifying whether the "Part" 
file actually exists and creating it if not.   

Is there a quicker way to do this than actually opening the file in the
algorithm ?

Is there a better way to achieve the same results?

Thanks in advance.  
Simon

--
===========================
Simon Verona
Director
Dealer Management Services Ltd

email: [email protected]
tel: 0845 686 2300





--~--~---------~--~----~------------~-------~--~----~
Please read the posting guidelines at: 
http://groups.google.com/group/jBASE/web/Posting%20Guidelines

IMPORTANT: Type T24: at the start of the subject line for questions specific to 
Globus/T24

To post, send email to [email protected]
To unsubscribe, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/jBASE?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to