dbTalk Databases Forums  

fopen error

comp.databases.pick comp.databases.pick


Discuss fopen error in the comp.databases.pick forum.



Reply
 
Thread Tools Display Modes
  #41  
Old   
Tony Gravagno
 
Posts: n/a

Default Re: fopen error - 10-23-2008 , 02:34 PM






dtsig wrote:

Quote:
On Oct 23, 10:42*am, Tony Gravagno
address.is.in.po... (AT) removethis (DOT) com.invalid> wrote:
dtsig wrote:
According to refman.pdf "The stream is returned as a pointer to a
character or 0 if an error occurred. *system(0) contains the error
number."

When we open an os level file with the %fopen command we get an error
of 27

streamFrom = (char*)%fopen(fileReadFrom, oFlag)
if streamFrom = 0 then err = system(0) ; debug

My question is ... where is the definition of the error numbers
returned?

...
I have looked at the unix.h table but have not found anything.

Hi Dave, you're close. You're now working in C world so the data is in
a place familiar to C developers, ERRNO.H.

In D3, that's dm,bp,unix.h, errno.h. *There you'll see error 27 is
EFBIG, which is "File too large". *Aside from trying to read a file
that's over 2GB in size, I'm not sure what would cause this in D3.
Maybe trying to read a host OS file that's larger than the 100MB VME
blob? Or possibly just more than your available overflow frames.
Please let us know if you find out what tripped this. *I do occasional
work with these functions and information is tough to find.

Regards,
T

No .. it is the size and the fact that PICK is to current sw what old
IBMPC sw was to 32bit <G

Another attempt to do real world stuff with the tools at hand. Will
work out a way with better tools to resize things to that PICK can
handle it <g

Thanks for the quick reply
Have fun blaming D3 for this here and in the U2 forum, but if you do
some research you'll find people everywhere have the same issues
(Google "fopen 2gb").

Can we take a step back and discuss what it is that you're trying to
read from a 2gb file? As we've discussed before this might not be the
right approach to the business problem you're trying to solve.

T


Reply With Quote
  #42  
Old   
Martin Phillips
 
Posts: n/a

Default Re: fopen error - 10-23-2008 , 03:42 PM






Quote:
Have fun blaming D3 for this here and in the U2 forum, but if you do
some research you'll find people everywhere have the same issues
Not everyone, Tony. QM sequential file processing (READSEQ, WRITESEQ,
etc) can handle files over 2Gb.


Martin Phillips, Ladybridge Systems.


Reply With Quote
  #43  
Old   
Martin Phillips
 
Posts: n/a

Default Re: fopen error - 10-23-2008 , 03:42 PM



Quote:
Have fun blaming D3 for this here and in the U2 forum, but if you do
some research you'll find people everywhere have the same issues
Not everyone, Tony. QM sequential file processing (READSEQ, WRITESEQ,
etc) can handle files over 2Gb.


Martin Phillips, Ladybridge Systems.


Reply With Quote
  #44  
Old   
Martin Phillips
 
Posts: n/a

Default Re: fopen error - 10-23-2008 , 03:42 PM



Quote:
Have fun blaming D3 for this here and in the U2 forum, but if you do
some research you'll find people everywhere have the same issues
Not everyone, Tony. QM sequential file processing (READSEQ, WRITESEQ,
etc) can handle files over 2Gb.


Martin Phillips, Ladybridge Systems.


Reply With Quote
  #45  
Old   
Martin Phillips
 
Posts: n/a

Default Re: fopen error - 10-23-2008 , 03:42 PM



Quote:
Have fun blaming D3 for this here and in the U2 forum, but if you do
some research you'll find people everywhere have the same issues
Not everyone, Tony. QM sequential file processing (READSEQ, WRITESEQ,
etc) can handle files over 2Gb.


Martin Phillips, Ladybridge Systems.


Reply With Quote
  #46  
Old   
Martin Phillips
 
Posts: n/a

Default Re: fopen error - 10-23-2008 , 03:42 PM



Quote:
Have fun blaming D3 for this here and in the U2 forum, but if you do
some research you'll find people everywhere have the same issues
Not everyone, Tony. QM sequential file processing (READSEQ, WRITESEQ,
etc) can handle files over 2Gb.


Martin Phillips, Ladybridge Systems.


Reply With Quote
  #47  
Old   
Martin Phillips
 
Posts: n/a

Default Re: fopen error - 10-23-2008 , 03:42 PM



Quote:
Have fun blaming D3 for this here and in the U2 forum, but if you do
some research you'll find people everywhere have the same issues
Not everyone, Tony. QM sequential file processing (READSEQ, WRITESEQ,
etc) can handle files over 2Gb.


Martin Phillips, Ladybridge Systems.


Reply With Quote
  #48  
Old   
Martin Phillips
 
Posts: n/a

Default Re: fopen error - 10-23-2008 , 03:42 PM



Quote:
Have fun blaming D3 for this here and in the U2 forum, but if you do
some research you'll find people everywhere have the same issues
Not everyone, Tony. QM sequential file processing (READSEQ, WRITESEQ,
etc) can handle files over 2Gb.


Martin Phillips, Ladybridge Systems.


Reply With Quote
  #49  
Old   
Martin Phillips
 
Posts: n/a

Default Re: fopen error - 10-23-2008 , 03:42 PM



Quote:
Have fun blaming D3 for this here and in the U2 forum, but if you do
some research you'll find people everywhere have the same issues
Not everyone, Tony. QM sequential file processing (READSEQ, WRITESEQ,
etc) can handle files over 2Gb.


Martin Phillips, Ladybridge Systems.


Reply With Quote
  #50  
Old   
dtsig
 
Posts: n/a

Default Re: fopen error - 10-27-2008 , 08:28 AM



On Oct 23, 12:34*pm, Tony Gravagno
<address.is.in.po... (AT) removethis (DOT) com.invalid> wrote:
Quote:
dtsig wrote:
On Oct 23, 10:42*am, Tony Gravagno
address.is.in.po... (AT) removethis (DOT) com.invalid> wrote:
dtsig wrote:
According to refman.pdf "The stream is returned as a pointer to a
character or 0 if an error occurred. *system(0) contains the error
number."

When we open an os level file with the %fopen command we get an error
of 27

streamFrom = (char*)%fopen(fileReadFrom, oFlag)
if streamFrom = 0 then err = system(0) ; debug

My question is ... where is the definition of the error numbers
returned?

...
I have looked at the unix.h table but have not found anything.

Hi Dave, you're close. You're now working in C world so the data is in
a place familiar to C developers, ERRNO.H.

In D3, that's dm,bp,unix.h, errno.h. *There you'll see error 27 is
EFBIG, which is "File too large". *Aside from trying to read a file
that's over 2GB in size, I'm not sure what would cause this in D3.
Maybe trying to read a host OS file that's larger than the 100MB VME
blob? Or possibly just more than your available overflow frames.
Please let us know if you find out what tripped this. *I do occasional
work with these functions and information is tough to find.

Regards,
T

No .. it is the size and the fact that PICK is to current sw what old
IBMPC sw was to 32bit <G

Another attempt to do real world stuff with the tools at hand. *Will
work out a way with better tools to resize things to that PICK can
handle it <g

Thanks for the quick reply

Have fun blaming D3 for this here and in the U2 forum, but if you do
some research you'll find people everywhere have the same issues
(Google "fopen 2gb").

Can we take a step back and discuss what it is that you're trying to
read from a 2gb file? *As we've discussed before this might not be the
right approach to the business problem you're trying to solve.

T
I agree that using D3 to get data in that is needed in the database is
not the appropriate method of accessing the data.

Here is how I normally determine something like this

1) client request to have data loaded
2) we discuss the need/use of the data. How important better outside
etc
3) if user is sure that this is for their best use we import the data
4) use d3 to import the data
5) if d3 can't import the data then we determine it isn't really
important <G>

But not to worry. we are using an external tool to break the data in
to little enough chunks for D3 to handle. Though the inability of D3
to handle it and no "plans" to add the ability has made the user
scratch their head, we have made the user comfortable knowing there
are tools out there we can use to break the data down

Thanks


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.