DSXchange

It's also at the top of the page (at least in Internet Explorer).

They will if they can. They're less likely to if you keep pushing.

If it's urgent involve your official support provider. After all, that's what you're paying them for.

Please describe your symptoms more completely. "Causing problems" isn't that helpful - I have children who do that! Any ...CS map is only related to communication between DataStage server and client. EBCDIC conversion should not be an issue, because every EBCDIC code point has an ASCII equ...

You seem to have stated the requirement quite well. I am presuming, of course, that your mapping specification correctly identifies the lookup key(s).

What you don't seem to have done is thought through the rule to be followed when the lookup does not succeed and when the lookup succeeds.

There is a separate "Connectivity Guide" manual for each database in the Information Server manual set. That's where I would expect to find that information. Otherwise the release notes or the Planning, Installation and Configuration Guide.

Use a reject link on your target stage. The sqlcode column (automatically added) will contain the error code. You can direct the reject link wherever you link, for example to an Oracle table. Use a Transformer stage invoking DataStage macros, system variables, etc. to obtain information about where ...

There is an optional automatic conversion when you upgrade in place. Otherwise there is a conversion tool that you can use. Or, of course, you can effect the change manually.

I suspect these files are created by the IPC stage (possible also from Link Partitioner and Link Collector stages). They should be cleaned up automatically but would not be, for example, if the job aborted. Provided the job using them is not running (which should be clear from the date/time modified...

What is the NLS map setting for your DataStage/QualityStage job?

As well as determining the job name from the Job activity name, you could alternatively scan the sequence's own log to get the job name.

Well, I had understood that it was only the server job that was of interest. Even so, the $ErrSource activity variable will give you the name of the activity that triggered the Exception Handler, and the routine could use that information to determine which job's log to interrogate.

Stuart beat me to it! You can specify sampling anywhere you change analysis settings - from project-wide down to at run time.

Next time you're in that screen read the help on entering ASCII codes for non-printing characters.

In version 8.5 both the Header ("Welcome to InfoSphere Business Glossary") and the welcome text are available as editable fields in Web Console for Information Server, Glossary tab, Glossary Settings > Edit Settings.