DSXchange

I can't imagine there'd be a problem with that but what do I know.

If you do, don't post them here - I'd suggest creating a posting on the subject over in the FAQs forum, then link to them here.

Yes, it should work just fine as noted. Can you post the start and end times from all three jobs? Don't expect the two jobs to start at the exact same time, it should start the first and then once started, it should start the second one. If the first job completes quickly, then it can appear as if t...

And your job design looks like this?

No dependancies between Job2 and Job3 other than the links back to JOBA? They should both start at approximately the same time.

Well... the one problem you've found so far is project specific. However, that's not to say that's the only problem you've got. Did you search for your error message here and read what other people did to discover the extent of their problem and how they recovered? Ray has posted quite a bit on the ...

The entire project in question. How old are your backups? Again, any idea what happened?

It's important to note the "in the same sequence" part of the answer. That is a Sequence job stage and it would make the new parameter value available to any jobs that are downstream from it in the same Sequence as the UserVariables stage in question.

What happened? Sounds like you may have run out of space where DataStage is installed and corrupted your installation... do you have backups?

Sure, run OK triggers from JOBA to both Job2 and Job3. They will both start after JOBA completes successfully.

As you've already found in your other thread with this question you cannot use wildcards in the WFF stage.

Yes, simply don't link them together.

If the hashed file was created in an account, then "COUNT <Name>" in the Administrator's command window would work. For a pathed hashed file, you'll need to create a VOC entry first, then count.

You need to ensure the $CLASSPATH includes the directory where your class lives. Should be as simple as that.

Then take whatever the proposed script did and do the same thing from the routine using the DSExecute() function.