DSXchange

You can use Column Import stage to reparse the Raw data type, or you can write it into a text file.

Column based impact analysis is in a future version (8.2?). It was demonstrated at IOD 2008.

Use a sequence with an appropriate Execute Command activity to retrieve the file name and pass it to a Job activity as a parameter value.

Use the report-generating capabilities in Designer preserving the "intermediate XML" and grab what you want from that.

Long answer is also "no".
It's the hashing algorithm that governs on which page/group/frame any particular record resides.
As noted, the only way to get sorted data out is to sort those rows.

Make sure that the date literal is of the correct format for your job.
Try surrounding your date with quote characters.

Probably a BuildOp.

I suspect you have these strings (separated by / in your example) as separate fields in the hashed file. Fields in hashed files are accessed by ordinal number, not by name, so your metadata in the link where you are writing to the hashed file does not correspond to the metadata in the link where you...

Welcome aboard. You need to do some work setting up users via the Web console for Information Server. Users must be Suite Users and also have a product role (either Administrator or User) for DataStage. Then you need to use DataStage Administrator to assign DataStage roles to anyone credentialled as...

Correct. This can only be changed (deliberately) at the TCL command line, and you would only do that if other applications were going to access the hashed file using non-UV-UTF8 character encoding. This was more important prior to version 6.0, when other UniVerse applications might have accessed dat...

No. Once a stage failure causes the job to stop all virtual Data Sets (data in memory) are discarded. If you want to preserve them then you DO need intermediate storage (which implies separate job for Stage C at the very least). There *may* be something clever you could do with message queues, but y...

It would probably be a sequence, rather than an individual job, that runs continuously. What happens if another of the files appears while one is being processed? You have to be able to handle rapid arrival of files. Don't forget to be able to trigger the job to shut down gracefully, perhaps by chec...

You won't. You won't see it for HASHED file stage either. That's how "they" make sure you can't change it from NONE in the GUI.

Join stage requires its inputs to be sorted on the join key(s).

OK, three keys, and therefore three comparisons in the lookup SQL.

Please post the SQL statement on the reference link.