DataStage (from IBM) talks natively to UniData.
> - Original Message -
> From: "Jeff Butera" <[EMAIL PROTECTED]>
> To: u2-users@listserver.u2ug.org
> Subject: [U2] Pentaho/ETL Tools
> Date: Fri, 14 Nov 2008 22:44:59 -0500 (EST)
>
>
> We're in the midst of creating a data warehouse from o
MITS - www.mits.com
Native to many MV platforms - Universe, UniData, D3 etc...
And yes, we sell it and I implement it, but I would still recommend it - so I
don't believe an AD marker is appropriate.
Marvin R. Fisher
Technical Resource Group
A Pipeline Group Company
2850 Red Hill Ave.
Suite 11
I would have to challenge the concept of putting the DCOUNT as the first
value and counting backwards.
99% of the time FOR..NEXT loops start at 1 and go to some end. We assume
that there's a test for surpassing the second variable at each iteration of
FOR. But is the first variable touched only on
We're in the midst of creating a data warehouse from our UniData databases
and exploring the possibility of using Pentaho. Their ETL tool does have
an entry for Universe (not Unidata), but the connection methods are JDBC,
ODBC or JNDI.
We don't want to create an SQL-view of Unidata merely for
Thanks Mark. It's nice to know we're not crazy (at least in this matter).
Thank you to all who responded. I/we appreciate the advice, especially the use
of COUNT. It's amazing how easily tunnel-vision sets in and prohibits the
consideration of something like COUNT when that is exactly what infor
1) PICK
2) EXECUTE
3) Good idea
Jef
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hona, David S
Sent: Friday, 14 November 2008 5:08 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] SELECT-READNEXT That's odd
What UV account flavour?
What does SR.
Hey, save the variable by looping backwards - if the code in the loop
allows it, of course...
FOR A = DCOUNT(WORK.THINGY,VM) TO 1 STEP -1
code
NEXT A
-Original Message-
Also for any newbies watching. Do not put DCOUNT as the second value in
a
FOR...NEXT Loop. Assign it once prior to th
I don't know all of the settings within U2 vs other MV platforms but one
thing that was tricky for me straddling both is the concept that items from
one active list remain despite a conclusion of the use of that list. Case in
point is a SSELECT statement feeding IDS to a Data/Basic report program t
I wrote this little subroutine that will accomplish this easily. You
can either pass in just the file name or the file name with a much of
selection criteria:
SUBROUTINE HUB.COUNT.FILE (FILENAME,RCNT)
CMD = 'COUNT'
CMD<-1> = FILENAME
SWAP @AM WITH " " IN CMD
CALL SB.DISP(9,CMD)
The 'COUNT' command is also very good at establishing if and how many
records match a certain criteria without utilizing a select list.
David Laansma
IT Manager
Hubbard Supply Co.
Direct: 810-342-7143
Office:810-234-8681
Fax: 810-234-6142
www.hubbardsupply.com
"Delivering Products, Services, and
Stewart
Thanks for posting this. Very useful information.
Regards
Brian
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Mitchell, Stewart
> Sent: 13 November 2008 23:50
> To: u2-users@listserver.u2ug.org
> Subject: [U2][UV] Performance Improv
I would actually have expected that behaviour.
What is this piece of code actually try to achieve?
Is READNEXT only used to test if the SELECT statement returned any items?
In that case the CAPTURING clause with the EXECUTE statement would be a
better tool to test that.
Or you could execute CLEA
Hi Marcos,
Did you successfully re-link UV?
If so, why don't you try the "CONNECT" command to connect to your data
source.
Regards,
David
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Marcos Fogaca
Sent: Tuesday, 11 November 2008 12:09 AM
To: u2-user
What UV account flavour?
What does SR.EXECUTESQL do exactly: EXECUTE or BCI SQLExecute ?
Why don't you clearselect 0, if you're not going to process the result
select list? Like "READNEXT DEPENDANT.ID THEN CLEARSELECT 0 ELSE"..it
seems pointless ? Or are am I missing something?
-Original Me
14 matches
Mail list logo