DSXchange

There's no plug-in for that that I know of and one would typically use the "TX" product for things of that nature. Otherwise it's going to be something you'd need to tear apart yourself. From looking at the format it doesn't look like it would be too bad to handle. :wink: Read the file as ...

Start someplace like here:

http://www.unixtimestamp.com/index.php

A Key column has nothing to do with indexes or database Primary Keys or any such concept. It simply means the column(s) to be used in the where clause.

srinivas.g wrote:Performance wise Inline sort is best compare to explicit sort stages.

Based on what? Under the covers they're both the same tsort operator.

'Code' doesn't necessarily mean your 'code', could be a driver or parallel framework bug, etc. Involve your official support provider.

PH stands for 'Phantom' or background process. It is a communication area that should be pruned of 'old' information on a regular basis. There is no 'moving to production' component to this. Once a job completes this information is no longer needed.

The Start Loop and End Loop stages, oddly enough. Optionally a User Variables stage as well to derive values at runtime, for example your number of times to loop. Read the docs, they are explained there with several examples.

They've been posted here fairly recently, it might be a little bit of a PITA but a search should find them.

Where did you launch uvsh from? Did you get any kind of a message about something "not being set up"? Are you properly logged into your project? Does that work in the Administrator?

First you must identify the character, then you can strip it easily. A hex editor is the easiest way to do that and there are a ton of free ones out there.

I'm not sure there really is a need for that option with a Type 30. But don't forget the stage supports all types, so it could be more appropriate for the static types. Curious what others think.

In other words, it executes an operating system command. And you put in whatever is required to run it.

So... this is resolved? If so, mark it as such using the button at the top of the page.

Is that the sum total of the error(s) you get? What is your job design?

It's a character set issue, not a data type issue. Have you tried stripping it from the field? Add $APT_DISABLE_COMBINATION set to True in your job and rerun to know which stage is throwing the error.