DSXchange

Theoretically, yes. Why not try it and let us know?

We can't help you with that until you document your business requirement that governs which record goes into which file.

So, some kind of test of the form

is desirable, where CurrentJobName is initialized to DSJobName (DataStage macro) or DSGetJobInfo(DSJ.ME, DSJ.JOBNAME).

The transaction log is full. DB2 will not accept any more transactions until it is either purged or enlarged. That's why it closes the connection.

Nothing to do with DataStage.

Performing arithmetic will strip the leading zeroes, because arithmetic in DataStage BASIC returns the shortest possible valid string representation of the result. Use Fmt() to reinstate the leading zeroes if you really do require them (though I can't think why you would).

Approximately (packet_size / row_size) or a small multiple thereof should be your starting point for experimentation.

What authentication are you using in Information Server? How is that user ID credentialled with respect to DataStage role(s)?

Do you want to do this many times or just once?

If many times, why not assemble the CREATE INDEX statements into a stored procedure and execute that?

Otherwise, how have you attempted to execute multiple statements? Have you tried terminating the first one with a double semi-colon (";;")?

Compiling a parallel job converts your design into an Orchestrate shell script that can be used as input when the job run request is made. Compiling in no sense executes the job. There are three execution modes: normal, validate and reset. A normal run is exactly what it sounds like. A reset is requ...

If you have the XML stages then you have the documents.

In particular note that this is not a DataStage problem; it is a problem in the configuration of Oracle.
Talk with your DBA about auto-extending table spaces.

Not being the author, nor responsible for the author, I find no reason to test. If I believe an SDK routine is suitable for my purposes, I use it; if I believe it needs improvement, I create and use an improved version. I do believe that a "reset" routine falls into the category of needing to manage...

"They" did a lot of work with Transformers for version 7.5 - they now generate code that's quite close to an operator. The incentive to remove them is not as great as it once was. There is no real alternative to taking the first character somewhere - the Switch stage does not have any computational ...

Have you though? Have you, for example, tested it when someone else is in the process of updating the same sequence name?

Everything in the SDK was put together in a hurry, and it shows.
Nearly every routine in the SDK can be improved.