iSeries Remote Systems
v6.0.1

com.ibm.etools.iseries.core.comm
Class ISeriesReleaseVerify

java.lang.Object
  extended bycom.ibm.etools.iseries.core.comm.ISeriesReleaseVerify

public class ISeriesReleaseVerify
extends Object


Field Summary
static String copyright
           
 
Constructor Summary
ISeriesReleaseVerify()
          Constructor for ISeriesReleaseVerify class
 
Method Summary
 void addPID(ISeriesPIDVerify pidVerify)
          Adds a PID to this ISeriesReleaseVerify
 ISeriesVRM getHostVRM()
          Gets the host VRM associated with this release
 List getPIDs()
          Gets the PIDs associated with this ISeriesReleaseVerify
 boolean isPIDSuccessfull()
          Returns true if all the PIDs checked were successfull
 void setHostVRM(ISeriesVRM p_hostVRM)
          Sets the host VRM associated with this release
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Field Detail

copyright

public static final String copyright
See Also:
Constant Field Values
Constructor Detail

ISeriesReleaseVerify

public ISeriesReleaseVerify()
Constructor for ISeriesReleaseVerify class

Method Detail

setHostVRM

public void setHostVRM(ISeriesVRM p_hostVRM)
Sets the host VRM associated with this release


getHostVRM

public ISeriesVRM getHostVRM()
Gets the host VRM associated with this release


addPID

public void addPID(ISeriesPIDVerify pidVerify)
Adds a PID to this ISeriesReleaseVerify


getPIDs

public List getPIDs()
Gets the PIDs associated with this ISeriesReleaseVerify


isPIDSuccessfull

public boolean isPIDSuccessfull()
Returns true if all the PIDs checked were successfull


iSeries Remote Systems
v6.0.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.