An application may be placed in APPLHOLD status using APPLJOB ALL with HOLD option, or HOLD option on APPL, or HA from CSF.
The hold-count (HC) field of a job is modified by the predecessor/successor statements (e.g. AFTER and RELEASE).
Is there any other “hold” status than above?
Are there alternate approaches to controlling workflow that is scheduled (i.e. other than HOLD)? Can a triggered event that has an EICLASS set to MPL(0) execute?
Release : 11.4 and above
Component : CA ESP WORKLOAD AUTOMATION
An application may be placed in APPLHOLD status using APPLJOB ALL with HOLD option, or HOLD option on APPL, or HA from CSF.
Q: Does it prevent the APPL from taking any further action (e.g. submitting additional jobs)?The hold-count (HC) field of a job is modified by the predecessor/successor statements (e.g. AFTER and RELEASE).
Q: Can any other commands modify this field? Q: Is there any other “hold” status than above?
A: Yes. For example, you can use HOLD option for resource, so the resource won't be released until the JOB completes successfully.
Q: Are there alternate approaches to controlling workflow that is scheduled (i.e. other than HOLD)?
A: "OPER QUIESCE" and "OPER CLASS - HOLD" can be used to hold all workloads, and "OPER ESPCOM DEST(agent_name) QUIESCE" can be used to hold sending requests to one agent.
Q: Can a triggered event that has an EICLASS set to MPL(0) execute?
A: If the event required EICLASS with MPL(0) is set, then it will execute on default EICLASS(0); and if EICLASS(0) also has MPL(0), then the event won't execute.