Abstract: A method of providing access to Business Applications (BA) offering their services and interactively controlled by a multitude of BA panels, the BAs displaying succeeding BA panels dependent on user interactions, user specified data and the contents of any kind of data base the BA is operating on. The individual panels, the sequence of the panels as they are displayed by the BA and the activities required to launch a BA to display a succeeding panel results in a User Interaction Graph (UIB) modeling the spectrum of panel interactions with a BA. Analyzing the UIB generates Transaction Methods (TM) for autonomously executing and controlling a sequence of BA panels which, with the correct input information Passed over the TMs, initiate the required activities for traversing through a certain panel sequence and returning the output information gathered during its execution.

Abstract: A method and system of carrying out garbage collection in a computer system. Specifically, the method and system utilize low contention grey object sets for concurrent marking garbage collection. A garbage collector traces memory objects and identifies memory objects according to a three-color abstraction, identifying a memory object with a certain color if that memory object itself has been encountered by the garbage collector, but some of the objects to which the memory object refers have not yet been encountered. A packet manager organizes memory objects identified with the certain color into packets, provides services to obtain empty or partially full packets, and obtain full or partially full packets, and verifies whether a packet of the certain color is being accessed by one of the threads of the garbage collector.

Abstract: A method is described comprising inserting an allocation instruction within a routine if a function call instruction is found within the routine. Another method is described comprising inserting multiple allocation instructions within a routine by searching for one or more functional characteristics within the routine and inserting an allocation instruction within the routine if a functional characteristic is discovered. Another method is described comprising performing a first allocation for a first amount of register space at the entry block of a routine and then performing a second allocation for a second amount of register space for the live information within the routine at the time of the second allocation. Then, performing a function call to a second routine and performing a third allocation for a third amount of register space at the entry block of the second routine, the third amount of register space and the first amount register space having a common register.

Abstract: A linker and a method of linking object code modules using the linker is described in which a mechanism is defined for defining and passing relocations, termed compound relocations, in the object files, the compound relocations being expandable by the linker into a sequence of relocations all at the same offset. Each compound relocation has a type field denoting a compound relocation type indicator and an offset field indicating the offset where the compound relocation is to be expanded. The method comprises reading a compound relocation, recalling a predefined sequence of relocations, and executing the predefined sequence at the same location as the compound relocation. By defining compound relocations for frequently performed calculations object file bloat can be avoided, as the same sequences are not repeatedly written in the object code files.

Abstract: In a method for replacing technologically aging sub-systems and software in a system of which the sub-systems are components, a data bank is maintained by a service provider for each customer. In the data bank, the sub-system currently installed at the customer is indicated. Before replacing a part of a sub-system, the data bank is interrogated to determine whether, dependent on the age class of the sub-system, the entire sub-system should be replaced. If so, replacement of the entire sub-system is undertaken, and the data bank is updated. Similarly, before upgrading software for a customer's sub-system, the data bank is interrogated to determine whether replacement of the sub-system is required, given the age class of the sub-system. If so, the sub-system is replaced and software appropriate for the replaced sub-system is then installed.

Abstract: An apparatus, method, and system for generating semi-deployed enterprise java beans is provided. The apparatus, method and system make use of metadata to identify an intended deployment of an undeployed enterprise java bean. The metadata may be packaged with the undeployed enterprise java bean into a java archive file which is provided to a deployment tool either on the same computing device or a different computing device. The deployment tool may make use of the metadata when generating deployment classes for the undeployed enterprise java bean. However, if the deployment tool is unable to recognize the metadata or the use of the metadata is not wanted, the deployment tool may also deploy the undeployed enterprise java bean in a conventional manner.