Service Console commands

The Service Console supports the ras1 command, which is especially useful for dynamically enabling and disabling RAS1 traces. It also supports the bss1 command, which is also useful for troubleshooting.

The ras1 command can be used to alter KBB_RAS1 tracing parameters dynamically without the need to recycle the product.

The ras1 command is paired with one of the following subcommands:

log
Display RAS1 log capture buffer.
list
List the RAS1 filters in effect.
ctbld
Display the resident CTBLD data.
set serviceunit
Control traces and filters for serviceunit
units
Display the registered compilation units.
Remember:
  • The information inside the parentheses might be case-sensitive. Use the values provided by IBM® Software Support.
  • The settings set by Service Console commands remain in effect for the current activation of the product. After the product is recycled, the original trace settings are restored.
  • The documentation requests from IBM Software Support might conflict with your availability requirements.
For example, you can issue the following ras1 command from the Service Console to enable the kpx trace: 
ras1 set (UNIT:kpx ALL)
After you capture this trace, you can turn off tracing with the following service console command: 
ras1 set (UNIT:kpx ANY)
To turn on the control flow trace for the IBM MQ Monitoring Agent, the command is:
ras1 set (COMP:KMQ Flow)
To turn off tracing for the kbbcrcd class of the Windows™ OS agent, the command is:
ras1 set (UNIT:kbbcrcd ANY)
To see what tracing is already in effect, submit the following command: 
ras1 list
The bss1 command manages Basic System Services (BSS1). The command is paired with one of the following subcommands:
listenv
Display the resident TMS:Engine variables.
getenv envvar
Display environment variable, where envvar is any variable that can be returned from listenv.
setenv envvar
Assign an environment variable where envvar is any variable that can be returned from listenv.
info
Display BSS1_Info() data
config debugenv
Modifies the settings of the TMS:Engine debug environment variables: RES1_DEBUG, KDH_DEBUG, KDC_DEBUG, and KDE_DEBUG. The possible values, from most to least tracing messages, are: M (Max), D (Detail), Y (Yes) and N (Nominal). For example, the following config command alters the KDC_DEBUG variable value: 
BSS1 CONFIG KDC_DEBUG=Y