Module keyword

This topic applies only to the ABENDxxx, WAIT, and LOOP type-of-failure keywords.

DFSMSdss uses subtasking to isolate functions; thus, a dump might contain a task and subtasks as follows:

A DFSMSdss scheduler task
A subtask for the reader/interpreter
Subtasks for the DFSMSdss functions (for example, COPY or DUMP)
A subtask for managing SVC services
A subtask for managing IGWFAMS
A subtask for attached utilities.

Each task has its own task control block (TCB) and request block (RB) chain in the dump. An explanation of the subtasks follows:

The task for the scheduler is ADRDSSU, as indicated in the program request block/contents directory entry (PRB/CDE). Its normal state is waiting for the return from the EVENTS SVC (X'7D') in ADRDSSU.
The subtask for the reader/interpreter is ADRRI01, as indicated in the PRB/CDE. Its normal state is waiting for the return from the WAIT SVC (X'01') in ADRRI01.
The subtasks for the DFSMSdss functions are ADRBLDSA, ADRCGCR, ADRCPYD, ADRPRNT, ADREFRAG, ADRDDTFP, ADRDTDS, ADRDTDSC, ADRDDDS, ADRCMPR0, ADRRLSE0, ADRTDFP, ADRTDDS, or ADRKVOL, as indicated in the PRB/CDE.
The subtask that manages the SVC services is ADRSVCD. Its normal state is waiting for return from the WAIT SVC (X'01') in ADRSVCD.
The subtask that manages IGWFAMS is ADRATFMS. Its normal state is waiting for the return from the WAIT SVC (X'01') in ADRATFMS.
The subtask that manages other attached utilities is ADRMUTIL. Its normal state is waiting for the return from the WAIT SVC (X'01') in ADRMUTIL.

Procedure: Perform the following.

Locate the failing task by comparing the task identifier in the task-related messages to the task identifier in the function blocks for the executing functions. The task identifier is in the third halfword in the function block for the function. The function block is addressed by register 1 at entry to the function. This register is in the first save area on the save area chain under the TCB for the function. The ID in the message is a decimal number; the identifier in the function block is a hexadecimal number.
If the function keyword is CNTRL, the failing task is either the scheduler or the reader/interpreter. If both are present, inspect the program status words (PSWs) for these tasks to determine whether one is not in its normal state, as described in this topic.

_______________________________________________________________
Locate the active module.
Get the PSW for the failing task. This is usually found in the PRB and might not always be the error PSW identified at the beginning of the dump.
Starting at the address in the PSW, search backward through the dump for the module identifier. The identifier consists of the following two character strings (separated by from 20 to 80 bytes):
```
ADRxxxxx mm/dd/yyHDZ1A10 aparnum
  .
  .
  .
ptfnum,yr.day,hh:mm:ss
```
where:
ADRxxxxx

Module name

mm/dd/yy

Maintenance date

HDZ1A10

FMID of the release

aparnum

Current APAR number or "NONE"

ptfnum

Current program temporary fix (PTF) number or "NONE"

yr.day

Compile date

hh:mm:ss

Compile time
If the PSW does not point within a DFSMSdss module, use register 12 (base) or 14 (return) at the time of the error and repeat this search. You can usually find these registers in the first supervisor request block (SVRB) after the PRB for the failing task.
Examples:
1. 5695DF175 RA10 ABEND xxx function module
2. 5695DF175 RA10 WAIT function module
3. 5695DF175 RA10 LOOP function module
_______________________________________________________________
If you already know the PTF number, see Using the IBM Support Center. Otherwise, see Maintenance-level keyword.
_______________________________________________________________