DSXchange

Welcome. :D

So you've looked at the generated source code around the line number as noted in the error? Is it having a problem when you attempt to use the stage variable or when you are setting it?

I understand changing the reusable job to allow multiple instances doesn't solve the problem Actually, that sounds like the only solution you have. Both the Sequence job (no 'r' by the way) itself and the Server job inside will need to be multi-instance jobs. And yes, the Sequence's invocation ID c...

Using the FTP stage? Have you verified your metadata, the field types and sizes are indeed correct?

DateFromDaysSince() I would think.

You would need to upload it to any of the many free image servers and then use [img] tags to link to it in a post. Those sites will generate the links for you, typically.

What happens when you run the command yourself from the command line, does it behave as expected? Also, where did the dot come from at the beginning of the command? Actually, why don't you detail what you put in each 'box' in the stage.

Depends. 'Upgrade in place'? Nope. Build a new server and import from the old one? Yes.

And "Stage Name from PX job" means a hard-coded value or something derived? The confusion is the fact that you showed an example of a stage name with a "dot invocation id" tagged on to it and that's not correct.

Welcome aboard. :D

Not to sound like a smarty pants, but go ahead. That sounds perfectly reasonable, just add the column and setup the derivation for it. What part are you having a problem with?

You have to request it. You will not find it out there for download.

Don't pass the double-quotes in the first place, they are completely unnecessary there unless you have something like <shudder> a mixed-case table name.

Don't try to put a timestamp in a date field.

How many nodes?

Wait... you don't want to save things in Oracle or you do?

If not, where or in what format do you want to store things?

Running on how many nodes? What stage is the constraint in?