DSXchange

Just to double-check - these are "account-based" hashed files that live in the Project, yes? Out of curiousity, how many are we talking about?

Yah, it's a one-time thing so don't really see a need to generate it over and over again. Besides, whomever you are generating the XML for should have provided you with an xsd to help drive what you create.

The short answer is to setup a reject link from the stage to a Sequential File stage. Have you ever done that before? Give that a shot and then let us know any specific questions you may have.

They were aborted when run under a Sequence job because they exceeded a (probably 50) warning limit? Rather than your normal unlimited warning run when standalone? Is that the scenario you are describing?

In the target metadata? Then I'm out of ideas... if no-one else comes along, I'd suggest taking this to your official support provider.

Hmmm... while Informix supports CHAR fields up to 32,767 in length, I don't believe ODBC does. What happens if you declare it as a VARCHAR (or NVARCHAR) in the job?

What are the datatypes in your Informix target? Sounds like at least one of them is of a type that is not supported.

Well... three points.

1. I imagine Pavan solved this five years ago.
2. And by 'solved' I mean realized that they had no issue at all.
3. They already noted how to do it for "non-decimal values".

What are your actual Oracle datatypes in your source / target? Any LOB columns?

Just to be anal, the actual value is $ReturnValue. And don't forget that any non-zero return value will be considered a failure of the routine if you have the 'Automatically handle' option enabled.

SURA wrote:After the server restarted, i can see the copy of job.

Does this mean your problem is resolved and you can copy jobs now?

Why in the heck did you feel the need to go back and remove your original question after it was answered? That's a pretty crappy thing to do.

Sounds like a possible permissions issue if the compiler thinks it goes ok but it is in fact actually still uncompiled. Can you check? Use a different userid?

Did you find this? I found it documented in the Designer's Guide pdf, Chapter 14. Building job sequences, Table 4. Variables used in defining trigger expressions. For example, for the Execute Command stage it shows and explains: stage_label.$ReturnValue stage_label.$CommandName stage_label.$CommandO...

How about more specifics around what "unwanted character" might mean?