DSXchange

If you would prefer to use hashed files (so that they can be used in other, non-RTI-enabled jobs), you can use the UV stage to access them. The UV stage also offers multi-row return. However, you don't get the memory cache (but, then, you don't get that with ODBC stage either). Another advantage of ...

Best practice in this case is to make the jobs as atomic as possible, so that there's never any need to merge except at the control (job sequence) level. IMHO.

The number of lines in the file can be determined using wc -l filename One less than this can be obtained with expr `wc -l filename | awk '{print $1}'` You could create a command or script that captured one less than this value and used it in the head command. For example: lines=`wc -l fil...

In my case the difference turned out to be in Red Brick changing how CHAR data types are handled in SELECT statements between versions 6.10 and 6.20; prior to 6.10 they had an automatic TRIM applied, from 6.20 this ceased to be done. The problem was not in DataStage at all. Sorry about the delay in ...

Changes to DS_JOBOBJECTS are not required. Siva is showing you the form of the 200+ update statements you could use in place of the 200+ changes using Manager or Designer! If there is a systematic change to be made (as a silly example you might want to name your jobs JOB0001, JOB0002, and so on), yo...

SQLAllocHandle is a call to a function in the ODBC API, one of SQLAllocEnv, SQLAllocConnect or SQLAllocStmt. The DB2 API largely follows the conventions and protocols of the ODBC API. Without any other information it's really difficult to diagnose further. However, you may find the following informa...

Can you see the mapped drives when you try to import a table definition?

Is your ALLOWNFS configuration value set to 1?

That's a BASIC expression. A suitable BASIC expression would be Fmt(YR,"R%4") : "-" : Fmt(MO,"R%2") : "-" : Fmt(DA, "R%2") Apparently (according to other posts on this forum), you should seek to use a non-BASIC expression if y...

This should work. For each row in the hashed file there is a set of two columns possibly called UpperLimit and LowerLimit. DSLink1 is the stream input and DSLink2 is a reference input link. You can constrain which rows are delivered from the hashed file using the Selection tab; if you don't use the ...

Here's the test program; 0001: OPENSEQ "FREDFILE" TO HFILE 0002: THEN WEOFSEQ HFILE 0003: WRITESEQ "LINE 1" TO HFILE ELSE NULL 0004: WRITESEQ "LINE 2" TO HFILE ELSE NULL 0005: !!! WEOFSEQ HFILE 0006: CLOSESEQ HFILE 0007: STOP 0008: END I inspected the result with filepeek and with vi . It made no di...

It's always possible. No-one's perfect. I'm remembering from Prime INFORMATION, but believe that CLOSESEQ behaves as I described in UniVerse and therefore in DataStage. Maybe will do the test in my copious free time!

You may find the article Date Conversion Demystified useful too. Beware that some stage types convert the date into DataStage internal format (an integer), while other stage types don't. You did not specify which stage type you are using. Basically, though, if the dates are arriving as character str...

You need to know two tricks. One is that the data in the work sheets must be in columnar format with column headings (these become the "column names") in the imported "table definition". The second is that Excel ODBC driver reports worksheet names as system table names, so you have to check the "Sys...

You don't need WeofSeq at the end. CloseSeq will write an end of file mark if you have written to the file and you're at the end of the file. Your problem can be solved fairly easily given that there is only one line in the file. OpenSeq .... To hFile Then ReadSeq Line From hFile Then * Position to ...

DataStage does not have its own passwords. It relies upon operating system authentication. The only exception is on Windows, where the user id and password for running scheduled jobs may be stored. None of this affects what you're trying to do. The first thing you have to do is to verify that the Da...