DSXchange

In this particular case you are specifying fixed-width format. Therefore, however null is represented must have the same width as its field. Right click on the nullable field in the Columns grid and choose Edit Row. Then fill in a suitable value (maybe 19 spaces) in the Null Value property.

Is it really a single quote, or a back tick ( ` )? Anyway clicking the GetSQLInfo button in the ODBC stage will load the correct character and, as a useful side effect, prove connectivity to the data source. Error-free (silent) execution equals good connection.

The "ade" part is like the DataStage "signature" - if you execute an ipcs command at UNIX you will encounted a number of shared memory segments whose signatures begin 0xade... Thus the "ade" files for the RTI interface are temporary files needed for storage or communication between processes. Try ls...

When Write Method is "Load" the bulk loader will be invoked. View Data can not "view" the bulk loader, which is why View Data is disabled. Switch the Write Method to "Upsert" and View Data will be enabled (but several of your other stage properties will be invalidated).

Because DELETE is DML and TRUNCATE TABLE is not.

Or, if there's some reason not to sort by GK4 and GK5 up front (for example you may not have them until you've performed a lookup or join) then Option 2 is definitiely to be preferred - but you MUST preserve the sorting order of GK1 through GK3. Do this with an explicit Sort stage, with GK1 through ...

That's not really what ProfileStage does. Profile stage tells you what's out there, in terms of single columns, within-table dependencies and between-table dependences, and can suggest a 3NF schema on those bases. It doesn't really have any comparison facilities. QualityStage is a better tool for pe...

The Otherwise/Log output must be executed AFTER all other output links (except the Reject link, if you have one). Use the output link execution order tool (rightmost on the Transformer stage toolbar) to ensure that this is so.

Yes, now that you've "given it the big A" perhaps you could mark the thread as Resolved?

(Beat me to it!)

Or, even simpler,

Or, even simpler than that,

What did you learn when you effected a Search for this question? This question has definitely been answered before.

LIST.ITEM (and SORT.ITEM) omit any fields that are not populated. I advise not trying to use these commands, as they will show you values for which no metadata exists, and there is no way we will be wasting time describing to you the up to 316 fields that might occur in a DS_JOBOBJECTS record. Parti...

If you must: SELECT DS_JOBOBJECTS.NAME, DS_JOBOBJECTS.OLETYPE FROM DS_JOBS, DS_JOBOBJECTS WHERE DS_JOBS.JOBID = DS_JOBOBJECTS.OBJIDNO AND DS_JOBS.NAME = '<<Job name>>' AND DS_JOBOBJECTS.OLETYPE LIKE '%Stage'; (You don't need to know a value to join on it.)

How about you tell your team lead that the answer is "no"? After all, SQL can not be executed directly from the command line, and the table definition of DS_JOBOBJECTS is made deliberately incomplete by the vendor. But you might like to use the -report option with the dsjob command. dsjob -report [-...

No, it simply means that your data are not sorted in the same way that you're telling the Aggregator stage that they are sorted.