DSXchange

I'm never really certain what attempting to overwrite /dev/null implies, and it may be different on different variants of UNIX. That's why I always choose "append". YMMV.

There is NO WAY that requirement could be urgent.

/dev/null is a "black hole" - it can accept any number of rows. I usually make the output rule "append" when writing to /dev/null.

On Windows you can use .\NUL since there is a NUL file in every folder.

Of course it's possible. If you grouped by sex ('M' or 'F') you would only get two output rows. Think about it. How many distinct values are there in the column by which you are grouping?

From sort operations where the memory demanded exceeds the value allowed by the "scratch" parameters in uvconfig - SCRMIN, SCRMAX and so on.

Delete the project directory (recursively) and try again. You may also need to delete the project entry from UV.ACCOUNT and to repair the SQL system tables (VERIFY.SQL command).

Replacements for parameter markers in the WHERE clause are those columns marked as Key in your metadata.

Red Brick also has NTILE - has had since day 1 - it's an idea that Oracle "borrowed".

All three variants are hugely different. Server generates DataStage BASIC, parallel generates Orchestrate shell script (osh) and C++, mainframe generates COBOL and JCL. In server and mainframe you tend to do most of the work in Transformer stage. In parallel you tend to use specific stage types for ...

A Date parameter will only accept the date part. It will not accept a timestamp.
I also note that there's no ":" between the hours and minutes part of your timestamp; however, fixing that won't change the behaviour of a Date parameter. Supply a date value, or make the parameter type String.

There is a SIGN function. Read about it in the DataStage BASIC manual.

There's no problem at all in reading from a hashed file, provided they're not using "lock for update". In fact, you can even set up "public shared hashed file cache" so that there's only one copy in memory. It's all in the dsdskche.pdf manual (and involves a change to uvconfig and therefore a re-sta...

Colin left out the vital piece of knowledge that you can do this from the Administrator client's Command window (if you can get that far) or from a telnet session into the server machine, operating in the uv shell within your project directory.

How are the input data being delivered?

It might be clearer - easier to maintain - if you take two passes through the data. The first pass populates a hashed file after totalling (summing) the ao_code for each branch number. Depending on source, you can get this via SQL, or via an Aggregator stage. The second pass then looks up the total ...