I have a datastage job which calls a DOS command after it finishes processing. I have run it more than 30 times in a day. However, occassionaly, this after-job command does not work. However, when I restart again, it will always work. Any idea? Thanks in advance.
It is not problem with datastage. First execute dos command manually and check whether it is working fine or not.
In our project we faced same error while executing shell script.
The problem may be that when you execute the DOS command, at that time it doesnot execute means there may be some problem in that in the sense the command is creating some error.
As sometimes it works, this shows datastage job is fine.
If you restart, then it works, means then your command get the sufficient resources required and thats why it runs.
So check the things with your Command.
With regard,
Yatin Mittal
cheerfu1 wrote:Hi,
I have a datastage job which calls a DOS command after it finishes processing. I have run it more than 30 times in a day. However, occassionaly, this after-job command does not work. However, when I restart again, it will always work. Any idea? Thanks in advance.
Inspect the code for ExecDOS in the Routines branch. If the exit status of the command (ERRORLEVEL in DOS terminology) is other than zero, the job will be aborted because the ErrorCode argument will be set to that non-zero value.
You need to determine what the exit status of your command is. Perhaps you can create a custom version of ExecDOS that includes some additional diagnostic messages (you can enable/disable these with conditional compilation techniques - yes, even in version 4.x) and maybe also guarantees that your touch command works.
Were you aware that DataStage on Windows has its own touch command? It's in the DataStage Engine's bin folder.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.