DSXchange

That is purely because of the PRINT statements in your code. DataStage logs a warning if anything "unexpected" appears in the output. Comment out the PRINT statements, or change them to DSLogInfo() calls, and the warning will vanish.

You will find, if you take up these services, that you must agree to your materials being "offshored". Make of that what you will.

1., 2., and 3. These are old-fashioned UniVerse naming conventions. If I remember correctly, "%" names are used internally in the engine (that is to say we don't use them at all), "!" names are functions that came from Prime INFORMATION (and the code for which expects to call such names - !GET.PATHN...

The repository is supposed to be "open", so you should be able to determine what tables are in it. Nothing has been publicly documented, as far as I am aware, regarding the data model of XMETA, so you will have to figure out where the data you require actually resides; I don't believe anyone here ha...

That's pretty much it, Wade. Protected means what it says. It's the whole SDLC (software development lifecycle) thing - nothing changes in production. So your choices, it seems to me, are two: compile before exporting temporarily un-protect the production project The second option may be the only on...

Welcome aboard. The DataDirect ODBC driver (for it is that that is represented by the VM*.so files) is shipped with DataStage. You do not need to download them. They can be found in the branded_odbc/lib directory.

Obviously it will "look" quite similar, since it is performing the same task. Tip: when "drawing" in DSXchange, use Code tags, and use Preview to get it right. Once you move to version 8 of DataStage, loading of the dimensions and the fact table can all be done in the one stream (if that's how you w...

It IS in the log. Look for events like "this step has 14 data sets". That is the execution score. The one with no data sets is the licensing score.

Welcome aboard.

Oconv() and Iconv() functions are not available in parallel Transformer stages.

This is a non-trivial process. Have you taken one of IBM's training classes? Essentially you create suite users for Information Server, then allocate suite roles and product roles. You can also set up a default DataStage user whose credentials suite users who have not been allocated a DataStage role...

Search the forum for a routine called OpenSequentialFile. It covers all the possibilities.

Basically, you have to position to end-of-file using a Seek statement (or a loop of ReadSeq statements) before attempting a WriteSeq statement. This is managed within the OpenSequentialFile routine.

So long as you don't mind your jobs taking rather longer because the loading of the tables is no longer occurring in parallel.

Isn't your support provider providing support, which you are paying them to do?

Yes, but first are the column widths adequate? You may need additional FMT specifiers. Research the commands COMO and DIVERT.OUT in your UniVerse documentation. Another way is to redirect stdout of your DataStage shell. For example cd $ProjectDir . $DSHOME/dsenv $DSHOME/bin/dssh "SELECT NAME FM...

Wanna bet? I'm involved right now in a Japanese & English mix. Yes, I understand what you're saying - that there has to be some measure of compatability - and business agreement on common terms - before data marts (or any other silos of information) can be merged in any meaningful sense. IBM's B...