DSXchange

If your sequential file is a delimited format you can add a Null Field Value property (for example "") on the Format tab.

That's got nothing to do with read and write cache.

Also, you need to ensure that read and write are in the same Transformer stage. Also recommended is "lock for update" when reading - this sets a row level lock anticipating the write when the record is not found.

Look at your documentation. There is a set of Connectivity guides, one for each supported database types.

You have a separate status record for each invocation. Each has its own wave number. As Mike notes, the wave number has nothing to do with the invocation ID. Wave number is only used internally, for example when resetting a job.

Oracle (10g only) must be installed before Information Server 8.1.

The Information Server software includes scripts for creating the repository database, users, etc.

Use eDiscovery to determine the contents of and relationships between the tables. The metadata thus obtained can be used in DataStage jobs to move samples of rows to text files.

The alternative is manually to import the table definitions. You should be able to do 500 in, say, five man-days.

$CommandOutput needs to be qualified with the name of the Execute Command activity to which it refers, for example GetFileCount.$CommandOutput

Except that I know the support people to be honest about these things I might cynically suggest that IBM's next recommendation will be to purchase pSeries machines from them!

Bulk load is non-transactional, so COMMIT doesn't come into it.

Welcome aboard. While DSXchange does not "give solutions" (other than those of us who do it for hire), we are happy to answer specific problems you may have encountered when attempting it yourself. For a start, there is no such thing as version 8.3 of DataStage, nor even 8.2. So it seems t...

Double click on the (qualified) job name in Status view in Director. The Wave number is shown in that detail window.

Not additional privileges to sysibm.systables, but SELECT privilege to those tables in which partitioning information is stored is required. Consult with your DBA.

Please think this through a bit more carefully. StringToDate("01/":DateToString(StringToDate('201011',"%yyyy%mm"),"%mm/%yyyy"),"%dd-%mmm-%yyyy") The inner dates use "/" delimiter, but you specified "-" in the outer StringToDate() function. ...

I'm brave enough to say "Yes".

No, as you note it's always site-specific. Start by trying ISO8859-15 (or its equivalent) across the board.