Adabas Dump Formatting Tool (ADAFDP)

The message is displayed on the console and written to DDPRINT at the point where the format begins and terminates.

If an Abend code and program status word (PSW) were saved in ADAMPM by the Adabas ESTAE, ADAFDP displays these. In addition, ADAFDP determines the module whose entry point best fits the PSW and calculates the offset within that module. If the ADAMPM abend code and PSW are zero, ADAFDP does not format this information.

ADAFDP formats and displays the location of each of the Adabas nucleus modules resident in the address space.

ADAFDP formats and displays the location of any user exit loaded with the Adabas nucleus.

ADAFDP formats and displays the location of any hyperexit loaded with the Adabas nucleus. Hyperexits 10-31 are displayed as A-U, respectively.

Registers 0-7/8-F, which are saved in ADANC0. ADAFDP determines if any of these registers contains an address that points at a nucleus pool in storage. If yes, ADAFDP indicates which pool and snaps storage at that address. If the register is 12 and it points to a user thread, ADAFDP snaps the entire thread.

Registers 0-7/8-F, which are saved in ADANC0 as a result of a user abend. ADAFDP determines if any of these saved registers contains an address that points at a nucleus pool in storage. If yes, ADAFDP indicates which pool and snaps storage at that location. If the saved register is 12 and it points to a user thread, ADAFDP snaps the entire thread.

Registers 0-7/8-F, which were saved in ADAMPM by the Adabas ESTAE. These are the same registers displayed with the ADAM99 message. ADAFDP determines if any of these saved registers contains an address that points within a nucleus pool in storage. If yes, ADAFDP indicates which pool and snaps storage at that location.

ADAFDP determines begin/ending address locations for pools and tables for the Adabas nucleus. These addresses are presented for easy location in the actual dump. See Pool Abbreviations for more information.

ADAFDP formats the physical threads including threads 0, -1, and -2. The number of lines depends on the value of NT. The thread that was active at the time of the abnormal termination (if any) is marked by a pointer “- ->”.

For any of the threads -2 to NT that had assigned work to perform, ADAFDP formats and displays information about the status of that thread. See User Threads for more information:

ADAFDP scans the command queue and formats information for any command found in the queue. See Command Information for more information.

ADAFDP check the integrity of several pools within the Adabas nucleus address space. If an error is detected within that pool, ADAFDP indicates which pool and what type of error was encountered. In addition, ADAFDP snaps storage at the location where the error was detected.

ADAFDP scans the buffer pool header for RABNs that were active or being updated. See RABN Information for more information.

Registers 0-7/8-F found saved in ADAIOR at this offset. If ADAFDP determines that any of these register values is pointing within an Adabas pool, it snaps storage at that location.

Registers 0-7/8-F found saved in ADAIOR at this offset. If ADAFDP determines that any of these register values is pointing within an Adabas pool, it snaps storage at that location.

The ICCB address to which this offset in ADAIOR points.

Format of ADAIOR trace table; same as that found with the ADAM99 message.

• *Active*: the currently active thread

• In Use: thread has been assigned work

• Waiting For I/O: waiting for a block not in buffer pool

• Waiting For RABN: waiting for a RABN already in use

• Waiting For Work-2 Area Block: similar to waiting for I/O

• Waiting Workpool Space: provides number of bytes in decimal

• Ready To Run: waiting to be selected for execution

FL: format buffer length
RL: record buffer length
SL: search buffer length
VL: value buffer length
IL: ISN buffer length

• First Byte: General Purpose Flag

  • X’80’: User buffers in service partition, region, address space

  • X’40’: ET command waiting for 12 call

  • X’20’: Waiting for 16 call

  • X’10’: 16 call required

  • X’08’: Attached buffer

  • X’04’: Attached buffer required

  • X’02’: X-memory lock held (MVS only)

• Second Byte: Selection Flag

  • X’80’: In process

  • X’40’: Ready to be selected

  • X’20’: Search for UQE done

  • X’10’: UQE found

  • X’08’: Not selectable during BSS=x’80’ status

  • X’04’: Not selectable during ET-SYNC

  • X’02’: Waiting for space

  • X’01’: Waiting for ISN in HQ

• AKZ X’40’: Active indicator

• UKZ X’20’: Update indicator

• RKZ X’10’: Read indicator

• XKZ X’04’: Access is waiting for block

• YKZ X’02’: Update is waiting for block

• SKZ X’01’: Write indicator