AutoSys Health Check Data Collection Procedure

Products

• Autosys Workload Automation

Issue/Introduction

This article outlines the steps for collecting data for an AutoSys Health Check, a service provided by Broadcom to ensure stability, performance, and resource efficiency of your AutoSys environment.

Environment

• OS: Linux/UNIX/Windows
• Product: AutoSys Workload Automation
  • Version(s): All Supported Versions

Resolution

Preparing for Data Collection:

• Obtain Check-Up Utilities: Download the following class files from your assigned AutoSys Health Check case:
  • SendJAva.class
  • WF_CleanUp.class
  • EEMPerfTest.class


• Install Utilities:
  • Copy the class files to the AutoSys client libraries folder:
    • UNIX/Linux: $AUTOSYS/lib
    • Windows: %AUTOSYS%\lib
  • Create an output directory for storing data files:
    • UNIX/Linux: mkdir /tmp/AutoSysCheckUp_$AUTOSERV
    • Windows: mkdir %TEMP%\AutoSysCheckUp_%AUTOSERV%


• Prerequisites:
  • JRE 1.8 64-bit: Required for AutoSys r12 and above.
  • Source AutoSys Environment: Before running any data collection utilities.

Running the Utilities:

1. SendJAva Utility:
   
2. • Purpose: Collects data about your AutoSys instance.
     
     
   • Usage: java -cp ".:./*:$AUTOSYS/lib/*" SendJAva 'hostname' 9000 ACE "/tmp/AutoSysCheckUp_$AUTOSERV" CONFIG
     • Parameters:
       • LIBPATH: Path to the class files and AutoSys libraries.
       • HOSTNAME: Hostname of the AutoSys instance.
       • PORT: Port of the AutoSys instance.
       • AUTOSERV: Instance name.
       • OUTPUTDIR: Output directory for the data files.
       • ENC_TYPE: Encryption type (DEFAULT, CONFIG, NONE, AES).
       • Optional: USER, NODE, PASSWORD: For EEM access.
         
         Example (UNIX):
         java -cp ".:./*:$AUTOSYS/lib/*" SendJAva 'hostname' 9000 ACE "/tmp/AutoSysCheckUp_$AUTOSERV" CONFIG
         
         Example (Windows):
         java -cp ".;./*;%AUTOSYS%/lib/*" SendJAva 'hostname' 9000 ACE "/tmp" CONFIG


3. WF_CleanUp Utility:
   
   • Purpose: Identifies stale jobs and jobs with missing calendars.
     
     
   • Usage: java -cp ".:./*:$AUTOSYS/lib/*" WF_CleanUp 'hostname' 9000 DEFAULT "/tmp/AutoSysCheckUp_$AUTOSERV" X
     • Parameters:
       • LIBPATH: Path to the class files and AutoSys libraries.
       • HOSTNAME: Hostname of the AutoSys instance.
       • PORT: Port of the AutoSys instance.
       • OUTPUTDIR: Output directory for the data files.
       • X: Number of months defining a "stale job".
       • ENC_TYPE: Encryption type (DEFAULT, CONFIG, NONE, AES).
     • Output: Creates JobsMissingCalendar.csv and a CSV file with stale job information.
       
       
4. EEMPerfTest Utility:
   
   • Purpose: Evaluates the efficiency of your EEM policies.
     
     
   • Usage: java -cp.:./*:$AUTOSYS/lib/*:$AUTOSYS/install/webserver/AEWS/WEB-INF/lib/*" EEMPerfTest as_server_hostname server_port ENCRYPTION_KEY|NONE|DEFAULT|CONFIG InstaceID testuserid EiamAdmin_Password EEM_Hostname JobPrefix "/tmp/AutoSysCheckUp_$AUTOSERV" [chkappl]
     
     • Parameters:
       • LIBPATH: Path to the class files and AutoSys libraries.
       • AppServerhostname: Hostname of the AppServer.
       • server_port: Port of the AppServer.
       • ENCRYPTION_KEY: Encryption key (NONE, DEFAULT, CONFIG, or a custom key).
       • InstanceID: Instance ID.
       • testuserid: Test user ID.
       • EiamAdmin_Password: EIAM admin password.
       • EEM_Hostname: EEM hostname.
       • JobPrefix: Job prefix (use '%' for all jobs).
       • output_dir: Output directory.
       • Optional: chkappl: Perform additional checks for as-appl resource class.
         
         
     • Output:
       • Stdout: Summary of jobs, job types, and machine types.
       • Instance_EEMPerformance.txt: Detailed results.
       • CSV output (if ISCSV=true): Detailed data in CSV format.

Generating Execution Statistics:

• Optional: Use autoaggr to generate monthly statistics for long-term growth analysis.
  
  Example:
  autoaggr -m -J -F "01/01/2020" -c -o /tmp/AutoSysCheckUp_$AUTOSERV/autoaggr_M_$AUTOSERV.csv

Submitting Data:

• After completing the data collection, gather the generated files from the output directory and attach them to your assigned AutoSys Check-Up case.

Additional Information

Note: This is a summary of a more detailed version of the documentation that accompanies the Health Check package that is provided by Broadcom. Always refer to the original documentation for detailed instructions and troubleshooting information.