SUMMARY (Summarize Stack Information)

The SUMMARY command lists information about all the stacks in the system. You can control the information that is displayed about the stacks and the order in which the stacks are displayed.

Syntax 

── SUMMARY ─┬───────────────────────────────────────────┬──────────────┤
            ├─ PARTIALONLY ─────────────────────────────┤
            ├───────────────────────────────────────────┤
            │ ┌◄───────────────┐                        │
            └─┴─<summary item>─┴─┬──────────────────────┐
                                 └─<sort specification>─┘

<summary item> 

──┬─ CPURATE ────────────────────────┬─────────────────────────────────┤
  ├─ CREATION ───────────────────────┤
  ├─ KIND ───────────────────────────┤
  ├─ LANGUAGE ───────────────────────┤
  ├─ LASTALIVE ──────────────────────┤
  ├─ MIXNO ──────────────────────────┤
  ├─ NAME ───────────────────────────┤
  ├─ PIB ─┬─<PIB cell name>──────────┤
  │       └─ # ──<offset>────────────┤
  ├─<quoted wild-card string>────────┤
  ├─ RELEASEID ──────────────────────┤
  ├─ STACK ─┬─<stack base cell name>─┤
  │         └─ # ──<offset>──────────┤
  ├─ STACKINFO ──────────────────────┤
  ├─ STACKNO ────────────────────────┤
  ├─ STACKSTATUS ────────────────────┤
  ├─ STATUS ─────────────────────────┤
  ├─ TAB ─┬─<TAB cell name>──────────┤
  │       └─ # ──<offset>────────────┤
  ├─ TCP ──<hex number>──────────────┤
  └─ TYPE ───────────────────────────┘

<sort specification> 

            ┌◄───────────────────────────────────────┐
── SORT BY ─┴─/3\─ ITEM ──<integer>─┬──────────────┬─┴─────────────────┤
                                    ├─ ASCENDING ──┤
                                    └─ DESCENDING ─┘

Explanation

The following text describes the meaning of each construct. Refer to “File Title” earlier in this section for an explanation of the rules for specifying a file title.

SUMMARY

Displays the following information for each stack in the system: stack number, mix number, name, kind, status, and type. Active stacks and the stack that took the dump are identified.

SUMMARY PARTIALONLY

Specifies that only the stacks that were included as part of the Partial Memory Dump are listed in the output display. All stacks are included in the partial dump; however, only those stacks related to the stack that requested the dump have their off stack areas included in the dump. These stacks are marked with an asterisk (*) in the SUMMARY display.

This option has no affect with any other type of dump.

SUMMARY <summary item>

Specifies the information to be displayed for each stack in the system. The stack number is always displayed. A limit is placed on the number of items that can be displayed based on the size of each item selected and the display medium requested (for example, terminal or printer). If you request too many items, DUMPANALYZER displays an error message.

SUMMARY <summary item> <sort specification>

Sorts the stacks by as many as three of the items specified in the summary item list.

<summary item>

Specifies the items to be displayed. The following table lists the summary item options:

Specify . . .

To display . . .

CPURATE

Percentage of recent processor utilization.

CREATION

The creation date and time for the object code file of each process.

KIND

The process kind, such as MCP, independent runner, segment dictionary, or frozen library.

LANGUAGE

The object code file language of each process.

LASTALIVE

The time in seconds since the stack was last executing.

MIXNO

The mix number of each process.

NAME

The name of each process (normally the object code file title).

PIB <PIB cell name> PIB # <offset>

The contents of the specified PIB cell for each process.

<quoted wild-card string>

The stacks with names that match the wild-card string in the summary listing. The wild-card characters are as follows:

  • The equal sign (=), which matches any sequence of characters.

    EXAMPLE: SUMMARY "=PRINT="

    RESULT: Reports only those stacks that have the string PRINT anywhere in the stack name.

  • The question mark (?), matches any single character.

EXAMPLE: SUMMARY "=P?X="

RESULT: Reports only those stacks the have the letter P, followed by any single character, followed by the letter X, anywhere in the stack name.

Note: DUMPANALYZER does not convert into uppercase characters the contents of quoted strings that might refer to lowercase file titles.

RELEASEID

The RELEASEID file attribute of the object code file of each process. This file attribute, if not null, reflects the Mark release level of the object code file.

STACK <stack cell name> STACK # <offset>

The contents of the specified stack cell for each process.

STACKINFO

The STACKINFO word for each process.

STACKNO

The stack number for each process.

STATUS

The current process status (READY, WAITING, or FROZEN).

TAB <TAB cell name> TAB # <offset>

Displays the contents of the specified TAB cell for each process.

TCP

Displays the contents of the specified TCPINFO word for each processor.

Note: If you specify TCP as a summary item for a dump from a machine that has no TCP, DUMPANALYZER displays the following error message: “ERROR: SCANNING TCP.”.

TYPE

The process type, such as PROCESS, RUN, and so on.

Note: If you specify TCP as a summary item for a dump from a machine that has no TCP, DUMPANALYZER displays the following error message: “ERROR: SCANNING TCP.”.

<sort specification>

Identifies the item to be sorted by its numerical position in the summary item list. For the first item in the list, use the <integer> 1; for the second, use <integer> 2, and so forth.

