System and method for extracting and cataloging specified file activity data

Abstract

To provide a system for use in restoring data processing capabilities in the event of an interruption, and a non-transitory computer-readable medium.SOLUTION: A system includes: a user catalog that when executed by a processor configures the system to store indexes of data utilized by the system; a system management facility (SMF) program that when executed by the processor configures the system to create SMF audit records that track the catalog activity as SMF data; and a virtual catalog program that when executed by the processor configures the system to intercept portions of the SMF data over a timeline. The portions corresponding to the creation, deletion and modification of the data files, and the intercepted portions of the SMF data over the timeline are catalogued.SELECTED DRAWING: Figure 3

Description

Technical Field

[0001] This example relates to techniques and processes for extracting and cataloging specific file activity data.

Background Art

[0002] Mainframe computing is a computing platform currently used by large enterprises worldwide. Mainframes often process workloads such as accounting, accounts receivable, general ledger, payroll, and various applications required for specific business needs. These workloads are generally referred to as jobs.

[0003] A mainframe is a complex environment that includes databases and datasets (e.g., files). These data typically exist on a direct access storage device (DASD) or on a disk drive. In addition to DASD, mainframe applications are also provided on one or more tape drives / devices to store portions of this data. One or more tape drives may also serve as the primary repository for important information within a mainframe application. Today, the tape can be either a physical tape to be implemented on read hardware or a virtual tape that is disk-based storage emulating the physical tape.

Summary of the Invention

[0004] One embodiment is a system for use in restoring data processing functions during an interruption event, comprising a processor, a storage device accessible by the processor, and a user catalog program that configures the system to store an index of data used by the system when executed by the processor. The system further includes a system administration function (SMF) program that configures the system to generate SMF audit records that track catalog activity as SMF data when executed by the processor, and a virtual catalog program that configures the system to intercept portions of the SMF data on a timeline when executed by the processor. The portions correspond to the creation, deletion, and modification of data files, and catalog the intercepted portions of the SMF data on the timeline. After an interruption is detected, the processor restores the system's data processing functions based on a combination of the index stored by the user catalog program and the intercepted portions of the SMF data by the virtual catalog program.

[0005] One embodiment provides a non-temporary computer-readable medium for use in restoring data processing functions during an interruption event, comprising a user catalog program incorporated into the medium and configured to store an index of data used by the system when executed by a processor. The non-temporary computer-readable medium further includes a system administration function (SMF) program incorporated into the medium and configured to generate SMF audit records that track the catalog activity as SMF data when executed by the processor, and a virtual catalog program incorporated into the medium and configured to intercept portions of the SMF data on a timeline when executed by the processor. The portions correspond to the creation, deletion, and modification of data files, and catalog the intercepted portions of the SMF data on the timeline. After an interruption is detected, the processor restores the system's data processing functions based on a combination of the index stored by the user catalog program and the intercepted portions of the SMF data by the virtual catalog program.

[0006] Other objectives, advantages, and novel features of the embodiments are, in part, described below, and in part will become clear to those in the same field by examining the following description and accompanying drawings, or by learning through the fabrication and operation of the embodiments. The objectives and advantages of the subject matter of the present invention can be realized and achieved by the methodologies, means, and combinations thereof pointed out in particular in the claims. [Brief explanation of the drawing]

[0007] [Figure 1] Figure 1 is a process flow diagram of an example of the read and write operations to DASD and tape, as well as the generation and recording of system management function data. [Figure 2]Figure 2 is a process flow diagram illustrating an example of the read and write operations to DASD and tape, as well as the selection and extraction of system management function data for cataloging extracted SMF data into a 3D virtual catalog. [Figure 3] Figure 3 shows an example of an interface that illustrates the information stored in the 3D virtual catalog in comparison with the user catalog. [Figure 4] Figure 4 is a simplified functional block diagram of a computer that can be configured as a server and / or mainframe. [Figure 5] Figure 5 is a simplified functional block diagram of a personal computer, other workstation, or terminal device. [Modes for carrying out the invention]

