error code: 114 Attempt to access item beyond bounds of memory (Signal 11)


    Sponsored Links


  • 1. Sort/Merge Error
    I am getting the following error message when I compile. ** DIAGNOSTIC MESSAGE ** (INVCBRK) C:\Cobol\Proj8.cbl 89: JMN2896I-S SORT-MERGE FILE CAN ONLY SPECIFY FILE-IDENTIFIER IN ASSIGN CLAUSE. STATISTICS: HIGHEST SEVERITY CODE=S, PROGRAM UNIT=1 Can anyone give me any suggestions on what to do to correct this problem? Thanks
  • 2. OT: Life style(s), personal beliefs, faith, opinions, and all that JAZZ
    LX-i < XXXX@XXXXX.COM > wrote: >It's called "hate the sin, love the sinner." What it means is that you >don't write off a person just because they're doing something which >displeases God.. And since when has God been making His displeasure known?? Surely, what you really mean is "..doing something which displeases those persons who set themselves up as God's representatives"..? >... (at times, we all do those sorts of things). What it >does *not* mean is that you can't call a spade a spade. Some folks appear to become upset when said "spade" is referred to as a "f*cking shovel". :-) -- Jeff. Ironbridge, Shrops, U.K. XXXX@XXXXX.COM (remove the x..x round u-net for return address) and don't bother with ralf4, it's a spamtrap and I never go there.. :) ... "There are few hours in life more agreeable than the hour dedicated to the ceremony known as afternoon tea.." Henry James, (1843 - 1916).
  • 3. Mainframe Standards (was: Infinite Loops and Explicit Exits
    "Robert Wagner" < XXXX@XXXXX.COM > wrote in message news: XXXX@XXXXX.COM ... > On Tue, 16 Nov 2004 15:16:36 GMT, "Howard Brazee" < XXXX@XXXXX.COM > > wrote: > <snip> > > Most mainframe shop standards stifle progress by mandating Lowest > Common Denominator. They should elevate inexperienced programmers > rather than lowering everyone else to their level. > The "coding standards" that I am aware of at (IBM) mainframe shops that see the mainframe as a good place to develop and maintain COBOL code do *not* stifle proress and/or mandate the lowest common denominator. They encourage (rarely require) a common coding style that makes it (relatively) easy for an experienced COBOL programmer to "take over" an existing program and to quickly understand its function - as well as to avoid some common errors. Although I am not aware of such shops, I can easily imagine that an IBM mainframe shop that is trying to move its COBOL *off* the mainframe might not have kept its compiler or its programmers "current" and therefore, may have had a stifling style. -- Bill Klein wmklein <at>

Re: error code: 114 Attempt to access item beyond bounds of memory (Signal 11)

Postby Wiggy » Wed, 06 Aug 2003 08:37:54 GMT

Server Express docs can be found online at the Micro Focus SupportLine site

Check the User's Guide, Chapter 7.


Similar Threads:

1.114 Attempt to access item beyond bounds of memory - (Signal 11)


I'm trying to run a cobol program and calling "DBOPEN" with parameters

I'm trying to open the database with read mode.

When I animate the program, at this specific point of calling "DBOPEN"
, Attempt to access item beyond bounds of memory - (Signal 11) occurs.
I'm not able to proceed further.

Help needed in this case.

With Kind Regards,

2.Microfocus Cobol - Execution error code: 114

Has anyone else had this problem?

We have recently upgraded our Unix box to HP-UX 11 & Microfocus Cobol
OCDS 4.1.40. All our cobol sources were recompiled under the new
version of OS and OCDS.

Also worth mention is that the same source program also runs on
various other flavours of Unix OS & Cobol, e.g. AIX 4.33/4.1.20, HP-UX
10.20/4.1.20, HP-UX 10.20/4.1.40 without any problems.

Having recompiled I am getting the following error when I run the

HPD/Micro Focus Cobol Errors                                        
Execution error : file '/opt/users/programs/ifa/IFA54RN/PFS2150.gnt'
error code: 114, pc=0, call=107, seg=0                              
114     Attempt to access item beyond bounds of memory (Signal 10)  
HP/MF COBOL Version: v4.1.40                                        
HP-UX hp9000 B.11.00 A 9000/806                                     
pid: 4483 gid: 20 uid: 116                                          

I have managed to isolate where the program is falling over, here is a
section of the code:

MOVE WC-KEY(WC-IND) TO WPFS9260-KEY.              
CALL "PFS9260" USING WS-COMMON,                   
IF WPFS9260-APPLIED-TO = "Y"                      
   GO TO CD999-EXIT.                              
MOVE WC-KEY(WC-IND) TO WPFS9290-KEY.              
offending line
CALL "PFS9290" USING WS-COMMON,                   
IF WPFS9290-ERROR = "Y"                           
   GO TO CD999-EXIT.                              

In the code above, the program falls over with the error mentioned
above on the line indicated.

Interestingly though, if I put in a DISPLAY statement just prior to
the offending line, as shown in the code above, the program runs
through without any problem.

The other thing is that if I run just the .int, (renamed the .gnt)
then the program works fine. So it appears that the problem lies in
the gnt and something is getting corrupted. We've done the usual of
updating the machine to the latest OS patches.

Does anyone have any ideas of how to get around this. I don't think
the problem lies with the code (although not a 100& sure), since this
same program is compiled on various different platforms running our
other versions of Unix and Cobol. So if there were a problem in the
code, I'd expect to get the same problem on our other unix boxes.

Anyway - if anyone can give me some ideas to try out, I'd really
appreciate it.


3.Signal 11 error (core)

This statement gives core dump

  if( pError->pFileName[0] != '\0' )

can someone suggest why ?

This statement was failing in all our unix environments so we changed
it to:

if( !(pError->pFunctionName == NULL))

It worked for some environments then now again it failed in 1
Any idea ?

All memory allocation have been done.

4.pthread_create returns error code 11

i have a code that uses pthread, but when i use pthread_create()
method it returns error code 11. I have found out that this is often
because of exceeding the THREAD_MAX limit for the process. But i want
to use only about 24 threads at a given time, and i destroy the
threads (or atleast i thought so) can someone tell me what i am doing
wrong here it would be of great help! thanks!

 for (i=0; i<no_pairs; ){
        for (j=0; j<MAX_THREADS && i<no_pairs; j++,i++){
            data[j].a = seeds[i/no_seeds];
            data[j].b = seeds[i%no_seeds];
            data[j].N = N;
            data[j].L = nones+nzeros;
            data[j].p1 = get_string (seeds[i/no_seeds], nzeros
            data[j].p2 = get_string (seeds[i%no_seeds], nzeros
            data[j].results = pairs[i];
            rc = pthread_create (&threads[j], &attr, run_actree, (void
            if (rc) {
                printf ("ERROR; return code from pthread_create() is
\n", rc);
                exit (-1);
        for (k=0; k<j; k++){
            rc = pthread_join (threads[k], &status);
            if (rc) {
                printf("ERROR; return code from pthread_join() is %d
\n", rc);

    pthread_attr_destroy (&attr);

Above is the main loop i create threads in, MAX_THREADS = 24

Any help as to where i am going wrong is greatly appreciated.

5.comp.lang.ada Digest, Vol 19, Issue 114

6. oracle10g SQLBEX giving 114 with Oracle Dynamic SQL Method 4 (ora9 works well)

7. errore 114

8. Server Express 64bit and Oracle 9i problem (114) on AIX 5.2

Return to cobol


Who is online

Users browsing this forum: No registered users and 60 guest