Hi Shahid,
again my answers from the other group
1: In DataStage on flowlevel, you can use a Message Handler to demote a warning to an information, also you can decide how many warnings in a run to tolerate before aborting the run of a flow, on pipeline level you can decide what to do after a activity that has finished ok, with warning or error.
2: I am not sure if I understand your question correctly, but in a pipeline (CP4D, not DaaS (DataStage as a Service, hosted by IBM), you are not allowed to execute java or C code in DaaS) you can run a "Run Bash script" node, which should allow you to run about anything that is runable on your server, maybe there is even an easier way here, this is not really my topic. In DataStage flows there is also Java Integration stage, that lets you "invoke Java classes from Datastage flows", but I have never used it, you can check the information for this stage about what it is able to do. If you need to access SAP, then there are connectors to do so directly, I used those 15 years ago to access SAP R/3 with DataStage.
3: Yes, in legacy you have the DataStage Director and the Operations Console, which together work very well (according to my colleagues that do operations), while in CP4D there is now the Job Dashboard, which in my opinion does the job, but currently (for what we need) not as well as in legacy, IBM is currently working on bringing the Job Dashboard to the same functionallity level as we are used to in legacy. You can see the row counts for every link in a flow, both in the design view (for the current run) or in the logs (for every run where you still have the logs).
4: Currently when using the join stage, the columns have to be named (it is easy to rename the columns in your flow before the join) the same, this comes from the underlying operator which has a -key KeyColumn attribute, when using the lookup stage (which also supports between or Greater than istead of onlöy equal conditions) the column names can be different. There is alos the Merge stage which I have never used outside of training, as far as I remember it also needs column names which are equal.
Short answer on this, the keycolumnnames for a join can be different in your source, but for using the joinstage you have to rename them (well at least one of them) in your flow to make it work.