IP Library › Granted Patent US 12,625,734
Granted Patent B2
US 12,625,734 · App. 17/568,804 · Granted May 12, 2026

High availability scheduler event tracking

Inventors: Xin Xin Dong (Beijing, CN); Ming Qiao Shang Guan (Beijing, CN); Mai Zeng (Beijing, CN); Wei Song (Beijing, CN)
Assignee: International Business Machines Corporation
G06F9/5038G06F9/5016G06F9/5044G06F2209/508
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,625,734
App. No.
17/568,804
Granted
May 12, 2026
Kind
B2
Abstract

Aspects include monitoring, by a controller, an operational status of a tracker system that is configured to track and record a current status of a job being executed and to report completion of the job to the controller. The recording includes storing two copies of the current status, where a first copy is stored in a shared memory location accessible by the controller. In response to determining, based on the monitoring, that the tracker system is operational, waiting to receive a job completion message for the job from the tracker system and performing a job completion action based on receiving the job completion message. In response to determining that the tracker system is not operational, obtaining the current status of the job from the shared memory location and performing the job completion action based on the current status indicating that the job has completed.

Claims (33)

1 . A method comprising:

monitoring, by a controller, an operational status of a job tracking module that is configured to track and record a current status of a job being executed and to report completion of the job to the controller, the recording comprising storing two copies of the current status, a first copy stored in a coupling facility (CF) list structure that is globally addressable by a plurality of logical partitions (LPARs) of a sysplex and accessible by the controller, and a second copy stored in an extendable common service area (ECSA) queue resident in a same LPAR of the plurality of LPARs as the job tracking module and not directly accessible by the controller;

in response to determining, based on the monitoring, that the job tracking module is operational, waiting to receive a job completion message for the job from the job tracking module and performing a job completion action based on receiving the job completion message, wherein the job completion action is selected from a plurality of job completion actions based on how the job completed, wherein how the job completed is one of in error, canceled, or without error;

in response to determining, based on the monitoring, that the job tracking module is not operational:

obtaining the current status of the job from the CF list structure; and

performing the job completion action based on the current status indicating that the job has completed, wherein performing the job completion action enables the controller to continue execution of other jobs or actions that depend on the job being executed, thereby alleviating processing delays and improving response times responsive to the job tracking module not being operational; and

in response to determining that the job tracking module becomes available after not being operational for a period of time, resynchronizing events between the ECSA queue, the CF list structure, and an event dataset.

2 . The method of claim 1 , wherein current status records corresponding to the job are removed from the CF list structure upon completion of the job.

3 . The method of claim 1 , wherein it is determined that the job tracking module is not operational in response to the controller not being able to communicate with the job tracking module.

4 . The method of claim 1 , wherein the job completion action comprises initiating execution of a second job.

5 . The method of claim 1 , wherein the current status of the job is obtained from one or both of a system management facility (SMF) record and a job entry system (JES) record.

6 . A system comprising:

one or more processors for executing computer-readable instructions, the computer-readable instructions controlling the one or more processors to perform operations comprising:

monitoring, by a controller, an operational status of a job tracking module that is configured to track and record a current status of a job being executed and to report completion of the job to the controller, the recording comprising storing two copies of the current status, a first copy stored in a coupling facility (CF) list structure that is globally addressable by a plurality of logical partitions (LPARs) of a sysplex and accessible by the controller, and a second copy stored in an extendable common service area (ECSA) queue resident in a same LPAR of the plurality of LPARs as the job tracking module and not directly accessible by the controller;

in response to determining, based on the monitoring, that the job tracking module is operational, waiting to receive a job completion message for the job from the job tracking module and performing a job completion action based on receiving the job completion message, wherein the job completion action is selected from a plurality of job completion actions based on how the job completed, wherein how the job completed is one of in error, canceled, or without error;

in response to determining, based on the monitoring, that the job tracking module is not operational:

obtaining the current status of the job from the CF list structure; and

performing the job completion action based on the current status indicating that the job has completed, wherein performing the job completion action enables the controller to continue execution of other jobs or actions that depend on the job being executed, thereby alleviating processing delays and improving response times responsive to the job tracking module not being operational; and

in response to determining that the job tracking module becomes available after not being operational for a period of time, resynchronizing events between the ECSA queue, the CF list structure, and an event dataset.

7 . The system of claim 6 , wherein current status records corresponding to the job are removed from the CF list structure upon completion of the job.

8 . The system of claim 6 , wherein it is determined that the job tracking module is not operational in response to the controller not being able to communicate with the job tracking module.

9 . The system of claim 6 , wherein the job completion action comprises initiating execution of a second job.

