Running Universe 10.0.17 on Windows Server 2003 32bit:


Can I create a distributed file for a data file that is part of shared
dictionary (ie a multi-level data file)?



I can't seem to get the syntax right.



Here is the scenario.  We have a large stock file with current
transactions called STOCK that contains about 2 years of transactions
and a growing history file with data copied from STOCK,STOCK to
STOCK,HIST on a semi-annual basis.   We've had to limit this STOCK,HIST
file to about 2 years because of the 2GB limit.



We are on Windows Server 2003 32bit and cannot create 64bit files, so
I'd like to implement a distributed file for this STOCK,HIST and copy in
about 4 to 6gb of older (offline) history data into it.



Since the records are pure numeric and sequential I was going to create
10 part files and use the partitioning algorithm as INTERNAL
"@ID[LEN(@ID),1]+1".



What would be my steps and syntax to do this?



>From my research, I have been successful at using DEFINE.DF, etc to do
this at the primary datafile level like STOCK (aka STOCK,STOCK) but not
when I reference a sub data file off of STOCK (like STOCK,HIST) it blows
up.  Sample below using similar names:



Creating the files work fine:



:CREATE-FILE TEST.STOCK 1,1 101,1

:CREATE-FILE TEST.STOCK.HIST.PART1 1,1 101,1



Then using the following to associate TEST.STOCK,HIST with the first
part file fails:



:DEFINE.DF DATA TEST.STOCK,HIST ADDING TEST.STOCK.HIST.PART1 1 INTERNAL
"@ID[LEN(@ID),1]+1"



I get:



DICT and PDICT are not legal keywords with multilevel DATA files.

File not created.



If I leave out 'DATA' above, no difference.



All of the existing applications software and dictionaries reference
STOCK (comma) HIST or I'd just rewrite this as a new data file like
STOCK (DOT) HIST and be done. This may end up being the work-around if
this just won't work.



Either multi level data files are not supported or I'm not getting the
syntax correct.  Any help would be much appreciated!





-Troy
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/

Reply via email to