[0008] In the detailed description below, numerous specific details are provided as examples to provide a full understanding of the relevant teachings. However, it will be apparent to those skilled in the art that these teachings can be performed without such details. In other examples, well-known methods, procedures, components, and / or circuits are described at a relatively high level without detail to avoid unnecessarily obscuring aspects of these teachings.

[0009] In one example of a mainframe environment, a job is a collection of programs or job steps that instruct the processor to perform a specific function. When a job is represented as a sequence of Job Control Language (JCL) statements, each job step is defined by an execution statement that references a program and supported by a DD "data definition" statement that represents the dataset to be processed. When a job contains one or more programs or one or more job steps, a single job step may represent a single procedure, program, and / or one or more steps, functions, and / or other processes that include other elements, each performing some form of processing. Thus, a single job step is a single entry in a job, but is not limited to performing only a single step of processing. A job is also sometimes referred to as a batch job because the processor processes a collection of JCLs in a batch. In this mainframe environment, jobs are processed continuously. These jobs periodically reference datasets (e.g., files) as part of their processing. Therefore, at a given point in time, several jobs may open several datasets and process data related to those opened datasets. Furthermore, while one or more jobs can access a dataset, they typically cannot write to it simultaneously. Each individual job can know which of one or more datasets is open at a given time, but the mainframe environment and / or the applications managing the mainframe environment cannot know which datasets are open at that time, and / or which job is processing which dataset. Therefore, when a disaster or some event occurs that disrupts processing by the mainframe environment or various jobs within the mainframe environment, one or more individuals, groups, and / or organizations facing the restoration of the mainframe environment's processing capabilities cannot know which of the one or more datasets was affected by that disaster or other event.Certain mainframe applications do not readily have detailed information about the start and end times of multiple jobs and / or multiple job steps, as well as the open and close times of multiple datasets, making it difficult to detect inconsistencies within and between the various replicated storage systems they use.

[0010] Therefore, it would be useful to have a system that tracks the activity and location of specific data on a timeline (for example, DATASET.ONE was created in volume 1 on date 1 and then deleted from volume 1 on date 2). One example of achieving this is a system that includes a processor, several storage devices accessible by the processor, a System Administration Function (SMF) program that, when executed by the processor, configures the system to extract and store data that catalogs the creation, deletion, and modification of data files as SMF data, and a virtual catalog program. The virtual catalog program, when executed by the processor, configures the system to intercept portions of the SMF data on the timeline that correspond to the activity of a user's specific data file, catalog the selected portions of the SMF data on the timeline, and output the selected portions of the SMF data that correspond to the user's request and identify the creation, deletion, and modification of a user's specific data file on the timeline. The emphasis of the virtual catalog program is on tracking the actions of a dataset (e.g., creation, update, deletion, modification, etc.) and indexing by the dataset name and dataset timestamp. Therefore, the virtual catalog program is keyed by datasets and presents a time-series representation of the requested datasets and how to use them.

[0011] The following embodiments improve the ability to determine which of one or more datasets is currently open and which of one or more jobs is currently processing which dataset. In one example, system records are used to determine which job is currently processing which dataset. For example, a System Management Function (SMF) record is generated each time a job starts or ends. An SMF record is also generated each time a job step within a job finishes. Furthermore, an SMF record is generated each time a Virtual Memory Access Method (VSAM) dataset is cataloged or deleted, or each time a non-VSAM dataset is cataloged or deleted.

[0012] Certain SMF data is intercepted by a virtual catalog program and stored in a virtual catalog. This interception and storage of SMF data according to one embodiment is referred to herein as “3D Virtual Katalog” (registered trademark). In the event of a disaster or other interruption in the mainframe environment, instead of searching and analyzing the entire set of SMF data (e.g., a set of SMF data from different systems in a given environment), the data in the 3D Virtual Catalog is reviewed to find the storage history of the relevant data. This method allows jobs and / or datasets to be positioned so that appropriate actions to remediate processing in the mainframe environment are performed from the appropriate locations.

