Rational Developer for Power Systems Software
V7.6

com.ibm.etools.iseries.subsystems.qsys.commands
Class QSYSParameterToken

java.lang.Object
  extended by com.ibm.etools.iseries.subsystems.qsys.commands.QSYSParameterToken

public class QSYSParameterToken
extends Object

Help class to contain the information of a parameter to be used when adding the adding the command line parameters to the command


Field Summary
static String Copyright
           
 
Constructor Summary
QSYSParameterToken(String paramToken)
           
 
Method Summary
 String getCompleteToken()
          Return the complete parameter
 String getKeyword()
          Return the keyword specified in the parameter
 String getValue()
          Return the value specified in the parameter
 boolean isEnclosedWithBrackets()
          Return if the parameter is enclosed with brackets.
 boolean isProtected()
          Return if the parameter is specified as proctected i.e.
 
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

QSYSParameterToken

public QSYSParameterToken(String paramToken)
Method Detail

getValue

public String getValue()
Return the value specified in the parameter


getKeyword

public String getKeyword()
Return the keyword specified in the parameter


getCompleteToken

public String getCompleteToken()
Return the complete parameter


isEnclosedWithBrackets

public boolean isEnclosedWithBrackets()
Return if the parameter is enclosed with brackets.


isProtected

public boolean isProtected()
Return if the parameter is specified as proctected i.e. prepended with ?* or ?%.


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.