Activate trace
Component: | BS2000 |
Functional area: | Error logging |
Domain: | ERROR-LOGGING |
Privileges: | TSOS |
Routing code: | R |
Function
The START-TRACE command is used to activate the switchable traces. Traces serve to document certain process developments independently of a problem situation. The traces are stored in memory and are overwritten with a wrap-around algorithm.
Both permanent and temporary traces are recorded.
Temporary, switchable traces can be activated for diagnosing problem situations of a development or test phase.
In BS2000 operation, traces are managed by the trace manager, which allows subsystems to report traces via a program interface. The trace manager also supports diagnostic data preparation (for CDUMP) and evaluation (for SODA and DAMP) for all connected traces.
Format
START-TRACE | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
Operands
TRACE-IDENTIFICATION =
Specifies whether all or only specific traces from the list of switchable traces are to be activated.
Possible values are listed in the following table:
Trace ID | Brief description |
|---|---|
CCOPY | CCOPY trace |
CMSTRACE | CMS trace |
CUIRTR | CUIR trace |
DISKAI | Trace for disk attention interrupt processing |
DIVTRACE | DIV trace |
DLMTRACE | DLM trace |
DPRTCOM | DPRINTCM communication trace |
EMMIO | EMMIO trace |
FITC | FITC trace |
GSVOLEVT | Trace for GSVOL |
MAILCEVT | Trace for mail sender (MAILCLNT subsystem) |
MRSCAT | MRSCAT occupation trace |
MSCFLOG | Trace for MSCF errors |
NDVMTRAC | BAVOLMON I/O trace |
PRNGDEVT | Trace for random number generator (PRNGD subsystem) |
SM2EVENT | SM2 error trace |
SM2FUNCT | SM2 trace for user call |
TBOURSE | ETMBOWK trace |
TDISAM | K-ISAM trace |
TDISAMNK | NK-ISAM trace |
TFASTPAM | Trace of the access method |
TJLOGLOW | JMS trace |
TJOBPOOL | JMS-JOBPOOL trace |
TLOCK | Task lock management trace |
TNDM#ALL * | Trace for all NDM FE |
TNDM#NKA | Trace for FE NKA module |
TNDM#NKD | Trace for FE NKD module |
TNDM#NKG | Trace for FE NKG module |
TNDM#NKL | Trace for FE NKL module |
TNDM#NKR | Trace for FE NKR module |
TNDM#NKS | Trace for FE NKS module |
TNDM#NKT | Trace for FE NKT module |
TNDM#NKV | Trace for FE NKV module |
TRFA | Remote file access trace |
TRSOADM | RSO trace |
TSSVADM | SPOOL trace |
VMMALLOC | Trace for VM allocation |
*) | If the trace TNDM#ALL is switched on, all the other NDM traces (TNDM#...) are automatically set to the “ON” state. If any one of these traces is then deactivated by a STOP-TRACE, the NDM general trace TNDM#ALL is put into the “ON_OFF” state. |
TRACE-IDENTIFICATION = list-poss(51): <name 1..8>(...)
Specifies the names of up to 51 traces to be activated. The specified traces must be OFF (deactivated) or ON/OFF (trace is only partially activated, i.e. it collects information on different events).
If the traces involved are not statically defined, they are assigned to a specific subsystem that can be defined in more detail in the following operands.
SUBSYSTEM-NAME =
Specifies the subsystem to which the trace is assigned.
SUBSYSTEM-NAME = *ALL
The traces are to be activated in all cases, regardless of the subsystem to which they are assigned.
SUBSYSTEM-NAME = <name 1..8>
Exact specification of the subsystem to which the trace to be activated is assigned.
SUBSYSTEM-NAME = *NONE
Only statically defined traces that are not assigned to any subsystem are to be activated.
SUBSYSTEM-VERSION =
Specifies the version of the subsystem to which the trace is assigned.
SUBSYSTEM-VERSION = *ALL
The traces are to be activated for all versions of the selected subsystem.
SUBSYSTEM-VERSION = <product-version without-man-corr> / <product-version mandatory-man-corr>
Specifies the version number.
If a version number is specified, the format specified here must be identical to the format used when the subsystem was defined (release and correction status mandatory or not allowed; see also "SDF syntax representation").
TRACE-IDENTIFICATION = *ALL(...)
All traces are to be activated.
If the traces involved are not statically defined, they are assigned to a specific subsystem that can be defined in more detail in the following operands.
SUBSYSTEM-NAME =
Specifies the subsystem to which the trace is assigned.
SUBSYSTEM-NAME = *ALL
The traces are to be activated in all cases, regardless of the subsystem to which they are assigned.
SUBSYSTEM-NAME = <structured-name 1..8>
Exact specification of the subsystem to which the trace to be activated is assigned.
SUBSYSTEM-NAME = *NONE
Only traces that are not assigned to any subsystem are to be activated.
SUBSYSTEM-VERSION =
Specifies the version of the subsystem to which the trace is assigned.
SUBSYSTEM-VERSION = *ALL
The traces are to be activated for all versions of the selected subsystem.
SUBSYSTEM-VERSION = <product-version without-man-corr> / <product-version mandatory-man-corr>
Specifies the version number.
If a version number is specified, the format specified here must be identical to the format used when the subsystem was defined (release and correction status mandatory or not allowed; see also "SDF syntax representation").
Return codes
(SC2) | SC1 | Maincode | Meaning |
|---|---|---|---|
0 | CMD0001 | No error | |
1 | 0 | CMD0001 | Specified traces are already “on” |
2 | 0 | PDT0201 | One of the specified traces is already “on” |
32 | CMD0221 | Internal error | |
1 | 32 | PDT0203 | Specified trace not switchable |
2 | 32 | PDT0203 | One of the traces specified in the list is not switchable |
1 | 32 | PDT0210 | Invalid on/off pattern for the specified trace |
2 | 32 | PDT0210 | Invalid on/off pattern for one of the traces specified in the list |
1 | 64 | PDT0200 | One of the traces specified in the list does not exist |
2 | 64 | PDT0200 | Trace is of type PERMANENT |
1 | 64 | PDT0202 | Trace is of type PERMANENT |
2 | 64 | PDT0202 | One of the traces specified in the list is of the type PERMANENT |
64 | PDT0209 | No authorization for command | |
1 | 64 | PDT0214 | Activation of some traces was rejected with different error messages; no action taken |
2 | 64 | PDT0214 | Activation of some traces was rejected with different error messages; other specified traces were activated |