Abstract: An autonomic component installation system. The system can include a catalog of host components installed within a computing system and an autonomic installer coupled to the catalog and programmed to determine, when installing an upgraded component, whether the upgraded component provides component capabilities required by the host components in the catalog. The catalog can include both host components and respective publicly accessible data, method implementations and method prototypes provided by the host components. Consequently, the autonomic installer can determine whether the upgraded component will have access to required publicly accessible data and method implementations. The autonomic installer further can be configured to determine whether modifications included in the upgraded component have caused changes in associated method prototypes which differ from the method prototypes in the catalog.

Abstract: A method for the autonomic management of autonomic systems can include monitoring a managed system and recommending a course of action to be performed in the managed system. It can be determined whether the recommended course of action has been performed by an administrator. Responsive to the determination, it further can be determined whether an outcome from the course of action comports with a predicted outcome. If so, a point count can be changed responsive to a further determination that the outcome from the course of action comports with the predicted outcome. Conversely, the point count can be oppositely changed responsive to a further determination that the outcome from the course of action does not comports with the predicted outcome. In any case, when the point count crosses a threshold value, the management of the managed system can be transitioned to an adaptive component.

Abstract: A method for the autonomic management of autonomic systems can include monitoring a managed system and recommending a course of action to be performed in the managed system. It can be determined whether the recommended course of action has been performed by an administrator. Responsive to the determination, it further can be determined whether an outcome from the course of action comports with a predicted outcome. If so, a point count can be changed responsive to a further determination that the outcome from the course of action comports with the predicted outcome. Conversely, the point count can be oppositely changed responsive to a further determination that the outcome from the course of action does not comports with the predicted outcome. In any case, when the point count crosses a threshold value, the management of the managed system can be transitioned to an adaptive component.

Abstract: A method for the autonomic management of autonomic systems can include monitoring a managed system and recommending a course of action to be performed in the managed system. It can be determined whether the recommended course of action has been performed by an administrator. Responsive to the determination, it further can be determined whether an outcome from the course of action comports with a predicted outcome. If so, a point count can be changed responsive to a further determination that the outcome from the course of action comports with the predicted outcome. Conversely, the point count can be oppositely changed responsive to a further determination that the outcome from the course of action does not comports with the predicted outcome. In any case, when the point count crosses a threshold value, the management of the managed system can be transitioned to an adaptive component.

Abstract: An autonomic component installation system. The system can include a catalog of host components installed within a computing system and an autonomic installer coupled to the catalog and programmed to determine, when installing an upgraded component, whether the upgraded component provides component capabilities required by the host components in the catalog. The catalog can include both host components and respective publicly accessible data, method implementations and method prototypes provided by the host components. Consequently, the autonomic installer can determine whether the upgraded component will have access to required publicly accessible data and method implementations. The autonomic installer further can be configured to determine whether modifications included in the upgraded component have caused changes in associated method prototypes which differ from the method prototypes in the catalog.

Abstract: A method, system, and computer-readable code for a technique with which files encoded according to the Extensible Markup Language (XML) notation can be marked up to indicate that the content of the file (or some portion thereof) is dynamic in nature and is to be updated automatically to reflect changing information. The proposed technique provides a novel way to specify that a data repository should be accessed as the source of the updates. Techniques are defined for specifying that this data repository access occurs once, and for specifying that it occurs when a set of conditions are satisfied (which may include periodically repeating the data repository access and content update). In one aspect, the data repository is a database; in another aspect, the data repository is a file system. Preferably, the Lightweight Directory Access Protocol (LDAP) is used as an access method when the data repository being accessed is a database storing an LDAP directory.

Abstract: Objects including Java bytecodes are embedded in a 3270 datastream structured field. The 3270 datastream structured field, including the objects so embedded, are passed between a primary logical unit and a secondary logical unit that communicate with each other over a network using 3270 datastream architecture. An initialization protocol sends a Read Partition (Query) structured field from the primary logical unit to the secondary logical unit, to query whether the secondary logical unit supports Java. The secondary logical unit sends a Query Reply structured field to the primary logical unit in response to receipt of the Read Partition (Query) from the primary logical unit if the secondary logical unit supports Java. In response to receipt of the Query Reply structured field from the secondary logical unit, the 3270 datastream structured field including embedded objects such as Java bytecodes is passed between the primary logical unit and the secondary logical unit.