DSXchange

Those were Private, were they not? I'm assuming this would be a public forum.

Well, you knew that would be coming next, so...

Didn't Kim write / post something to do that?

Why not use one of the 'Key Management' routines in the sdk? By the way, what happens when your last number used is 9999?

Perhaps I should have worded my post more carefully. You'd actually need to supply more useful information so people can help - that doesn't really add all that much, if anything.

I think that would be fine.

Without supplying more information about your database and how exactly you are using the stage or things you've tried, I would think about the only answer would be - because it's the default.

The workaround is to hit the Back button in the browser when it's had enough time to get posted. You're now back at your message; now open the forum. Alternatively, just click on the link that takes you back to the forum. You will find that your post is there (at the top of the list) but still mark...

Do the problem only happen to you or does everyone have the same issue?

Ok, sorry. What can that tell you other than the fact that an entry does in fact exist? Seemed to me that any such 'MAXFETCH' tunables would be elsewhere, hence the thought that perhaps you meant 'the other file'.

Craig - I don't have anything to add, the error does seem very odd. What about if you were to have the admin people restart DataStage from 'root' - do any of the symptoms persist (jobs running under dsadm, connectivity)? I would tend to think that something else has changed with regards to user per...

And why do you find that strange if you 'closed the previous session'?

And now you are stuck again? Do you understand how relative paths work? From DSEngine, you can run this two ways: ./bin/dsjob -or- cd bin ./dsjob Either one should work. If you had the normal $DSHOME environment variable set, you could do this from anywhere by providing an absolute path to the exec...

And?

I don't care how you get there, but move to your DSEngine directory, which is one up from the bin directory you seem to know all about and execute the command I noted. Then try dsjob. Again.

Search the forums for "unhandled failure", it has been discussed here a bajillion times.