DSXchange

SQLSTATE is specific to ODBC. Use DBMSCODE if you want the error code generated by DB2/UDB, and use LASTERR if you want the text associated with that code. Remember to specify the link that connects to DB2 when selecting these link variables in your design - not the link that connects to the rejects...

Use the UNIX command test (with -z option) in an Execute Command activity, or use OpenSeq, FileInfo() and CloseSeq in a Routine activity.

And the command textbox cannot be empty or space.

That's why I suggested source or . in the Command field.

In DataStage you draw a picture of what you want to happen. lookup | | V source ---> transformer ---> target | | V rejects Each word represents a "stage". Then you edit each stage to fill in the details, for example which file is the source, what its format is, and so on. Your lookup will probably n...

Run the job in the Debugger. Set a breakpoint on the output link. Edit the breakpoint so that the expression is

Put some diagnostic DSLogInfo calls into the code to figure out whether any of it gets executed. I think you will find that it doesn't even get that far. Copy the job control code from the job sequence and paste it onto the job control tab of a new server job, and add diagnostic calls in that also. ...

Preferable is to use a small job (staying in the graphical paradigm). The job sends zero rows to the hashed file via a Hashed File stage, and the "clear file before writing" box is checked. Job runs in under one second.

Server routines force you to know DataStage BASIC.

And there are probably a lot more C programmers out there than there are DataStage/UniVerse BASIC programmers.

What's the point? If you're going to program, you need to know/learn the programming language of choice for the application.

Welcome aboard! :D That behaviour usually only occurs where there is an OCCURS clause in the file definition. Can you check the FD manually to determine whether there is an OCCURS clause? You might also inspect (or even post) the generated COBOL code to try to ascertain why these repeats are occurri...

Never abort.

Retain control.

In a job sequence perform the FTP. Then test the size of the result. If this is non-zero, then proceed with the job that processes it.

What happens if you put source or . in the Command field, and #path#/command in the Parameters field?

It may be - and I'm guessing here - that the XML stage you've used is limited to 2GB and the file is actually slightly larger. The error message indicates that the process failed to reach end-of-file. If, for example, the XML stage had been written with a signed 32-bit offset pointer, it could not r...

Partitioning is completely irrelevant for output links. Partitioning (and, perhaps, sorting) is relevant on input links. If you're writing to a sequential file, it must run in sequential mode. If you don't need to sort, don't. You don't need to sort to write rows into a sequential file, unless the c...

Can't be done unless the data are partitioned on the join key(s) using the same partitioning algorithm or the Entire partitioning algorithm for the probe table. Otherwise you can't be certain that you will find the row in the probe table on the partition where the driver row exists. Given that the p...

Based on your assertion that there is no suitable stage type it appears that you will need to create your own stage. Read the chapter on custom stages in the Parallel Job Developer's Guide. Come along to the Server to Parallel Transition class immediately following II LIVE in Las Vegas. Sounds like ...