DSXchange

Whether server or parallel jobs, once you've set them up as real-time services they're pretty much impossible to use any form of Debugger to diagnose; you probably need extra output links instead.

Reading the ReadMe file?!!

Whatever would happen if everyone started doing that?!!

All hashed file lookups are LEFT outer joins (the row returned from the reference input link contains NULL in every column if the key is not matched). It is provable that any RIGHT outer join can be rewritten as a LEFT outer join, but that word "rewritten" says it all; your job design would require ...

Depending on your data base you may also be able to use a sequence or a SERIAL data type or a GUID. All a surrogate key has to be is unique, but you must have some mechanism for returning it to DataStage.

I must disagree strongly with Sainath's suggestion. You definitely do not want every hashed file to be 64-bit enabled. Once the corruption has been repaired (or the hashed file created afresh) you can check whether it is 32-bit or 64-bit by attempting to use uvfixfile on it (this utility does not su...

If job1 writes the information to a text file, you could use an Execute Command activity to read the file (cat filename on UNIX or type filename on Windows). Output from the command is available in downstream activities when you click "Use Parameter".

I don't really like what you're doing. Principally, what is @ID doing, and how is it actually specified in the expression in the BASIC Transformer? You really shouldn't, however, be querying the repository tables in this way for every row processed - you can end up with a deadlock situation if DataS...

There will be some kind of "remote shell" or "remote execution" mechanism that you can employ. Not currently working where I can check for details. A search of this forum might turn up something!

Are you perhaps reading from a Sequential File stage with the "first line is column names" property set? (However, that does not explain your case number 4.)

You will, of course, need a C++ compiler (such as Visual Studio C++) if you plan to use Transformer stages or BuildOps. But, hey, disk space is cheap!

Your query is not the same as Kim's. You left out @SVM, 1 as the second and third arguments of the field function.

This stuff is not in the public domain. That's why you can't find it in the PDFs. We've come to learn the structures by inspection (hacking?).

You have (or had) a whole lot of DSLogInfo() calls with only one argument. DSLogInfo() requires two arguments. Open a text file with the OpenSeq statement. Make sure to handle all possible conditions, particularly that it may be locked for update by another process. Read a line at a time from the te...

Welcome aboard! :D You have misread my post. I did not claim that server jobs can not address partitioned tables. Indeed, I suggested that a multi-instance server job could have instances addressing each partition, if that is what is needed. On UNIX systems DataStage server jobs are always multi-pro...

Every five minutes is rather extreme - you're almost in the realm of creating a real-time service! Between StartLoop and EndLoop you can, for example, include a Routine Activity that invokes a routine that does nothing but sleep for five minutes. You can certainly do it yourself in a server job usin...

You don't use DSAttachJob() at all. DSJ.ME already has its value. Use it directly for the first argument of DSGetStageInfo or DSGetLinkInfo, or whatever other interrogation function you are using.