Abstract: A method and system for displaying database record organization characteristics of IMS databases. In one embodiment, the method involves receiving information associated with a plurality of database records from an IMS database (e.g., information associated with ranges of database records). The database information may comprise information concerning database record organization characteristics. A working storage array may be built to consolidate the information associated with the plurality of database records. A plurality of view envelopes may be constructed. The plurality of view envelopes, along with a legend, may be graphically displayed on a display. User input may be received to request “inspection”, “identification”, “inspection/identification”, or “detailed inspection” of a selected view envelope. Various methods may be used to “mark”, “unmark”, and “submit” at least one DBR to the mainframe computer system for reorganization.

Abstract: Methods, devices and systems which facilitate the conversion of database objects from one schema version (e.g., an earlier version) to another schema version (e.g., a newer version) without requiring the objects be unloaded and reloaded are described. In general, data object conversion applies to both table space objects and index space objects. The described transformation techniques may be used to convert any object whose schema changes occur at the page-level.

Abstract: A system architecture and a method for managing using a cellular architecture to allow multi-tier management of events such as the managing of the actual impact or the potential impact of IT infrastructure situations on business services. A preferred embodiment includes a high availability management backbone to frame monitoring operations using a cross-domain model where IT component events are abstracted into IT Aggregate events. By combining IT Aggregate events with transaction events, an operational representation of the business services is possible. Another feature is the ability to connect this information to dependent business user groups such as internal end-users or external customers for direct impact measurement.

Abstract: Techniques to update/change a database without incurring a user outage include receiving a user-specified change command which is then evaluated to determine which portion(s) of the target database will change as a result of the command. Shadow copies of those portions are then created and updated in accordance with the change command. The change command is next applied against the target database and any portion(s) placed in a restricted status because of this action are reset to an un-restricted state. The updated shadow portion(s) are then swapped for the corresponding portion(s) of the target database.

Abstract: Methods and systems for providing access to spaces in a database during a recovery process affecting the database. Spaces in the database that are affected by the recovery process are identified and I/O requests sent to a media manager associated with the database are intercepted. If the I/O request is for a read operation to a space affected by the recovery process and the corresponding page has been recovered, the data in the page may be read. If the page has not been recovered, the read operation may be held in a cache until the recovery utility indicates that the page has been recovered. If the I/O request is for a write operation to a space affected by the recovery process, the data may be written to a cache.

Abstract: Systems and methods for network service management, wherein the internet service management system includes one or more components which collectively enable an administrator to obtain a site-wide view of network activities on servers such as web servers, FTP servers, e-mail servers, domain name servers, etc. In addition to collecting information relating to web server latency and processing time, the internet service management system may collect actual user transaction information and system information from end users on client computers. The internet service management system may provide domain summary information for a domain, or it may provide management information organized by “categories” according to how a site manager wants to view and manage his business; e.g., byline of business (books, auctions, music, etc.), by site function (searches, shopping cart, support, quotes, sales automation), or most any other categorization customers may choose.

Abstract: To facilitate gathering of information required for root cause analysis associated with the abnormal behavior of an attribute (“problem attribute”), a user can specify causation attributes associated with the problem attribute. When the abnormal behavior is detected for the problem attribute, the causation attributes are automatically polled and stored in a database. The user can later examine the values of the causation attributes to determine if there is a causal relationship to the abnormal behavior of the problem attribute.

Abstract: A system architecture and a method for managing using a cellular architecture to allow multi-tier management of events such as the managing of the actual impact or the potential impact of IT infrastructure situations on business services. A preferred embodiment includes a high availability management backbone to frame monitoring operations using a cross-domain model where IT component events are abstracted into IT Aggregate events. By combining IT Aggregate events with transaction events, an operational representation of the business services is possible. Another feature is the ability to connect this information to dependent business user groups such as internal end-users or external customers for direct impact measurement.

Abstract: Specified data sets may be tracked from creation to end-of-life (e.g., deletion). Between creation and end-of-life, data set storage changes may be recorded (i.e., when additional storage is allocated or when some storage is released). During a subsequent allocation cycle, this information may be used in conjunction with user-specified allocation rules to manage or control the data set's initial allocation.

Abstract: Techniques to create physically and transactionally consistent copies of one or more database objects without impacting the availability of the target database objects are described. In one technique, a consistent copy is created as of the time a copy utility is executed. In another technique, a consistent copy is created as of an arbitrary specified time. This approach modifies a prior copy to bring it “up-to-date.” In yet another technique, a consistent copy is created by starting with a current snapshot of the target database objects and selectively removing updates from it back to a user specified arbitrary point-in-time. Each of the described techniques generate consistent copies of the target database objects without blocking users from accessing the target objects during the copy operation.

Abstract: Embodiments of the present invention generate identification rules to classify requests as corresponding to particular transactions. Embodiments of the present invention examine a set of sample requests, determine patterns in the sample requests and generate identification rules based on the request patterns to classify subsequent requests as corresponding to particular transactions. As more sample requests are processed, embodiments of the present invention can update the identification rules. Put another way, embodiments of the present invention can automatically learn how to classify requests better as more requests are processed.

