US 11,740,888 B2
Method and system for verification of patch installation
Rob L Gantz, III, Plain City, OH (US); Brian S Elliott, Worthington, OH (US); Bob Reid, Columbus, OH (US); Kiran Kumar Bodala, Chittoor (IN); Subhashini Gajendran, Chennai (IN); Anubhav Gupta, Bangalore (IN); and Sangeetha Varanavasi, Perundurai (IN)
Assigned to JPMORGAN CHASE BANK, N.A., New York, NY (US)
Filed by JPMorgan Chase Bank, N.A., New York, NY (US)
Filed on Jul. 16, 2021, as Appl. No. 17/305,884.
Claims priority of provisional application 63/052,656, filed on Jul. 16, 2020.
Prior Publication US 2022/0019421 A1, Jan. 20, 2022
Int. Cl. G06F 8/65 (2018.01); G06F 9/451 (2018.01)
CPC G06F 8/65 (2013.01) [G06F 9/451 (2018.02)] 20 Claims
OG exemplary drawing
 
1. A method for maintaining software within a mainframe computing apparatus, the method being implemented by at least one processor, the method comprising:
receiving, by the at least one processor, at least one software module;
determining, by the at least one processor based on at least one risk attribute assigned to the received at least one software module, a criticality for the at least one software module;
deploying, by the at least one processor, the received at least one software module to at least one destination within the mainframe computing apparatus based on the determined criticality;
scanning, by the at least one processor, at least one mainframe logical partition within which the at least one software module is intended to be installed;
determining, by the at least one processor, whether the at least one software module has been installed based on a result of the scanning;
retrieving, by the at least one processor, based on the determined criticality, an operating level agreement that is applicable to the at least one software module;
determining, by the at least one processor, based on the retrieved operating level agreement, for each respective one of at least one mainframe logical partition within which the at least one software module is intended to be installed, whether an installation of the at least one software module has occurred before a corresponding target installation day of a specified month that is based on the operating level agreement; and
based on whether the installation of the at least one software module has occurred before a corresponding target installation day of a specified month that is based on the operating level agreement, determining whether the operating level agreement has been violated.