Created On: 11 November 2011
Problem:
Normally, when there is a COBOL program abend and a runtime error is returned, the name of the program in which the error occurred is displayed.
However, there was an issue where error code 114 - Attempt to access item beyond bounds of memory (Signal 11) – was being returned from many COBOL programs in the application. However the program name was not being displayed in the error message. For example:
Execution error : file ‘’
Error code: 114, pc=0, call=1, seg=0
114 Attempt to access item beyond bounds of memory (Signal11)
Normally, the name of the program would be inside the quotes: Execution error: file ‘prog_name’.
Because as there was no file name included they were unable to identify which program was returning the error.
Further testing showed that the error was occurring after the program had completed the execution of all code – i.e. the error was occurring on exit.
The client was running Server Express 5.1 WrapPack 5 on HP-UX 11.23 PA-RISC.
The same programs recompiled and tested on other HP-UX machines did not return the 114 error.
However, there was an issue where error code 114 - Attempt to access item beyond bounds of memory (Signal 11) – was being returned from many COBOL programs in the application. However the program name was not being displayed in the error message. For example:
Execution error : file ‘’
Error code: 114, pc=0, call=1, seg=0
114 Attempt to access item beyond bounds of memory (Signal11)
Normally, the name of the program would be inside the quotes: Execution error: file ‘prog_name’.
Because as there was no file name included they were unable to identify which program was returning the error.
Further testing showed that the error was occurring after the program had completed the execution of all code – i.e. the error was occurring on exit.
The client was running Server Express 5.1 WrapPack 5 on HP-UX 11.23 PA-RISC.
The same programs recompiled and tested on other HP-UX machines did not return the 114 error.
Resolution:
This was determined to be a linker issue on the HP machine. It was not a Micro Focus issue and was acknowledged by HP.
The problem was being caused during compilation.
The resolution was to install the latest linker patches from HP. Specifically; they needed a patch that includes a fix for QXCR1001052562, dated November 2010 or later. The version of /usr/ccs/lbin/ld32 should be 11.70 or later.
Please check the following link:
http://archives.neohapsis.com/archives/hp/2011-q1/0008.html
If you look in this document for QXCR1001052562, you’ll find reference to 11.23 and patch PHSS_41491. This is the fix to apply, but if in doubt then cross check with HP.
Also, look in the following HP document for reference to PHSS_41491
http://h21007.www2.hp.com/portal/site/dspp/menuitem.863c3e4cbcdc3f3515b49c108973a801/?ciid=8b080f1bace021100f1bace02110275d6e10RCRD
Please note that these are linker issues, so the patches must be applied to the machine on which the programs are compiled. All programs must be recompiled once the patches have been installed. Applying these to the production machine will not resolve the error.
This error is very specific to this platform and linker patch versions.
The problem was being caused during compilation.
The resolution was to install the latest linker patches from HP. Specifically; they needed a patch that includes a fix for QXCR1001052562, dated November 2010 or later. The version of /usr/ccs/lbin/ld32 should be 11.70 or later.
Please check the following link:
http://archives.neohapsis.com/archives/hp/2011-q1/0008.html
If you look in this document for QXCR1001052562, you’ll find reference to 11.23 and patch PHSS_41491. This is the fix to apply, but if in doubt then cross check with HP.
Also, look in the following HP document for reference to PHSS_41491
http://h21007.www2.hp.com/portal/site/dspp/menuitem.863c3e4cbcdc3f3515b49c108973a801/?ciid=8b080f1bace021100f1bace02110275d6e10RCRD
Please note that these are linker issues, so the patches must be applied to the machine on which the programs are compiled. All programs must be recompiled once the patches have been installed. Applying these to the production machine will not resolve the error.
This error is very specific to this platform and linker patch versions.
Old KB# 35204
