SAS batch job hangs up when scheduled from CONTROL_M

[sasuser]

hi all,

I am totally new to CONTROL_M; I have a set of DOS batch jobs (each a separate .bat file); Each batch file invokes several programs written in SAS language;

When these batch scripts are executed directly, everything works as expected;

However when scheduled using CONTROL_M , one of the batch jobs runs for some time , and then hangs up;

I have been to find out where it stopped...the point where it stops, the SAS code tries to invoke few DOS commands..first DOS command is simple CD command ..and then a DOS utility program is run ..this program uncompresses files (GZIP.exe); If this step is successful I expect to see uncompressed files, but that does not happen;

Looks to me that for some reason, when jobs are launched from CONTROL_M DOS commands are failing somehow ..

please give me suggestions, ideas what could be wrong here, or if I am missing?


thanks in advance;
Shankar

[philmalmaison]

hags up "yellow ? executing status ?"
use the right _exit from the controlm agent...
be sure that return code is send back by the script to the agent


regards
philmalmaison

[th_alejandro]

Hi, this is the problem with new users that use Control-M to sheduling old bat file o script not designed for Control-M or script with pour functionality. I have to re-write all script in my system in migration to Control-M, because jobs and functionality area diferents. My recomendation : re-engineering...., separate scripts un various scripts depending in his funitionality and join with conditions to perform the same.

[fyot]

Hi

Don't forget, you must consider Control-M as a black box, launching what you need.

If you want Control-M to react depending on information existing in your standard output, or depending on error code sent by your command, or your script, you must prepare your script to be able to send that.

If not, Control-M could wait a lot of time to react correctly.