DSXchange

Environment variables set through the Designer client are stored in the DSParams file in the project. You can read from that. However passwords are stored in encrypted form, so you would need to be able to decrypt it.

Fetch SNO from the target in another stream in your job, increment it and merge or join it into the main flow. Or use a separate job to extract and increment SNO and pass this value to the main job as a parameter.

You don't have two digits in the month but your format string says that you do.

Do learn to read what the error messages are telling you.

By posting in the correct forum (so that we understand what software, what job type, what version, etc. that you're using) would be a good start.
Asking the same question more than once is frowned upon also.

By posting in the correct forum (so that we understand what software, what job type, what version, etc. that you're using) would be a good start.

Message handlers are stored in the same location in 8.5 but you have to move them yourself - they're not picked up by the exporter. The same is true if you happen to have any named message handlers.

My solution will work with either edition.

You have to extract the date portion from the input string, perhaps using substring if the size is constant or Field() functions otherwise. Then all you need to do is to convert the hyphen characters to empty string ("") in the result. Convert("-", "", Field(Field(InLin...

There is no guarantee whatsoever that parallel jobs are faster than server jobs, particularly for small to medium data volumes.

Even flash disks can perform better than spinning disks.

The servers are not starting correctly. Check SystemOut.log and SystemErr.log for the WebSphere Application Server. Use the serverStatus.bat command to determine whether server1 is running.

String to timestamp is not an implicit conversion - you will need to specify a conversion function in a Modify or Transformer stage to achieve a data type of Timestamp.

Add a Reject link to the Sequential File stage to see if any records could not be written.

One more thing.

A sort supported by a B-tree index will outperform anything that DataStage can do, because a B-tree index is already stored in sorted order and simply has to be scanned.

I didn't claim they're all in the same Peek entry. Information is logged as it arrives, and multiple nodes' information tends to collide. But if you look at all the Peek entries for node 0, for example, you'll find a total of 10 rows (or whatever you set it to). Ditto for node 1, and so on.