DSXchange

That sounds like the normal reset message, so did it not add the 'From previous run...' entry? Are you actually doing anything 'before job'?

Then it would seem you are firmly in the hands of your support provider.

Only? How many more do you need?

Inside them would be an option to drive the 'direction' of the pivot.

Scroll over to the 'Data Type' property (pretty sure that's the name) for those and set it to 'XML'. That will tell it that it is already XML and to not futz with it.

Rows to columns is also known as a 'vertical pivot', something you could do an exact search for here to get all kinds of help. Which also means you should look at the Pivot stage but the capabilities there depend on your exact 8.x version.

First thing to try is to Reset the aborted job and see if a 'From previous run...' message is added to the log. If so, post the contents.

Relocated. Next time please pay more attention to where you are posting.

You need to decide which one is appropriate for each job being run. You may want to ensure that Aborts are resolved manually before restarting or you may be fine with them automatically resetting. Like many things... it depends.

Use StringToTimestamp() if you actually want a timestamp. For the format you posted, do that and then convert it back to a number.

In the parallel product. And I believe that it is a paid option, meaning you have to purchase 'DataStage Connectivity for Teradata' to get that capability.

So these are multi-instance Sequence jobs? I believe that you are correct in that if you need to worry about specific instances not existing, then you'd need to leverage the API in order to do the proper checks and conditional reset you need. Seems to me that could either be accomplished via scripte...

Good... that's how we are handling it with Informatica and the DoD at DISA.

There is no other way... and you shouldn't need to 'expose' the file at all, you should be able to lock it down in a manner that your security people approve. Have you specifically ask them?

Pam, the first question that comes to mind is: have there been any changes made to the code that I left there? I don't recall ever seeing the behaviour you've noted but have seen something almost the opposite where it goes to start a job and never hears back that it started and thus you get a 'livin...

You might want to try right-clicking on the stage and selecting 'Grid style' to verify all of the settings. Do this in both dev and test to compare.