XLPARSE CHANGE LOG

2012/06/28  - Fixed error in pgm COMPILE when creating serrvice program XLPARSE/GPPARSER4.
2010/10/11  - Provided support for converting numeric spreasheet columns to character database fields.
            - Supported multiple members on the target database file.
2010/04/15  - Added controls on receiving database fields.
              The length of a receiving database character field
              can now be longer than the size of the corresponding spreadsheet column.
2010/03/22  - Command ADDENVVAR requires the user profile to have *JOBCTL special authority.
              Without this special authority, the ADDENVVAR commands issued from pgm XLSCONVERT are not executed.
              This makes XLSCONVERT to fail.
              Added a monitor routine in XLSCONVERT to check current user profile special authorities.
2010/03/19  - Program XLSTABLE. Changed the way the decimal dot is replaced by a decimal comma.
            - Program XLSCONVERT. Made some aggiustements on the "FormulaCell" internal subprocedure.
2010/03/18  - Announcing XLPARSE2 as successor of XLPARSE
            - Added parameters CLASSPATH and JAVAVER to command XLPARSE/XLSTABLE
            - All the Java classes are now in directory /xlparse/java
2010/03/11  - Command XLSTABLE now issues an escape message whenever an abnormal condition is detected.
            - Changes to command XLSTABLE:
              -- Parameter COLHDG(*YES/*NO) has been replaced by parameter HLINES(0-99).
              -- Parameter DATEFMT(*YMD/*MDY/*DMY) has been added.
            - Changes to command XLSCONVERT:
              -- Parameter DATEFMT(*YMD/*MDY/*DMY) has been added.
2010/03/10  - On systems where system value QDECFMT defines the decimal point as a comma,
              numeric values were reports as multiplied by 1000000. Now fixed.
            - Fixed the case where the DDSR source member is different from the physical file name.
            - Formula values like "<string> [ ..." are now reset to blank in XLSCONVERT.
2010/03/09  - Date fields now converted to char fields in XLSCONVERT,
              thus simplifying XLSTABLE process.
            - Fixed the case where a sheet row is missing the final column(s).
            - Changed XLSTABLE command, providing a value *AUTO for parameter DATECOL.
            - Parameter SETOUTID in command XLSTABLE renamed COLHDG.
            - Fixed columns lengths in XLSCONVERT when SETOUTID(*NO).
2010/03/08  - Fixed some parsing techniques in pgm XLSCONVERT.
2010/03/07  - Added the utility XLSTABLE (Transform an XLS sheet to a physical file).
              See page http://www.easy400.net/xlparse/whatsnew/xlparse.txt
2010/03/05  - Changed subprocedure XLSGETCELL.
            - Rendering of "formula" numeric values was improved (float values supported) for XLSCONVERT.
2010/01/19  - POI 3.6 Java classes found not good. Java Classes 3.2 are back.
            - The problem was detected with an .xls spreadsheet from Nijac van Kampen, The Netherlands.
              A spreadshert from him (/xlparse/samples/sample10.xls) could not be processed by command
              XLSCONVERT with POI 3.6. After replacing POI with release 3.2, it worked.
2010/01/05  - POI 3.2 Java classes replaced by POI 3.6 ones.
            - Removed support for decimal point other than ".".
2009/12/01  - Added one more parameter (SetOUTID) to command XLSCONVERT.
            This parameter allows to optionally differentiate the data type of file QTEMP/XLSOUTF records
            as documented in record format field OUTID:
              -- "B" meaning 'Sheet title'
              -- "H" meaning 'Column headers"
              -- "D" meaning 'Data columns'.
            If you specify SETOUTID(*NO), data type "D" is assigned to all records.
2009/11/30  - Several fixes to XLSCONVERT:
      *   - More cases added to "FormulaCell".
      *   - Fixed the number of decimal digits for numeric values out of "FormulaCell".
      *   - Fixed bug, if multiple worksheets, the last line of all but the last sheet
      *     was not output.
      *   - Round up negative values such as -3.5499999999999999999 to -3.55 .
      *   - In NumberCell procedure. Use 25.x variables instead of 15.x to avoid numeric overflow.
      *   - Make classpath a parameter so it can be controlled.
      *   - Make Java version a parameter and allow use of system default.
      *   - Check for error after use of DOCMD and report when we should not proceed.
      *   - If errors occurs, exit with CPF9898 so standard error monitors will catch it.
      *   - If errors occur, exit with an escape message instead of sending a message to *EXT
      *     then ending 'normally'
2009/10/14  - Now able to process also formulas starting by [FORMULA] .
2009/03/24  - XLSCONVERT would bump out if a cell size exceeds 999.
              That happened for a long formula.
              Maximum cell size is now 999.999.999
              though its contents cannot exceed 5.000 byte.
2009/03/20  - Subprocedure XLSGETCELL was ignoring the last column in the
              spreadsheet image available in file QTEMP/XLSOUTF .
2009/03/19  - Pgm XLSCONVERT was not showing minus sign for negative numbers.