DSXchange

I was surprised to see in this thread that DataStage reports No default type conversion from type "date" to type "string[10]". ​ I had formed the view that everything could be implicitly converted to string if the size is large enough. However, upon checking the IBM Knowledge Cen...

Make sure that you do this, or specify one of the environment variables that prevent DataStage from inserting a tsort operator. Otherwise your sorted data will be re-sorted, a waste of everyone's time.

So, to the computer hosting DSXchange, pavan5035 and pavi are not the same.

Login as pavi and you should be able to see the premium content.

... and pay particular attention to partitioning requirements therefor.

Try removing -wait from the dsjob command. Technically -wait and -jobstatus are incompatible options. The -jobstatus option will still cause the command to wait until the job completes, so that it can report the job status.

Metadata Workbench does not require that you have a sequence. It does, however, require that you've used, or converted to, shared table definitions.

Does what you've done throw an error, or merely an incorrect result?
^ is a numeric token, so would never match any part of "metal chassis". Try this pattern/action instead:

What happens if you specify DSJ.JOBINTERIMSTATUS in the call to DSGetJobInfo() ?

You must be a local Administrator. Domain Administrator will not do it.

If you have Metadata Workbench you can request a data lineage report that will give you the transformations.

Can't you update the password in the Connector you are using to read from source?

SURA wrote:That's not seems consistence to me!

Given that the official decoding of 99 is "other" it is entirely consistent.

Can you try using the istool command to export and import the Parameter Set? (or its GUI, Information Server Manager)