Ambiguous File Error

Problem: Your application gets an error and aborts, returning an ambiguous AcuServer error message (9D). For example:

FILE ERROR #9D ON SEQ1.DAT
MYAPP ABORTED

Diagnostics

Run your application again with the -x option:

runcbl -x your-usual-options program-name

This time when your application gets the error, the runtime will report the extended error code and associated error text. For example:

File system error value = 102
Invalid connection password specified by client

If your runtime options include the -e switch to redirect error output to a log file, look for the extended error message in your log file.