z/OS MVS IPCS Customization
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Conditions on Entry to an IPCS Exit Routine

z/OS MVS IPCS Customization
SA23-1383-00

  • For IPCS and ABEND/SNAP Formatting
    The exit routine receives control for either type of formatting with:
    • A program status word (PSW) in primary mode and enabled, pageable, in task mode
    • The addressing and residence modes specified when the exit was link-edited
    The exit routine should obtain working storage from the subpool specified in field ADPLSBPL, by coding:
    GETMAIN ... SP=adplsbpl_value

    adplsbpl_value is the value in field ADPLSBPL, contained in BLSABDPL.

    The exit routine must release all resources it acquired before the routine completes processing.

    For both ABEND/SNAP and IPCS formatting, the system provides recovery for an exit routine. Use the ESTAE and ESTAEX macros to provide additional recovery if desired, but do not have recovery routines request retry. To ensure appropriate resource clean-up, permit percolation to the recovery routines supplied by the system.

  • For IPCS Formatting

    An exit routine runs in PSW key 8 and problem state under a task control block (TCB) established for IPCS or ISPF logical screen processing.

  • For ABEND/SNAP Formatting

    An exit routine runs in PSW key 0 and supervisor state under any TCB for which SNAP (direct request) or ABEND (indirect request) processing has been requested. The routine should be carefully audited to ensure that it introduces neither security nor integrity exposures into the system.

    No locks are held when the exit routine receives control. The exit routine cannot issue the ENQ macro or obtain any locks.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014