DSXchange

SQL Functions are always assumed to be able to deliver null (and therefore to be nullable). Short of using an intermediate temporary table I don't believe there is any solution. You could use a message handler to demote the message to informational.

I stand by my solution and claim that no "other" solution is required to meet the need described in pat_raman2000's two posts.

Yes, you do need to stage the data. A flat file is as good a way as any.

You can not do this in a server job.

You could achieve it with routines that employ BCI functions (which mimic ODBC API functions).

No. You must use environment variable names as documented in the DataStage or Orchestrate manuals. No others will be recognized (unless in your own expressions - and there you can not affect "buffering, debugging, partitioning, reporting and so on").

My usage of "commit" is the standard, (almost) universally understood one.

Then you must build this in - "automatic" handling only applies when a job (or other) activity actually fails - aborts. Take a Warning trigger from your job activity and run it into a Routine activity that invokes UtilityFatalToLog() routine.

For whatever reason your system is having a problem with the node name "issaq". Is it defined in the hosts file?
%WINNT_ROOT%\System32\Drivers\Etc\hosts

In a CMD shell on the server can you ping issaq successfully?

Possibly. Not if the constraints involve mutually exclusive conditions (that is, any one input row can be directed to only one table).

Partitioning is not relevant to this question; partitioning only ensures that any one row will be processed on only one processing node.

No. That would certainly cripple the job, but would not delete it. There are many other entries for a job, including in DS_JOBOBJECTS, VOC and all the job-specific repository tables DS_TEMPnnn and RT_*nnn and their corresponding file dictionaries, not to mention dependencies that might be recorded i...

Why not just use @OUTROWNUM system variable, perhaps added to a constant (starting value) supplied as a job parameter?

You say you have five columns, you show me a record schema with three columns, and that you are discarding two of those. Why not select just the one column that you need? To get rid of the error, just do as it says - add some null handling. I suspect there is more to your job design than you are tel...

There is no dsenv file on Windows-based DataStage servers. You can set up environment variables using Control Panel > System > Environment.
(Depending on which version of Windows, Environment may be a command button on one of the tabs in the System dialog.)

Default values are coded within the osh executable and used if the environment variable is not set. If the environment variable is set (anywhere) then its value takes precedence over the default value.

Welcome aboard. Add a sort ahead of the Aggregator stage, sorting by the grouping (duplicate identifier) keys. You can use a Sort stage or, if the data are coming from a relational table, specify the ordering in the extraction. On the Output page General tab, select the Group By option rather than t...