Rational Developer for Power Systems Software
V7.6

com.ibm.etools.iseries.subsystems.qsys.comm
Class IBMiPTFVerify

java.lang.Object
  extended by com.ibm.etools.iseries.subsystems.qsys.comm.IBMiPTFVerify

public class IBMiPTFVerify
extends Object


Field Summary
static String copyright
           
 
Constructor Summary
IBMiPTFVerify(String p_ptfStr, boolean p_required)
          The constructor for the ISeriesPTFVerify class
 
Method Summary
 String getPTFStr()
          Returns the PTF string.
 boolean isRequired()
          Returns true if this PTF is required.
 boolean isSuccessfull()
          Returns true if the PTF was successfull.
 void setSuccessfull(boolean success)
          Sets this PTF to successfull or not.
 
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

IBMiPTFVerify

public IBMiPTFVerify(String p_ptfStr,
                     boolean p_required)
The constructor for the ISeriesPTFVerify class

Parameters:
p_ptfStr - The PTF string.
p_required - A boolean, representing if this PTF is required.
Method Detail

getPTFStr

public String getPTFStr()
Returns the PTF string.


isRequired

public boolean isRequired()
Returns true if this PTF is required.


setSuccessfull

public void setSuccessfull(boolean success)
Sets this PTF to successfull or not.


isSuccessfull

public boolean isSuccessfull()
Returns true if the PTF was successfull. Also would return true if it was never set, since by default successfull is true.


Rational Developer for Power Systems Software
V7.6

Copyright 2011 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.