DSXchange

I don't, because DataStage allows two jobs to be compared even if they're in different projects. Right click on one of the jobs in the Repository and choose either "Compare Against" or "Cross Project Compare" from the menu.

I didn't, because it's obvious that the OP has no SDLC in place.

The PXPivot stage parses into separate columns with generated names based on the first pivot column.

Also, it appears that the OP requires comma-delimited lists in single columns, not multiple columns. This is not what the PXPivot stage provides, hence the need for downstream processing.

If no jobs are running (which was the original question) and there are no connected clients then the number of processes on the DataStage server should be three, the DataStage RPC daemon (dsrpcd), the ASB Node agent and the logging agent. Three more processes will exist if you have version 8.7 or la...

Is the WSDL import successful? While importing, are the operations defined in the WSDL displayed?

Actually, no.

The changes should be wrought in a DEV environment.

Search the internet for "Software Development LifeCycle".

That's the way the PX Pivot stage works when executing a vertical pivot. You can parse and rename the columns as desired using, for example, Copy and Column Export stages.

There is a Preserve Type property (or some such name) in the Aggregator stage that allows it to work with string data, among other things.

This is a classic "fork join" job design. Search DSXchange for examples of how it's done. Basically, though, you use a Copy stage to make two copies of your data. Apply an Aggregator to perform the counts and run the two inputs into a Join stage. Downstream of that, filter out those groups...

Welcome aboard. Use an Aggregator stage.

When you say "pass this routine" do you mean "pass the output from this routine"?

Try applying a Lower() function to the string. It may not like the embedded field marks.

Are all the connection properties set up correctly in your ODBC Connector stage? What error message is generated? Can you Test the connection from within the ODBC Connector stage? Can you View Data?

The short answer is that Runtime Column Propagation allows you not to specify complete metadata; you only have to specify the columns on which you want to perform transformation. Columns available on the input will be propagated through the stage even though they're not named, when RCP is enabled.

Does the DSN exist in the uvodbc.config file in your project?

Not something I've done recently, but it certainly appears that way.

There's nothing to prevent you from adjusting the imported metadata, but you risk getting metadata mismatch warnings if you do.