Isn't InterCall available for UD? It's supposedly the underlying interface
to UV for UO and UOJ.
Regards,
David
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Ken Wallis
I could be way off here, but I strongly suspect that ObjectCall has one
important
Hona, David S wrote:
Isn't InterCall available for UD? It's supposedly the
underlying interface to UV for UO and UOJ.
David,
InterCall definitely is available for UD. In my earlier post I think I
erroneously called it UniCall.
I do not believe that InterCall is the underlying interface for UO
If only ...
You shouldnt torture us like that - on our first day back to work after the
Easter weekend!
Now I'm going to spend the rest of the day thinking about the Black Barn
vineyard in Hawkes bay...
Enjoy your roadshow you swine grin
Brian Leach
-Original Message-
From: [EMAIL
Brian,
Whilst I appreciate YOUR position, you have to remember that I'll be leaving
NEWCASTLE, NSW - you know, the Hunter Valley? Port Stephens? Lake Macquarie? All on
the doorstop !
It IS a hard life, and I'm glad I get to do it !
PS: We are usually on the lookout for skilled people looking
Except for one possible inconsistency with the instructions regarding
OPENSEQ, the documentation seems very straight-forward. However, I'm
still missing something.
My intention is to:
1) create a record (if it doesn't already exist) in a DIR-type
file;
2) clear said record if
I've always just opened the file and deleted the record before the OPENSEQ
OPEN 'MBP' TO F.MBP THEN
FILE.NAME='customer_tm.txt'
DELETE F.MBP,FILE.NAME
OPENSEQ 'MBP',FILE.NAME TO F.SEQ ELSE NULL
END ELSE
END
Mel Maresh
-Original Message-
I may be over simplifying this but there appears to be a STOP missing
after the CLOSESEQ command. If this is actually the case in your code, the
WEOFSEQ will be executed one last time before the program terminates.
Could this possibly be the reason?
dan
If you don't position the file with READSEQ, and you don't use the
APPEND clause on WRITESEQ, it should overwrite the file from the
beginning. The initial WEOFSEQ should be unnecessary, and in fact is
probably why you're only seeing an empty file. We use sequential file
processing in a number of
Should have read farther through your code. Your problem is the APPEND
clause on the WRITESEQ statement. This means append this record to the
END of the file. You don't normally need to use this clause unless you
want to ADD data to the end of an existing file. You also don't need
the
That WAS the reason.
Thank you very much.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 13, 2004 11:51 AM
To: U2 Users Discussion List
Subject: Re: [UD] OPENSEQ, WEOFSEQ, CLOSESEQ
I may be over simplifying this but there appears to be a
Comments inline:
When I take the initial WEOFSEQ out, the first run will
produce the result I need. But if I run the program again,
the error statement is returned each time the WRITESEQ
statement is executed. When WEOFSEQ is executed right
after the OPEN... statement, I get the desired
We are running UV 9.4. And I am hoping that is the cause of my problem
I have developed a connection pooling mechanism for our Java apps. Pretty
standard stuff (java wise). Just a bunch of UniSession objects in a Stack.
When the application fires up, it logs in 10 sessions and pushes them on
Goo'day,
Check the archives.
IIRC, somebody (Ray Wurlod??? ) published a *complete* set of code for
OPENSEQ/READSEQ/WEOFSEQ, etc, full of THEN ELSE's about 12 to 18 months ago
that goes a long way to getting the damn thing working correctly.
At 03:14 14/04/04, you wrote:
Except for one
Follow up:
It turns out, if I leave 'them' alone. i.e. Don't run PORT.STATUS,
everything is fine.
It's as though PORT.STATUS triggers some kind of clean up.
I can live with that. But if anyone can give some insight into what
PORT.STATUS may be doing behind the scenes I'd be curious to
On Behalf Of Daly, Mark
I've tried using the UniSession setTimeout() method. But it
doesn't seem to have any effect.
Dave Meeks posted in April'02 suggesting setTimeout(), so I assume it
was working then. No telling whether IBM broke it after that, though!
Have you tested it outside your
I think the target was for next year.
David Jordan
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Steve Mayo
Sent: Wednesday, 14 April 2004 2:46 AM
To: [EMAIL PROTECTED]
Subject: The future of U2
Hi,
Does anyone out there know whether IBM is
Ken Wallis wrote:
InterCall definitely is available for UD. In my earlier post I think I
erroneously called it UniCall.
I do not believe that InterCall is the underlying interface for UO or UOJ.
Those are based on UCI AFAIK. There is no UNIX client piece for UCI that I
know of. Last time I
Ken Wallis wrote:
Hona, David S wrote:
Well, we've been using UCI on Solaris and HP-UX for a number
of years, so it is definitively available.
Sorry David, can you just confirm that for me? You have client 'C' or
other
language programs running on Solaris and HP-UX which use UCI as the API
I believe the wording was DB2 and then others based on 'demand'.
Roger
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Ross Ferris
Sent: Tuesday, April 13, 2004 11:06 PM
To: U2 Users Discussion List
Subject: RE: The future of U2
I'd also think that
Hona, David S wrote:
Yes, I can confirm - we have two live client 'C'
applications on Solaris
and HP-UX servers - utilising the IBM UniCall Interface (UCI)
library, to
interface to another Solaris host server (where the UV DBMS resides).
The interface works quite well, albeit with a couple
Hi
I have a client who has a paragraph that does a SELECT and sends the result
to a print queue. In other words, the results of the SELECT are a print
job. But how can we/she print headings with that SELECT?
Example code:
CT VOC UCA.WEEKLYAUDIT
UCA.WEEKLYAUDIT
0001 PA
0002 SP-ASSIGN Q21
Wow, thanks. So easy. :o)
-Original Message-
From: Hona, David S [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 14 April 2004 14:38
To: 'U2 Users Discussion List'
Subject: RE: How to display a heading with a SELECT statement?
Add FORCE to your LIST.
It's a very annoying UV feature ;-)
1) Being unfamiliar with this, I checked the manuals regarding the use of
FORCE in a LIST and I couldn't find that reference in the manuals. Could
it be for UniData rather than UV?
2) Let the FORCE be with you. . . grin Hey, it's just too good a pun to
resist.
Steve
At 02:38 PM 4/14/04
It does work with UV.
I found it in the User Reference pdf on page 1-50: Use in any RetrieVe
sentence to force the display of column headings and headers when no records
are selected.
AdrianW
-Original Message-
From: Steven M Wagner [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 14 April
24 matches
Mail list logo
