z/OS Communications Server: SNA Diagnosis Vol 1, Techniques and Procedures
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


ABDUMP service aid

z/OS Communications Server: SNA Diagnosis Vol 1, Techniques and Procedures
GC27-3667-00

ABDUMP operates as part of the operating system abnormal termination (abend) procedure. It automatically formats and prints abend dumps. (See Abend dump.)

During ABDUMP processing, VTAM® formats control blocks related to the abnormally ending task and prints them as part of the dump created by ABDUMP.

The following information shows ABDUMP formats the control blocks.

Note: This is an alphabetical list of the control blocks that might be in a dump. They might be in a different order in the dump.
Control block
Description
ACDEB
VTAM data extent block for the abnormally ending task
APPCB
LU 6.2 control block
COPR
Control operator control block associated with the abnormally ending task
CRA
Component recovery area for the abnormally ending task
FMCB
Function management control block and extensions for the abnormally ending task
HSICB
Half-session information control block for the abnormally ending task
LUCB
Logical unit control block associated with the abnormally ending task
MPST
Memory-process scheduling table for the abnormally ending task
NSICB
Logical-network-services information control block for the abnormally ending task
NSSCB
Logical-network-services storage control block for the abnormally ending task
PST
Process scheduling table for the abnormally ending task
RAB
LU 6.2 resource allocation block for the abnormally ending task
RDTE
Resource-definition-table application program entry for the abnormally ending task
SAB
LU 6.2 logical-resource manager-session allocation block for the abnormally ending task
The following information shows formatted data areas described in :
  • ACDEB
  • CRA
  • FMCB
  • LUCB
  • MPST
  • PST
  • RDTE
The following information appears for each control block:
  • A header line with the name and hexadecimal address of the beginning of the control block
  • Under the header, the name of each selected field (as it appears in that control block's mapping DSECT) and the contents of the field (listed sequentially)
  • After the formatted printout, a hexadecimal dump of the entire control block

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014