Make debug variables available in TRACE DEBUG as they are available in TRACE FATAL

Description: Extend the TRACE logging functionality to include debug variables in TRACE and DEBUG levels, similar to the existing behavior in TRACE FATAL. This will provide more detailed information during debugging and troubleshooting.

Use Case: Developers need to diagnose complex JCL issues and require access to variable values to understand program behavior at a granular level. Currently, this is only possible with TRACE FATAL, which is too verbose for general debugging.

Proposed Solution:

• Modify the logging mechanism to include debug variables when TRACE or DEBUG is specified.
• Ensure that the existing TRACE FATAL level is unaffected.
• Provide a configuration option to control the inclusion of debug variables in TRACE/DEBUG (e.g., a flag in the jclx_config.ini file).
• Maintain the current log output format, extending it to include variable information.

Benefits:

• Improved debugging capabilities.
• Increased developer efficiency by providing necessary information at appropriate log levels.
• Reduced need for excessive logging or code modifications to diagnose issues.

Example:

• Current behavior (jclx -l FATAL): Debug variables are included in the log output.
• Enhanced behavior (jclx -l DEBUG): Debug variables are now included in the DEBUG log output.

Considerations:

• Potential performance impact of variable collection.
• Configuration options to enable/disable this feature.
• Security implications of logging variable data (e.g., sensitive information).
• Log volume increase and management.