Dave:
The reason I suspected a joke was because most of us have never lived with
restricted variable name lengths and no longer live with 8.3 DOS file names,
except of course rundll32.exe, svchost.exe, etc. :-)
A real pain when the application is used on various mvDbms environments.
Thanks very
Hi Manu,
I'll guess that you are close to the limit of what a Windows server can
handle. If you expect growth I would go for Solaris or AIX since it's much
more scalable than a Windows server is. Linux could also be an alternative.
Windows and Linux for servers with 1-4 CPU's works fine, if you
I'm pretty sure everyone is talking about the named common name not the
variable names (i.e. the name between the slashes in COMMON /ABC$123/
LONG.VARIABLE.NAME1, ETC
The variables names defined within your common block should be able to be any
length you like (perhaps restricted to 32
I probably should have been more clear -- that's why we rearranged and put
our 'most unique' details at the front of the Named Common block -- but
ulimately, we truncated all at 7 characters.
DW
-Original Message-
In terms of readability/maintainability, the named common label can be
Did you know you can force UniData flavor by using the lowercase verb
equivalent? list, sort, etc.
Thank you,
David A. Green
DAG Consulting
(480) 813-1725
www.dagconsulting.com
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bill Haskett
Sent: Monday,
This may sound silly but the fastest way we have found is to back it up
onto tape and then load the data from the tape to the new machine.
Jeffrey Lettau
ERP Systems Manager
polkaudio
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Susan Joslyn
David,
you are of course right. I am not sure what Bill is thinking. I am
still wondering why we are staying with file names 8.3. Come on folks
how many characters do you need.
Most MV devs know that vars only need a couple of characters .. I, II,
III etc.
there is way too much typing going
Susan,
You didn't mention what operating systems you were dealing with, but I had
a similar situation with Unix and found the following to be quite
effective:
1. tar the data into a single tar archive file
2. gzip the archive file (I got 6:1 compression ratio on top of the tar
compression)
3.
Susan,
You didn't mention what operating systems you were dealing with, but I had
a similar situation with Unix and found the following to be quite
effective:
1. tar the data into a single tar archive file
2. gzip the archive file (I got 6:1 compression ratio on top of the tar
compression)
3.
Thanks David, I forgot about that. :-)
Bill
P.S. Still doesn't explain why ECLTYPE P doesn't use phrases.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
David A. Green
Sent: Tuesday, December 27, 2005 5:38 AM
To:
Of course, programs won't compile in PICK mode if the label exceeds 7
characters. :-)
Bill
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
David Wolverton
Sent: Tuesday, December 27, 2005 4:58 AM
To: u2-users@listserver.u2ug.org
Subject: RE:
This is only a guess, as I have no first hand experience with that
error. Is it possible that the item that was locked was re-read after
being updated in storage and with no COMMIT? It ought to be fairly
easy to test that as a possible means of replicating the problem.
john
On 12/23/05,
On Behalf Of Mark Johnson
Perhaps the big difference is that while an older environment could
have
hundreds of spreadsheets or basic programs, a MV system probably
won'd have but
a few names common entities.
And if you're using an include to bring in the named common, what's
the big deal
i did do a test, and it appears that i am mistaken. I can create all
types of errors but not that particular one. Would it be possible to
put out more data on the error without sacrificing confidentiality?
john
On 12/27/05, john reid [EMAIL PROTECTED] wrote:
This is only a guess, as I have no
I think I saw a similar problem when a subroutine reopened an opened File.
This caused all the Record locks to be dropped and as the records were not
locked to the isolation level, this caused a fatal. It was painful to
track, even using the error clauses, the program fataled without going
For those of you who have been around The List for the 9 or so years
I hosted it, you know I rarely give endorsements. This is one of
those exceptions that pleases me. My friend and colleague, Mark
Baldridge, has his first article published on IBM's Developer Works.
The topic is profiling
16 matches
Mail list logo
