CMD.EXE - large number on server

ecclesr · Post by **ecclesr** » Thu Jul 06, 2006 2:32 am

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

roy · Post by **roy** » Thu Jul 06, 2006 8:32 am

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,

ecclesr · Post by **ecclesr** » Thu Jul 06, 2006 3:35 pm

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

ecclesr · Post by **ecclesr** » Sun Jul 09, 2006 5:00 pm

How are people running the project backup batch job

I am running my batch job via datastage so the parameters are passed

How are people running batch jobs that will running for a period of time

Thanking you all in advance

ray.wurlod · Post by **ray.wurlod** » Sun Jul 09, 2006 5:53 pm

Try running them via the START command (which also allows you to assert their priority).

thirupri · Post by **thirupri** » Mon Jul 10, 2006 9:22 am

Hi ecclesr,

If you like my idea please do as follow:

First create the batch file in a specific directory. Then create a sequential Job in that use the Execute command stage. Then call this Job in the Server Job so the next job will not start till this job completes.