DSXchange

Do you want to copy them from one transform stage to another? I don't know of a way to do this in the designer, unfortunately. It might be possible to do via cut-and-paste from a .dsx export file.

DataStage also has an aggregator stage with similar functionality. Have you tried using that?

I think we are still unclear as to where this is happening and what is triggering it. It seems to be a executing a TCL shell command but using a UNIX type path.

Use notepad++ or some other tool that will let you see the true binary contents. Using the CFF stage is "too late" to find errors in this case.

"Command Activity" lets you execute a shell command. This would be a SQL Command to your database to get the results from the table. This result can be check in the job sequence and can be used as the condition on whether or not to execute a job.

Do you mean how many stage output links have constraints or how many rows go through those constraints at runtime?

But in your first post you mentioned that you had a binary local copy - that is the one where I'd like to see what the binary values are and if they are actually a COMP-3 representation.

Can you post the hex values in the source for one of those packed decimal columns as well as the PIC clause for that column?

By looking at the line number that is a pretty big transform stage and it will be difficult to locate your error. You can always look at the actual "evalexp.C" line 5898.

If you reset the job and then see if additional information is visible in the "from previous run..." entry.

Sainath, sure - that's what text editors and other applications do. But I think that the OP might imagine one could "update" records in a flat file via DataStage PX jobs and that won't work.

I haven't seen messages of this type, could you perhaps post the full log message? Is this for all jobs or certain jobs?

Bear in mind that flat files cannot normally be "updated" in the sense of replacing line nn with another value.

Lol - so both of us were wrong. OP regarding their version, me regarding which version is the right one

Try seeing if your CONFIG file is valid, either via UNIX "orchadmin check" or via the "Configurations" toolbar item in the designer.

And if you manually use SQL to do the same insert statement is the error the same?