Abstract: A compiler-loader system enables the creation of different loaded executable images in target computers complying with different versions of an instruction-set architecture, the different images being created from a single executable program on secondary storage. The compiler generates an executable program containing a routine executable on both versions of the target computers, and also containing an architecture entry with (i) an address of the program location from which the routine is called, (ii) an instruction executable on only one version of the target computers that performs the same function as the routine but with superior performance, and (iii) a value indicating which version of the target machines the instruction can be executed on. The loader determines whether the target machine can execute the instruction, and if so replaces the subroutine call appearing at the address in the architecture entry with the instruction appearing in the architecture entry.

Abstract: A compiler-loader system enables the creation of different loaded executable images in target computers complying with different versions of an instruction-set architecture, the different images being created from a single executable program on secondary storage. The compiler generates an executable program containing a routine executable on both versions of the target computers, and also containing an architecture entry with (i) an address of the program location from which the routine is called, (ii) an instruction executable on only one version of the target computers that performs the same function as the routine but with superior performance, and (iii) a value indicating which version of the target machines the instruction can be executed on. The loader determines whether the target machine can execute the instruction, and if so replaces the subroutine call appearing at the address in the architecture entry with the instruction appearing in the architecture entry.

Abstract: A memory resource allocation look ahead system is implemented in event logger (14), operating in conjunction with one or more event sinks (18). When the event logger (14) is called, all information in the argument fist is copied into an event buffer maintained by the logger (14), and the buffer is placed at the input end of queue (44). The event sinks 18 contain a similar queue. In operation of the event logger 14, an evd.sub.-- get.sub.-- event routine is used to obtain event reports from the event queue (44). The evd.sub.-- get.sub.-- event routine includes a next.sub.-- size.sub.-- hint argument, giving the size of the event record that will be obtained with the next call to evd.sub.-- get.sub.-- event. The next.sub.-- size.sub.-- hint argument is used to allocate memory for the next call to evd.sub.-- get.sub.-- event.

Abstract: A computer system has a management system for performing management operations with respect to system components. Each component is capable of being controlled in accordance with one or more management protocols. One or more management tools generate management commands that specify management operations to be performed by a specified set of system components. The system includes a plurality of protocol engines, each of which implements a specific management protocol with respect to a set of system components. Each protocol engine responds to system management commands by generating instructions for performing the specified management operation in accordance with a predefined management protocol. A common agent interface receives the instructions generated by a protocol engine and sends corresponding commands in a protocol non-specific format to the target system components which are the object of the specified management operation.