Rational Developer for Power Systems Software
V7.6

com.ibm.etools.iseries.comm
Class ISeriesListSpoolFilesHeader

java.lang.Object
  extended by com.ibm.etools.iseries.comm.ISeriesListSpoolFilesHeader

public class ISeriesListSpoolFilesHeader
extends Object

This class encapsulates the SpoolFile list header information available after a call to ISeriesListSpoolFiles. This is information pertaining to the file which contained the SpoolFiles retrieved.


Field Summary
static String Copyright
           
 
Constructor Summary
protected ISeriesListSpoolFilesHeader(AS400 system, byte[] data400, int headerOffset, int hostCCSID)
          The constructor is not public.
 
Method Summary
 String getUserName()
          Return name of user used to get the list.
 void writeHeaderInfo(PrintWriter logFileStream)
          Write out to file stream information in this header.
 
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

ISeriesListSpoolFilesHeader

protected ISeriesListSpoolFilesHeader(AS400 system,
                                      byte[] data400,
                                      int headerOffset,
                                      int hostCCSID)
The constructor is not public. Only ISeriesListSpoolFiles can create objects of this class.

Method Detail

getUserName

public String getUserName()
Return name of user used to get the list.


writeHeaderInfo

public void writeHeaderInfo(PrintWriter logFileStream)
Write out to file stream information in this header. To write to System.out pass new PrintWriter(System.out)


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.