Sections of the Language Environment LEDATA VERBEXIT formatted output

Table 1 lists the sections of the LEDATA VERBEXIT output, which appear independently of the Language Environment-conforming languages used.

Table 1. Contents of the Language Environment LEDATA VERBEXIT formatted output (AMODE 64)
Section Number and Heading	Contents
[1] - [8] CEEDUMP Formatted Control Blocks: These sections are included when the CEEDUMP parameter is specified on the LEDATA invocation.
[1] - [4] NTHREADS data: These sections are also included, once for each thread, when the NTHREADS() parameter is specified on the LEDATA invocations. For a description of NTHREADS, see Report type parameters.
[1] Enclave Identifier	Names the enclave for which information is provided.
[2] Information for thread	Shows the system identifier for the thread. Each thread has a unique identifier.
[3] Registers and PSW	Displays the register and program status word (PSW) values that were used to create the traceback. These values may come from the TCB, the RTM2 work area, a linkage stack entry or output from the BPXGMSTA service. This section is not displayed when the DSA() parameter is specified on the LEDATA invocation.
[4] Traceback	For all active routines in a particular thread, the traceback section shows routine information in two parts. The first part contains: DSA number: A number assigned to the information for this active routine by LEDATA. The number is only used to associate information from the first part of the traceback with information in the second part of the traceback. Entry: For C/C++ routines, this is the function name. If a function name or entry point was not specified for a particular routine, then the string NoName will appear. Entry point offset Load module Program unit: The primary entry point of the external procedure. For C routines, this is the compile unit name. For Language Environment-conforming assemblers, this is the ENTNAME = value on the CELQPRLG macro. Service level: The latest service level applied to the compile unit (for example, for IBM® products, it would be the PTF number. Status: Routine status can be call, exception, or running. The second part contains: DSA number: A number assigned to the information for this active routine by LEDATA. The number is only used to associate information from the first part of the traceback with information in the second part of the traceback. Stack frame (DSA) address Entry point address Program unit address Program unit offset: The offset of the last instruction to run in the routine. If the offset is a negative number, zero, or a very large positive number, the routine associated with the offset probably did not allocate a save area, or the routine could have been called using SVC-assisted linkage. Adding the program unit address to the offset gives you the location of the current instruction in the routine. This offset is from the starting address of the routine.
[5] Control Blocks Associated with the Thread	Lists the contents of the thread synchronization queue element (SQEL).
[6] Enclave Control Blocks	If the POSIX runtime option was set to ON, this section lists the contents of the mutex and condition variable control blocks, the enclave level latch table, and the thread synchronization trace block and trace table. If the HEAPCHK runtime option is set to ON, this section lists the contents of the HEAPCHK options control block (HCOP) and the HEAPCHK element tables (HCEL). A HEAPCHK element table contains the location and length of all allocated storage elements for a heap in the order that they were allocated.
[7] Language Environment Trace Table	If the TRACE runtime option was set to ON, this section shows the contents of the Language Environment trace table.
[8] Process Control Blocks	If the POSIX runtime option was set to ON, this section lists the contents of the process level latch table.
[9] - [17] Summary: These sections are included when the SUMMARY parameter is specified on the LEDATA invocation.
[9] Summary Header	The summary header section contains: Address of Thread control block (TCB) Release number Address Space ID (ASID)
[10] Active Members List	Lists active members, which is extracted from the enclave member list (MEML).
[11] CEELAA	Formats the contents of the Language Environment library anchor area (LAA). Seez/OS Language Environment Vendor Interfaces for a description of the fields in the LAA.
[12] CEELCA	Formats the contents of the Language Environment library control area (LCA). See z/OS Language Environment Vendor Interfaces for a description of the fields in the LCA.
[13] CEECAA	Formats the contents of the Language Environment common anchor area (CAA). Seez/OS Language Environment Vendor Interfaces for a description of the fields in the CAA. If there is any, DLL failure data is also formatted.
[14] CEEPCB	Formats the contents of the Language Environment process control block (PCB), and the process level member list.
[15] CEERCB	Formats the contents of the Language Environment region control block (RCB).
[16] CEEEDB	Formats the contents of the Language Environment enclave data block (EDB), and the enclave level member list.
[17] Runtime Options	Lists the runtime options in effect at the time of the dump, and indicates where they were set.
[18] Heap Storage Control Blocks	This section is included when the HEAP or SM parameter is specified on the LEDATA invocation. It formats the Enclave-level storage management control block (ENSQ) and for each different type of heap storage: Heap control block (HPCQ) Chain of heap anchor blocks (HANQ). A HANQ immediately precedes each segment of heap storage. This section includes a detailed heap segment report for each segment in the dump. For more information about the detailed heap segment report, see Understanding the HEAP LEDATA output.
[19] Stack Storage Control Blocks	This section is included when the STACK or SM parameter is specified on the LEDATA invocation. This section formats: Stack anchor (SANC) Chain of dynamic save areas (DSA)
[20] Condition Management Control Blocks	This section is included when the CM parameter is specified on the LEDATA invocation. It formats the chain of Condition Information Block Headers (CIBH) and Condition Information Blocks. The Machine State Information Block is contained with the CIBH starting with the field labeled MCH_EYE.
[21] Message Processing Control Blocks	This section is included when the MH parameter is specified on the LEDATA invocation.
[22] Preinitialization Information	This section is included when the PTBL parameter is specified on the LEDATA invocation. It formats information related to preinitialization. See PTBL LEDATA output for more information. If the preinitialization service CELQPIPI was not used to initialize this environment, the message: `No PIPICB associated with CAA` is displayed instead.