Abstract: A method for preventing data overlays in a data storage system is disclosed. In one embodiment, such a method detects a write operation directed to a storage area of a data storage system. The write operation includes one or more of a format write operation and a full-track write operation. Upon detecting the write operation, the method determines a data set that is associated with the storage area. The method analyzes metadata associated with the data set to determine whether the storage area contains valid data. In the event the storage area contains valid data, the method performs a data protection operation that prevents execution of the write operation and/or logs details of the write operation. A corresponding system and computer program product are also disclosed.

Abstract: A method for tracking actions performed in association with a data set includes identifying multiple sources of historical information describing actions performed on the data set. The method periodically gathers this historical information from the multiple sources and compiles the historical information in a centralized repository. In certain embodiments, the method stores the historical information in the form of individual records associated with the data set. In the event any actions performed on the data set are the result of policies established for the data set, the method determines the policies associated with the actions where possible. The method includes these policies with the historical information in the centralized repository. A corresponding system and computer program product are also disclosed.

Abstract: A method for providing different message information to users based on authorization level is disclosed. In one embodiment, such a method includes detecting an event, such as an error or abnormal termination, in a hardware or software product. The method generates a message in association with the event and determines an authorization level of a user intended to receive the message. In the event the user is associated with a first authorization level, the method includes first content in the message. In the event the user is associated with a second authorization level, the method includes second content in the message. The second content may be more comprehensive than the first content. A corresponding system and computer program product are also disclosed.

Abstract: A method for preventing data overlays in a data storage system is disclosed. In one embodiment, such a method detects a write operation directed to a storage area of a data storage system. The write operation includes one or more of a format write operation and a full-track write operation. Upon detecting the write operation, the method determines a data set that is associated with the storage area. The method analyzes metadata associated with the data set to determine whether the storage area contains valid data. In the event the storage area contains valid data, the method performs a data protection operation that prevents execution of the write operation and/or logs details of the write operation. A corresponding system and computer program product are also disclosed.

Abstract: A method for allocating storage space in a volume to a new data set is disclosed. In one embodiment, such a method includes maintaining, for a volume, a record of available storage elements. The method further receives an allocation request to allocate available storage elements in the volume to accommodate a new data set. The method allocates available storage elements in the volume to the new data set to fulfill the allocation request. In doing so, the method favors storage elements that have been available for a longer amount of time over storage elements that have been available for a shorter amount of time. A corresponding system and computer program product are also disclosed.

Abstract: A new layer for runtime detection of vendor hooks, with respect to a program module, includes mapping of branching instructions and their respective targets. When the program module is compiled, branch instructions are mapped and recorded to generate one or more branch maps. A branch map includes target program module addresses (or associated respective placeholders) and respective instruction offsets. At runtime, placeholders are replaced with respective target program module addresses. At runtime, actual branching information is compared to branching information included in the branch map. If a discrepancy is detected between runtime branching information and the corresponding branching information recorded in the branch map, a responsive action is triggered.

Abstract: A method for allocating storage space in a volume to a new data set is disclosed. In one embodiment, such a method includes maintaining, for a volume, a record of available storage elements. The method further receives an allocation request to allocate available storage elements in the volume to accommodate a new data set. The method allocates available storage elements in the volume to the new data set to fulfill the allocation request. In doing so, the method favors storage elements that have been available for a longer amount of time over storage elements that have been available for a shorter amount of time. A corresponding system and computer program product are also disclosed.

Abstract: A method for preserving and recovering a deleted data set is disclosed. In one embodiment, such a method includes, upon deleting a data set from a volume, gathering metadata associated with the data set. This metadata is saved in a volume table of contents (VTOC) associated with the volume. Upon writing over a storage area occupied by the data set on the volume, the method deletes the metadata from the VTOC. Upon receiving an instruction to restore the data set, the method determines if the metadata is present in the VTOC. If the metadata is present in the VTOC, the method uses the metadata to rebuild control information associated with the data set and thereby restore the data set to the volume. A corresponding system and computer program product are also disclosed.

Abstract: A method for providing different message information to users based on authorization level is disclosed. In one embodiment, such a method includes detecting an event, such as an error or abnormal termination, in a hardware or software product. The method generates a message in association with the event and determines an authorization level of a user intended to receive the message. In the event the user is associated with a first authorization level, the method includes first content in the message. In the event the user is associated with a second authorization level, the method includes second content in the message. The second content may be more comprehensive than the first content. A corresponding system and computer program product are also disclosed.

Abstract: A new layer for runtime detection of vendor hooks, with respect to a program module, includes mapping of branching instructions and their respective targets. When the program module is compiled, branch instructions are mapped and recorded to generate one or more branch maps. A branch map includes target program module addresses (or associated respective placeholders) and respective instruction offsets. At runtime, placeholders are replaced with respective target program module addresses. At runtime, actual branching information is compared to branching information included in the branch map. If a discrepancy is detected between runtime branching information and the corresponding branching information recorded in the branch map, a responsive action is triggered.

Abstract: A method for verifying that software modules have a consistent code level is disclosed. In one embodiment, such a method includes updating a software product comprising a plurality of software modules. Upon updating the software product, the method updates a code-level table that documents an expected code level for each of the software modules. When a software module is called, the method determines an actual code level of the software module and compares the actual code level with the expected code level indicated in the code-level table. If the actual code level matches the expected code level, the method allows execution of the software module. If the actual code level does not match the expected code level, the method terminates execution of the software module. A corresponding system and computer program product are also disclosed.

Abstract: A method for tracking actions performed in association with a data set includes identifying multiple sources of historical information describing actions performed on the data set. The method periodically gathers this historical information from the multiple sources and compiles the historical information in a centralized repository. In certain embodiments, the method stores the historical information in the form of individual records associated with the data set. In the event any actions performed on the data set are the result of policies established for the data set, the method determines the policies associated with the actions where possible. The method includes these policies with the historical information in the centralized repository. A corresponding system and computer program product are also disclosed.