KDS_X_TEMS_DEBUG_TRACE
This parameter determines whether to activate TMS:Engine debugging services.
- Required or optional
- Optional
- Location where the parameter value is stored
- KDSSYSIN member of the rhilev.rte.RKANPARU library
for the runtime environment of the monitoring server
- Parameter name and syntax
DEBUG(N|Y)- Default value
DEBUG(N)- Permissible values
DEBUG(N)orDEBUG(Y)
- PARMGEN name
- KDS_X_TEMS_DEBUG_TRACE
- Description
- Determines whether to activate TMS:Engine debugging services.
A setting of
Yautomatically turns on the internal trace with the default number of entries (1024), resulting in an increase in CPU use, storage use, and number of messages issued. The amount of increase depends on the activity in the Tivoli Enterprise Monitoring Server address space.The setting for this parameter and the setting for the KDS_X_TEMS_STORAGE_STGDEBUG parameter interact.
- If the KDS_X_TEMS_STORAGE_STGDEBUG parameter is included (not commented out and not deleted), the KDS_X_TEMS_DEBUG_TRACE parameter must precede it. Otherwise, KDS_X_TEMS_DEBUG_TRACE overrides KDS_X_TEMS_STORAGE_STGDEBUG.
- If the KDS_X_TEMS_STORAGE_STGDEBUG parameter
is commented out or omitted, and the setting for KDS_X_TEMS_DEBUG_TRACE is
Y, basic storage debugging is turned on, causing an increase in storage use. - If the setting for the KDS_X_TEMS_STORAGE_STGDEBUG parameter
is
N, and the setting for KDS_X_TEMS_DEBUG_TRACE isY, no storage debugging is performed. - If the setting for the KDS_X_TEMS_STORAGE_STGDEBUG parameter
is
YorX, and the setting for KDS_X_TEMS_DEBUG_TRACE isN, storage debugging is performed, but no other debugging is performed.
- Related parameters
-
- KDS_X_TEMS_STORAGE_STGDEBUG
- KDS_HUB_* parameters (values for the Primary HUB TEMS that the z/OS Remote TEMS reports to)