Abstract: A method, system, and medium for compressing systems management information in a historical data store. Dynamically determining the appropriate compression algorithm to apply based on the type of data being compressed and stored. As further input is received for any particular measurement, the appropriate compression algorithm will be automatically selected from the set of available compression algorithms or be defined by a user configuration parameter. The amount of historical data stored with the minimal amount of data loss is optimized by the system dynamically changing the compression algorithm used for the given input data over a particular time span. The system engineer is therefore presented with the pertinent information for monitoring, administrating and diagnosing system activities.

Abstract: Data is often populated into Configuration Management Databases (CMDBs) from different sources. Because the data can come from a variety of sources, it may have inconsistencies—and may even be incomplete. A Normalization Engine (NE) may be able to automatically clean up the incoming data based on certain rules and knowledge. In one embodiment, the NE takes each Configuration Item (CI) or group of CIs that are to be normalized and applies a rule or a set of rules to see if the data may be cleaned up, and, if so, updates the CI or group of CIs accordingly. In particular, one embodiment may allow for the CI's data to be normalized by doing a look up against a Product Catalog and/or an Alias Catalog. In another embodiment, the NE architecture could be fully extensible, allowing for the creation of custom, rules-based plug-ins by users and/or third parties.

Abstract: Methods and systems to automate the deployment from one SMP/E installed run-time mainframe system logical partition (LPAR) to one or more different and distinct LPARs within a mainframe environment are described. Deployment may consist of distributing one or more installation items (e.g., complete products, product upgrades, patches and/or temporary fixes) from one installation environment to another target system. Also, the installed items may have optionally undergone further configuration after the initial installation and prior to actual automated deployment. Each of the target systems are communicatively coupled to the first (i.e., source) LPAR.

Abstract: An enhanced resource reconciliation process is disclosed to examine the metadata hierarchy of unidentified instances of configuration objects within a particular “data partition” (sometimes called a dataset) of an enterprise configuration management database (CMDB) and perform reconciliation against a target dataset, such as a golden, i.e., production, dataset. The enhanced reconciliation process could identify against instances in the production dataset that are of the same class as the unidentified instance—as well as instances that come from any “candidate” classes. Candidate classes could consist of, e.g., classes upstream or downstream from the unidentified instance in the metadata hierarchy.

Abstract: A method for measuring and determining the duplex modes of a network interface. The method assumes the network interface to be operating in a half-duplex mode until the bandwidth utilization reaches a threshold. When the threshold is reached, the method checks the traffic collision in the interface. If there is no collision, then the duplex mode is determined to be full-duplex. If there is collision, then the duplex mode is determined to be half-duplex and an alarm is set off. In another embodiment, the interface type is determined through SNMP. If the interface is a WAN interface, then the interface is determined to be full-duplex.

Abstract: A mechanism works in conjunction with a DB2® Log and an analysis tool, such as BMC's Log Master™, to handle logged data for Large Objects (LOBs) stored in tables of a DB2 database system. A plurality of controls track data logged for the LOBs. The mechanism reads log records from a DB2 Log and uses the controls to determine which of the tracked LOBs is associated with the log records and obtains data from those associated log records. The mechanism builds keys to index the data and stores the keys and the data in a Virtual Storage Access Method store having Key Sequenced Data Sets maintained separate from the log record store for the DB2 Log. When requested by the analysis tool, the data in the store can be reassembled using the keys and map records in the first store that map the logged data for the tracked LOBs.

Abstract: An improved method and system for controlling free space distribution by key range within a database. In one embodiment, a data structure including key ranges of a plurality of database tables and indexes, and a plurality of key range free space parameters is created. The plurality of database tables and indexes may include a plurality of page sets, which may include rows of data and keys. Time values may be associated with the plurality of free space parameters. The key range free space parameters may have values assigned to them. The key range free space parameters may be user-defined or automatically generated using growth trend analysis, based on key range growth statistics. The rows of data and keys within the plurality of page sets may be redistributed by a reorganization process. The redistributing may reference the key ranges of the data structure and the key range free space parameters.

Abstract: A method and system for unloading an IMS database. Segments in the segment array are stored in an indexed order or are stored in a relative byte address (RBA) order. In both cases, either an image copy of an IMS database or an actual IMS database processed sequentially may be utilized. For indexed order storage, a lookup table may be created to include a key value and a segment array location. A segment array may be created to store both the root and child segments from the IMS database. For RBA ordered storage, a first segment array may be created to store the root segments from the IMS database in a sequential order. Additionally, a second segment array may be created to store the child segments from the IMS database in a relative byte address (RBA) order.

Abstract: A Web Services availability cache is part of a computer system, such as an enterprise system of a business or organization. The availability cache is populated with information from Web Services communicatively connected to the computer system by a network connection. In one embodiment, the availability cache is populated based on each request handled by a server process associated with the availability cache. A server receives a request from a client having an application dependent upon information from the Web Service. The server sends the request to the Web Service and stores returned information in the availability cache. Also, the server sends the returned information to the client, which initiated to request. Once the cache is populated, the server handles subsequent requests for information from the client by using the Web Service if it is available or by using the availability cache if the Web Service is not available.