DSXchange

jayeeta_aec wrote:But could please take up littile burden for me? Please post the command only that you have mentioned.

Premium membership is one of the ways that DSXchange's hosting and bandwidth costs are defrayed. It's not expensive, at less than 30c (Rs12) per day, and well worth having.

... or use the SDK routine UtilityRunJob() for running the other job from the Transformer stage.

First off, there's no such thing as a job sequencer. You got it right in your subject line.

Second, when's the interview?

In version 7 Usage Analysis is a tool available in the Manager client specifically to answer the question "in which jobs is the selected component used"? It depends, to some extent, on the Dependencies tab being kept up to date in those jobs, and on the linkage between table definitions lo...

I need some time to digest and think about this one. Please be patient. in the meantime, keep us updated with anything useful you get from your official support provider.

Please be more specific about what you mean by "compare". QualityStage may not be the tool of preference.

On Demand Strategies is the company that supports DSXchange. Contact information can be found on their website. Dennis James is editor@dsxchange.com among other hats.

Find out who put them there and on whose advice. They are not standard, so please post the results of your research here.

Show us the value that you passed to the parameter.

Show us the value that the parameter received (get these from the job log "job starting" event).

The same issue?!! That quotes are being stripped in a parameter?

Details, please.

You need to be far more specific about what you mean by "does not work".

You have marked this thread as having a workaround. Care to share what that might be?

My earlier post provides a solution using a routine.

DB2 is storing the format 011010101010100100101001010111010010110101010001000

You can change the display characteristics of your viewing tool if you want it to be displayed differently from default.

Show us what you are trying to do and we may be able to be of more help in diagnosing what "does not work" in this particular case. In future please try to be more specific. File size is readily determined if you have opened the file for sequential access (that is, using OpenSeq). Use the ...

You can only "mend" what you call "bad" characters if you know what they are and what they should be. You can, of course, eliminate them (with permission).

Oconv() supports NLSmapname as its second argument - perhaps you could investiate this?

That won't help you, because your table names will be different.

Table names in XMETA all carry an eight hexadecimal digit suffix tied to the individual installation of the Information Server product/environment to which they relate.