[0013] As shown in Figure 1, the IBM mainframe, also known as the "z platform," includes a CPU / ZOS 102 that runs the z / OS operating system, which executes jobs / tasks 100 that read from and write to DASD 104 and tape 106, and a user catalog system 108 to describe the data residing across the numerous storage devices typically configured in the system. These user catalogs are elements of the Data Function Product (DFP) and an integral part of the operating system (OS). As part of the system's operation, jobs and tasks create, modify, or delete data on the system, and the catalogs record this activity in the catalog structure for referential consistency. The catalog itself is an indexed file so that data can be quickly searched when it exists in the storage environment. ICF is an abbreviation that describes this function. ICF stands for Integrated Catalog Function. All storage operates on the concept that data (e.g., SYS2.DATASET.ONE, SYS3.DATASET.TWO, and SYS3.DATASET.THREE) is contained in one volume, either tape volume 106 or disk volume 104, also known as direct access storage (DASD). The distinction between tape 106 and DASD 104 is that DASD storage is online to the system, while tape data is typically offline and comes online only when requested by a process or task. A single DASD volume can contain numerous files, also known as datasets. Numerous tasks can simultaneously access datasets on disk on the same volume, as there are typically multiple paths to reach the data on the same DASD volume. Tape, on the other hand, is dedicated to being allocated to a single task at a time. Tape data can stack multiple datasets on a single volume, like DASD. However, only one task can access a single dataset on a single tape volume at a time. Tape data is processed in a linear or sequential manner.The primary related information for any dataset is the name of the dataset, the one or more volumes on which the dataset resides, and, in the case of tape data, the file sequence on the linear tape where the data resides. An example of a catalog entry and tape dataset for DASD is shown below.

[0014] Several key fields in the catalog record include the basic catalog structure (BCS). Each record in the catalog entry consists of some of the following fields: Dataset name: This is the key, and there is only one record for each dataset. Device type: The type of device on which the data resides. For example, DASD device 3390. Volume serial number: Each volume has a 6-digit serial number consisting of letters or numbers. File sequence: Locations related to a dataset, especially sequential tapes. Volume sequence: A location relative to one volume for a dataset that is expanded across multiple volumes. This ensures that the data is read in the correct time series. example

[0015] [Table 1]

[0016] In the above example, four data sets, two DASDs (disks) and two tape data sets are shown. The two disk data sets exist on DASD device 3390 and occupy space on volume PRD001. The third and fourth data sets are tape data sets and exist on a single volume 100000. The file sequence represents the location of related data on the tape volume. The disk volume holds several volume structures indicating where the volume on which the data actually exists is located, and these can be the volume catalog, volume catalog index, and VSAM volume data set. In both cases, the catalog tracks one or more volumes on which the data exists. The volume sequence represents the order of the volumes associated with a particular data set. A single data set may exceed the limit capacity of the volume on which it is written and require more volumes to include the data set. In this case, a series of volumes are grouped together and the volume sequence defines the order in which the volumes should be accessed. Example

[0017]

Table 2

[0018] All catalog activities are captured by the SMF task through the SMF data storage 110. Specifically, the SMF data is generated within the operating system through the SMF task 114 that tracks catalog activities. As a result, the catalog task 112 tracks the location of all data on the system in the user catalog 108, and the SMF task 114 writes SMF audit records to the SMF storage 110 that tracks this catalog activity. More specifically, the catalog service generates an audit log of catalog activity when a data set is created, modified (by adding a volume to the data set), or deleted. Example

[0019]

Table 3

[0020] It is beneficial to have the responsibility of explaining where the dataset exists along the timeline scale. During the process of normal task activities, data is read, generated, and the used data is deleted. In some cases, it is necessary to restore data from a backup created along the timeline, for example, at 16:00 on Tuesday. The conventional user catalog 108 structure is insufficient because it only allows the user through a user terminal (not shown) to find out where the data is currently located. On the other hand, the 3D virtual catalog 202 described below records this activity along the timeline.