The stack number is the default sort item. DUMPANALYZER resolves any ambiguity remaining after it finishes all other sorting by comparing stack numbers. You can explicitly sort by the stack number by referring to it as ITEM 0, which might be useful if the stack number is to be the second of three sort items.

The final option for the sort specification is the order that the item is to be sorted in; ascending is the default. STACKINFO, STACKSTATUS, and items in the stack or the PIB are sorted numerically; all other items are sorted alphabetically.

Example 1

The following example shows the output from a SUMMARY command.

INPUT: SUMMARY
STK   MIX #                NAME              KIND   STATUS   TYPE
--- --------- ------------------------------ ---- ---------- ----
012   16/16   *SYSTEM/MCP/39018A ON DISK.    MCP  FROZEN
014    0/0    ETERNALIR.                     I.R. READY      RUN
02B    0/0    ANSWERING/SERVICE/04.          I.R. WAITING    RUN
02C    0/0    AREAMANAGER.                   I.R. ASLEEP     RUN
02D    0/0    HANDLEIOPEVENTS.               I.R. READY      RUN
02E    0/0    HUNGIOHANDLER.                 I.R. READY      RUN
033    0/0    ANABOLISM.                     I.R. WAITING    RUN
034    0/0    ONESECONDBURDEN.               I.R. READY      RUN
036 4353/4353 *SYSTEM/38/CENTRALSUPPORT.     LIB  WAITING    RUN
037    2/2    CONTROLLOR.                    I.R. READY      RUN
038    3/3    MAINTLINEIR.                   I.R. READY      RUN
039    0/0    PLM.                           I.R. READY      RUN
03B           *SYSTEM/38/CENTRALSUPPORT ON D SEGD UNEMPLOYED
03C    2/6    *SUBSIDIARYTASK.               I.R. WAITING    PROC
03F 4354/4354 *SYSTEM/GENERALSUPPORT.        LIB  FROZEN     RUN
040           *SYSTEM/GENERALSUPPORT ON DISK SEGD UNEMPLOYED
042 4355/4355 *SYSTEM/WFLSUPPORT.            LIB  FROZEN     RUN
043           *SYSTEM/WFLSUPPORT ON DISK.    SEGD UNEMPLOYED
046 4359/4359 "PRINT_SUBSYSTEM_INITIALIZATIO I.R. WAITING    RUN
048 4361/4361 "JOBFILE/CONVERTER".           I.R. READY      RUN
049 4356/4356 *SYSTEM/DISKCACHESUPPORT/38.   LIB  FROZEN     RUN
04B 4357/4357 *SYSTEM/PRINT/SUPPORT.         LIB  WAITING    RUN
04C           *SYSTEM/DISKCACHESUPPORT/38 ON SEGD UNEMPLOYED
04D    0/0    "SLOG_MONITOR".                I.R. READY      RUN
04E           *SYSTEM/PRINT/SUPPORT ON DISK. SEGD UNEMPLOYED
04F 4358/4358 *SYSTEM/JOBFORMATTER.          LIB  FROZEN     RUN
050           *SYSTEM/JOBFORMATTER ON DISK.  SEGD UNEMPLOYED
057    0/0    OLAYSCOUT.                     I.R. READY      RUN
058    0/0    KEYIN.                         I.R. BLOCKED    RUN  DUMP

Example 2

The following example requests that four items be displayed and that the stacks be sorted by the LASTALIVE time in ascending order, so that the stacks that were most recently on the processor (relative to the time of the dump) are displayed first. 

INPUT: SUMMARY MIXNO NAME LASTALIVE SORT BY ITEM 3 
STK   MIX #                NAME              LASTALIVE
--- --------- ------------------------------ ---------------
0F5 2776/2776 "->MARC<-".                       -9.706 DUMP
7DB 8297/3640 (CBG)OBJECT/PM/ACCESS ON PACK.     0.000 ACT
02B    0/0    IDLE/PROCESSOR/05.                 0.002
02D    0/0    IDLE/PROCESSOR/04.                 0.002
0DC 2726/2763 *SYSTEM/COMS.                      0.007
07C 2722/2722 *SYSTEM/CANDE.                     0.008
037    2/2    CONTROLLOR.                        0.008
06F 2718/2718 "NSP109/03".                       0.012
0AC 2710/2735 SYSTEM/BNAMCS.                     0.020
729 2738/5931 STATUS/CHANGE/SFA15AB.             0.026
014 2751/2751 ETERNALIR.                         0.031
06E 2717/2717 "NSP111/04".                       0.032
0EE 2773/2773 (ANGUS)OBJECT/PROGRAM/AGENT/CO     0.036
0CF 2710/2754 SYSTEM/X25MONITOR.                 0.040
0D8 2726/2760 COMS/TANK.                         0.040
06D 2716/2716 *SYSTEM/PRINT/ROUTER.              0.046
1D5 2738/2970 TASKING/MESSAGE/HANDLER.           0.099
07A    0/0    "CALL_WS_SHERIFF".                 0.099
1D4 2738/2969 TASKING/STATE/CONTROLLER.          0.100
140 2722/2850 *CANDE/STACK01.                    0.101
Prev  Up  Next
SUBPORT (Subport Analysis)   Home  TAB (Task Attribute Block)