DSXchange

Another, rather old-fashioned, approach is to treat them as very long (perhaps even unbounded) VARCHAR and apply hex conversion (for example RAWTOHEX in Oracle, HEX in MySQL) while extracting, and use the reverse functions when loading.

My point is that many of them (such as my east Asian customers) can not easily understand these forms.

Add an echo command so you can learn what the script is actually trying to execute.

A common group is probably a better solution, and making sure that the umask for all users is set to 002.

It's in the PXEngine's bin directory.

ppgoml wrote:There is a file named "DSParam" that includes parameters information.

No there isn't.

But there is one called DSParams.

Not "u", but "you". Not "abt", but "about".

U was a city in ancient Babylonia. Abt was an engineer who invented a particular style of cogged railway for steep ascents and descents.

Do ALL variants of grid management software work that way? In particular, does Sun Grid Manager behave thus?

If you happen to be in the UK you will be able to find any number of peers in the House of Lords.

Do you need to migrate them at all? Would it be sufficient to have jobs running in the new environment create them afresh? (That's one of the things Validate Job is useful to do.)

I'd be very surprised if a sequence could be ISD enabled. Any job that can be ISD enabled needs to able to listen (e.g. ISD Input stage) and send. There's nothing in a sequence that fulfils this requirement.

Internal formats were the same in 7.5, 8.0 and 8.1 (for example the major version number for jobs was 50 if I recall correctly). The internal format is different in 8.5 (for example looping in Transformer) and the major version number for jobs is 56. They are incompatible. You could try editing the ...

There are some good online tutorials, which you can find using an Internet search engine.

The ones from .edu web sites seem to be more thorough.

DIS file and DAT file. Say it, rather than read it.

Neither is a particularly meaningful suffix.

I don't believe the Pivot stage supports multiple outputs but, if it did, you have an easy answer.

Otherwise use a Copy stage to distribute the required columns to three independent Pivot stages.