[0021] In particular, the VKAT task 204 and the 3D virtual catalog 202, shown in FIG. 2 and implemented with an IBM mainframe, are specific functions (e.g., programs) that run in parallel with the user catalog 108 of the z / OS system and provide the capacity to record dataset activities together with the information held by the user catalog 108 of z / OS. By combining the information held in the user catalog 108 and the information held in the 3D virtual catalog 202, the system can explain the location of the current dataset, as well as the location for the dataset that has been deleted and / or modified to accommodate more volumes. This information is beneficial when there are (a huge number of) volume backups and when the user wants to know when and where the data existed at a specific point in time.

[0022] The catalog environment includes multiple user catalogs 108 to describe all data in the z / OS environment, while the 3D virtual catalog 202 tracks data because it changes from the time the system starts. In operation, the VKAT task, a 3D virtual catalog task executed by the CPU 102, intercepts SMF data related to user catalog activity and puts it into the 3D virtual catalog / maintains the 3D virtual catalog. Key fields within the 3D virtual catalog 202 include the dataset name and an activity timestamp detailing the time of each activity in this dataset. The 3D virtual catalog task can maintain anchor control blocks and can delete old records to keep the system properly and efficiently managed. As a result, the 3D virtual catalog 202 occupies a fragment of the area that becomes the z / OS catalog 108 area itself. The 3D virtual catalog 202 is a keyed and indexed data structure with keys consisting of the name of the dataset itself and the activity timestamp of the monitored dataset. The monitored dataset can be a segment of all datasets or a set of all datasets to meet the system's user requests. The monitoring process scans catalog activity records from SMF110 and may also record activity within the 3D virtual catalog 202 itself. Through a user terminal (not shown), the user can walk through records associated with one or more datasets to find out when and where this data existed at any specific point in time from the system's inception. This collection continues as long as the system is reading SMF activity records, or back to where the user wishes to describe the dataset activity.

[0023] The primary field of the 3D virtual catalog structure includes a portion of the following fields: Dataset name: This is the key, and there is only one record for each dataset. Activity Timestamp: The date and time the catalog activity occurred. Event: An event that was captured and modified the monitored dataset. For example: To generate / to catalog Delete / Uncataloged Change the name Added volume Device type: The type of device on which the data resides. For example, DASD device 3390. Volume serial number: Each volume has a 6-digit serial number consisting of letters or numbers. File sequence: Locations related to a dataset, especially sequential tapes. Volume sequence: A location relative to one volume for a dataset that is expanded across multiple volumes. This ensures that the data is read in the correct time series. Generally, the dataset name and activity timestamp are fields used to generate a unique key for each record in the 3D virtual catalog 202.

[0024] In addition to maintaining records related to the monitored dataset in the virtual 3D catalog, the system also maintains anchor control block records that define the time span the system is recording. Retention parameters define how far back the system should retain virtual 3D catalog information. Periodically, the system performs maintenance to delete old records that have exceeded their retention period. For example, if the system is configured for 7-day retention, during the maintenance phase, records that have exceeded the retention threshold can be deleted, and the anchor control block can be adapted to reflect the current adjusted time value.

[0025] An example of the types of information stored in the 3D virtual catalog 202 compared to the user catalog 108 is shown in Figure 3. It is well known that the user catalog 108 itself provides only limited information about the data. However, the 3D virtual catalog interface display 302 shown in Figure 3 retrieves information from both the user catalog 108 (information not circled) and the 3D virtual catalog 202 (information circled) to provide a complete picture of the monitored dataset. This includes displaying information about when and where (e.g., on which volume) SYS2.DATASET.ONE was created and deleted, when SYS3.DATASET.TWO was renamed, and when and where (e.g., on which volume) SYS3.DATASET.THREE was extended. For illustrative purposes, three specific examples of the 3D virtual catalog 202 in operation are shown below.

[0026] Example 1 1. SYS3.DATASET.SIX existed on the system for one day between April 1st and April 2nd. Suppose someone wants to restore a copy of a dataset when a volume backup occurs. User catalog: Does not contain any records related to this dataset. 3D virtual catalog: Includes the following:

[0027] [Table 4]

