Configuration Variables for Dynamic Runtime Tracing

Use the following configuration variables in the dynamic runtime tracing configuration file (analyze.process-ID.cfg).

`OUTPUT_FILENAME_PATTERN`	This variable determines the name of the report file that the tracing output is written to. Use the following special parameters to help configure the name: If the file name starts with a plus sign ("+"), the report is appended to the specified file. By default, a new report overwrites the specified file. If the name contains the string `%p`, when the report is generated that string is replaced with the process ID (PID) of the runtime from which the report originates. If the name contains the string `%d`, that string is replaced with the current date in the form YYYYMMDD where YYYY is the year, MM month and DD day. If the name contains the string `%t`, that string is replaced with the current time in the form HHMMSSTTT where HH is the hour, MM minute, SS second and TTT milliseconds. If the name contains the string `%u`, that string is replaced with the username. If the name contains the string `%h`, that string is replaced with the hostname. Default value: analyze.`process-ID`.rpt
`FILE_IO`	This variable determines the type of file IO operations that are traced. In the following example, only the OPEN and CLOSE operations are traced: FILE_IO OPEN CLOSE Permissible values: any combination of MAKE, OPEN, CLOSE, READ, NEXT, PREVIOUS, START, WRITE, REWRITE, DELETE, UNLOCK, or ALL (TRUE or ON) to trace all - Default value: 0
`PROGRAM_INFO`	The variable determines the type of program operations that are traced. In the following example, only the CALL and PERFORM operations are traced: PROGRAM_INFO CALL PERFORM Permissible values: any combination of CALL, CALLSUB, EXIT, CANCEL, PERFORM, ENTER, LEAVE, or ALL (TRUE or ON) to trace all (except CALLSUB - this must be specified explicitly to trace calls within the sub() function) - Default value: 0 Note: The PERFORM, ENTER, and LEAVE operations relate to performing, entering, and leaving a section or paragraph during a PERFORM statement. Tracing these operations requires that your program was compiled for symbolic debugging (-Gs).
`COLLECT_STATS`	When set to TRUE, a Counts section at the end of the tracing output that keeps a count of the traced FILE_IO and PROGRAM_INFO operations. If both FILE_IO and PROGRAM_INFO are not set, this variable has no effect. Permissible values: TRUE, FALSE - Default value: TRUE
`DUMP_RUNTIME_STATE`	When set to TRUE, the current state of the program being traced is included, as long as the program was compiled for symbolic debugging (-Gs) and with line number mapping enabled (-Gl). When TRUE, the runtime configuration variables that control the Abend Diagnostic Report (ACU_DUMP_WIDTH and ACU_DUMP_TABLE_LIMIT) will be honored when dumping the program state. See Using the Abend Diagnostic Report (ADR) for more information. Note that the dump is written to the report specified by OUTPUT_FILENAME_PATTERN (the ACU_DUMP_FILE variable is ignored in this situation). Permissible values: TRUE, FALSE - Default value: TRUE