Why does Control-M job log shows job submission timestamp later than application side job submission timestamp ?

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.


    PRODUCT:

    Control-M/Agent for UNIX and Microsoft Windows


    COMPONENT:

    Control-M/Agent for UNIX and Microsoft Windows


    APPLIES TO:

    Control-M/Agent for UNIX and Microsoft Windows Control Modules such as Control-M for SAP



    PROBLEM:

    The Control-M job log shows the job submission time later than job submission time observed in the application server, even though the time setting in the Control-M/Agent and application server are same.

    In the following example, the Control-M/Agent and SAP application are installed on same machine and job submission time from job log and job's output are different(usually less than 1 minute):

    |0707|0705|JOB AU_ECOM_AUTO_DELIVERY    |011di|TR|5101|STARTED AT 20180707070555 ON <SAPAgentName>

    But, the job's output shows the SAP side job submission as follows: 

    Date Time Class No. Message 
    --------------------+------------+-------- 
    07.07.2018 07:05:38 | 00 516 | Job started 


    CAUSE:

    Disk volume installed with Control-M/Agent is very slow.


    SOLUTION:

    Following slowness at Control-M/Agent could be observed due to the slow performance of the disk volume where the Control-M/Agent is installed:

    - delayed in job submission (time difference between agent accepted the job and started the job)
    - delayed in job status update (Starved job message)

    For example, following messages could be seen in daily log for the job:

    0707 070058  34 JOB AU_ECOM_AUTO_DELIVERY (ORDERID 011di, RUNNO 00001) ACCEPTED, OWNER N/A, APPL TYPE SAP, AGENT NAME <SAPAgentName>
    0707 070555   1 JOB AU_ECOM_AUTO_DELIVERY (ORDERID 011di, RUNNO 00001) STARTED (07031000), OWNER N/A, APPL TYPE SAP
    0707 071052  48 Starved JOB (ORDERID 011di, RUNNO 00001) found and is not tracked for 286 seconds.

    Using the disk_benchmark utility found under following locations could be used to check the performance of disk volume where Control-M/Agent is installed:

    - For Windows, run DOS and change to agent's toolbox folder and run:
    disk_benchmark .\test

    - For Unix/Linux, login as agent user and change to agent's ctm/toolbox folder and run:
    disk_benchmark ./test

    The sample output should look like following for slow disk volume:

    /home/ctmagent/ctm/toolbox$ disk_benchmark ./test
    2281 open/write/close in 10 seconds. Time for each write 4.384042 milliseconds

    NOTE: For normal operation, the time for each write should be less than 0.02 milliseconds.


    Article Number:

    000155867


    Article Type:

    Solutions to a Product Problem



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