MFILES possibly? - check you are not too low.
Allow all the O.S. level partfiles in the complete distributed file set
including indexes as well as your normal allowances.
Otherwise triggers (as suggested elsewhere) or try a LIST.SICA ...
Regards
JayJay
---
u2-users mailing list
u2-users@lis
Price
Sent: Thursday, September 14, 2006 12:12
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Debugging a program using distributed files causes
core dump
It varies as it is at the point where I decide to stop 'S'tepping
through the debugger. It is never the same line of code.
Bre
6 12:59 PM
To: 'u2-users@listserver.u2ug.org'
Subject: RE: [U2] Debugging a program using distributed files causes
core dump
When running in Visual mode, what is the last program statement you see
before the blowup?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECT
same record.
Brenda
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob Woodward
Sent: Thursday, September 14, 2006 10:39 AM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Debugging a program using distributed files causes
core dump
How about a bad
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob Woodward
Sent: Thursday, September 14, 2006 10:39 AM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Debugging a program using distributed files causes
core dump
How about a bad data record? If I was the one running this, I
e looked at all I want to see, I just hit 'C' to
continue and it blows up.
Brenda
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brian Leach
Sent: Thursday, September 14, 2006 9:52 AM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Debuggin
re to keep in mind when you
complete a loop that you may not get to your EXIT message.
BobW
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brenda Price
Sent: Thursday, September 14, 2006 7:13 AM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Debugg
esn't help answering Brenda's question though.
Brian
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of jpb
> Sent: 14 September 2006 14:21
> To: u2-users@listserver.u2ug.org
> Subject: Re: [U2] Debugging a program using dist
: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Wednesday, September 13, 2006 8:18 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Debugging a program using distributed files causes
core dump
Does the process continue through a program where the source
Huh???
- Original Message -
From: <[EMAIL PROTECTED]>
To:
Sent: Wednesday, September 13, 2006 8:18 PM
Subject: RE: [U2] Debugging a program using distributed files causes core
dump
Does the process continue through a program where the source file is
pointing to the
Does the process continue through a program where the source file is
pointing to the object file ... like the DF algorithm ... the debugger
could maybe be trying to display or traverse binary where it expects
source? Or through a program compiled with source symbols suppressed
No, we don't use triggers.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob Woodward
Sent: Wednesday, September 13, 2006 11:26 AM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Debugging a program using distributed files causes
core dump
I trust some mates more familiar with distributed files will also
respond...
but you might try this just to get you going:
UniVerse handles things differently if you do
OPEN '','CUST' TO FILENAME ELSE GOSUB DEALWITHIT
SELECT FILENAME
LOOP WHILE READNEXT
more.stuff
REPEAT
or
EXECUTE 'SSELECT
Is it possible that you have a trigger on the file? Triggers don't do
well with the debugger.
BobW
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brenda Price
Sent: Wednesday, September 13, 2006 8:17 AM
To: u2-users@listserver.u2ug.org
Subject: [U2] De
14 matches
Mail list logo