DSXchange

I included them because the External Parameter Helper for that field in the StartLoop stage included them when I cobbled a snippet together to double-check the syntax. So I'm thin'n they really need to be there, Queeks Draw.

You shouldn't have to, have you tried it yet? If you've tried it and had a problem, what exact value was returned from the Execute Command stage and what problem did you have? You are using #Execute_Command_Stage.$CommandOutput<1># for the To: value in the StartLoop, yes? The stage adds field marks ...

You wouldn't typically need to do anything like that there as Server / Sequence jobs are not strongly typed like PX jobs. What exactly do you have going on that makes you think you need to do that?

Why specifically "using ICONV and OCONV"? Those are Server functions and would thus require a BASIC Transformer stage.

From the command line, meaning with dsjob, you need two steps: 1. Check the status of the last run using -jobinfo 2. If needed, reset the job using -run -mode RESET Then do your -run -mode NORMAL run. Now, I suppose one could just always reset regardless, but you need the first two steps for the &qu...

It's not always presented as a discrete option. From the manuals: If the property value begins with FILE=, the remaining text is interpreted as a pathname, and the contents of the file supplies the property value. Meaning, there are stages where you can say 'User Defined' and then do as above to hav...

So it seems like you have the 'Log warnings after activities that finish with status other than OK' enabled. That would tell the Sequence to log something in its own log when it sees a problem happen in another process it is running. Those jobs will still have the actual problem details in their own...

Right, with a caveat. A Sequence job won't care about problems in the jobs it runs unless you tell it to and they will still be logged in the problematic job's log, not the Sequence job's log. So anything bad in the Sequence job's log is from the Sequence itself... which could, of course, be from a ...

What did you want in the second run, something other than it continuing where it left off?

No problem. If you still have questions about what you need to do, best to start a new post IMHO. And if you are curious what kind of things you could actually use that option for, a google for 'oracle connection string options' will turn that up. A need to leverage that should be pretty rare, if ev...

True, constraints do make that a little... trickier.

And another reason I suggested SQL was the fact that this was a 'one time' thing.

Hmmm... you can think of 'instance' to mean database (the part that goes after the @ in something like sqlplus) and 'the same server' can have multiple instances on it. Schemas in the same instance aren't an issue as long as you have the grants you need, so just fully qualify the tables and you'll b...

I'd also be curious what exactly "Select * Update Statement" means. You don't "*" anything in DataStage so wondering if what you are selecting matches up well with your metadata.

I know this is a little old school, but you don't need anything special to do that - open a cmd/DOS window and use command line ftp. Sure, you may have to learn how to 'open' and 'get' or 'put' but it's always there... waiting for you.

Me, I'd be careful about persisting too much data directly in $DSHOME or even on the same partition as DataStage is installed. Since running out of space there is still a Very Bad Thing, I'd keep all that as separate as possible.