I created the errlog file and it does appear to be logging some messages.
Do I have to do anything in uniadmin as I see a couple of error messages
when universe first starts up.
Sun Mar 01 01:00:11 -4701 NT AUTHORITY\system uniVerse Log Daemon started
Sun Mar 01 01:00:11 -4701 NT
Well,
Apparantly the problem was a item ID was in the file.
Also, in looking at this example (not expecting a blank Item ID)
SELECT FILENAME
LOOP
READNEXT ID ELSE EXIT
WHILE ID DO
CODE
CODE with GOSUB
CODE
CODE
REPEAT
SELECT FILENAME
LOOP WHILE READNEXT ID
We use Windows and its kept at \\Mars\UVDB\TOOLS\ERRLOG.BACKUP
Eric Armstrong
Lobel Financial
IT Dept
-Original Message-
From: Mike Roosa [mailto:mike.ro...@gmail.com]
Sent: Friday, February 27, 2009 7:32 AM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] AUTOLOGOUT and ON.ABORT
I
Allen,
Regarding your loop structure below. What happens if the ID is empty string?
Won't it bail out before all the ids are read!
Eric Armstrong
Lobel Financial
IT Dept
-Original Message-
From: Allen Egerton [mailto:aeger...@pobox.com]
Sent: Friday, February 27, 2009 8:37 AM
To:
You should read your uvconfig file (and Manual) to see if you have a flag for
it in the Windows version of Universe. On the Unix version, the only thing I
need to do in order to turn on the loggin is to create the errlog file.
Your admin menu may have an option for it somewhere.
-
It shouldn't, at least not to a empty ID because the
condition test is on the READNEXT, not the ID.
However, it will pass an empty ID to the coding, which
could be worse, if there aren't constraint checks on
the ID.
George
-Original Message-
From: owner-u2-us...@listserver.u2ug.org
I tend to use:
SELECT FILENAME
EOF = @FALSE
LOOP
READNEXT ID ELSE EOF = @TRUE
UNTIL EOF DO
CODE
CODE
CODE with GOSUB
CODE
CODE
REPEAT
The advantage here is that it allows you to bail out of the loop of you want
to by setting EOF
David
--
From:
Eric Armstrong wrote:
Allen,
Regarding your loop structure below. What happens if the ID is empty string?
Won't it bail out before all the ids are read!
Eric Armstrong
Lobel Financial
IT Dept
Nope. It's running off of an active select list, it'll process the
record. Since I'm selecting
I never thought about a ID. Is this something you would do
deliberately for some reason or is it something that would happen
accidently? Can you write a record with a null ID? What would it hash
to?
Regarding your loop structure below. What happens if the ID is empty
string?
Won't it bail
It happens accidently with us, and Universe writes the record just fine.
Eric Armstrong
Lobel Financial
IT Dept
-Original Message-
From: charles_shaf...@ntn-bower.com
[mailto:charles_shaf...@ntn-bower.com]
Sent: Monday, March 02, 2009 10:47 AM
To: u2-users@listserver.u2ug.org
Subject:
I use
LOOP
READNEXT ID ELSE ID = ''
UNTIL ID = ''
Do Stuff
REPEAT
I thought this was a safe way to check for the end of the list. I just
used the ID as a flag and I wasn't sure what the value would be at the end
of a list. I guess I was assuming that a SELECT list would not
Depends
If you want to try to put a stealthy record in a file, you it's deliberate.
Most times, it accidental due to a Write who's ID for whatever reason had a
value of
and it will come back to bite you if you don't consider it, case in point I
didn't
even consider that to be the
And the disadvantage is that you still have an active select list when
you set EOF to TRUE.
David Beaty wrote:
I tend to use:
SELECT FILENAME
EOF = @FALSE
LOOP
READNEXT ID ELSE EOF = @TRUE
UNTIL EOF DO
CODE
CODE
CODE with GOSUB
CODE
CODE
REPEAT
The advantage here is that it allows you to
I have had to abandon that as well.
Eric Armstrong
Lobel Financial
IT Dept
-Original Message-
From: charles_shaf...@ntn-bower.com
[mailto:charles_shaf...@ntn-bower.com]
Sent: Monday, March 02, 2009 11:18 AM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] Strange happening...
I use
We have found out the hard way that an unintentional empty string record
ID can also produce some VERY strange record lock situations. It seems
like everyone who tries to access the file winds up queued for a record
lock on the bad ID. (UD/SB+/Prelude)
As a rule of thumb, one shouldn't use a string as a boolean unless it's
intended to be a boolean like a 0 or a 1. I've encountered many bugs because a
test would do:
IF VARIABLE THEN
Instead of:
IF VARIABLE NETHEN ...
or IF LEN(VARIABLE) 0
- Original Message
From: Timothy
Mark Johnson suggested the following change
Before
GOOD.ANS=FALSE
LOOP UNTIL GOOD.ANS DO
PRINT ENTER 'Y' OR 'N' :;INPUT ANS
IF ANS=Y OR ANS=N THEN GOOD.ANS=TRUE REPEAT
after
LOOP WHILE TRUE DO
PRINT ENTER 'Y' OR 'N' :;INPUT ANS
IF ANS=Y OR ANS=N THEN EXIT
REPEAT
These forms all work
The case can be tested also if n/y are acceptable:
LOOP PRINT ENTER 'Y' OR 'N' :;INPUT ANS,1
UNTIL INDEX('NY',UPCASE(ANS),1) REPEAT
*-- P.AM will contain a boolean value 0 for N, 1 for Y --*
FOR X = 1 TO (X+1)
PRINT ENTER 'Y' OR 'N' :;INPUT ANS,1
FIND UPCASE(ANS) IN N:@AM:Y SETTING P.AM
18 matches
Mail list logo
