DSXchange

Pages 7-2 through 7-73 of the Parallel Job Advanced Developer's Guide are about the C-callable DataStage API.

Decimal[2] wants four characters in the string: " 01.". The first character is for the sign. That's probably why string[2] generated an access violation.

There are steps that you should have taken. Diligent and systematic management of table definitions. Usage Analysis relies upon the linkage between the Repository and the job design being maintained and preserved. In short, this means that you import table definitions into the Repository and load th...

If the log says invalid user name/password it's almost certainly invalid user name/password.

Try using Complex Flat File stage.

If this really is a parallel job as you have indicated there may be more issues with your approach. Will you execute this query on each processing node? In that case you will retrieve different values. Do you really need to get the value? Why not just incorporate the reference to the sequence in use...

The first instance of a multi-instance job will run OK without an invocation ID. The second won't - it will report "job already running" (indirectly).

Were I your customer I would be angry that you arbitrarily and without consultation elected not to preserve my multi-instance settings.

Make sure the 32-bit libraries appear ahead of the 64-bit libraries in your shared library search path.

We'd love to help you out - which way did you come in? You've been here long enough to know that we encourage self help. In this case a Google search (or similar) would have turned up thousands of hits, including the SyncSort web site itself where you can get loads of additional information. A searc...

The obvious thing to check for is newline characters in your data.

From the Administrator client you can issue UNIX commands via the SH verb. Find the job in status view of Director. Double click to identify the process ID of the job's parent process. Using ps or any other command, identify the child processes of the job's parent process. Check that none of these h...

Use dos2unix from a before-stage or before-job subroutine (ExecSH). If the file was DOS-style it's now UNIX-style. If it was already UNIX-style, it remains so.

Write cache enabled is usually the better choice, since random writes to groups can be done to memory addresses then the groups flushed in sequential order to disk. There will be an interval during the flushing when the row count ceases to increment (they are all in memory) but the clock keeps runni...