Service Console commands for troubleshooting: ras1 and bss1
The Service Console supports the following commands for troubleshooting: ras1 and bss1.
ras1
The ras1 command is useful for troubleshooting and is paired with one of the following subcommands:
Subcommand | Description |
---|---|
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. |
The ras1 command is especially useful for dynamically enabling and disabling RAS1 traces. The documentation requests from IBM Software Support might 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. For example, to enable the kpx trace, you can issue the following service console command:
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)
To see what tracing is already in effect, submit the following command:
ras1 list
- The information inside the parentheses may 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.
bss1
The bss1 command manages BSS1 (Basic System Services) and is paired with one of the following subcommands:
Subcommand | Description |
---|---|
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 BSS2_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:
|