I am executing a number of NT batch jobs via DsExcute
As expected the batch job is initiated and the datastage job continues
ie datastage job finished in 30 seconds the batch job still running until it finishes later
As a result I notice under Window task manager on the server there are are large number of orphan processes -
Is the a way to avoid all these orphan processes
Thanking you all in advance
CMD.EXE - large number on server
Moderators: chulett, rschirm, roy
Hi,
Usually orphand processes are found in development servers where they crash and may leave unterminated processes.
This is usually not the case on production environments.
So if this regards your development server you need to periodically clean it or reboot it.
IHTH,
Usually orphand processes are found in development servers where they crash and may leave unterminated processes.
This is usually not the case on production environments.
So if this regards your development server you need to periodically clean it or reboot it.
IHTH,
Roy R.
Time is money but when you don't have money time is all you can afford.
Search before posting:)
Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
Time is money but when you don't have money time is all you can afford.
Search before posting:)
Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
No the batch job is not crashing
The batch job is run at least 4 time a day, the batch job completes successfully, when I look at the server task manager after say a week
I have the large number of cmd.exe
I am initiating the batch job via a job control so that I can encrypt the some of the parameters being passed to to batch job
I believe the issue is due to the initating datastage job completing after
it has executed Dsexecute to execute the command to run the batch job
When the batch job completes it has no job to return to.
Also as the datastage job has already completed I do not get to capture the return code if the batch job had failed
Thanking you all in advance
The batch job is run at least 4 time a day, the batch job completes successfully, when I look at the server task manager after say a week
I have the large number of cmd.exe
I am initiating the batch job via a job control so that I can encrypt the some of the parameters being passed to to batch job
I believe the issue is due to the initating datastage job completing after
it has executed Dsexecute to execute the command to run the batch job
When the batch job completes it has no job to return to.
Also as the datastage job has already completed I do not get to capture the return code if the batch job had failed
Thanking you all in advance
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact: