The SEGV is a secondary consequence of things spinning out of control after the initial triggering error which is a stack overflow on a file open statement. The core dump suggests that there are 301 files open at that point (after 2443 opens and closes), which leads me to suspect that your FILES= allocation in the miame.ini might only be set to 300? In that case, the error is legitimate (for better or worse, that is the official error for overflowing the file allocation table, even though it's a bit confusing since that doesn't sound like "stack overflow").
That doesn't justify the SEGV during the error trapping, but the fact that the error trapping is also trying to open files is leading to a kind of death spiral. I'll study that to look for a more elegant way to handle it, but first let's confirm the diagnosis of the initial stack overflow.
