Microfocus Server Express 64-bit COBOL with Solaris 9


We are having trouble getting the 64-bit COBOL from Microfocus (4.0 SP2) to compile cleanly with Solaris 9 (64-bit).  We think we have a 32-bit and 64-bit library mismatch, but we aren't sure what else to try to fix this.   The error message that we see is "114     Attempt to access item beyond bounds of memory".
Who is Participating?
jimennisConnect With a Mentor DirectorAuthor Commented:
Our issue turned out to be the pathing for the as command.  We had to revise pathing to use the gnu 'as' command to resolve our issue with the 64-bit version of COBOL.

to check your installed solaris whether is 32 or 64 bit, use the command

isainfo -v

for more info man isainfo

Please see the linkbelow:


jimennisDirectorAuthor Commented:
The server is set for 64-bit support and can handle 32-bit applications also,

pluto:/usr/lib/cobol#isainfo -v
64-bit sparcv9 applications
32-bit sparc applications

with 64-bit kernel support:

pluto:/usr/lib/cobol#isainfo -vk
64-bit sparcv9 kernel modules
Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.


How do you find the link provided ?
Brian UtterbackPrinciple Software EngineerCommented:
Are you getting this error at compile time or run time? This is a the error message that the Cobol runtime
returns when a SEGV is detected. If you get this at compile time, it indicates that the compiler itself
is crashing.

A common cause of this error on Micro Focus Cobol is using incompatible index or animator files. If you have
indexed data files, you may need to rebuild them, the same if you have animator files from a previous
version of the compiler or files built on a different platform.
jimennisDirectorAuthor Commented:
The error is occurring after compilation, when the program is running.  I will check with my programmer on Monday (I am out of state) about any indexes that we might be using.
I think of the following possibilities;
1) Parameters passed by modules compiled in 32-bit mode being accessed in a module compiled in 64-bit mode
2) Index overflow of an array (trivial ... probably your programmer would have checked)
3) Reading "File Section" definition mismatch with the actual file on the disk ... probably your 32-bit/64-bit mismatch may kick in particularly for variables defined as COMP, COMP-1, COMP-2 etc as the storage space used while creation which I guess could be in 32-bit environment will be different in 64-bit environment. Check MF cobol COMP, 1, & 2 definitions for number of bytes allocated
I hope the above help
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.