10 . The system of claim 6 , wherein the current status of the job is obtained from one or both of a system management facility (SMF) record and a job entry system (JES) record.

11 . A computer program product comprising a computer-readable storage medium having program instructions embodied therewith, the program instructions executable by one or more processors to cause the one or more processors to perform operations comprising:

monitoring, by a controller, an operational status of a job tracking module that is configured to track and record a current status of a job being executed and to report completion of the job to the controller, the recording comprising storing two copies of the current status, a first copy stored in a coupling facility (CF) list structure that is globally addressable by a plurality of logical partitions (LPARs) of a sysplex and accessible by the controller, and a second copy stored in an extendable common service area (ECSA) queue resident in a same LPAR of the plurality of LPARs as the job tracking module and not directly accessible by the controller;

in response to determining, based on the monitoring, that the job tracking module is operational, waiting to receive a job completion message for the job from the job tracking module and performing a job completion action based on receiving the job completion message, wherein the job completion action is selected from a plurality of job completion actions based on how the job completed, wherein how the job completed is one of in error, canceled, or without error;

in response to determining, based on the monitoring, that the job tracking module is not operational:

obtaining the current status of the job from the CF list structure; and

performing the job completion action based on the current status indicating that the job has completed, wherein performing the job completion action enables the controller to continue execution of other jobs or actions that depend on the job being executed, thereby alleviating processing delays and improving response times responsive to the job tracking module not being operational; and

in response to determining that the job tracking module becomes available after not being operational for a period of time, resynchronizing events between the ECSA queue, the CF list structure, and an event dataset.

12 . The computer program product of claim 11 , wherein current status records corresponding to the job are removed from the CF list structure upon completion of the job.

13 . The computer program product of claim 11 , wherein it is determined that the job tracking module is not operational in response to the controller not being able to communicate with the job tracking module.

14 . The computer program product of claim 11 , wherein the job completion action comprises initiating execution of a second job.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 5, 2022
From: DONG, XIN XIN; SHANG GUAN, MING QIAO; ZENG, MAI; SONG, WEI
To: INTERNATIONAL BUSINESS MACHINES CORPORATION
Reel/Frame 058553/0072 →
Continuity (1)
Related Publication 20230214265A1 · Jul 6, 2023
References Cited (25)
US 6108689A · Fagen · 2000 [cited by examiner]
US 10140068B1 · Holdman · 2018 [cited by examiner]
US 10452531B1 · Jung · 2019 [cited by examiner]
US 20100169895A1 · Dice · 2010 [cited by examiner]
US 20100287565A1 · Edmeades · 2010 [cited by examiner]
US 20130185586A1 · Vachharajani et al. · 2013 [cited by applicant]
US 20130332507A1 · Du · 2013 [cited by examiner]
US 20140092806A1 · Kidron · 2014 [cited by examiner]
US 20140130054A1 · Molkov · 2014 [cited by examiner]
US 20140325256A1 · Lambert · 2014 [cited by examiner]
US 20150100547A1 · Holmes-Higgin · 2015 [cited by examiner]
US 20170242673A1 · Catalano · 2017 [cited by examiner]
US 20180095855A1 · Sanakkayala · 2018 [cited by examiner]
US 20200045108A1 · Elko et al. · 2020 [cited by applicant]
US 20220188147A1 · Nudelman · 2022 [cited by examiner]
JP 2000347884A · 2000 [cited by applicant]
JP 2007094821A · 2007 [cited by applicant]
WO WO2010008984A2 · 2010 [cited by examiner]
“Configuring Sysplex for high availability”, Published Date: Sep. 9, 2021, 3 pages. [cited by applicant]
David Raften et al., “Parallel Sysplex Availability Checklist”, Published Date: Jun. 2020, 69 pages. [cited by applicant]
IBM, “Achieving the Highest Levels of Parallel Sysplex Availability”, Published Date: Dec. 2004, 294 pages. [cited by applicant]
IBM, “High Availability for SAP on zSeries Using Autonomic Computing Technologies”, Published Date: Aug. 2004, 356 pages. [cited by applicant]
Robert Vaupel, “High Availability and Scalability of Mainframe Environments using System z and z/OS as example”, Published Date: Jan. 2013, 346 pages. [cited by applicant]
Peter Mell et al., “The NIST Definition of Cloud Computing”, NIST, Special Publication 800-145, Sep. 2011, 7 pages. [cited by applicant]
Japan Patent Office, “Notice of Reasons for Refusal” Feb. 17, 2026, 04 Pages, JP Application No. 2022-204349. [cited by applicant]