Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

The status window (W2)

&pagelevel(5)&pagelevel

The status window provides an overview of the opened diagnosis object. The first four lines contain general information on the type of diagnosis object and on its environment during creation (e.g. BS2000 version, CPU type or memory size).
The status window is displayed automatically on opening the diagnosis object and contains the input fields “TID”, “TSN”, “Mode select” and “Window length”.

Figure 10: Input fields in the header line for the status window

Mode select

The information shown in the “Mode select” input field for the status window (W2) can be influenced by different modes. The possible modes are INF, TSK, PLK and SLK:

INF

Besides the standard details displayed in the first three lines of the status window, additional information on the dump generator, diagnosis object and selected  product is returned. The INF mode is set automatically if the dump file containsmore than one object (product), e.g. in the case of a complete VM2000 SLED.

DAMP can analyze the following objects:

  • active BS2000 system

  • system, user and area dumps with a BS2000 dump object

  • SNAP dump with a BS2000 dump object

  • SLED with a BS2000 dump object

  • SLED with a VM2000 dump object (complete VM2000 SLED)

  • SLED with a SLED dump object (SLED from a SLED / Dump from a SLED)

  • SLED with some other dump object such as SIR, for example

  • virtual machine (VM) under VM2000

  • predecessor system in SLED
    (predecessor systems are BS2000, VM2000 or other systems)

Example windows for the mentioned object types can be found as of "The status window (W2)".

The mode can be set by the user by means of the “INF” entry in the header line. If an object selection was made in dump files with multiple objects (complete VM2000 SLED, SLED from a SLED / Dump from a SLED), entering “-” / in INF mode cancels the selection.

In INF mode, as much information as possible is displayed. One exception is theso-called SELF-LOADER (see "Editing SLEDs without a BS2000 structure").
The following information is currently displayed:

  • the name of the dump file and the HSI of the analyzed object

  • the memory sizes of the analyzed object

  • the CPU type followed by Virtual Machine when a virtual machine is concerned
    (after live migration, the new system name followed by (after Live-Mig) is also output here)

  • the type and version of the dump generator of the object to be analyzed

  • the contents of the product ID; included in this is the name and the version of the product, and if available, the address of the so-called dump testament (contains internal SLED information).

By marking (see section "Marking" (Modifying the diagnostic windows)) the address of the dump testament, the memory contents of the dump testament can be output to a standard window with the RM or ABS addressing mode.

Depending on the dump file type, the following information is included:

  • For system, user, and area dumps
    the complete contents of the “dump title” dummy section.

  • In the case of a SLED

    • The contents of the BS2000 crash message with printable text.
      A VM2000 crash message is not recognized by DAMP.

    • The contents of the Time of Day register is output in edited form.

    • Information relating to additional dump objects, for example, PREVIOUS SYSTEM or DUMPED SYSTEM. In the case of a VM2000 dump object, an overall view of the virtual machines in the overall system is offered. The required dump object is selected by means of marking.

    • If a STARTUP dump exists, a message.

  • In the case of a SNAP dump

    • The address of the SNAP information.

    • The contents of the SNAP message.

    • Information relating to the $SNAP call, for example, the function area from which the call was started, the TSN of the caller, the address of the SNAP call, and the start address of the GP register record.

  • If the file to be analyzed is opened as a PAM file, details on the opened file, e.g. the file name, the file size and the last-page pointer, are automatically provided in this mode. 

Example windows for the various dump file types in INF mode  

Figure 11: Information screen in the status window (W2). Dump created by CDUMP. Dump object: BS2000 (SU x86 after Live Migration)

INF

Figure 12: Information screen in the status window (W2). Dump created by SNAP. Dump object: BS2000 (SU /390 after abnormal system termination)

Figure 13: Information screen in the status window (W2). Dump created by SLED. Dump object: BS2000 (S server)

Figure 14: Information screen in the status window (W2). Dump created by SLED; dump object: VM2000

Figure 15: Information screen in the status window (W2). Dump created by SLED; dump object: SLED

Figure 16: Information screen in the status window (W2). Dump created by SLED; dump object: BS2000 in the monitor VM

