home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC68709 Status: Geschlossen

RUNNING COBOL APPLICATION MAY FAIL WILL MEMORY BOUNDARY ERRORS.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
Cobol progrma worked fine in old environment. Moving to db2 v9.5 
fp4 and recompiled and now failing. 
 
After running the old module against the system it worked ok. 
After compiling the new module with Micro Focus on our system32 
they got the following error. 
 
Below is the error they are getting when running COBDB2. They 
have run the MicroFocus debug utility to determine that the 
error is occurring on the ?call sqlgcrea? statement. 
 
$ ./COBDB2 COLTEST,/data/db2/coltest 
CREATing database ... 
please wait... this will take a while ... 
 
Execution error : file 'COBDB2' 
error code: 114, pc=0, call=1, seg=0 
114     Attempt to access item beyond bounds of memory (Signal 
11)
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The sqledbdesc structure is incompatible between             * 
* 32-bitcobolapplications and 64-bit db2. This leads to        * 
* memoryboundaryissues at run-time.See CRM 39121,344,000 for   * 
* details.Cobolprogrma worked fine in old environment. Moving  * 
* to db2v9.5fp4 and recompiled and now failing.After running   * 
* the oldmodule against the system it workedok.  After         * 
* compiling thenew module with Micro Focus on oursystem32 they * 
* got thefollowing error.Below is the error they are getting   * 
* whenrunning COBDB2.They  have run the MicroFocus debug       * 
* utilityto determinethat the error is occurring on the call   * 
* sqlgcreastatement../COBDB2                                   * 
* COLTEST,/data/db2/coltestCREATingdatabase ...please wait...  * 
* this will take a while...Execution error : file              * 
* 'COBDB2'error code: 114, pc=0,call=1, seg=0114    Attempt to * 
* access item beyond bounds ofmemory(Signal 11)                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 9.7 Fix Pack 3.                       * 
****************************************************************
Local-Fix:
Modify sqlenv.cbl file to add $IF clause. For example, the 
modified file will look like this: 
 
(...) 
      * default extent size 
           05 SQLTSEXT               PIC S9(9) COMP-5. 
$IF P64 SET 
           05 FILLER                    PIC X(4). 
$END 
           05 SQLCATTS               USAGE IS POINTER. 
           05 SQLUSRTS               USAGE IS POINTER. 
(...) 
 
 
instead of like this: 
 
(...) 
      * default extent size 
           05 SQLTSEXT               PIC S9(9) COMP-5. 
 
           05 FILLER                    PIC X(4). 
 
           05 SQLCATTS               USAGE IS POINTER. 
           05 SQLUSRTS               USAGE IS POINTER. 
(...)
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Problem was first fixed in DB2 version 9.7 Fix Pack 3.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
18.05.2010
24.08.2010
24.08.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP3
Problem behoben lt. FixList in der Version
9.7.0.3 FixList
9.7.0.3 FixList