Determining User History for AutoSys Job Executions Using Autotrack
search cancel

Determining User History for AutoSys Job Executions Using Autotrack

book

Article ID: 401322

calendar_today

Updated On:

Products

Autosys Workload Automation

Issue/Introduction

A need exists to identify which users have manually executed specific AutoSys jobs. This involves querying the system for a historical record of job runs initiated by particular users. If the AutoSys autotrack feature is not enabled (e.g., autotrack -l returns CAUAJM_I_50150 AutoTrack Level=0), historical data on user-initiated job runs will not be available prior to its enablement.

Environment

Product: Autosys Workload Automation

Resolution

To find the history of users who ran an AutoSys job, the autotrack feature must be enabled.

  1. Check Autotrack Status:
    Determine if autotrack is currently enabled and at what level by running the following command:

    autotrack -l
    
    • If the output is CAUAJM_I_50150 AutoTrack Level=0autotrack is disabled. Historical data for user job runs will not be available for the period it was disabled. Data will only be captured from the point autotrack is enabled.
    • If autotrack is enabled (Level 1 or 2), proceed to the next step.
  2. Query Job History (if Autotrack is Enabled):
    If autotrack is enabled, you can use various autotrack commands to retrieve the history.

    • To find all tracked changes for a specific job:
      bash autotrack -J <jobname> -v
    • To find all jobs run by a specific user (e.g., ejmcommander):
      bash autotrack -J % -U ejmcommander -v
    • To find sendevent actions issued by a specific user (e.g., ejmcommander):
      bash autotrack -J % -U ejmcommander -t S -v
      Example output for autotrack -J % -U ejmcommander -t S -v:
    ejmcommander 06/11/2025 17:49:31 CAUAJM_I_50152 Sendevent issued. eoid: PRDz10000269 job_name: Job1 command: sendevent -E FORCE_STARTJOB -J Job1 -C " " -P 10
    ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
    ejmcommander 06/11/2025 17:52:09 CAUAJM_I_50152 Sendevent issued. eoid: PRDz10000270 job_name: Job1 command: sendevent -E FORCE_STARTJOB -J Job1 -C " " -P 10
    ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
    ejmcommander 06/12/2025 22:11:30 CAUAJM_I_50152 Sendevent issued. eoid: PRDz10000271 job_name: Job2 command: sendevent -E STARTJOB -J Job2 -C " " -P 10
    
  3. Considerations for Enabling Autotrack:
    If autotrack is disabled and you wish to enable it:

    • Database Space: Enabling autotrack will consume additional database space. The amount will vary based on activity.
    • Autotrack Levels:
      • Level 1: Tracks various database changes including sendevent actions. 
      • Level 2: Tracks the same information as Level 1, but also writes the job definition for overrides and job definition changes.
        • Important: see links below for considerations on impact.
    • Enabling Autotrack: Refer to the "autotrack Command -- Tracks Changes to the Database" section in the AutoSys Workload Automation documentation for instructions on enabling and configuring autotrack.
    • Database Maintenance: If autotrack is enabled, it is crucial to perform regular database maintenance. Review the "DBMaint Command -- Maintain the AutoSys Workload Automation Database" documentation for best practices.

 

Additional Information

Additional Information for autotrack, impact, and maintenance can be found in the documentation pages below.