Statements and parameters for EXSPATxx

SPINRCVY

Specifies the actions that the system is to take to end a spin loop that is not caused by a SIGP failure. SPINRCVY must be the first entry on a record defining these actions. At least one action is required on a SPINRCVY statement. You can specify a maximum of eight parameters on a SPINRCVY statement.

ABEND: The system abnormally ends the current unit of work on the processor that is causing the excessive spin (abend code X'071') and takes a SLIP dump if the installation is running with the IBM-supplied default for IEASLPxx. Recovery routines for the unit of work are allowed to retry.
ACR: The system invokes alternate CPU recovery (ACR) processing for the processor causing the excessive spin. The processor is taken offline.
OPER: The system issues message IEE331A and processes the operator's reply. If the message could not be issued, or if the operator does not respond, the processor that is in an excessive spin is put into a restartable wait state (X'09n'). The operator can respond to the message with ABEND, ACR, TERM, SPIN, or U (equivalent to SPIN) to continue.
SPIN: Specifies that the spinning processor is to continue spinning. An informational message (IEE178I) is displayed.
TERM: The system abnormally ends the current unit of work on the processor that is causing the excessive spin (abend code X'071') and takes a SLIP dump if the installation is running with the IBM-supplied default for IEASLPxx. Recovery routines for the unit of work are not allowed to retry.

SPINTIME=sss

Specifies the excessive spin loop timeout interval, where sss is the number of seconds. sss can be one through three digits but must be at least 10 seconds. For MVS™ running in a native or basic mode, or in an LPAR with dedicated CPs, the default is 10 seconds. For MVS running on VM or in an LPAR with shared CPs, the default spin loop timeout interval is 40 seconds.

Default value: 10 seconds or 40 seconds

Notes:

In a PR/SM™ environment, system configuration and weighting affect the amount of processing (CPU cycles) that occurs in each partition during the timeout interval.
The specified SPINTIME value affects the default value of the INTERVAL parameter in the COUPLExx member of SYS1.PARMLIB. If the excessive spin parameters are not explicitly set in an EXSPATxx parmlib member, the IBM® supplied default spin parameters are used: the derived spin failure detection interval can be 45 seconds or 165 seconds depending on the configuration. See the INTERVAL parameter in the COUPLExx member for more information.
For an MVS system that is running in a non-dedicated PR/SM environment or under VM, if you specify non-default values for SPINTIME, consider the following facts:
- The more processing power (CPU cycles) available to the system, the less time it needs to resolve a spin loop.
- The less processing power available to the system, the more time it needs to resolve a spin loop.
- Specifying a SPINTIME that is too low might cause premature excessive spin conditions.
If your system is running in a logical partition that is sharing central processing resources, and you want to use a SPINTIME value of less than the default time (40 seconds), the BLWSPINR member of SYS1.SAMPLIB contains an exec that can help you evaluate your spintime requirements.