In message
2b1985075953c947a7a53a53987adab22b5...@arnold.hkmetalcraft.lan,
Brutzman, Bill bi...@hkmetalcraft.com writes
A user here obtained an error message...
COMMON size mismatch in subroutine HOP.R87.
Upon logging out and then logging back in again... The HOP program was
able to
that's from basic, I meant from the prompt.
Save-list works, but only to type 1/19 files, not with type 30 files,
well, it still works, but not in a usable way.
although, that could be an undocumented feature of save-list, you can
write items to a type 30 file, that can't be read back or
I Just tested this.
If the file is a type 30 file, and you do an open path, it sill only
reads the items in the DATA/OVER.30 portion, and ignores any other
files that are in the directory, like ones that SAVE.LIST would put
there.
-Original Message-
From:
1. The program was not created by an auto-generator.
2. The user only has one way to go in.
3. Others here may have been in the program when he went in. Also,
others here have access to an older version of
the program that may have been active when this user went in... likely
having the same
Since all common variables are cleared when you exit UniVerse, and
eliminates the error, is it possible your user used a LOGTO command to
switch environments that have different versions of the subroutine
HOP.R87?
We had both a Test and a Prod environment on the same box, and experienced
UniVerse ODBC Client
Version 4.0.3
Build 7251
February, 2008
on both PC's
We are not SHIMS. We are not Prelude.
This may be a lost cause. Perhaps a better way to approach this problem
is via an external program talking to
Brutzman, Bill wrote:
UniVerse ODBC Client
Version 4.0.3
Build 7251
February, 2008
on both PC's
We are not SHIMS. We are not Prelude.
This may be a lost cause. Perhaps a better way to approach this problem
is via an
We are doing this with separate ODBC account that has a subset of
dictionaries with I-descriptors that call subroutines to extract the
required data back to UPS. The VOC entries on the ODBC account point
back to the production data.
We used a different logon since we did not want our Universe
Question: If you are doing a select statement and within the
statement you have a eval phrase and this eval phrase contains all
constants (ie, DATE() - 14), does Universe recalculate that constant
value with each record iteration or is it smart enough to know that this
is a constant value
DATE() is not a constant, but rather a function that will return a different
value each day.
You can see the object code that is produced using VLIST and examine it for
optimizations.
Best regards,
Henry
Henry P. Unger
Hitech Systems, Inc.
http://www.hitech.com
-Original Message-
Barry
'Date() - 14' isn't constant - the Date() function is designed specifically
to be evaluated each time. '@DATE - 14', on the other hand, should be
constant.
You should see a difference between the two if you run a query across
midnight...
Same with TIME() and @TIME: try both on a long LIST
Hi Henry,
You can see the object code that is produced using VLIST and
examine it for optimizations.
The particular optimsiation that Barry is looking for would not show in the
object code. For a truly constant I-type expression, the query procesor
could evaluate it just once and store the
Hi Martin,
I was under the impression that an EVAL calls the same compiler that an
I-type does, and that any expression optimization would be done therein.
Expanding beyond that, it would be interesting if the I-type compiler was
able to detect that a particular expression does result in a
Hi Henry,
I was under the impression that an EVAL calls the same compiler
that an I-type does, and that any expression optimization would be
done therein.
As far as I know, EVAL does indeed call the same compiler. As I think you
realise, the point is that an I-type expression such as
1:
Hi Martin,
I did say not, so we are saying the same thing.
I like that QM is smart about it.
Best regards,
Henry
Henry P. Unger
Hitech Systems, Inc.
http://www.hitech.com
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On
Research continues and I have more question for the group: my Oracle
buddies rebuild their indexes at least weekly. Seems to be a best
practice. Seems odd to not be able to trust that your index is correct. Is
this a concern for ud 7.1?
TIA,
Brad.
ud 7.1
AIX 5.3
U.S. BANCORP made the
I think Oracle's indexing scheme is much more complicated that
Unidata's, so I don't think you can compare the two. I do rebuild some
of the dynamic files on occasion to get some space back. Other than
that, I leave them alone and haven't had problems. - Rod
-Original Message-
From:
Thanks, Rod. One more thing. I've written a test program to simplify index
creation and building. When I run it under type U or type P using
BUILD.INDEX or BUILD-INDEX, it gives me the Enter New line to
continue... prompt after each screen of *'s. Definitely not desirable for
an automated
It's probably for performance - when a table has lots of
inserts/deletions the index gets fragmented.
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of
bradley.sch...@usbank.com
Sent: Thursday, July 16, 2009 1:00 PM
Brad,
We have a client with over 3 million records with 14 indices running on
Unidata 7.2. We have never rebuilt the indexes in over two years. The last
time we rebuilt them we added some 2 more indexes. We just purged about a
1/2 million records with no problems on the indexes that are used
In your program, do a CRT @(-1) at the top of the program to disable the paging.
John Israel
Sr. Programmer/Analyst
Dayton Superior Corporation
721 Richard St.
Dayton, OH 45342
937-866-0711 x44380
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
Try adding CAPTURING TRASH to the end of your EXECUTE statements.
Mark
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of
bradley.sch...@usbank.com
Sent: Thursday, July 16, 2009 1:19 PM
To: U2 Users List
Subject: Re:
Hi Henry,
I did say not, so we are saying the same thing.
Whoops! I missed one word. Guess which one!
Martin Phillips
Ladybridge Systems Ltd
17b Coldstream Lane, Hardingstone, Northampton, NN4 6DB
+44-(0)1604-709200
___
U2-Users mailing list
I usually do a TERM 132,999
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of
bradley.sch...@usbank.com
Sent: Thursday, July 16, 2009 3:19 PM
To: U2 Users List
Subject: Re: [U2] More questions on indexing
Thanks,
Any PRINT @ will turn off automatic pagination. You can also use BPIOCPN.
Thanks,
David A. Green
www.dagconsulting.com
(480) 813-1725
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of
bradley.sch...@usbank.com
Sent:
TERM 132,0 should work too.
Thanks,
David A. Green
www.dagconsulting.com
(480) 813-1725
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Baakkonen, Rodney
A (Rod) 46K
Sent: Thursday, July 16, 2009 1:25 PM
To: U2
Brad:
I've defined indexes in my files with dictionary items like INDEX_1,
etc. Thus only these dictionaries are ever used for indexing. A file
may have 4 or 5 indexes (INDEX_1 - INDEX_4).
I wrote another program to do the indexing for a single file or an
entire account by executing the
One more thing that we do. We build a database of our indexes every
night using a 'cron'. It does a
find / \( -name 'idx001' -o -name 'X_*' \) at a UNIX level.
The results of this 'find' are then passed into a Unidata program. Using
a combination of LIST.INDEX and INDICES we get all the info we
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of
Brutzman, Bill
Sent: Thursday, July 16, 2009 8:20 AM
To: U2 Users List
Subject: Re: [U2] ODBC to UPS WorldShip
UniVerse
Henry,
EVAL compiles the expression and writes the result into the dictionary, runs
the query and then deletes the dictionary item. For your test to be valid you
would need to ignore the overheads of the compile, write to and delete from
dictionary which in your example are significant
Consider becoming a customer integrator and use the web XML API. It's not
that complicated to implement if you're doing domestics only. If you're
doing international, then it's a bit more complex but nothing like FedEx.
We've been fully automated with both FedEx and UPS in terms of
In Unidata (v6.x) you can issue the command BUILD.INDEX MYFILE ALL. With the
KEYWORD ALL it's builds/rebuilds all the indexes that have been created on
the file. I would hate to have to remember that INDEX_1 is say, Customer
Name, verus a dictionary named CUST_NAME.
I would agree with others, I
Good point, Andy. I had considered that, but guessed that it would not be a
significant factor.
Just in case, I created a file with a million records, and reran the tests.
Here are the results:
COUNT TESTFILE WITH F1 = 'V'
Elapsed 7.4796
COUNT TESTFILE WITH F1 = EVAL 'V'
Elapsed 23.2558
Seems
In message
of44cc39a8.134b5a9d-on882575f5.006f2b76-862575f5.006fa...@usbank.com,
bradley.sch...@usbank.com writes
Thanks, Rod. One more thing. I've written a test program to simplify index
creation and building. When I run it under type U or type P using
BUILD.INDEX or BUILD-INDEX, it gives me
I concur with Glen's assessment that some of these services can
be unstable. Not long after writing NebulaShip
(nospamNebula-RnD.com/products/ship.htm) I realized that even
though the product was stable that we might be getting emergency
calls when services were down. I stopped advertising the
35 matches
Mail list logo
