DSXchange

Which is why 'UP' is restricted to Administrator usage only, it seems.

One would assume so, why have a DOWN option without having an UP? Might as well just have a CHAP function in that case. It's also what I'm assuming Ray is referring to when he said:

"You can not raise your priority. Only a DataStage Administrator can do that with this command."

So, your requirement is to be able to skip *any* single job in a Sequence job? Or 'some jobs in it'? Regardless, interesting requirement. If your Sequence has Checkpoints enabled, then it does seem like you could do something outside the job itself to 'reset' or manipulate the checkpoints to make it...

There's nothing 'definite' about just using a varchar, there's more to it than that. Seya, what does your target SQL look like, specifically for your DATE field? Obviously, you've got a perfectly valid date format, but you need to make sure the date format you are using matches what the SQL is expec...

Yah, yah... I'll get right on that.

Can you describe under what circumstances you would envision a job needing to be skipped? If it's not something checkpoints can achieve, it may just mean that you need to build a conditional branch into your job stream...

Let me put it this way. While I didn't totally agree with their assesment, the group here that I installed it for decided not to use it after taking it for a spin. Sure, there are 'Log Reader' stages and it brings Perl integration and other cool things into DataStage but they felt the performance wa...

'CHAP DOWN'? Really? First I've ever heard of that.

No, it's free and I've got it installed. From what I recall that 'pack' is only for Server jobs. And it's been deprecated from what I hear and is not available in 8.x.

Don't know how. Been using the product since the 3.0 days and never had a need to do anything of the sort, so never went over to the Dark Side.

If you are certain that it exists, then yes I would assume a permissions issue.

No, what it should mean is since the Operator role can only see 'released' jobs, there's nothing to see and thus nothing to run.

No problem. You just needed to bring the variables outside of the quoted string bits so they could be recognized as variables and substituted properly.

Time to mark this as Resolved.

There is no 'proper way' to do something illegal.

What makes you think you need to do this? Or is this just an academic expedition into DataStage hackerdom?

Please post the complete error(s) from the job's log regarding the file error.

We need to recover the original code with the design.

Recover? Either you have it or you don't. What about in your development environment or in Version Control? Exports of the project you've archived somewhere?