Tools that observe and manipulate the run-time behavior of parallel and distributed systems are essential for developing and maintaining these systems. Sometimes users would even need to use several tools at the same time in order to have a higher functionality at their disposal. Today, tools developed independently by different vendors are, however, not able to interoperate. Interoperability not only allows concurrent use of tools, but also can lead to an added value for the user. A debugger interoperating with a checkpointing system, for example, can provide a debugging environment where the debugged program can be reset to any previous state, thus speeding up cyclic debugging for long running programs. Using this example scenario, we derive requirements that should be met by the tools“ software infrastructure in order to enable interoperability. A review of existing infrastructures shows that these requirements are only partially met today. In an ongoing research effort, support for all of the requirements is built into the OMIS compliant on-line monitoring system OCM

@article{IRTTFDSACS00,
	author	 = {Roland Wismüller and Thomas Ludwig},
	title	 = {{Interoperable Run Time Tools for Distributed Systems - A Case Study}},
	year	 = {2000},
	publisher	 = {Springer},
	address	 = {Berlin / Heidelberg, Germany},
	journal	 = {The Journal of Supercomputing},
	series	 = {17-3},
	pages	 = {277--289},
	issn	 = {0920-8542},
	doi	 = {http://dx.doi.org/10.1023/A:1026515407398},
	abstract	 = {Tools that observe and manipulate the run-time behavior of parallel and distributed systems are essential for developing and maintaining these systems. Sometimes users would even need to use several tools at the same time in order to have a higher functionality at their disposal. Today, tools developed independently by different vendors are, however, not able to interoperate. Interoperability not only allows concurrent use of tools, but also can lead to an added value for the user. A debugger interoperating with a checkpointing system, for example, can provide a debugging environment where the debugged program can be reset to any previous state, thus speeding up cyclic debugging for long running programs. Using this example scenario, we derive requirements that should be met by the tools'' software infrastructure in order to enable interoperability. A review of existing infrastructures shows that these requirements are only partially met today. In an ongoing research effort, support for all of the requirements is built into the OMIS compliant on-line monitoring system OCM},
	url	 = {http://www.springerlink.com/content/r851853209046q80/fulltext.pdf},
}