DSXchange

Or...

What version and platform?

You 'develop' on the Server, not the Client technically. Same goes with your 'environments', the Client version isn't what drives that bus.

CRC32 will generate a 'unique' value based on the input string, but not as a four digit number ALWAYS. An MD5 encryption generates a 32 digit hex number. I'd guess you'd need to roll your own.

How many times are you going to post this?

Suggest you look closer in the 'Cleanup Resources' panel. The "pid" won't always show based on the job name, sometimes you have to lookup the job number and then look for an RT_* entry with that number:

RT_CONFIGnnn
RT_LOGnnn

Etc.

No, not really. Why not just do this in a Server job and be done with it?

Installing a database, MySQL or otherwise, does nothing to DataStage or its ODBC config files. The installation of the "branded ODBC" components all happens when you install the DataStage server.

Yes, hashed records are unique per key field(s) so the trick here is to write the hashed file with enough keys so that your records survive and then use fewer keys when looking up with the UV stage.

As far as I know, yes, but I don't have any personal experience with 8.x or parameter sets yet.

Have you tried the solution posted above?

Create a parameter in the Sequence job for the state and pass it to the PX job's matching parameter in the Job Activity state.

Unless you are in debug mode, I think. No clue how you get there but I do believe I vaguely recall Master Ray mentioning that.

Should be on your Client CDROM in the "Unsupported Utilities" directory, from what I recall.

Just copy the relevant portion of the log message(s) to your clipboard then include it/them here as text, no need for a screenshot.