I think it's a universe/unidata difference. I get the segmentation fault
running unidata in ecl type U as well.
Here's some interesting info and an ugly hack--in unidata.
It seems completely wrong to me (UV in Prime flavour)
Apparently, the keywords SUBROUTINE and FUNCTION are interchangable
Then I would suspect that the local based U2 Headhunters would have the best
clues to that
Joe Chelston, Matt Hart et al
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED]
Sent: Thursday, June 23, 2005 5:25 PM
To: u2-users@listserver.u2ug.org
Well, the idea was to produce something that could be called as a
function from basic, because the function calling syntax is cool and
convenient in a lot of cases, but that could also be used in a I-type.
For things to work in SUBR in an i-type, you need that extra parameter.
Of course you could
Something I did in some subroutines which makes them more of a multi
tasker (I-descriptors) and flexible, is to pass file variables as
parameters - when you can. So, the subroutine would look something
like;
snip
SUBROUTINE GET.NEXT.IJKEY(FILE.CN, ERR, F.STAT, IJKEY)
$INCLUDE HEADERS
Yes, I'm sure we all would... :)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED]
Sent: Thursday, June 23, 2005 5:25 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Parsippany
Wow, wouldn't we all love to get a list like that.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Anthony
Dzikiewicz
Sent: Friday, June 24, 2005 9:40 AM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Custom Functions
Something I did in some subroutines which makes them more of a multi
tasker
FYI, from IBM's Today Newsletter...
Ascential and IBM - Hear the complete story.
Attend the live webcast, Wednesday, June 29 at 11:00 am eastern. Hear
the complete story of Ascential and IBM.
http://www.ibm.com/isource/cgi-bin/goto?on=IMNL605K11
This webcast will cover the IBM Information
One I can thing of, and I normally work on UV and prefer, is that you
can debug programs which interact with file which have triggers on them.
In UV this is not possible and is seen as an enhancement!
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL
I'm hoping someone has a solution to an issue plaguing one of our clients.
The system is Universe 10 over AIX, using OleDB from .NET client and it is
running normally for telnet users.
Many SQL select statements are being issued to the server
successfully, but once in a while an E_FAIL error
That's a useful feature. Anyone else know of any?
I've noticed that unidata is accomodating about letting you run
subroutines as though they were programs, and calling programs as though
they were subroutines. Is that an advantage or something scary?
-Original Message-
From: [EMAIL
Just a guess ...
When we use ODBC we often see this type of error, when the record we are
trying to access is locked.
There does not seem to be anyway to force a READ ONLY connection via
ODBC. I'm not sure about OleDB.
Noah
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL
When I said 'hack' I meant the ugly code that I had to create to make
the trick work--the idea of having to put a dummy parameter into the
function call in the basic program in order to make it compatable with
the subr call in the i-type. Sorry for the confusion there.
-Original Message-
12 matches
Mail list logo