INF

Figure 17: Information screen in the status window (W2). Predecessor system; dump object: BS2000

TSK

This mode is set automatically if a SLED or SNAP with a BS2000 object or the currently active system is to be analyzed and information relating to a number of tasks is available. Only the first 14 tasks are initially shown in the status window (W2). Each line contains the information for one task and can be marked.
The mode is indicated by the entry “TSK” in the key line. You can scroll in the task list by entering +, -, ++, --, +n, -n in the command line and pressing . The  or key can be used instead of “+” or “-” .

When diagnosing the active system, the task list is updated only on positioning with “--” to the beginning of the list (i.e. when TID 0001 is displayed).

When diagnosing the active system, the termination or creation of tasks can also result in inconsistencies in other windows. If necessary, these have to be updated by bringing the task list up to date.

TSK

In the event of a system dump the output of the task list can be set by entering “TSK” in the field mode selection (PLK mode is set by default for the 'error task'). For a system dump the task list also contains all tasks from the BS2000 system to be diagnosed. A task can be selected for further diagnosis by marking a line.

CAUTION!
The system dump contains system-wide data for all tasks, but only the local task data of the 'error task'. When the system data (e.g. for PCB chaining) of the other tasks is analyzed extra special care is called for as these tasks cannot be stopped when the system dump is taken.

The task list can be sorted according to various criteria. To do this you must select a column in the header line. Sorting takes place in ascending order in accordance with the content of the column selected. The default setting is sorting according to TID (1st column).


Figure 18: Task overview in the status window (W2)

PLK

This mode is set automatically if an area, user or system dump containing only one task is being edited. It can also be set by marking a task line or by entering a TID/TSN in the TSK mode. The right-hand part of the 4-byte TID is sufficient when selecting a task.
All PCBs associated with this task and the related information is then output. The edited output of a PCB can be displayed in the stack window (W3) by marking a PCB line.
The symbol PLK appears in the key line.

User PCBs are marked in the output line with an “*” (asterisk).

The column headed A_MODE in the PCB overview for x86 objects lists the context type as well as the addressing mode. CIS stands for a PCB with a /390 context and X86 for a PCB with an x86 context.. With these objects, the following output is possible:

  • x86 systems’ objects:
    CIS 31 or CIS 24 if the PCB has a /390 context (code executing in /390 mode – i.e. as an emulation – with 31-bit or 24-bit addressing)

PLK
  • x86 systems’ objects:
    X86 32, X86 31 or X86 24 if the PCB has an x86 context (code executing in x86 mode – i.e. natively – with 32-bit, 31-bit or 24-bit addressing)

You can return from the first PCB to the task overview with / “-” or by entering TSK in the Mode select field.

Figure 19: PCB overview in the status window (W2), dump file with X86 object

SLK

In this mode, the call chain is output via the TPR program manager (SPL linkage). To do this, the mode field in the title line of the window must be overwritten with the symbol SLK. The edited output of this program manager stack can be displayed in the stack window (W3) by marking one of the stack lines shown.
The symbol SLK appears in the key line.

Figure 20: Chain of program manager calls in the status window (W2)

You can return from the first stack to the task overview with / “-” or by entering TSK in the “Mode select” field.

Paging in the status window

You may enter the following: +, -, ++, --, +n, -n or press the function keys  (page forward by one window length, which corresponds to +) and (page backward by one window length, which corresponds to -). For further details, see the section on "Paging in a diagnostic window" (Modifying the diagnostic windows).

Note on paging forward

When paging forward (+, ++, +n, ), you stop at the end of the listing involved, and you are not automatically returned to the start of the listing.

Note on paging backward

  • Pressing the key and entering “-” in the PLK and SLK modes pages back to the task list if the first PCB or first stack is currently visible in the window. Selecting the TSK mode also returns you to the task overview. The current task is then the first task in the overview.

  • When diagnosing the current system, the task list is regenerated on paging back to the first task in the list with “--” in TSK mode.

  • If a dump object was selected in dump files with multiple objects, entering or “-” in INF mode cancels the selection.