CTF trace is not working on 2.3 U2 on Linux

The situation:

CTF trace is not working on 2.3.2 U2 on SUSE Linux. This ctf trace config file has worked for years
but for some reason it no longer works in the Linux environment, however this CTF configuration
file still works in the Windows environment.

These are the settings in the ES-Environment:
 
[ES-Environment]
ES_ROOT=/home/mfcobol/ES/$ES_SERVER
MFTRACE_CONFIG=$ES_ROOT/SYSTEM/CONFIG/ctf.cfg
MFTRACE_LOGS=$ES_ROOT/SYSTEM/CTFLOGS
 
version @(#)cob.c            2.3.2.29
PRN=KXCSU/AAF:Ao.U4.13.04
PTI=32/64 bit
PTI=Micro Focus Enterprise Developer Unix Components 2.3 - Update 2
PTI=Update 2
PTI=pkg_135843
PTI=RPM
PTI=ES
PTI=SOA Configured
 
The directory structure exists and is all owned by “mfcobol”, the owner of the ES region.
The CTF config file contains the following but when the region is started nothing is written
to the CTFLOGS directory.
 
CTF.cfg
 
# MFTRACE configuration file
 
mftrace.application               = cassi
mftrace.dest                      = textfile
mftrace.emitter.textfile#Format   = $(TIME) $(THREAD) $(COMPONENT) $(EVENT) $(LEVEL) :$(DATA)
mftrace.level.mf.esxa             = debug
## Enable all tracing
mftrace.comp.mf.esxa#all          = true
 
################################################
# CASSPOOL Tracing
################################################
mftrace.level.mf.mvs.casspool           = debug
mftrace.comp.mf.mvs.casspool#restart    = true
 
################################################
# MVSRGDG Tracing
################################################
mftrace.level.mf.mvs.mvsrgdg            = debug
mftrace.comp.mf.mvs.mvsrgdg#entry      = true
mftrace.comp.mf.mvs.mvsrgdg#restart    = true
 
################################################
# JCL Tracing
################################################
mftrace.level.mf.mvs.mfjcl              = debug
mftrace.comp.mf.mvs.mfjcl#msgs          = true
mftrace.comp.mf.mvs.mfjcl#pgm           = true
 
################################################
# MJRM Tracing
################################################
mftrace.level.mf.mvs.mjrm               = debug
mftrace.comp.mf.mvs.mjrm#entry          = true
mftrace.comp.mf.mvs.mjrm#enq            = true
 
################################################
# MVSCATIO Tracing
################################################
mftrace.level.mf.mvs.mvscatio           = debug
mftrace.comp.mf.mvs.mvscatio#entry      = true
 
################################################
# RTS Tracing
################################################
mftrace.level.mf.rts                    = debug
mftrace.comp.mf.rts#pgmsearch           = true
mftrace.comp.mf.rts#pgmload             = true
 
################################################
# Filehandler Tracing
################################################
mftrace.level.mf.mffh.xfh               = debug
mftrace.comp.mf.mffh.xfh#all            = true


The resolution:


The crux of the matter lies with the

    mftrace.application               = cassi

entry in the configuration file. If this is changed to

    mftrace.application               = cassi32

or

    mftrace.application               = cassi64

(depending on the system's bit-mode) the CTF trace logs will
be produced.