hi all,
I have a problem like this:
1) I modify a Job J1, I save it and compile it
2) I run the Job, datastage execute the OLD job !!
any idea ??
THANKS!
A.M
Datastage execute OLD job!!!
Moderators: chulett, rschirm, roy
More information please! 
Define 'old job' and what makes you think DataStage ran it. If you worked on a job, saved it back to the same name and recompiled it - all with no issues - there is no 'old job' for DataStage to run. Unless there's more to this story.
The only other thing I can think of as a possibility is a permissions issue. The userid used to change it was different than the userid used to create it and somehow the changes didn't 'stick'. But I don't see how all that could happen... silently.
Define 'old job' and what makes you think DataStage ran it. If you worked on a job, saved it back to the same name and recompiled it - all with no issues - there is no 'old job' for DataStage to run. Unless there's more to this story.
The only other thing I can think of as a possibility is a permissions issue. The userid used to change it was different than the userid used to create it and somehow the changes didn't 'stick'. But I don't see how all that could happen... silently.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
You could check the umask setting in the ds.rc script.
This is now set to a umask value of 002 but it was not set at version 5.x and on some unix platforms this stops one user from creating/importing a job and another user compiling/changing it. (when all datastage users should have full access to each others work)
This is now set to a umask value of 002 but it was not set at version 5.x and on some unix platforms this stops one user from creating/importing a job and another user compiling/changing it. (when all datastage users should have full access to each others work)