Exception messages are the most important check output, because they identify potential problems and suggest a solution.

• The complete explanation and details for exception messages are issued to the message buffer, where you can view it with either SDSF, HZSPRINT, or in the log stream.
• By default, the exception message text is also issued as a WTO, prefaced by an HZS WTO message. The HZS message issued reflects the SEVERITY={HIGH | MEDIUM | LOW | NONE} and WTOTYPE={CRITICAL|EVENTUAL|INFORMATIONAL|HARDCOPY|NONE} parameters defined for the check. (You can update these parameters to control the severity and descriptor code for the check.)

Exception message example 1 - An exception message as it appears in the message buffer: The following example shows an exception message in the message buffer. Note that IBM Health Checker for z/OS issues information both before and after the exception message with data including the check owner and name, the severity of the check, and the check parameter in use.

CHECK(IBMGRS,GRS_MODE)                    
START TIME: 06/12/2007 18:44:00.421390    
CHECK DATE: 20050105  CHECK SEVERITY: LOW 
CHECK PARM: STAR  


ISGH0301E Global Resource Serialization is in RING mode.  Global Resource
          Serialization STAR mode was expected.

Explanation: The check found an unexpected mode when global resource serialization 
          star mode was expected. Use star mode for best performance in a parallel sysplex.

System Action: The system might perform significantly worse than if it was in star mode.

Operator Response: Contact your system programmer.

System Programmer Response: See z/OS MVS Planning: Global Resource Serialization for 
          more information on converting to global resource serialization star mode.

Problem Determination: N/A

Source: Global resource serialization

Reference Documentation: z/OS MVS Planning: Global Resource Serialization

Automation: N/A

Detecting Module: ISGHCGRS, ISGHCMSG

END TIME: 06/12/2007 18:44:02.003761  STATUS: EXCEPTION-LOW 

CHECK(IBMXCF,XCF_SFM_ACTIVE)                                                    
START TIME: 06/07/2005 10:40:38.132396                                          
CHECK DATE: 20050130  CHECK SEVERITY: MEDIUM                                    
CHECK PARM: ACTIVE                                                              
                                                                                
                                                                                
* Medium Severity Exception *                                                   
                                                                                
IXCH0514E The state of Sysplex Failure Management is NOT consistent             
with the IBMXCF recommendation.                                                 
                                                                                
  Explanation:  Sysplex Failure Management (SFM) is INACTIVE on this            
    system. The IBMXCF specification requires that SFM be ACTIVE.               
                                                                                
  System Action:  The system continues processing normally.                     
                                                                                
  Operator Response:  Report the problem to the system programmer.              
                                                                                
  System Programmer Response:  Define an SFM policy with the                    
    administrative data utility IXCMIAPU.                                       
                                                                                
    Start an SFM policy by issuing 'SETXCF                                      
    START,POLICY,TYPE=SFM,POLNAME=xx' at the operating system console.          
                                                                                
    Stop an active SFM policy by issuing 'SETXCF STOP,POLICY,TYPE=SFM'          
    at the operating system console.                                            
                                                                                
    IBM suggests that SFM should be ACTIVE.                                     
                                                                                
  Problem Determination:  N/A                                                   
                                                                                
  Source:  Parallel Sysplex (XCF)                                               
                                                                                
  Reference Documentation:                                                      
    z/OS MVS Setting Up a Sysplex                                               
                                                                                
  Automation:  N/A  
  Check Reason:  An SFM policy provides better failure management.              
                                                                                
END TIME: 06/07/2005 10:40:39.091924  STATUS: EXCEPTION-MED      

Exception message example 2 - An exception WTO message on the system console: The example below shows how the same check exception message WTO looks on the system console. Note that IBM Health Checker for z/OS issues an HZS message, HZS0002E, and then the check exception WTO appears as part of that message:

B7VBID47  HZS0002E CHECK(IBMXCF,XCF_SFM_ACTIVE):                         
IXCH0514E The state of Sysplex Failure Management is NOT consistent      
with the IBMXCF recommendation.  

Exception message example 3 - An exception WTO message in the system log: The example below shows the same check exception message WTO again, this time on the system console. Note that IBM Health Checker for z/OS issues an HZS message, HZS0002E, and then the check exception WTO appears as part of that message:

031 01000000  HZS0002E CHECK(IBMXCF,XCF_SFM_ACTIVE): 882                        
882 01000000  IXCH0514E The state of Sysplex Failure Management is NOT consistent
882 01000000  with the IBMXCF recommendation.