DSXchange

Caltog, per my previous post - can you see if this is reproduceable with a job that has just your read and a write stage? I just wrote a test job going back and forth using 168 and normal commas as separators and cannot reproduce the problem you are having. Have you checked to make sure you are usin...

I've tried combining commands in a modify stage as well and have come to the conclusion that this is not possible.

Where are you using "SUM(AMT)"? It sounds like a new column in your SQL query - and the metadata of that new column is most likely creating it as a nullable column. If you change your metadata for this column to be not nullable but add a null default handler in your row definition the error will go ...

Would it be possible to write a new job that just reads the source and writes to a sequential file with non-nullable set on that column? does the error go away?

Check each and every stage in your job to see if the "nullable - yes" has not mistakenly been clicked on.

Das, I thought I had already pointed out the stage to use: the DataStage job sequence "Execute Command Stage" to execute a UNIX script. Did you require an example?

If you click "nullable" on some stage in your job then it might cause the warning message you are seeing. PX thinks it is nullable somewhere. Also, contrary to my previous mail, could you check your DDL in the database to see if the AMT column is declared as non-nullable there as well?

Does this error happen in the same way when you write this job with just 2 stages, the source sequential stage and an output sequential stage using a different delimiter? Have you specified the delimeter as a text character or used the numeric 168 representation?

Where did you check the metadata? Using the DB's describe or the DS Manager isn't going to help. You need to start at the source stage in the columns tab and for that column right-mouse-click-edit-row to see what is set. Then do that for each stage to make sure you haven't changed those attributes i...

The FTP plugin in DataStage will transfer files and data content. There is no need for a model - if you drop the FTP plugin stage onto the canvas in your Designer you will see that most of the options are similar to those you would use in an interactive FTP session. In addition, you can always call ...

It looks like your script is missing the actual "ftp" command.

If you check carefully in your source definition for the column "AMT" you will find that it is declared as nullable, hence that warning message. Whether the actual column is declared as nullable or not in the database is a different matter, but DataStage is reporting the potential problem based on t...

There are several ways to do this from DataStage Server, the method you use depends upon where you wish to do this. In sequences you have have a command activity stage, in Server jobs you can call a script from a before/after routine or use ExecSH or the DSExecute function.

You can define jobs to be declared as "multi-instance"; these jobs can run several times in parallel. Each instance of the job run gets a unique identifier when started to differentiate it from the others.This is also called the invocation id.

The lower level definition will take precedence. But setting a buffer to such a high value will have no benefit to job speed at all, in fact it might even cause the job to run slower. to quote myself from some thread a long time ago: ...you might not be using explicit IPC stages, but by specifying i...