com.ibm.etools.iseries.edit.verifiers.comm.bridge
Class EDOUT2Struct
java.lang.Object
com.ibm.etools.iseries.edit.verifiers.comm.bridge.EDOUT2Struct
public class EDOUT2Struct
- extends Object
This class corresponds to the CODE comm EDCODE struct defined in evfcsys.h
typedef struct {
SHORT count; // number of user defined codes
CHAR currencySymbol; // Currency symbol
CHAR systemDate[6]; // Date format
CHAR decimalSeparator; // Decimal separator
CHAR dateSeparator; // Date separator
CHAR timeSeparator; // Time separator
CHAR userId[11]; // User identifier
CHAR jobDescription[11]; // Profile job description
CHAR jobLibrary[11]; // Profile job library
EDCODE editCode[5]; // User defined edit code
} EDOUT2; // Edit code struct for request = 3
Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
copyright
public static final String copyright
- See Also:
- Constant Field Values
EDOUT2Struct
public EDOUT2Struct(IISeriesEditDescriptionsInfo editDescriptions)
- Constructor for EDOUT2Struct.
getCount
protected short getCount()
getCurrencySymbol
protected char getCurrencySymbol()
getSystemDateFormat
protected String getSystemDateFormat()
getDecimalSeparator
protected char getDecimalSeparator()
getDateSeparator
protected char getDateSeparator()
getTimeSeparator
protected char getTimeSeparator()
getUserID
protected String getUserID()
getJobDescription
protected String getJobDescription()
getJobLibrary
protected String getJobLibrary()
getEditDescriptions
protected Collection getEditDescriptions()
write
protected void write(JavaToCOutputStream out)
throws IOException
- Write the datastructure to the output stream
- Throws:
IOException
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.