DSXchange

While you can delete individual jobs from the Director, you cannot delete folders from there. That needs to happen in the Manager or Designer.

Still, same advice applies. Think of $DSHOME as "where DataStage is installed" and make sure the full "bin" directory is in your PATH. Or try the other two ways noted.

No, that would convert individual characters not strings.

I would say "Delete it from the Manager" but from what I understand that's gone in 8.x, so... "Delete it from the Designer Repository window".

So... a path problem. You'd either need to ensure $DSHOME is in your $PATH statement or fully path the command or cd to where it lives and execute it from there. Normal command line stuff.

If all the main sequence does is chain together lower level sequence jobs, then I'd agree that you could do it that way. You could also have the main sequence do all of the notification, success or failure, if you like. Not sure if either way is "better" than the other.

From what I recall it is the order they were added to the Sequence, which more than likely is the order they run in but may not be.

It's an operating system command, not an internal DataStage command. Run it from a command prompt.

Three DB stages chained together by transformers is most of it. You'd need to explain what to do with the last "select *" information, though.

Correct, it does not support wildcards.

Come on, you waited what... 20 minutes before pushing? Relax, people will answer when they can.
From the command line.

Or there's always the front door. Open the Sequence job / Job Properties / Dependencies tab for a list of all the jobs the Sequence runs.

What you need is a PX version of the Server EReplace() function. And, what do you know...

viewtopic.php?t=106358

Once you start down the "manual deletion" path (and thus destroyed any automated mechanism) it seems you'll have to walk that manual path to its end. At this point you would just use rm to "clear the memory", I assume.

There's a dsjob option that will get a list of the jobs in any given project: -ljobs off the top of my head. You could redirect that output to a file for processing or just pipe it thru "wc -l" to get a count.