DSXchange

I'm not sure 'at heart' is the appropriate expression.

I did find a 'Feedback' link on the page and submitted my thoughts on all this to whomever, if anyone, reads such a thing. I'll post whatever comes of it.

If I had any clue where to provide this 'friendly feedback' I certainly would.

Ugh... no indication of which posts are new since your last visit, you get to figure that out for yourself. And they screwed up the import of the old ADN posts, the formatting for things like bold and italics are all horked up.

I don't see myself spending alot of time over there anymore.

As a newbie, you might want to check this post. ADN doesn't exist anymore but you can get the documents it discusses at Kim Duke's site. They help explain the concept. Basically you are comparing a current value (Plan_id) to the value from the previous row (svkey) to see if it has changed. If it has...

You need to 'source' your dsenv file first:

Switch to PuTTY.

I used Reflection X long time gone and recently Exceed. Ended up dumping it in favor of PuTTY. Free, easy to use and light-weight.

As noted, your code seems to be 'fine', being pretty much exactly what DataStage generates when you use the 'Add Job' button. That being said, this kind of problem is just usually a timing problem. Some other process (or person) ran the job and when this one tried to you got the dreaded 'job is not ...

Doing that would only reset the job, not reset it and then run it. If you want to emulate the 'Reset if required then run' functionality of a Sequence job, you need to do both.

And if you want to do it 'right', check the status of the job and only issue the RUNRESET if you need to.

You lost me when you threw in the 'C' and 'f' words... not really sure what you mean by a COBOL Stored Procedure file. Perhaps you could explain a little more what you've got? Unless everyone else knows what this is...

Yup, not a Function but a Link Variable. Which is also where you'll find it explained in the Help - check the Index for links, variables for an explanation of the several that are available. You'll find there are both Input and Output variables, btw.

What's the nature of the abort? Adding a delay really shouldn't solve your problem, it's probably something specific to the Sequence. However, with that being said - create a routine that does a 'sleep' based on the input arg and add it (via a Routine Activity stage) between the two jobs and you've ...

Yes, that's part of what is documented in the online help. It only 'automatically handles' failures it thinks that you are not explicitly handling yourself.

Does that section include a connection to a Shared Container? Those will (unfortunately) never show counts on the canvas.

We've had this conversation many times here, Rod. I don't have time to do it justice, but I'm sure a search would turn up several examples. This is how the new 'Automatically handle activities that fail' option works in Sequence jobs. Check the docs / online help, it has two suggestions on handling ...