DSXchange

Basically, the link row count shows the number of rows that resulted from the lookup operation itself. In your case, all lookups succeeded, so there were 3000 rows returned along that link. If some of the lookups had failed, fewer than 3000 rows would have been processed along that link. The fact th...

Welcome aboard! :D The answer is yes. Reporting Assistant - Doc_Tool.mdb If you are asking about the doc_tool.mdb that comes with DataStage clients (it's in the Documentation Tool folder), you populate this with metadata using the DataStage Manager client. Choose the tool in the toolbar that looks l...

As a general rule, DataStage tries only to use generic functionality. Things (such as pthread) that are specific to one or two variants of UNIX mitigate against easy portability between platforms, so are avoided.

No

Sorry about that. I've edited the code adding one line, the $INCLUDE declaration. This loads the constants used by the FileInfo() function, in particular FINFO$IS.FILEVAR.
It should be OK now.

This is a sharing place, you should publish your solution.

The delimiter used in multi-column key values (you did not specify this in your question) is a text mark, which can be accessed as the system variable @TM.

ODBC stage to extract from SQL Server to feed the stream input. ODBC stage or DB2 stage to extract from DB2 to feed the reference input. Perhaps better (from a performance point of view) would be to pre-load a hashed file with only the needed columns and rows from DB2 and to use the hashed file stag...

The use of -jobinfo in the topic suggests that you want to do this within the dsjob command line interface. Source code for dsjob exists (see Appendix A of the Server Job Developer's Guide ) so, if you had figured out how to extract the information you need from the Repository (but see my previous p...

The problem with Craig's approach is it only picks up the jobs that are actually run. If a job was not run, because of some conditional in the sequence, checking the log won't find it. The only "solution" would involve knowledge of the metadata underneath a job sequence. This has not been published ...

Probably the fastest approach is to do it in BASIC as I outlined earlier, with the opened directory held open by having its file variable declared to be in COMMON. The modified code is: FUNCTION FileExists(ThePathname) $INCLUDE UNIVERSE.INCLUDE FILEINFO.H COMMON /FileExists/FileVariable * Re...

Alternatively, with access to the server, they could be given scripts that use the dsjob command. dsjob with the -logsum option can be used to view the log, with the -logdetail option to view the detail of a particular event, with the -lognewest to search for the newest entry of a particular type.

There's no capacity for this in the Director client. If they're in the Operator role (or the Developer role) they can submit job run requests. If you can make a business case, open an enhancement request with Ascential. You might ask for the log viewer to be able to be segregated from the Director c...

I did once hear DataStage's use of the Registry defined as "profligate". On the other hand, there are a heck of a lot of functions (OK, objects and their methods) in the clients and, or course, in your case, intrinsic functions in the Windows-based DataStage server engine. If you've had several vers...

What are the data types of the key columns? What are the data types of the input columns you are using as reference key expressions? These must match. The best approach is to make them all VarChar, Trim the key when loading the hashed file, and Trim the columns making up the reference key expression...

Could be worth posting this one on ADN, some of the Ascential folks have had experience, and are allowed to post there.