[0028] From the information contained in 3D virtual catalog 202, the user learns that the dataset existed on two volumes, PROD01 and PROD02, from 9:00 AM on April 1st to 11:00 PM on April 2nd.

[0029] Example 2 1. One old dataset, TEST.OLD.DSN, was removed from the user catalog on April 15th. User catalog: Does not contain any records related to this dataset. 3D virtual catalog: Includes the following:

[0030] [Table 5]

[0031] From 3D virtual catalog 202, users can see that the dataset in question existed on TEST21 until 7:21 AM on April 15th.

[0032] Example 3 1. Examine the existing old dataset, TEST.OLD.DATASET.TWO. User Catalog:

[0033] [Table 6]

[0034] 3D virtual catalog: Includes:

[0035] [Table 7]

[0036] The current z / OS user catalog 108 shows that the dataset is allocated to two volumes, DEV201 / DEV202, while the 3D virtual catalog 202 adds capacity indicating that the dataset was originally a single-volume dataset and was expanded to two volumes on March 9th at 9am. The 3D virtual catalog 202 adds capacity that the user would otherwise not have known about.

[0037] The collection of tools is provided to list information from the 3D virtual catalog 202. These programs are designed to interact with standard interfaces such as the following: Catalog search interface IDCAMZ List Function Catalog Locating Service

[0038] After providing basic information from the catalog itself via a standard interface, more time-series details will be provided, encompassing fields ingested through SMF collections from the 3D virtual catalog 202. This data extends back to the time range recorded in the anchor control block, from the current time. The 3D virtual catalog 202 offers benefits throughout the dataset's lifecycle, including the ability to identify which volumes the dataset resides in at a given point in time.

[0039] Figures 4 and 5 provide functional block diagrams of computer hardware platforms. Figure 4 shows a network or host computer platform used to implement a typical server and / or mainframe, including, but not limited to, a tape system 402, DASDs 404, user input / output 406, communication ports 408, and a system processor 410 including CPUs, memory, an operating system, applications, batch jobs, SMF, etc. Figure 5 represents a computer with user interface elements used to implement a personal computer or other type of workstation or terminal device, although the computer in Figure 5 can also function as a server if properly programmed. In this example, the computer in Figure 5 includes a monitor 500, keyboard 502, mouse 504, communication ports 506, database 508, user I / O 510, RAM 512, ROM 514, CPU 516, etc. The structure and general operation of the equipment shown in Figures 4 and 5 are considered obvious from the higher-level diagrams.

[0040] For example, it is known that a mainframe has a data communication interface and input / output (I / O) controllers for packet data communication. The input / output controllers communicate with various I / O elements and storage functions. Storage functions include one or more direct access storage devices (DASDs) and / or one or more tape systems. Such storage functions provide storage for data, jobs for managing batch processing, and applications. The mainframe includes communication ports, I / O controllers, and an internal communication bus that provides communication channels between one or more system processors. Each system processor includes one or more central processing units (CPUs), local memory corresponding to each CPU, and shared memory available to any CPU. The operating system (OS) run by the system processors manages various jobs and applications currently running to perform appropriate processing. The OS also provides system management functions (SMFs), open exit points for managing mainframe operations, and various jobs and applications currently running. The hardware elements, operating system, jobs, and applications of such a mainframe are the same as in the past. Of course, mainframe functions may be implemented in a distributed manner across several similar platforms to distribute the processing load, and / or replicated across one or more similar platforms to provide processing surplus. As such, Figure 4 also shows a replication environment. Although the details of the replication environment are not illustrated, such a replication environment typically includes elements similar to those already described in relation to the primary mainframe in Figure 4.

[0041] Similarly, computer-type user terminal devices such as PCs are known to include a data communication interface CPU, main memory, and one or more mass storage devices for storing user data and various executable programs. Various types of user terminal devices also include various user input and user output elements. For example, one computer includes a keyboard, a cursor control / selection device such as a mouse, trackball, or touchpad, and a display output. The hardware elements, operating systems, and programming languages ​​for user terminal devices are also the same as before.

