DSXchange

UniVerse BASIC is a superset of Pick BASIC. Indeed, UniVerse BASIC is not one language, but six, and one of its variants (not the one used originally in DataStage) is very close to Pick BASIC. None of that affects DataStage; it's more a matter for those who develop applications under UniVerse. And t...

The Copy stage can:

change field names

drop fields

re-order fields

change data type to a compatible (automatically converted) data type

The Copy stage can not:

change data in any way

add fields

change data type to an incompatible data type

Top marks for the misleading etymology!

OK start your presentation with a slide that outlines the difference between a hammer and a screwdriver. If you only have one you can do the job of the other, but it's not pretty.

1. Yes. See this document for the history and current players. They include D3, mvBase, mvEnterprise, UniVision, Reality, jBase, ONware, Open Insight, and JOI. 2. No published standards but, since UniVerse and UniData claim to have more than 70% of the market, then that's pretty much a de facto stan...

This won't help; I include it for interest only. UniVerse version 10 (the first after the split from DataStage) introduced a TO.XML keyword that dumps the result of the query as an XML document. Further options allow this to be attribute-centric or element-centric, and to include DTD or to exclude i...

Prefer Seq() function. Seq() returns the ASCII code value associated with a character. If you have NLS enabled and are using multi-byte encoding, prefer UniSeq() to Seq(). UniSeq() returns the Unicode code value associated with a character. If you have a single-byte character set, UniSeq() returns t...

Therefore we await Bala's response.

Anything is possible. It may be that you are now dealing with larger volumes of data than previously, and that the version of DataStage is not a factor. Or it may be. Can you execute the query "natively" in UniData without any problem?

It's a scheduling tool more than anything. However, if all you want to do is move stuff around within Oracle, then a combination of PL/SQL scripts scheduled from SeeBeyond/JCAPS will do the trick for you. When, in future, because of amalgamations, mergers, the need to capture data from or write data...

Before/after routines are executed once (maximum) per job run.

Transform functions are executed once per (output) row.

One example of an after-job subroutine is to archive/rename the file that has just been processed by the job.

".o" is object, ".so" is shared object. You create either with an appropriate option in your compiler/linker.

Import Table Definition is independent of job type, so you can import your stored procedure definition exactly as you would if you were intending to use it in a server job. The fact that the function failed to initialize may mean that the Stored Procedure stage has not been properly installed or reg...

Apparently not; it can also be thrown reading a stream of data. Reading the entire error message, we see that in the job src_ORA_Desc (no Invocation ID) the stage Seq_Trg_Desc and link Outto_Desc is generating the error. Can you please confirm your job design, with stage and link names? In particula...

Sounds very much like a timeout at the UniData end. Are the columns involved in the WHERE clause indexed? If they were, then maybe your SELECT would finish fast enough not to time out. Just a thought.