Jobs in dSeries / DE go in READY state when application is put on hold.

Products

• CA Workload Automation DE

Issue/Introduction

Jobs stay in READY state when an application starts and is put on hold.

Environment

ESP dSeries: 12.x

Cause

When job(s) start and go to READY state, and if the application is put on HOLD the same time, then jobs initial state will not change.  The job will continue to stay in READY, because it has already been sent to the agent.  Any subsequent change will be ignored, because the application is on HOLD and no changes can take place at job level.

20XXXXXX 12:34:00.000 [internal:messages] [INFO] DM.Appl.MY_APP.1: [20XX-XX-XX_12:34:00.000] Persisting msg targeted for ourself. AFM: 20XXXXXX 10020217+0500 CADE CADE /MAIN/MY_APP.1/JOB1234 State READY Conditions() StatusQ() Userid(user.USER1)

20XXXXXX 12:34:00.001 [internal:messages] [INFO] DM.Appl.MY_APP.1: [2025-02-05_10:02:05.708] Adding message directly onto our queue. AFM: 20XXXXXX 10020538+0500 CADE CADE /MAIN/MY_APP.1/JOB1234 State APPLHOLD Conditions() Userid(user.USER1)

Resolution

If an application needs to be on HOLD, then make sure to either force complete jobs that have already started or wait from them to complete.  Users may also hold the successor jobs instead of putting the whole application on APPLHOLD.