What is the internal process flow when a request is made to display a job's standard output (std_out) or standard error (std_err) log file?
Workload Automation AE (AutoSys Edition) 24.x
When a user requests job logs through the Workload Control Center (WCC) QuickView/Monitor tab, the WebUI, or via the command-line utility (autosyslog -J <job_name> -tO or -tE), the system executes the following architectural process flow:
Client Request: The client interface (WCC, WebUI, or the autosyslog binary) contacts the AutoSys Application Server.
Database Lookup: The Application Server queries the AutoSys database (ujo_job_runs and ujo_extended_jobrun_info tables) to determine:
The targeted execution machine (run_machine) where that specific job run occurred.
The full path and filename specified for the standard output or standard error file.
Agent Contact: The Application Server connects directly to the Workload Automation System Agent listening on that remote host.
Log Reading & Transfer: The Agent reads the requested file from its local file system and streams the data back to the Application Server using Application Framework Messages (AFM).
Display: The Application Server transmits the received text blocks back to the initiating client (WCC or command line) for display.
Additional Information * For tracking job run history and related path fields, review the following database structures:
ujo_job_runs
ujo_extended_jobrun_info