Remote Systems
v6.4.1

com.ibm.etools.systems.universal.util
Interface ICommunicationsDiagnostic

All Superinterfaces:
Runnable

public interface ICommunicationsDiagnostic
extends Runnable

An interface for ICommunicationsDiagnostic class


Field Summary
static int CANCEL_WAIT_REQUESTED
           
static String copyright
           
 
Method Summary
 int diagnosticStatus()
          diagnosticStatus
 void displayMessage(String id)
          Dispaly a message dialog
 boolean isNetworkDown()
          Check if network is down
 boolean isServerActive()
          Check if host server is still active
 void logError(String text)
          Log an error in the .log file
 void setUp(String id, boolean quiet, String server, ISystem system, String str1, String str2, String str3)
          Setup for the diagnostic
 
Methods inherited from interface java.lang.Runnable
run
 

Field Detail

copyright

public static final String copyright
See Also:
Constant Field Values

CANCEL_WAIT_REQUESTED

public static final int CANCEL_WAIT_REQUESTED
See Also:
Constant Field Values
Method Detail

setUp

public void setUp(String id,
                  boolean quiet,
                  String server,
                  ISystem system,
                  String str1,
                  String str2,
                  String str3)
Setup for the diagnostic


logError

public void logError(String text)
Log an error in the .log file


isNetworkDown

public boolean isNetworkDown()
Check if network is down

Returns:
true or false

isServerActive

public boolean isServerActive()
Check if host server is still active

Returns:
true or false

displayMessage

public void displayMessage(String id)
Dispaly a message dialog


diagnosticStatus

public int diagnosticStatus()
diagnosticStatus

Returns:
status

Remote Systems
v6.4.1

Copyright © 2005 IBM Corp. All Rights Reserved.

Note: This documentation is for part of an interim API that is still under development and expected to change significantly before reaching stability. It is being made available at this early stage to solicit feedback from pioneering adopters on the understanding that any code that uses this API will almost certainly be broken (repeatedly) as the API evolves.