AcuServer error 9D,110



AcuServer process returns a file status 9D,110.

What is the meaning of this error code?
What may be the cause and how to solve it?


The first important thing to do to analyze 9D errors is to record two important trace files: one for the runtime, one for the AcuServer process/daemon.

To record an ACUCOBOL-GT Runtime trace file, the following environment variables should be added to the runtime configuration file (cblconfi):


The information will be written into a text file.
To customize this file name and location and to collect a list of configuration variables loaded by the process itself, add the following -le flag to the runtime launch script:

wrun32.exe/runcbl -le c:\tmp\acuruntime.%p.log [any further flag] [program name]

To record an AcuServer trace file, the process must be stopped and restarted using the proper options.
This operation requires any clients to be stopped in advance, to avoid any possible ungraceful disconnection or further 9D errors.

To set the AcuServer logging, the process must be restarted this way:

acuserve -start [-c config] -e /tmp/acuserver.log -l -t 7 [-n portnum]

When both trace files are generated, they can be sent to the Micro Focus Customer Care for analysis.

With references to the 9D,110 error, AcuServer trace file may show a line like the following:

8433921 - signal 11 caught - Shutting down

Searching through the internet (it's a Linux error, rather than an AcuServer one), signal 11 means "segmentation fault".
It's a memory access violation on linux/UNIX systems.

This error may be caused by hardware failures, i.e. damaged disk area, corrupted Vision files, memory segments no more accessible.

A possible solution stands in rebuilding the Vision file that caused this issue, when possible.

Further help related to the signal 11 error caused by the hardware is available online.

A Guide for Troubleshooting a Segfault

Why Does The Segmentation Fault Occur on Linux / UNIX Systems?

What is a "segmentation violation"?

Comment List