=========================================== RELEASE NOTES FOR INFORMIX-ESQL/COBOL7.25.UC1 PRODUCT RELEASE DATE: February 1999 =========================================== TABLE OF CONTENTS I. OVERVIEW OF RELEASE NOTES II. LIMITS IN INFORMIX-ESQL/COBOL III. GETTING STARTED IV. BUGS FIXED (UNIX) IN THIS RELEASE I. OVERVIEW OF RELEASE NOTES The purpose of these release notes is to make the user aware of changes in products that might affect existing applications. The release notes contain information on changes from previous versions, known bugs, and workarounds. Bug numbers are assigned to known defects to assist you in identifying the defects to Customer Services personnel. The release notes document is not intended to be all-inclusive; it is a tool to assist you in the update process. Please consult Informix product manuals for additional information on product features and for clarification of product behavior. Note that this ESQLCOBREL_7.2 file applies only to the 7.25.UC1 release. It contains information you will need to know when upgrading from a 7.2x release. If you are upgrading from a release prior to 7.2, then you should also examine other release notes. INFORMIX-ESQL/COBOL 7.25.UC1 has been tested for the following Informix database servers: - Informix Dynamic Server, Version 7.2x and 7.3x - Informix Dynamic Server with Advanced Decision Support and Extended Parallel Options, Version 8.2x - Informix Dynamic Server with Universal Data Option, Version 9.14. Previous releases of ESQL/COBOL contained the XA libraries. This was done by mistake and was misleading to some customers. This version of ESQL/COBOL no longer contains the XA libraries. ESQL/COBOL does not support XA; ESQL/C does. Some customers have successfully used XA in conjunction with ESQL/C in an environment that includes ESQL/COBOL. However, the success of these environments does not imply that ESQL/COBOL supports XA. If for some reason you rely on ESQL/COBOL distributing the XA libraries, you will be able to get these libraries (as you always have able to) from either the 7.2x ESQL/C product, the 9.x ESQL/C that is part of the Client SDK product, or the 7.2x or 2.x Client SDK/Connect products. Earlier versions of ESQL/COBOL supported both the Ryan MacFarland RM COBOL-85 Compiler and AccuCOBOL compiler. Support for these compilers has been discontinued. Therefore, the INFORMIXCOBTYPE environment variable should always set to mf2. The esqlcobol script will warn you of the fact when the INFORMIXCOBTYPE is not set to mf2. Please note that although 7.25 ESQL/COBOL is only compatible with 7.23 ESQL/C runtime, it can work with 2.20 Client SDK/Connect in the following way. Both 2.20 Client SDK/Connect and 7.25 ESQL/COBOL can be installed in the same directory with the requirement that 7.25 ESQL/COBOL needs to be always installed first. Then all 7.25 ESQL/COBOL applications will be able to take advantage of the new GLS libraries and message files in 2.20 Client SDK/Connect. Note however that if a 7.25 ESQL/COBOL application is linked with an ESQL/C application, then it cannot make use of any shared libraries from 2.20 Client SDK/Connect. Trying to mix 7.25 ESQL/COBOL applicaiton and ESQL/C appliations that use 2.20 Client SDK/Connect will result in duplicate symbols or unresolved symbols at link time. II. LIMITS IN INFORMIX-ESQL/COBOL Size of host object name.................................132 chars Size of host object subscript............................132 chars Size of indicator object name............................132 chars Size of Value for fetch relative.........................132 chars Size of SQL identifier (table name, etc).................132 chars Size of number constant..................................132 chars Size of macro name.......................................132 chars Size of macro value......................................132 chars Size of statement name...................................132 chars Size of quoted string literal...........................1024 chars Number of statement_ids...........................machine specific Number of levels of host-language block nesting.................32 Number of levels of include-file nesting...................dynamic Length of line...........................................256 chars Size of statement label (sequence area)...................18 chars Number of nested records........................................16 III. GETTING STARTED ENVIRONMENTAL SETUP For SUN Solaris user, the following environment variables need to be setup in order to run INFORMIX-ESQL/COBOL with Mocro Focus COBOL: COBDIR=/usr/lib/cobol INFORMIXCOBDIR=$COBDIR INFORMIXCOB=cobol INFORMIXCOBTYPE=mf2 PATH=$COBDIR:$COBDIR/bin:$PATH LD_LIBRARY_PATH=$INFORMIXDIR/lib:$INFORMIXDIR/lib/esql:$COBDIR/coblib export COBDIR INFORMIXCOBDIR INFORMIXCOB INFORMIXCOBTYPE LD_LIBRARY_PATH export PATH Please note that COBDIR should be set to the location where Micro Focus COBOL compiler is installed. In this example, it is installed in /usr/lib/cobol. And $COBDIR/coblib should be added into LD_LIBRARY_PATH. Please note LD_LIBRARY_PATH is used for SUN Solaris user only. For other UNIX platforms, please refer to the machine speific note. COMPILING THE ESQL/COBOL PROGRAM: The esqlcobol command can be used to compile the ESQL/COBOL program. Enter the following command will compile the demo.eco program: esqlcobol demo.eco RUNNING THE ESQL/COBOL PROGRAM: The makerun command can be used to create a run-time program. Enter the following command will create a run-time program, called newrun in the current directory: makerun newrun Enter the following command will run the demo program: newrun demo For more detail information please refer to the Chapter one in Informix-ESQL/COBOL manual, version 7.2. IV. BUGS (UNIX) FIXED IN THIS RELEASE 55227 -201 AT PREPARED SELECT STATEMENT IN AN ESQL/COBOL PROGRAM. 56517 ERROR -406: COBOL FE OUT OF MEMORY WHEN DECLARING CURSOR IN LOOP, ONLY WITH BE 7.13.UC1, NOT 7.12.UC1. 56397 ESQLCOBOL GENERATES A SYNTACTIC INVALID COBOL PROGRAM IF USING WHENEVER STATEMENT AND A COBOL EVALUATE ... WHEN ... WHEN ... END-EVALUATE CONSTRUCT. 64905 ERROR -406: COBOL FE OUT OF MEMORY WHEN OPENING AND CLOSING A CURSOR IN A LOOP. 69502 BREAKING EXEC-SQL END DECLARE SECTION END-EXEC. ON MORE THAN 1 LINE CAUSES 33051 SYNTAX ERROR. 70128 ESQL/COBOL DOES NOT SUPPORT COBOL LOW-VALUE DATA CONSISTENTLY. 75074 EXCUTE INTO SQL DESCRIPTOR USING SQL DESCRIPTOR WITH ESQLCOBOL, PREPROCESSOR GENERATES TWICE INTO PART. 78325 ESQL/COBOL 7.22, 7.23: 88-LEVELS INSIDE EXEC SQL DECLARE AREAS PRODUCE AN EXTRA QUOTE ON CONTINUATION LINE WITH STRING VALID VALUES. 75508 IN ESQLCOBOL LENGTH OF HOSTVAR MUST BE DECLARED AS LENGTH + 1 INSTEAD OF THE LENGTH THAT IS REQUIRED. 80145 ESQL/COBOL CANNOT BE USED IN ANSI85 NESTED PROGRAMS. A new option -nested has been added into esqlcobol so that it will handle nested program correctly. If users want to use nested program feature in combination with ESQL/COBOL, they should always use the following command: esqlcobol -nested program.eco When nested option is used, the ESQL/COBOL preprocessor will include the necessary ESQL/COBOL variables as GLOBAL so that they can be shared with the containing nested program. 80872 SETTING DBMONEY TO "DM," (COMMA) LEADS TO WRONG RESULTS WHEN USING PACKED DECIMAL (E.G. PIC S99V99 COMP-3) HOSTVARIABLES. 85133 INCOMPLETE DATA RETURNING IN COBOL CLIENT IN JAPANESE LOCALE.