DSXchange

IsValid() tests the string. Don't apply StringToDate() first. What you really want is something like

Oconv() can accept a multi-valued list of conversions, which are applied one after another.
"D4YMD" generates "2011 12 06".
"MCN" applied to that removes the non-numeric characters, yielding "20111206".

Try the /O (omit) switch.

I don't believe so. Automated services is "all or nothing".

The Match Designer database is not used at all in jobs; it is only used by the Match Designer client. Tables in the Match Designer database are created automatically when you test a match specification. While you could certainly configure other clients to look at the Match Designer database, you wou...

I don't believe you even need those - everything (all four tiers) are in the 4GB main download of Information Server. I suspect that you need them only for the occasions you need to install WebSphere Application Server separately.

Yes it is. Basically you have to maintain counts (probably in stage variables) then, when the counts are reached, output your FormFeed character (or however else you are effecting a page break) and resetting the counter before proceeding with more rows. Similarly use stage variables (or an upstream ...

Parameter values are resolved when the job is started. Therefore, as you surmise, they can not legally be changed once an always-running job is running. You need to get them right when the job is started. It is also possible through ISD to create "on demand" jobs for infrequent access. The...

A Data Set can be viewed outside of DataStage, using the orchadmin command (search DSXchange or the manuals for more information). However there is no scope for selection; you can only read all rows (then, possibly, pass them through a filter of your choice).

Use Char(21) for the data type rather than VarChar(21). This should cause the reject behaviour you require. You could pass the reject link into a Column Import stage that re-parses the line as two Char(21) columns.

You may lack write privilege for the "target" directory if "test.csv" does not exist, or to "test.csv" if it does exist.

2. would come from the command LOGTO Checking.

3. would ordinarily come from a TERM or SET.TERM.TYPE command, which you would rarely use with DataStage.

No idea at the moment about RING. "Unidentified token" is a general parser error.

The conversion specification for Oconv() needs to be upper case - you may wish to get rid of the space delimiters that this gives by default.

What is the exact expression you used in the job parameter reference in the sequence Job activity?