Control-M/Agent fills proclog directory with many AT* AS* or AX* logs

Version 1
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    Control-M/Agent for UNIX and Microsoft Windows


    Control-M/Agent for UNIX and Microsoft Windows


    Control-M/Agent for UNIX and Microsoft Windows - all versions


    Why does the Control-M/Agent generating AT* or AS* logs with the following lines:

    CONTROL-M/Agent has encountered the following critical error:
    0707 09:49:57:123 AT:BE_COMMON_UpdateError: Failed to load file: './procid/XXXXX_1.DAT'

    Note that XXXXX is job order_id, and 1 is runcount of the job in above filename.


    Two different scenarios found:

    a) When Control-M/agent version 9.0.00 fixpack3 is not installed -

    The error suggests that the Control-M/Agent Tracker process couldn't find the particular job's process ID file while tracking the job.
    This could be that the job process somehow gone missing while the Control-M/Agent Tracker wasn't aware that happened.
    To prevent these messages, do the following steps:

    1. Check the job status file under Control-M/Agent's $CONTROLM/status & $CONTROLM/procid folders for the job status file(eg, xxxxx_0001.dsect) exists, and make sure the job is no longer running. 
    2. Stop the Control-M/Agent
    3. Delete the job status file, ie.  Control-M/Agent's $CONTROLM/status/<orderid_runcount.dsect file
    4. Restart the agent

    a) When Control-M/agent version 9.0.00 fixpack3 is installed -

    This is due to an issue introduced in Fixpack3 where the exception is triggered only when requesting the job ouput of a Control-M for SAP job.
    This issue is resolved in Control-M/Agent version 9 Fixpack4  (DO NOT INSTALL IT WITH AGENT DEPLOYMENT FEATURE )

    Article Number:


    Article Type:


      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles