DSXchange

If you are running 7.5 then any DataStage client installation includes the 'dsjob' executable. So it sounds like you should be able to use a Windows based scheduler to execute DataStage jobs on a UNIX server as long as the client was installed on the same machine as the scheduler.

Still think sleep would be your best bet. Write a routine to do the sleeping and use a Routine Activity stage to run it rather than trying to delay in the trigger.

It could even check the current time or job start time as an argument and sleep a computed length of time, I would think.

No, the import doesn't care what the name of the project it came from was. Bottom line is this new project is corrupted. There have been several fairly recent conversations on this very issue, including what needs to be done to fix it. As noted, a search should turn them up. If not, post back and we...

I remembered where I found the little tidbit I was referring to - here. Curious what anyone thinks of the specifics of this 'tip'.

I haven't tried to implement it, so can't vouch for it... just had it filed away in the back of my brain.

Great... smacked twice by Uncle Ray in one thread.

From what I recall, type in localuv for the dsn and you should be fine.

I think I read somewhere that you can actually use SETFILE to create a VOC record for the parent directory that your hash files live in. This would allow you to treat the directory as an 'account' and so avoid having to add individual VOC records for each hash file in the directory. Is this true? Ca...

Actually, it does - in 7.5 - which the OP seems to have.

Didn't even look deeply at the code itself, especially since it isn't formatted at all. Title of the thread mentioned Oracle procedures and I figured it was something that would require the stored procedure stage, mostly because it returns values. Seems like an awful lot of work. Aren't they going ...

Which 7.x version do you have? It's only with the release of the 7.5 version with its Store Procedure Stage where you can do something along the lines of what you are wanting to do.

Actually, both the ODBC and UV stages can return 'multi row result sets'. FYI.

You can not have same job name for two jobs in the same category. Just to clarify, you cannot have two jobs with the same name regardless of category. Each job name much be unique to the project. Unless, of course, (as people are suspecting) the structures holding this information are corrupt, then...

If you do come up with a solution, post it back here. I'm sure there would be plenty of people looking for a generic solution to this issue. In my mind, something to first determine the current setting is needed. If the option is found to be set, unset it and then put it back at the end of the backu...

Better yet, don't worry about it. As noted, that's just the way it is.

Ok, then I can only see a couple of solutions. No amount of 'renaming' will help, as you've found. So... 1) Find out where that option is stored in the registry (assuming it is) and somehow automagically turn it off and then back on again during your backup. 2) Run the backup from a different machin...