[0042] Accordingly, a method for recording each step time during job execution between the start and end of the mainframe computing environment as described above is embodied in a program. The program features of the technology may typically be considered a “product” or “manufactured item” in the form of executable code and / or associated data carried or implemented on a certain type of machine-readable medium. A “storage” type medium includes any or all of the memory of a computer, processor, associated module, etc., such as various semiconductor memories, tape drives, disk drives, etc., that provide non-temporary storage at any given time for software programming. All or part of the software may be communicated over a global information network (e.g., the Internet®) or other various communication networks. Such communication may enable the deployment of software from one computer or processor to another, for example, from a management server or host computer to a mainframe platform that runs various jobs. Accordingly, other types of media for carrying software elements include optical waves, radio waves, and electromagnetic waves used in physical interfaces between local devices via wired and terrestrial optical networks and various wireless links. The terms "computer" or "machine-readable medium" as used herein refer to any medium used to provide instructions to the processor for execution, unless they are limited to non-temporary, tangible "storage" media.

[0043] Non-volatile storage media include optical or magnetic disks, such as storage devices in any one or more computers, used, for example, to hold datasets and programs for enterprise applications. Volatile storage media include dynamic memory, such as the main memory of such computer platforms. Thus, common forms of computer-readable media include, for example, floppy disks, flexible disks, hard disks, magnetic tapes, any other magnetic media, CD-ROMs, DVDs or DVD-ROMs, any other optical media, punch card paper tapes, any other physical storage media including hole patterns, RAM, PROMs and EPROMs, flash EPROMs, any other memory chips or cartridges, or any other media from which a computer can read program code and / or data. Many of these forms of computer-readable media can be involved in transporting one or more sequences in one or more instructions for execution by a processor.

[0044] It will be understood that the terms and expressions used herein have the ordinary meanings that are given to such terms and expressions in relation to their respective fields of study and research, unless a specific meaning is stated herein. Relative terms such as "first" and "second" may be used solely to distinguish such entities or actions from others, without necessarily requiring or implying an actual relationship or order between them. The terms "comprises," "comprising," "includes," and "including," and other variations thereof, are intended to cover non-exclusive inclusion, such that a process, method, item, or apparatus containing a list of elements may include not only those elements but also other elements not explicitly listed or inherent in the above process, method, item, or apparatus. The elements following "a" and "an" do not, unless further constraints, exclude the existence of additional inherent elements in a process, method, item, or apparatus consisting of inherent elements.

[0045] Unless otherwise specified, any and all measurements, values, ratings, locations, sizes, dimensions, and other specifications described in this specification, including those enumerated in the patent claims, are approximate and not exact. They are intended to have a reasonable range that is consistent with the function to which they relate and with what is customary in the art to which they belong.

[0046] The above describes what is considered to be the best mode and / or other embodiment, and it is understood therein that various modifications may be made, that the subject matter disclosed herein may be carried out in various forms and embodiments, and that they may be applied in many uses (only some of which are described herein). The attached claims are intended to claim any and all modifications and variations that fall within the true scope of the concept.

Claims

1. 1. A system for use in restoring data processing functionality during an interruption event, comprising: A processor; a storage device accessible by said processor; a user catalog program which, when executed by said processor, configures said system to store an index of data utilized by said system; a system management facility (SMF) program that, when executed by the processor, configures the system to generate SMF audit records that track user catalog activity as SMF data; a virtual catalog program, when executed by the processor, a virtual catalog program that configures the system to intercept portions of the SMF data on a timeline that correspond to the creation, deletion and modification of data files, and to catalog the intercepted portions of the SMF data on the timeline in a virtual catalog; The data utilized by the system includes a data set and additional event data related to use of the data set after an interruption is detected; the processor recovering data processing functionality of the system based on a combination of the stored index by the user catalog program and the intercepted portion of SMF data by the virtual catalog program; A catalog activity record for each of the user catalog activities describing the location of the deleted and / or modified datasets prior to the interruption is not present in each of the stored indexes, but information regarding the deleted and / or modified datasets is present in the virtual catalog, the system.

2. 2. The system of claim 1, wherein the virtual catalog program, when executed by the processor, further configures the system to associate a system user with the intercepted portion of the SMF data.

