Abstract: Just-in-time dynamic instrumentation of a running software system may be achieved by registering one or more instrumentation probe handlers in an inactive state wherein the probe handlers reside in a memory space associated with the software system but are not instrumented into the software system. The probe handlers may each have one or more probe handler tags representing categories to which the probe handlers have been assigned. Tag query requests are periodically received and processed in order to provide information to a caller about registered probe handlers associated with a probe handler tag specified in the tag query request. A probe handler activation request can be made by specifying a probe handler or a probe handler tag. The request can be processed by placing the specified probe handler, or probe handlers associated with the tag, in an active state. The software system thus becomes dynamically instrumented to execute the probe handler(s) as part of the software system's execution flow.

Abstract: Just-in-time dynamic instrumentation of a running software system may be achieved by registering one or more instrumentation probe handlers in an inactive state wherein the probe handlers reside in a memory space associated with the software system but are not instrumented into the software system. The probe handlers may each have one or more probe handler tags representing categories to which the probe handlers have been assigned. Tag query requests are periodically received and processed in order to provide information to a caller about registered probe handlers associated with a probe handler tag specified in the tag query request. A probe handler activation request can be made by specifying a probe handler or a probe handler tag. The request can be processed by placing the specified probe handler, or probe handlers associated with the tag, in an active state. The software system thus becomes dynamically instrumented to execute the probe handler(s) as part of the software system's execution flow.

Abstract: A method and system for maintaining integrity of metadata associated with a migrated file. Following migration of data from a source filesystem to a destination filesystem, a tool is automatically invoked to detect if there are any differences in metadata associated with the files and/or folders at each location. Each select field of the metadata at the source filesystem is reviewed to ensure that it matches with the equivalent field at the destination filesystem. In the event at least one of the reviewed metadata fields does not match, an error is generated and forwarded to an operator.

Abstract: A method and system for maintaining integrity of metadata associated with a migrated file. Following migration of data from a source filesystem to a destination filesystem, a tool is automatically invoked to detect if there are any differences in metadata associated with the files and/or folders at each location. Each select field of the metadata at the source filesystem is reviewed to ensure that it matches with the equivalent field at the destination filesystem. In the event at least one of the reviewed metadata fields does not match, an error is generated and forwarded to an operator.