Use the following syntax from the Enterprise Developer command line to configure CTF dynamically.
At the prompt, enter:
cblctd <option-list>
where <option-list> is one or more of the following, separated by spaces:
| Syntax | Overview | Description |
|---|---|---|
| -Ct <component-name>:<property>[,<property>...] | Enable component properties | Sets each of the properties for the given component-name to true.
Example: -Ct mf.rts:memory,api |
| -Cf <component-name>:<property>[,<property>...] | Disable component properties | Sets each of the properties for the given component-name to false.
Example: -Cf mf.rts:memory,api |
| -Cv <component-name>:<property>=<value> | Set component property | Sets the property of the given component-name to the given value.
Example: -Cv mf.rts:api=true |
| -Et <emitter>:<property>[,<property>...] | Enable emitter properties | Sets each of the properties for the given emitter to true. (This change will only apply if no events have yet been output
by the emitter.)
Example: -Et textfile:MultiProc |
| -Ef <emitter>:<property>[,<property>...] | Disable emitter properties | Sets each of the properties for the given emitter to false. (This change will only apply if no events have yet been output
by the emitter.)
Example: -Ef binfile:Rununitld |
| -Ev <emitter>:<property>=<value> | Set emitter property | Sets the property of the given emitter to the given value. (This change will only apply if no events have yet been output
by the emitter.)
Example: -Ev textfile:file=myctf.log |
| -Dd <emitter> | Add emitter to default emitter list | Adds the given emitter to those used by default for the duration of the process. (This change will only apply if no events
have yet been output by the emitter.)
Example: -Dd binfile |
| -Dr <emitter> | Removes emitter from default list | Removes the given emitter from those used by default. (This change will only apply if no events have yet been output by the
emitter.)
Example: -Dr binfile |
| -Lc <component>:<level> | Sets component trace level | Set the component trace level that determines which events are emitted.
The level can be one of:
Examples: -Lc mf.rts:d and -Lc mf.rts:info |
| -f <filename> | Include options from text file |
<filename> is a text file containing dynamic CTF options on one or more lines.
Example: -f myctf.log |
| -p <process-id> | Application process ID |
The <process-id> of the COBOL application whose CTF settings are to be modified. This must be an application already executing with CTF enabled using MFTRACE_CONFIG. This option is mandatory if any of the above options have been specified. The <process-id> is the operating system's process identifier number for the COBOL application. It can be specified as a decimal integer, or an octal value (that is, base 8) if the integer begins with a leading zero. It can also be a hexadecimal value if it begins with a 0x. The required <process-id> can be determined using tools that form part of your operating system. For example, Task Manager on Windows . Examples: -p 1234 or -p 0x1234 |
| -q | Quiet output | Suppresses output of the banner. A message is still output if the command is unsuccessful.
|
| -h | Help | Displays help for the available options. |