3. 2. The system of claim 1, wherein the virtual catalog program, when executed by the processor, further configures the system to include a timestamp with each intercepted portion of the SMF data.

4. 2. The system of claim 1, wherein the virtual catalog program, when executed by the processor, further configures the system to identify a storage device that stores each intercepted portion of the SMF data.

5. 2. The system of claim 1, wherein after an interruption is detected, the virtual catalog program, when executed by the processor, further configures the system to display a combination of the stored index by the user catalog program and the intercepted portion of SMF data by the virtual catalog program in chronological order.

6. 1. A non-transitory computer readable medium for use in restoring data processing functionality during an interruption event, comprising: a user catalog program embodied on said medium, said user catalog program being configured, when executed by a processor, to configure said system to store an index of data utilized by the system; a system management facility (SMF) program embodied on said medium that, when executed by said processor, configures said system to generate SMF audit records that track catalog activity as SMF data; a virtual catalog program embodied on said medium, said virtual catalog program being, when executed by said processor, Intercepting portions of the SMF data on a timeline that correspond to the creation, deletion and modification of data files; and and a virtual catalog program that configures the system to catalog the intercepted portions of the SMF data on the timeline in a virtual catalog; The data utilized by the system includes a data set and additional event data related to use of the data set after an interruption is detected; the processor recovering data processing functionality of the system based on a combination of the stored index by the user catalog program and the intercepted portion of SMF data by the virtual catalog program; A non-transitory computer-readable medium, wherein catalog activity records for each of the user catalog activities describing the locations of the deleted and / or modified datasets prior to the interruption are not present in each of the stored indexes, but information regarding the deleted and / or modified datasets is present in the virtual catalog.

7. 7. The non-transitory computer readable medium of claim 6, wherein the virtual catalog program, when executed by the processor, further configures the system to associate a system user with the intercepted portion of the SMF data.

8. 7. The non-transitory computer-readable medium of claim 6, wherein the virtual catalog program, when executed by the processor, further configures the system to include a timestamp with each intercepted portion of the SMF data.

9. 7. The non-transitory computer-readable medium of claim 6, wherein the virtual catalog program, when executed by the processor, further configures the system to identify a storage device that stores each intercepted portion of the SMF data.

10. 7. The non-transitory computer-readable medium of claim 6, wherein after an interruption is detected, the virtual catalog program, when executed by the processor, further configures the system to display a combination of the stored index by the user catalog program and the intercepted portion of SMF data by the virtual catalog program in chronological order.

11. The system of claim 1, wherein repairing the data processing function of the system includes configuring each of the catalog activity records to be repaired within each of the stored indexes of the stored indexes.

12. The system of claim 1, wherein the SMF program does not identify which data used by the system is open at any given time.

13. The system of claim 1, wherein the SMF program does not identify which job is processing which data utilized by the system at any given time.

14. The system of claim 1, wherein the SMF data only finds where currently used data is located.

15. A method for restoring data processing functionality in the event of a computer system interruption, comprising: storing an index of data utilized by said computer system using a user catalog program; Generates SMF audit records that track user catalog activity as SMF data, intercepting portions of said SMF data on a timeline corresponding to the creation, deletion and modification of data files; cataloging the intercepted portion of the SMF data on the timeline in a virtual catalog; after an interruption is detected, restoring data processing functionality of the computer system based on a combination of the stored index and the intercepted portion of SMF data; After the interruption is detected, a user catalog activity record for each of the user catalog activities is not present in each of the stored indexes, but the non-existent user catalog activities are associated with a creation, deletion, or modification of a data file, and corresponding information regarding the creation, deletion, or modification is present in the virtual catalog; the respective user catalog activity records for the user catalog activity describing the location of deleted and / or modified data sets were present in the respective stored indexes at a time prior to the occurrence of a volume backup; The method, wherein restoring the data processing functionality of the computer system includes configuring each of the user catalog activity records to exist in the respective stored index of the stored indexes as each of the user catalog activity records existed at the previous point in time.

Images