Enabling CTF Tracing for MFBSIEMX

MFBSIEMX, the Event Manager user exit for MFBSI is CTF-enabled. Its activity can be traced using the Enterprise Developer Consolidated Tracing Facility. Use the following procedure to enable tracing for MFBSIEMX:

  1. Create a text file using this sample: 
    # MFTRACE configuration file

#mftrace.emitter.textfile#Format = $(TIME) $(THREAD) $(COMPONENT) $(EVENT) $(LEVEL) :$(DATA)
#mftrace.emitter.textfile#location = C:\MicroFocus\ProjectName\ES_JCL\MFBSI\ES-MFBSI

mftrace.dest                     = binfile
mftrace.emitter.binfile#location = C:\MicroFocus\ProjectName\ES_JCL\MFBSI\ES-MFBSI

mftrace.level                 = none
mftrace.level.mfbsi           = info
mftrace.comp.mfbsi.emx#all    = true

    Replace C:\MicroFocus\ProjectName\ES_JCL\MFBSI\ES-MFBSI with your CTF trace files folder.

  2. Access your configuration information and add the line MFTRACE_CONFIG=[Full_Location_of_CTF_cfg.file] to your configuration file.

    For example:

    MFTRACE_CONFIG=C:\MicroFocus\ProjectName\ES_JCL\MFBSI\ES-MFBSI\ctf.cfg

  3. Stop and restart your enterprise server.
  4. In the CTF folder, verify that a file named castrc.textfile.log exists. The file created is based on the emitter selection. In Windows, the bin file can be examined with the CTF Viewer.
    Event Description
    0 MFBSIEMX initialization started.
    1 MFBSI_DIR setting not found.
    2 File can not be created in the folder specified by MFBSI_DIR. Check the file status code.
    3 MFBSIEMX initialization ended.
    9 Enterprise server shutdown process started.
    10 Job execution started.
    11 Job execution ended.
    12 Job concluded.
    19 Batch SEP termination.
    20 Unexpected file status during MFBSIEMX execution.
    Note: File status 0/005 in the associated data usually indicates a JCL error.
Parent topic: Additional Notes