DSXchange

The driver you have installed does not support the SQLColumns() function. You need a more capable driver if you wish to import metadata.

Since the conductor process was unable to contact one or more section leaders, I would hazard the guess that your rsh permissions have not been set up properly for trusted connections between these processes.

Carefully read the paragraph of suggested things to examine in the output that you posted.

Not in a parameter or in a file, but perhaps in a hashed file or UniVerse table in the project account. Then, to do the lookup, access that hashed file using a UniVerse stage, which uses SQL. Just don't expect it to be fast. It won't be. Indexing the search column will help.

You DO have a hex editor - it's the od -x command in UNIX.

Did you bother to search the forums for this exact error message? I'm sure it's been posted many times before.

Join stage (and certain others) mandatorily require that inputs be identically sorted and partitioned, in the case of the Join stage on the specified join keys. Usually this implies the Hash partitioning algorithm but, for a single integer key, the modulus partitioning algorithm may prove more effic...

A Sequential File stage performs an import operation - attempting to translate from human-readable format to internal (binary) format. Try reading the file with a Complex Flat File stage.

No, only once for each Rule Set, or each time you modify a Rule Set. However, you do need to do it onto each DataStage/QualityStage server machine; this is the step you missed.

Provisioning is the act of transferring the Rule Set from the QualityStage client onto the server. Right click on the Rule Set and choose "Provision All" from the menu.

Actually it could be done using an External Source stage, but I wondered what you had in mind. But there's no advantage in a parallel job in using a hashed file - a sequential file would do as well - because the entire reference data set is imported into memory.

I have successfully used environment variable parameter set parameters. That is, I have been there but not seen the problem that you are reporting. However, I am using these parameters in a job in a location that is not a connection to a database (and obviously is not in a Connector). That may be a ...

In a parallel job? Please elaborate.

What's different in production? In production have you provisioned the rule set used by the Standardize stage?

Use a hex editor to find out what the "square box" actually is.

Space should be 32, NULL will probably be 128 (the internal value used to represent an out of band null in DataStage on UNIX).

Recall that DTM is VARCHAR. Therefore you can use substring. Within SQL the syntax is SUBSTRING (DTM FROM 1 FOR 10) I would probably add an I-descriptor to the dictionary of DS_AUDIT and use that in the query. 0001: I 0002: SUBSTRINGS(DTM,1,10) 0003: 0004: Date Modified 0005: 10R 0006: M 0007: MODS