AutoSys Jobs stuck in STARTING state on Mainframe (UUJMA) Machine

Products

• Autosys Workload Automation

Issue/Introduction

AutoSys jobs targeting a mainframe machine (Type: u / UUJMA) remain in a STARTING status indefinitely.

• The Scheduler and Application Server are online and functional.
• The target machine is reported as Online in autorep -m output.
• Manual attempts to restart or clear the jobs do not move them to a RUNNING or SUCCESS state immediately.

The job life cycle indicates that the AutoSys Scheduler successfully identified the job starting conditions and transmitted the request to the mainframe interface, but never received the execution acknowledgement required to transition to RUNNING.

 

Log Observations

In the event_demon logs, the following entries confirm a successful hand-off from AutoSys to the Cross Platform Interface:

[08/31/2026 10:33:40] CAUAJM_I_40245 EVENT: CHANGE_STATUS STATUS: STARTING JOB: test-job MACHINE: Test
[08/31/2026 10:33:40] CAUAJM_I_10073 AutoSys --> Cross Platform Interface: machine=Test job_name=test-job

Environment

• Product: AutoSys Workload Automation AE
• Machine Type: u (UUJMA - Unicenter Universal Job Management Agent)

Resolution

• CAUAJM_I_40245 confirms the event was processed by the scheduler.
• CAUAJM_I_10073 confirms the command was sent to the Cross Platform Interface (UUJMA).
• The absence of a subsequent RUNNING status event indicates the mainframe side failed to acknowledge the start of the job.
• Mainframe Investigation: Engaged the Mainframe Operations or Systems team to check the status of the UUJMA task and the internal job queues on the mainframe side. Refresh/restart of appopriate component to resolve this

Additional Information

To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on the respective region.