0

I have a .bat file that maps a network drive, runs an MS Access program then deletes the mapped drive and exits. When I run it through Control-M the .bat runs and finishes but the job in Control-M never ends. I have tried multiple things to end the file to send Control-M an exit code but nothing seems to be working. Below is the code:

@echo off
net use w: [path]
"C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" "Y:\MSAccess.mdb"
net use w: /delete

After this code I have tried the following commands:
exit
_exit 0
timeout /T 10

No matter what I try Control-M never seems to know that the job has finished. The sysout from Control-M also does not show any kind of exit code being sent back.

Gord Thompson
  • 116,920
  • 32
  • 215
  • 418
peel
  • 45
  • 1
  • 3
  • 7

4 Answers4

0

Control-M is probably waiting for all the processes started under it to exit before exiting the job itself. In your case, MSACCESS is still running when the end of the BAT is reached, so it prevents Control-M job to finish.

If you have your BAT to wait for MSACCESS to finish, 

net use w: [path]
start /b /wait "" "C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" "Y:\MSAccess.mdb"
net use w: /delete

this might alleviate (at least stetically) your problem

PA.
  • 28,486
  • 9
  • 71
  • 95
  • That did not work. It seems the issue is that the Access Database is not running when the .bat is ran through Control-M. I can log into the server as the Owner who is setup in Contorl-M and it runs fine but for some reason it does not run when Control-M does it. I am not a Control-M expert so do not know the difference between Contorl-M running a job as someone and actually running the job as them yourself. Thoughts? – peel Apr 05 '13 at 11:17
0

After some more testing and investigation the issue was happening earlier in the .bat. The MS Access database was never being opened and run. Therefore since it was never starting it was never ending or sending an error code. I am researching why the MS Access database was not running now, which may lead to another question.

peel
  • 45
  • 1
  • 3
  • 7
0

I had the same problem. I resolved my problem by adding the following at the end of the bat file: 

exit /b %errorlevel%
Dany
  • 1
  • 1
0

For Windows batch scrips, add exit /b %errorlevel% at the end of file. This will help to find script has processed properly and control job will end/endnotok.

milanbalazs
  • 4,811
  • 4
  • 23
  • 45
dhilip77
  • 11
  • 1