DSXchange

As noted a bazillion times already, the vendor deliberately does not publish this information, and reserves the right to change it at any time.

Anything you get here on DSXchange is the result of many hours of investigative work, which some unkinder individuals would call hacking.

I misread your question, assuming you had a job with no ROOT element. Now I understand that you see a difference of behaviour between versions of Financial products Markup Language.

You can find a few ideas with a Google search for "fpml schema root".

A common requirement and easily accomplished with a DataStage job. I usually capture the new key into the job's User Status area as well as updating it into the table. But adding N is a bit unusual - the only value I've ever used is 1.

Your format string specifies a four-digit year - your incoming data has only a two digit year. That suggests that what you need to do is to change the format string to use a two digit year.

Don't refer to these characters as "special" - they're not. If you must, refer to them as Control Set 0. Initialize a stage variable to contain a concatenated string of all 32 (specified using the Char() function) and use Convert() in the derivation expressions to convert this string of ch...

Ignore the warnings if they're occurring at design time. You'll also get warnings if you built or use user-defined SQL that contains parameter references.

What do you mean by "not working"?

Who are you? You're not the originator of this thread? Are you a colleague of kittu.raja? If not, how can we be sure that you're on an identical system? In any case, until kittu.raja posts the logic required (in English) how could we suggest how to implement that logic in a Transformer - or any othe...

No. The detail is already complete. Find out who has the Suite Administrator role at your site and get them to explain.

Does the export contain only the executable, not the design components?

Perform this query in a nuclear powered server to get a truly atomic method.

That wasn't my question.

No, only LPARs for me. Resources can be re-allocated between LPARs, but not on-the-fly. In one case, the standby system was initially allocated 0.1 CPUs !

Version 8 has quick and advanced search utilities to aid you in constructing the list of jobs that you must examine.

UniVerse manuals may be downloaded from Rocket Software - they don't totally describe DataStage, but the SQL at least is 100% compatible.

DataStage repository tables are deliberately not documented by the vendor, which reserves the right to change them at any time.

OK, the functions you used are for the parallel Transformer stage, not available in sequence activities. I would use a Nested Condition activity, with the expression