DSXchange

You can delete the instance records from RT_STATUSnnn table.

Visit Ernie's blogs, and read the chapters on these stage types in the DataStage manuals.

The leading zeroes are not significant. Don't worry about them. They are there to prove that precision and scale are being handled correctly. The internal representation, both in DataStage and in Oracle, is binary.

Check back through your record of support calls - you DO keep records, don't you? My guess is that it was added as a result of advice from your official support provider. Checking your PMR history (on IBM support portal) may be another avenue.

Flushing the cache is always a good idea when IP addresses are changed. It ought not to be necessary at other times, but does no harm.

I don't know whether exact search here is case sensitive, but do search for UNLOCK - that's the command. But be very careful using it - only unlock locks that can not be released by their owners. After all, locks are there for a reason.

First off, what do YOU understand by the diagnostic messages that have been produced?

There were errors dropping and creating tables (one can reasonably assume in IADB). Does that ring any bells for you? Does the phrase "database privileges" have any resonance?

The change to ConvertWeek function should be fairly easy. What have you attempted?

Welcome aboard.

What's different about the system, and other systems, during the slow times? "Nothing" clearly is not the correct answer.

muralidwhds wrote:Hi All,

How can we get the system out from a datastage job in DS V 8.0.1

Regards,
Murali

You can't, because there isn't one.

You find all the manuals in bookshelf.html.

On-line help is obtained by pressing F1 or clicking a Help button.

It's all in the manual. You have to capture the perfomance data when you run the job, then the Performance Analyzer reports on the captured statistics.

There are couple of libraries that have to be deployed as well. You can find out what these are in the manual about programming using the DataStage API.

Auto-purge takes no heed of instances.

200 characters is trivial. However, my solution assumed nine characters - that you would always generate three rows. You need a slightly different solution, as follows. Use Fmt() to process your final column into groups of three, then convert the text marks in that string into value marks. Write int...