DSXchange

There is a server Pivot stage, and this is exactly the task that it is intended to perform. Use the Pivot stage.

The contact number is the telephone number of your support provider, at least in the first instance. If they escalate it, then your contact details may be provided to a support group in IBM/Ascential who in turn will make contact with you. But do read the other thread on corrupted DS_JOBOBJECTS.

UtilityRunJob is not cataloged with a "DSU" prefix. From memory it's cataloged as "DSX.UTILITYRUNJOB". Someone with access to DataStage could perhaps verify this. That's the name that must be used in the CALLING clause. And note that it is case sensitive (all upper case).

The COUNT command is a quick test to see whether the entire file can be processed. In this case it can not, because at least one backward link (BLINK) pointer has become corrupted. The best repair at this time is to make sure no-one is using DataStage and no DataStage jobs are running then, at the o...

Use ExecSH rather than ExecTCL to execute mkdbfile command. If you're doing this from your own routine, change the shell argument of DSExecute from "UV" or "TCL" to "UNIX".

Is the column that supplies a value to Arg1 declared to be nullable?

Yes, there is a separate manual called Advanced Parallel Job Developer's Guide (also in your Docs folder) that covers custom code.

You also need "x" permission to be able to execute scripts. Check for this.

The error from j_close is because it was invoked with no job open. It's a consequence of the earlier error. Ignore it for now.

From which we can guess that the FKEYCOLS property relates for foreign key columns. I post this surmise against the possibility that others may be searching for this answer in future.

So Search for "unbalanced input". There's even an FAQ on exactly this.

chandra wrote:jod sequencer is not my point

Neither server nor parallel jobs have checkpointing capability, unless you design it in yourself.

Please quantify what the "perfect answer" would be.

A job is completed whether it not it fails. I am not aware of any way in which it's valid to claim - as your subject line does - that log view fails.

I have removed the premium content restriction since you won't be able to sign up over Easter. Please do so as early as possible - it's less than $1 per week, helps to sustain this site, and gives you access to all premium content. The restriction will be re-established after Easter.

OP = "original poster" (you).

Have you checked the permissions as I recommended?

Have you, indeed, read all the information that is available from the messages?

They're not errors, they're messages informing you about what's happening with your data so that you can perhaps optimize buffering and/or partitioning.

See earlier post and/or Search about "will partition despite preserve-partitioning flag".