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

cobol

    Sponsored Links

    Next

  • 1. COBOL Versions & SQL
    I wanted to ask everyone a question for a relative newbie. most of the cobol I've done has had some form of SQL, depending on the version of the DBMS, embedded in the COBOL itself. This is how I thought it had to be done. This applies to both SQL code for RDBMS and file reads for VSAM-type files. My question is, are there versions of COBOL out there that allow SQL to be called outside a program, or by language design, must the SQL be embedded in the COBOL programm and cannot be handled externally. Thank you very much in advance for your help!
  • 2. Standard way to implement ASCII control chars
    Using only COBOL 85 syntax, what is a portable method of representing ASCII control character values in a PIC X(1) field? The problem that I have encountered is that two separate vendors, claiming to produce COBOL 85 Standard syntax, both end up with a field like LINE-FEED PIC X(1) VALUE X'0A' in their code. To the best of my knowledge hex constants are non-standard (though widely implemented) and my compiler (Unisys 2200 series UCOB) will not accept that. For my specific compiler I know how to do this rather simply but that is based on either vendor extensions or knowledge of USAGE BINARY allocation rules which are also vendor specific. The best I've been able to muster so far as a solution would be MOVE FUNCTION CHAR(10) TO LINE-FEED. It should work but the function is collating sequence aware so would only hold true if an ASCII collating sequence were being used. I'm sure there is a common solution to this that I have overlooked so any help would be appreciated. Douglas Gallant
  • 3. Oracle Indicator Variables
    We're switching from Compaq Cobol to Microfocus Cobol and are having trouble with indicator variables. When doing selects, the query doesn't always return the correct results, and when doing updates, we receive date and number errors. The programs and variables work correctly under the Compaq Cobol and have for several years. Executing the same queries in SQL/Plus or TOAD will also return the correct results. Does anyone have any suggestions as to what is causing this and how we can correct it? Thanks, Dan

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
@
 http://www.**--****.com/ 
22indx.htm

Check the User's Guide, Chapter 7.

Simon.



Similar Threads:

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

Hi,

I'm trying to run a cobol program and calling "DBOPEN" with parameters
such as IMAGE-BASE, IMAGE-PASSWORD, IMAGE-MODE, IMAGE-STATUS.

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,
Vinod

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
program:

-------------------------------------------------------
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,                   
                     WPFS9260-PARAMETERS.         
IF WPFS9260-APPLIED-TO = "Y"                      
   GO TO CD999-EXIT.                              
MOVE WC-KEY(WC-IND) TO WPFS9290-KEY.              
DISPLAY "NOW MOVED WC-KEY..."
MOVE WC-NEW-DOCAPPNO(WC-IND) TO WPFS9290-APPLY-TO. <-----------
offending line
CALL "PFS9290" USING WS-COMMON,                   
                     WPFS9290-PARAMETERS,         
                     FFS031-SAVE-RECORD.          
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.

thanks
phil

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
environment.
 
Any idea ?

All memory allocation have been done.

4.Error 114 in Microfocus Server Express 2.2 when calling C functions

Are you executing with the threaded COBOL run-time? This is necessary on
HP-UX due to Oracle linking their own libraries with the threaded C run-time
on this platform.

If the code causing the RTS114 is the C code, which is calling Oracle
functions, does this trap, or fail in any other way, if you run it
standalone (i.e. without COBOL)?

Regarding your final point :

> Do you know a run-time option or a compiler option to prevent this error
> ? Microfocus support is not very quick in finding something...

Have you contacted SupportLine with a cutdown sample which demonstrates this
problem? It sounds like you've isolated where the problem is occuring which
is good, but is the NULL pointer due to a corruption coming from COBOL?

SimonT.


5.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
+nones-1);
            data[j].p2 = get_string (seeds[i%no_seeds], nzeros
+nones-1);
            data[j].results = pairs[i];
            rc = pthread_create (&threads[j], &attr, run_actree, (void
*)
&data[j]);
            if (rc) {
                printf ("ERROR; return code from pthread_create() is
%d
\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);
                exit(-1);
            }
        }
    }

    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.

6. Access Violation - Error Code 2 - Error SubCode 5333 - App Start Line 68

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

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



Return to cobol

 

Who is online

Users browsing this forum: No registered users and 4 guest