DSXchange

31531 is the port number used by the ASB Agent. If this agent has stopped for some reason, the fix is usually to restart it. Check first that the WebSphere Application Server itself (default\server1) is still running.

Welcome aboard.

The option is to set the Aggregation Type property to "Count Rows". You then nominate the column on the output link that will receive the count in the Count Output Column property.

It may not be transport blocks you need to change. These are only used for internal transmission of fixed length records. It may be buffer sizes you need to tune. Be very, very careful with these - tuning them through environment variables affects every buffer (link) in the job. It may be better, if...

It would appear I'm not alone.

Code -5 is DSJE.BADTYPE indicating (here) that the InfoType argument in DSGetStageInfo() is not recognized. This is because you used an underscore rather than a dot. The constant (given that the language here is DataStage BASIC) should be DSJ.STAGESTARTTIMESTAMP rather than DSJ_STAGESTARTTIMESTAMP (...

18 million keys is trivial for a hashed file to handle.

The easiest way is while importing the table definition of that file (assuming it exists) or creating the table definition (assuming it doesn't exist). Record the width of each field, which is stored in the Display Width field.

Please describe the configuration file under which this job is running, in particular the number of nodes and whether the disk and scratchdisk resources are shared between nodes.

Arnd asked you to monitor the space (with df, but du may be better) while the job is running. Have you done that?

Yes, for example here or here

And yes.

I'd probably create an after-job subroutine to get all the stage/link row counts from the job and write them to the file whose pathname was given as the input argument (input values field).

There's no such thing as rejects from a join - there's only the result of the join. It's the same in DataStage as it is in SQL.

None fail when the job is running, because all pick up only design time information. I prefer DSX over XML format when using DataStage/QualityStage Designer export, because it's the more compact format. You get ISX format if you use Information Server Manager for creating deployment packages ("...

Welcome aboard. As a general rule what you are trying to achieve is known as a "blocking operation" (the output can not be opened until the input is closed). Blocking operations are forbidden in parallel jobs, as they invalidate the pipeline mechanism. (You can use blocking operations in s...