]
Reply-To: u2-users@listserver.u2ug.org
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] WRITE issues??
Date: Mon, 21 May 2007 13:44:21 -0400
The more I think about this, I can't imagine it being a software problem
or a hardware problem. It doesn't make sense
Thanks everyone. I'm trying to answer all questions in the same email.
We have a very old system (about 20 years). It's mostly 'vanilla'
pick. We've been using UniVerse for longer than I've been working with
this system (4 years). I worked with MUMPS for the previous 23 years.
We don't
I know you already said it's ok, but I'd double check for READs where
READUs belong.
Especially since you've described this as having a Pick heritage from a
time when some Pick implementations and programmers did not handle
locking well.
One user's changes can easily wipe out another's.
WRITE
)
also has the MD's created on it
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Pamela J Robbins
Sent: Tuesday, May 22, 2007 9:07 AM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] WRITE issues??
Thanks everyone. I'm trying to answer all questions
Thanks,
I've already found a few. I tested them and you're correct. I saw it
happen. We're still
looking for more of those.
Pam
Stevenson, Charles wrote:
I know you already said it's ok, but I'd double check for READs where
READUs belong.
Especially since you've described this as having a
Has anyone seen a problem like this? The user claims they changed a
record, then checked to make sure it actually changed. They find
everything updated, but on checking days later, finds the data back in
it's original state. We've had several claims like this over the past
week and a half
Pam,
I've seen this with bad locking schemes. Does your application do
real U2 locking, or is it using a custom lock scheme?
Charles Barouch ([EMAIL PROTECTED])
Pamela J Robbins wrote:
They find everything updated, but on checking days later, finds the
data back in it's original
The more I think about this, I can't imagine it being a software problem
or a hardware problem. It doesn't make sense. It has to be user
problems. I did find a program that didn't have locks, but that's been
fixed and doesn't apply here.
Pamela J Robbins wrote:
Has anyone seen a problem
I had a customer who would take their nightly backup tape and restore it
to a secondary server the next day. Well, one time the operator got
confused about which machine he was on, and sure enough, restored prior
day's backup onto the Live system. Wonder if he's still there?
Mark
Has anyone
Pamela J Robbins wrote:
Has anyone seen a problem like this? The user claims they changed a
record, then checked to make sure it actually changed. They find
everything updated, but on checking days later, finds the data back in
it's original state. We've had several claims like this over
It's using READU to lock records. I did find a couple of programs
without locks at all. They were the root of some of the problems.
Unfortunately, when I put them in, one of the users decided to break out
of the system by closing SecureCrt and caused a problem. I would like
to redo the
Yes, it does sound like a programmer/operations issue and we have a new
user supervisor who is trying to make things more efficient. The
changes could be causing some of the problems. They're good changes,
but the users need to get used to them.
No test system, I keep praying for one
been made
but in actuality the array hasn't been updated.
Jerry
- Original Message -
From: Charlie Rubeor [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Monday, May 21, 2007 1:52 PM
Subject: Re: [U2] WRITE issues??
The only way that I know that this can happen is if the server
Here 'Trigger! Sounds like it may be time for some type (really
really simple) of update audit.
j
On 5/21/07, Pamela J Robbins [EMAIL PROTECTED] wrote:
Has anyone seen a problem like this? The user claims they changed a
record, then checked to make sure it actually changed. They find
Warning: This message has had one or more attachments removed
Warning: (not named).
Warning: Please read the AngelicHost-Attachment-Warning.txt attachment(s)
for more information.
Ditto, I had one boss that thought he would solve some locking issues by
putting a RELEASE in one of our main data
15 matches
Mail list logo
