|
Problem IC68709
|
Status: Closed |
RUNNING COBOL APPLICATION MAY FAIL WILL MEMORY BOUNDARY ERRORS. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* 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.
(...) |
| available fix packs: |
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
|
| Solution |
Problem was first fixed in DB2 version 9.7 Fix Pack 3. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 18.05.2010
24.08.2010
24.08.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP3
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.3
|
 |
| 9.7.0.3
|
|
