ALLOC_SPEC_WAIT_POLICY

Description:

Checks the value of the SPEC_WAIT POLICY in the current Allocation settings.

Reason for check:

This check ensure that the best SPEC_WAIT POLICY allocation setting for the particular environment is set. Certain SPEC_WAIT POLICY values can result in a deadlock.

z/OS® releases the check applies to:

z/OS V1R13 and later.

User override of IBM values:

The following sample shows the defaults for customizable values for this check. Use this sample to make permanent check customizations in an HZSPRMxx parmlib member used at IBM Health Checker for z/OS startup. If you just want a one-time only update to the check defaults, omit the first line (ADDREPLACE POLICY) and use the UPDATE statement on a MODIFY hzsproc command. Note that using non-POLICY UPDATEs in HZSPRMxx can lead to unexpected results and is therefore not recommended. End of change

ADDREPLACE POLICY[(policyname)] [STATEMENT(name)]
UPDATE
CHECK(IBMALLOC,ALLOC_SPEC_WAIT_POLICY )
ACTIVE
SEVERITY(LOW) 
INTERVAL(24:00) 
DATE('date_of_the_change')
PARM('POLICY(WTOR)')
REASON('The reason for the change.')

Debug support:

Verbose support:

Parameters accepted:

Yes. the following parameters are accepted to indicate the value of SPEC_WAIT POLICY the user wants as the recommended setting:

PARM('POLICY(WTOR)')
PARM('POLICY(CANCEL)')
PARM('POLICY(WAITHOLD)')
PARM('POLICY(WAITNOH)')

The default is PARM('POLICY(WTOR,CANCEL,WAITNOH)').

You can also specify more than one acceptable value by separating them via commas as such: PARM('POLICY(val1,val2...valn)'), where the values correspond to the different values of the SPEC_WAIT POLICY.

If any of these values match the current setting, then the check will be successful. If the checks finds that current SPEC_WAIT POLICYYsetting does not match the parameter, the check issues an exception.

Reference:

For additional information, see the ALLOCxx chapterz/OS MVS Initialization and Tuning Guide .

Messages:

This check issues the following messages:

IEFAH001I (successful)
IEFAH002E (exception)

See IEFA messages in z/OS MVS System Messages, Vol 8 (IEF-IGD).

SECLABEL recommended for multilevel security users:

SYSLOW - see z/OS Planning for Multilevel Security and the Common Criteria for information on using SECLABELs.

Output:

When successful, the report that the check produces is as follows:

CHECK(IBMALLOC,ALLOC_SPEC_WAIT_POLICY)                                  
START TIME: 10/25/2010 11:17:41.822822                                  
CHECK DATE: 20100831  CHECK SEVERITY: LOW                               
CHECK PARM: POLICY(WTOR,CANCEL,WAITNOH)                                 
                                                                        
                                                                        
IEFAH001I Option value WTOR matches the owner                           
recommendation of WTOR,CANCEL,WAITNOH                                   
                                                                        
END TIME: 10/25/2010 11:17:41.825402  STATUS: SUCCESSFUL

For an exception, the report that the check produces is as follows:

CHECK(IBMALLOC,ALLOC_SPEC_OFFLN_POLICY)     
START TIME: 10/25/2010 12:15:43.753021      
CHECK DATE: 20100831  CHECK SEVERITY: LOW                                 
CHECK PARM: POLICY(WTOR,CANCEL,WAITNOH)                                 
                                                                        
                                                                        
* Low Severity Exception *                                              
                                                                        
IEFAH002E Option value WAITHOLD does not match the owner                
recommendation of WTOR,CANCEL,WAITNOH                                        

END TIME: 09/24/2010 16:11:40.729241  STATUS: EXCEPTION-LOW