I have a 3rd party program I launch from a cmd batch
in a 24x7 Scheduler job. 24x7 is running as a
service. When I run the job DETACHED, the program hangs.
When I run the job NOT DETACHED, the program doesn't
hang. Any ideas why? I run all my jobs DETACHED in order
to avoid 24x7 going "comatose" whereby it is still
running as a service, but no longer dispatching jobs.
Thank you.

Running program jobs detached does not help in any way because they are already "detached" - they run as external processes. I don't know why that particular program hangs in one mode but not in the other, as I don't see any difference between these 2 modes, I mean any difference from a program point of view (unless it is trying to trace back the process tree). I simply would like to suggest running this job non-detached and save time by not looking why it hangs in the other mode.
: I have a 3rd party program I launch from a cmd batch
: in a 24x7 Scheduler job. 24x7 is running as a
: service. When I run the job DETACHED, the program hangs.
: When I run the job NOT DETACHED, the program doesn't
: hang. Any ideas why? I run all my jobs DETACHED in order
: to avoid 24x7 going "comatose" whereby it is still
: running as a service, but no longer dispatching jobs.
: Thank you.

Running DETACHED program jobs DETACHED apparently makes a difference in my environment.
I had a problem of 24x7 Scheduler Service going "comatose". All my jobs were running DETACHED,
but 2. Since reconfiguring them both to be DETACHED, I have not had a single recurrence
of the "comatose" problem. Both jobs are cmd.exe/batch jobs. So, my empirical evidence tells me
to stay with DETACHED.

Thank you for your reply... I thought I would see if this was a known issue with a quickie fix.

: Running program jobs detached does not help in any way because they are
: already "detached" - they run as external processes. I don't
: know why that particular program hangs in one mode but not in the other,
: as I don't see any difference between these 2 modes, I mean any difference
: from a program point of view (unless it is trying to trace back the
: process tree). I simply would like to suggest running this job
: non-detached and save time by not looking why it hangs in the other mode.

Well, apparently that particular job is doing something fancy if it cannot run detached and leads to the "comatose" problem when running not detached.

Try shelling this job using cmd.exe /C switch. In other words if the command line is currently like mybatch.bat try changing it to cmd /C mybatch.bat

: Running DETACHED program jobs DETACHED apparently makes a difference in my
: environment.
: I had a problem of 24x7 Scheduler Service going "comatose". All my
: jobs were running DETACHED,
: but 2. Since reconfiguring them both to be DETACHED, I have not had a single
: recurrence
: of the "comatose" problem. Both jobs are cmd.exe/batch jobs. So, my
: empirical evidence tells me
: to stay with DETACHED.

: Thank you for your reply... I thought I would see if this was a known issue
: with a quickie fix.

Nothing fancy in the 2 jobs I changed to DETACHED - just basic Win2K cmds.
I do use "cmd.exe /c mybatch.bat". Thank you for replying and giving this
your time and thought.

: Well, apparently that particular job is doing something fancy if it cannot
: run detached and leads to the "comatose" problem when running
: not detached.

: Try shelling this job using cmd.exe /C switch. In other words if the command
: line is currently like mybatch.bat try changing it to cmd /C mybatch.bat

Have you tryed running it without "cmd /C", using just the batch file name?
Do you have tracing options enabled in 24x7 by any chance?
Which W2K commands do use in the batch?

: Nothing fancy in the 2 jobs I changed to DETACHED - just basic Win2K cmds.
: I do use "cmd.exe /c mybatch.bat". Thank you for replying and
: giving this
: your time and thought.