Watch the critical queues

The CA 7 scheduler maintains several queues that give a quick health snapshot.

  • READY - jobs waiting for a start time or a resource. A growing READY count often means a downstream dependency has not been satisfied.
  • ACTIVE - jobs currently running. Look for unusually long runtimes compared with the job's historic average.
  • WAIT - jobs paused for a condition such as a missing file, a locked dataset or a manual operator hold.
  • HOLD - jobs that have been placed on hold by an operator. Verify that holds are intentional and have an expiry.

A nightly dashboard that shows the count and age of jobs in each queue lets you spot a backlog before it turns into a missed SLA.

Track job states and abends

CA 7 reports each job's state in the console and in SMF. The most useful states to watch are:

  1. RUNNING - normal execution. Compare the elapsed time with the job's typical duration.
  2. ABEND - abnormal termination. The abend code (ABEND=U9999) tells you whether the job can be restarted automatically.
  3. COMPLETED - successful finish. Verify that the job's output datasets are present.
  4. RESTARTED - a job that has been re-queued after an abend. Ensure the restart does not push the batch past its deadline.

When an abend occurs, read the abend code first. Some codes indicate a transient condition (for example, a file not found) that can be resolved quickly, while others (such as a program error) may require a code change.

Monitor required resources and prerequisites

Many batch delays are caused by missing prerequisites. Keep an eye on:

  • File-availability checks - jobs that wait for a file to appear often sit in the WAIT queue. Use a script to alert when the file has not arrived within a defined window.
  • Dataset locks - a locked VSAM or DB2 dataset can halt an entire job stream. The LOCK message in the console will show the holder and the waiting job.
  • External system status - if a job depends on a CICS region or an IMS transaction, confirm that the subsystem is up before the job starts.

Setting up simple alerts for these conditions reduces the time spent hunting for the root cause.

Use early-warning predictions

Instead of waiting for a job to finish late, predict the batch end time based on the current progress. The prediction logic needs:

  • The scheduled start time of the batch.
  • The elapsed time of each ACTIVE job.
  • Historic runtimes for each job in the batch.
  • Any pending WAIT or HOLD jobs and their age.

When the projected finish time crosses the SLA threshold, raise an alert in plain words, for example: "Batch XYZ likely to breach SLA by 02:15 - job ABC still waiting for file." This gives operators a clear call to action.

Take action from the same screen

A unified console that combines the queue view, job details and the ability to send a WTOR reply or a restart card saves time. Operators can:

  • Acknowledge a WAIT condition by confirming that the required file is now present.
  • Issue a restart card (RESTART JOB=ABC) directly from the dashboard.
  • Create a ticket in the integrated ticket tool so that the incident is recorded.

Having these actions on one screen reduces the number of steps between detection and remediation.

How Meridian helps

Meridian shows the CA 7 queues, job states, abends and resource alerts for every LPAR on one screen. It says in plain words, hours before the deadline, whether each named batch will meet its SLA, and names the job that decides it. Operators confirm WTOR replies and restarts from cards, and every action is recorded with its evidence. Meridian runs inside your network, and your data never leaves it. See how the prediction works or the article on CA 7 job restarts and batch SLAs.

---

By focusing on the READY, ACTIVE, WAIT and HOLD queues, watching job states and abends, monitoring prerequisites and using early-warning predictions, a CA 7 shop can see a late batch hours before it breaches its SLA. The right console ties the information together and provides the actions needed to keep the night running smoothly.