It looks like the file variable is getting hammered.
Is the VOC item OK?
Are you using RCVR as a variable anyplace else?
If you are re-opening the file you may need to close it first.
Hth
Colin
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listse
GS:
I answered these questions in a subsequent post.
I am opening the file ok... the record was whacked.
I now merely validate the record ID before continuing in the program.
--Bill
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.o
Bill,
If I read the error message correctly the problem is to do with opening the
file not reading the record.
Are you really opening the file for each record read?
Are you sure you are in the account where the RCVR file exists - i.e. does the
code cross-log at all?
Regards,
Gregor
-Origin
Thanks to Dan and Allen for writing but...
fixTool found no error.
My next step would be to reboot the server but... I did that yesterday...
cleanly... to install a new server keyboard sharing switch.
I suppose that I have to create a case with Rocket tech support.
--Bill
>ed VOC RELLEVEL
000
'NEWACC' not 'NEWACCT'.
(Allen - Sent from my paperweight)
On Mar 21, 2013, at 1:32 PM, Allen Egerton wrote:
> That will give the universe version for the current acct. Double check by CT
> NEWACCT RELLEVEL.They should match if the current acct is up to date.
>
> (Allen - Sent from my
That will give the universe version for the current acct. Double check by CT
NEWACCT RELLEVEL.They should match if the current acct is up to date.
(Allen - Sent from my paperweight)
On Mar 21, 2013, at 1:04 PM, Dan Goble wrote:
> To tell the version of UniVerse edit the VOC RELLEVEL and
To tell the version of UniVerse edit the VOC RELLEVEL and it will display the
version on attribute2
To the file for corruption I would recommend running the unix command fixtool
supplied by Rocket.
fixtool -helpwill show you all the options and syntax
Dan Goble | Senior Systems Engineer
I am having trouble with my Recent Receivers UniBasic app running on
UniVerse 10 ? on HP-Ux 11i v2.
The app buzzes through receivers file RCVR and then hangs up on this one.
The RCVR file is approx. 15-MB.
I tried deleting records but the same symptom recurs.
I resized the file in the SandBox
Jeffrey:
I had to set it to 2500 in Windows, otherwise I had problems.
HTH,
Bill
- Original Message -
*From:* jbut...@hampshire.edu
*To:* U2 Users List
*Date:* 3/21/2013 3:51 AM
*Subject:* [U2] unidata env var
We
Yup, we've bumped higher than 6000 before.
Jeff Butera
--
A tree falls the way it leans.
Be careful which way you lean.
The Lorax
On Mar 21, 2013, at 11:19 AM, Colin Alfke wrote:
> Then I'm not going to say anything about the 16384 we used to set it to :)
>
> Colin
>
> -Original Message--
Then I'm not going to say anything about the 16384 we used to set it to :)
Colin
-Original Message-
From: Dave Davis
Sent: Thursday, March 21, 2013 7:38 AM
To: U2 Users List
Subject: Re: [U2] unidata env var
Uppercase has always worked for me.
$VFIELDSIZE and $vfieldsize are distinct va
Blame the vendor (Datatel) for piggish code.
Jeff Butera
--
A tree falls the way it leans.
Be careful which way you lean.
The Lorax
On Mar 21, 2013, at 9:37 AM, Dave Davis wrote:
> Uppercase has always worked for me.
>
> $VFIELDSIZE and $vfieldsize are distinct variables to the operating syste
Uppercase has always worked for me.
$VFIELDSIZE and $vfieldsize are distinct variables to the operating system, so
I suspect you should stick with uppercase.
6000 - that's huge - what are you putting in these things? I've had to
increase to 380 or so before.
-Original Message-
From: u
We've had some issues with i-desc failing over years and the solution
was to set the evironment variable VFIELDSIZE to some amount (6000 or more).
My real question is does unidata care about case for this variable (on
*nix, not windoze)? I've seen it documented both as VFIELDSIZE and
vfieldsi
Is this the latest version of UV - also is this on linux or Windows ?
One thing to check is character encoding - if your lang settings are not
utf-8 but the xml contains utf-8 you can get memory errors.
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun.
15 matches
Mail list logo