Skip to Content
Information
Limited support BMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Batch Optimizer (Advanced and Standard) 2.9.

Internal trace management

Internal tracing can be activated when Job Optimizer Pipes is started or during Job Optimizer Pipes execution, and it can be modified or stopped during Job Optimizer Pipes execution. Under normal circumstances, the tracing facilities are dormant, but the setting can be displayed.

When activated, the trace information is either printed to the PRTDBG and DADUMP DD statements that are defined in the Job Optimizer Pipes Started Task procedure, or issued to the console (depending on the process that produces the trace information).

Tracing can be requested for specific components, a specific job, or a pipe. Each component has its own identifying numbers to produce the trace. These numbers are called the trace level. One or more trace levels can be activated at the same time. Trace levels can be modified during execution.

Customer Support can provide you with the list of the trace levels that should be used, depending on the problem that was encountered.

This section provides the following topics: 

Related topics

Problem-determination-commands

Glossary



 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

MainView Batch Optimizer (Advanced and Standard) 2.8