Service Console commands

Edit online

The Service Console supports the ras1 command, which is especially useful for dynamically enabling and disabling RAS1 traces. The documentation requests from IBM® Software Support may conflict with your availability requirements. The ras1 command can be used to alter KBB_RAS1 tracing parameters dynamically without the need to recycle the product. The Service Console also supports the bss1 command, which is also useful for troubleshooting.

Important: The content in this section was created for and applies to the original persistent data store, referred to as PDS V1. A new PDS version (referred to as PDS V2) now exists. PDS V1 will eventually be deprecated.
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 disable it with the following service console command: 
ras1 set (UNIT:kpx ANY)
The ras1 command is paired with one of the following subcommands:
log
Display RAS1 log capture buffer.
list
List the RAS1 filters in effect.
set serviceunit
Control traces and filters for serviceunit
To see what tracing is already in effect, submit the following command: 
ras1 list
Note:
  1. The information inside the parentheses may be case-sensitive. Use the values provided by IBM Software Support.
  2. 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 bss1 command manages BSS1 (Basic System Services). 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 setting of KDC_DEBUG: 
BSS1 CONFIG KDC_DEBUG=Y