DSXchange

The data is full of "zero bytes" \0\0\0\0 at this position.

There is no more detail. The Schema File property will accept a job parameter reference as its value. The parameter reference will be resolved when the stage starts.

Please mark this thread as Resolved using the green button at the top.

Posting the same question in more than one forum will not get you any more or different answers.

As far as I am aware DSXchange is not yet offering any 8.1 Information Server training, but you could check for yourself at the commercial sister site (www.dsxchange.net).

Exactly. The Cycle generator method has a sub property called Value - you add as many of these as you want to cycle through. For example if you want 60% F and 40% M, you could create 10 Value entries of which 4 are "M" and 6 are "F".

The usual way. Schema File is a property of the Sequential File stage (for example) and will accept a job parameter reference delimited with sharp signs.

Are you really using port number 31539 ? The default is 31538. (Beautiful name for the server: a beautiful piece of music* and a beautiful river.) * Also known in English/German as "The/Die Moldau": one of a suite of pieces called "Ma Vlast" (My Country) by Czech composer Smetana...

Transactional DELETE does not free up disk space - it remains within the hashed file structure for re-use. Commands CLEAR.FILE and RESIZE are non-transactional and do free up disk space. An appropriate syntax is RESIZE RT_LOGnnn * * * This does not alter any of the hashed file's tuning parameters, b...

Surrogate keys by definition provide UNIQUENESS. Holes in the sequence are irrelevant. With a block size of 1000 and starting at 1001, I would envisage (I have not tested it) that node 0 will generate 1001, 1002, ..., 2000, 3001, 3002, ... and node 1 will generate 2001, 2002, ..., 3000, 4001, 4002, ...

Read the manual on orchadmin command. It has additional options that allow you to force things (such as moving/deleting Data Sets) to occur.

US7ASCII character set can not contain Arabic characters. You are seeing this when using sqlplus. You need to specify a DataStage character map (and Oracle NLS_LANG setting) that does handle Arabic characters. Until you have done that, your other questions are largely moot. From the point of view of...

I suspect you're not stripping off the line terminator after reading from the parameter file. This will have been converted to a field mark (@FM). Search DSXchange for techniques.

Sort funnel the rows from the two sources then use Aggregator stage as suggested. If you only want 98 as output, use a Switch, Filter or Transformer stage to effect the desired filtering.

Knowing the exact version of DataStage (from Help > About) may be useful.