Jobs on a Windows Agent do not finish and stay in a Running Status.

Products

• CA Automic Applications Manager (AM)

Issue/Introduction

Jobs on a Windows Agent do not finish and stay in a Running Status.

Environment

Release: AAMOS499000-8.0-Automic Applications Manager-OS400 Agent
Component:

Resolution

Detailed Description and Symptoms

Jobs will stop processing but will stay in a running status in the backlog.  The output file will show "exiting BODY2".  The job may start running a minute later, or the next day with no explanation for the delay.

Investigation

Please have all users logged into Applications Manager close any file viewer they have open.  If this does not allow the job to start please have all users log out of the client completely.

Solution

Due to limitations in the Windows Operating system, opening the output file through the internal file viewer while the job is running will prevent BODY3.bat from starting.  This will prevent the job from finishing.  Because of this we do not recommend users open output files on jobs running on Windows until they are completed.  If it is necessary to look at the output while the job is running be sure to close the window quickly so the Job can continue processing.