Description

z/OS MVS Programming: Assembler Services Reference ABE-HSP

Description

z/OS MVS Programming: Assembler Services Reference ABE-HSP
SA23-1369-00

The ESPIE macro extends the function of the SPIE (specify program interruption exits) macro to callers in 31-bit addressing mode. For additional information concerning the relationship between the SPIE and the ESPIE macros, see the section on program interruptions in z/OS MVS Programming: Assembler Services Guide.

The ESPIE macro performs the following functions using the options specified:

Establishes an ESPIE environment (that is, identifies the interruption types that are to cause entry to the ESPIE exit routine) by executing the SET option of the ESPIE macro
Deletes an ESPIE environment (that is, cancels the current SPIE/ESPIE environment) by executing the RESET option of the ESPIE macro
Determines the current SPIE/ESPIE environment by executing the TEST option of the ESPIE macro.

The information documented under the following headings applies to all three options of the ESPIE macro (SET, RESET, and TEST):

“Environment”
“Programming Requirements”
“Restrictions”
“Performance Implications”
“ABEND Codes”

Environment

The requirements for the caller are:

Environmental factor	Requirement
Minimum authorization:	To issue ESPIE without encountering an abnormal end, callers must be in problem state, with a PSW key value that is equal to the TCB assigned key, except when ESPIE RESET is issued or ESPIE SET is issued with no interruption codes specified (where key 0 supervisor state is allowed).
Dispatchable unit mode:	Task
Cross memory mode:	PASN=HASN=SASN
AMODE:	24- or 31- or 64-bit
ASC mode:	Primary
Interrupt status:	Enabled for I/O and external interrupts
Locks:	No locks held
Control parameters:	Must be in the primary address space.

Programming requirements

None.

Restrictions

None.

Performance implications

Programs that need to intercept only specific hardware program check interruptions (such as arithmetic exceptions or data conversion exceptions) will find ESPIE to be more efficient than establishing an ESTAE environment to screen all abends for specific OCx abends. This is because the operating system must do significantly more processing to enter and retry from an ESTAE routine as compared to an ESPIE routine.

ABEND codes

ESPIE might return abend code X'46D'. See z/OS MVS System Codes for an explanation and programmer responses.

The information documented under the following headings is provided separately for each of the three options (SET, RESET, and TEST):

“Input Register Information”
“Output Register Information”
“Syntax”
“Parameters”
“Return and Reason Codes”
“Examples”