r and this will eliminate this technique/program from use.
Bill
>-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED] On Behalf Of Kevin King
>Sent: Saturday, September 01, 2007 8:47 PM
>To: u2-users@listserver.u2ug.org
>Subject: Re: [U2] UD: Variable
Is it just me, or as this output gets bigger does this seem like an
increasingly problematic implementation?
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
Bill Haskett wrote:
I altered SHM_LMINENTS from 32 to 64 (not sure why though) and restarted
UniData.
What's the difference between altering SHM_LMINTS (# of entries in the MI
table of an
LCT - currently set at 32) and SHM_GPAGESZ (the size of the global page in
a SM
segment - current set at 256).
>-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED] On Behalf Of Wally Terhune
>Sent: Saturday, September 01, 2007 10:32 AM
>To: u2-users@listserver.u2ug.org
>Subject: RE: [U2] UD: Variable size
>
>Ok -
>we don't generate ipclogs on Win
Ok -
we don't generate ipclogs on Windows - just UNIX systems. so...
1) Try running the program from a console session to see if there is a
screen message that doesn't get a chance to display before your telnet
disconnect.
2) Also - you can monitor the program's memory use from another session (o
PROTECTED]
>[mailto:[EMAIL PROTECTED] On Behalf Of Wally Terhune
>Sent: Saturday, September 01, 2007 7:50 AM
>To: u2-users@listserver.u2ug.org
>Subject: Re: [U2] UD: Variable size
>
>not enough information.
>terminates in what manner?
>with what error?
>on what platform?
&g
cc
stserver.u2ug.org
Subject
[U2] UD: Variable size
08/31/2007 09:24
x27;s worth of data as needed was easily fast enough to keep up with
users -- even when scrolling one line at a time.
Regards,
David Beahm
Date: Fri, 31 Aug 2007 20:24:29 -0700
From: "Bill Haskett" <[EMAIL PROTECTED]>
Subject: [U2] UD: Variable size
I run a screen scrolling
I run a screen scrolling program that builds a report as a BASIC variable then
scrolls it to screen one page at a time. I recently ran into a condition where
the
size of the report, in the internal BASIC variable, gets so large that UD
terminates,
and the telnet session aborts. It's not the dat
