DSXchange

This is a permanent restriction in PX transform stages per IBM Support. They are submitting an "enhancement request" to change the documentation to reflect this limitation; and will stop the automatic insertion of same in derivations.

Make sure that both calls of this job use different instance names.

Arnie, this was discussed in another current thread. The VarChar() function to use is PadChar()

I can't think of anything offhand that isn't in the manuals and don't have recent QualityStage experience. We certainly had a number of teething issues with Japanese, Chinese and Korean implementations years ago but the installed bases and experience levels in those languages is quite widespread/hig...

I'm sure there is a software-imposed limit somewhere, probably 256 or another higher power of two. It might be a limit imposed by the number of variables a BASIC program might have (I think the limit is 32Kb variables) - but a lot of processing is done in COMMON blocks or dynamic strings so that lim...

In order to understand how DataStage NLS uses CJK, you need to start off with understanding multibyte implementations at a system level; the rest is just an implementation question. There are some excellent reference works available (hardcover ones) that provide a very solid foundation in the basic ...

The UNIX command inherits the ENV settings of the calling job, so you will already have a setting for the APT_CONFIG_FILE.

This is due to how you use the routine activity in your job sequence. Have you added an output link that is condition/unconditional from the routine activity?

In your case control file and xxx.ds are synonymous

Are those 6 stars in the actual data?

Did you not like the answer you got in your almost identical thread posted here?

No through the orchadmin or DataSet management interfaces. Try writing a simple job to dump the DataSet into a flat file, then copy that flat file to your clipboard. The orchadmin dump command will dump the file without column names but does prepend some orchestrate informational messages.

Does this mean the same job, started by the same user, using the same parameters, will run when started from the Designer or Director? The information from the previous run unfortunately only shows informational and warning messages so doesn't help in locating the cause for failure.

balu124 - you need to use DSLink17.Call_date[4,3]

Sid wrote:...job that abends after 475,000 data rows...

How about posting the error messages?