Created On: 19 September 2012
Problem:
In certain instances CTF traces are not generated as expected. This can be caused by mftrace being set somewhere else in the environment variables and sometimes this can be hard to find.
Resolution:
Stop the ES Region
Open the Enterprise Developer command prompt and type
SET MFTRACE_CONFIG=C:\LOGS\CTF.CFG
next
MFTRACE_LOGS=C:\LOGS
next
CASSTART /RCICSSERV
If CICSSERV is the region name. Recreate and see if log files are generated now.
To Stop the region when you start this way you must stop using the following command:
CASSTOP /RCICSSERV
* C:\LOGS must exist and CTF.CFG must exist within the C:\LOGS directory.
Open the Enterprise Developer command prompt and type
SET MFTRACE_CONFIG=C:\LOGS\CTF.CFG
next
MFTRACE_LOGS=C:\LOGS
next
CASSTART /RCICSSERV
If CICSSERV is the region name. Recreate and see if log files are generated now.
To Stop the region when you start this way you must stop using the following command:
CASSTOP /RCICSSERV
* C:\LOGS must exist and CTF.CFG must exist within the C:\LOGS directory.
Incident #2585243
Support
Documentation
Training
Partner Portal
