IBM Support

OA46531: NEW FUNCTION RUNTIME DIAGNOSTICS RESULTS(HZR0200I) WILL INCLUDEJES2 CRITICAL NOTICES WHEN F HZR,ANALYZE COMMAND IS ISSUED. NF

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • New Function
    RunTime Diagnostics results(HZR0200I) will include JES2 critical
    notices when F HZR,analyze command is issued.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of z/OS Runtime Diagnostics        *
    *                 Services for HBB7790                         *
    ****************************************************************
    * PROBLEM DESCRIPTION: Provide diagnostics for new event JES2. *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Runtime Diagnostics is being extended to provide additional
    diagnostics to assist the system programmer in identifying
    symptoms contributing toward "sick, but not dead" behavior.
    JES2-detected health exceptions are being added as events in
    Runtime Diagnostics, invoked via the F HZR,ANALYZE system
    command.  Also, when PFA detects a potential rate that is too
    low (for the PFA checks that support "too low" processing) and
    invokes Runtime Diagnostics to determine if events exist, JES2
    Health Exception events will be returned by PFA when they exist
    and will cause PFA to issue an exception.
    

Problem conclusion

Temporary fix

Comments

  • Documentation:
    
    z/OS V2R1 Problem Management book (SC23-6844-01):
    
    In the section "Runtime Diagnostics symptoms", add a new topic
    "z/OS JES2 Health Exception Event" with text as follows:
    Runtime Diagnostics gathers information about the JES2
    subsystem.  Health events that can be returned from the JES2
    SSI interface will be available here.  An example of a
    possible event appears below:
    
    HZR0200I RUNTIME DIAGNOSTICS RESULT
    SUMMARY: SUCCESS
     REQ: 004 TARGET SYSTEM: SY1      HOME: SY1      2015/01/12
     INTERVAL:  60 MINUTES
     EVENTS:
      FOUND: 01 - PRIORITIES: HIGH:01  MED:00  LOW:00
      TYPES: JES2:01
    ----------------------------------------------------------------
    EVENT 01: HIGH - JES2         - SYSTEM: SY1      2015/01/12
    $HASP9158 JES2 PROCESSING STOPPED, $S NEEDED
      ERROR: JES2 CANNOT PROCESS NEW WORK.
     ACTION: $S TO ENABLE JES2 TO START PROCESSING NEW WORK.
    
    In the section 'Runtime Diagnostics debug options",
    add new keyword options for DEBUG as follows:
    JES2 Runtime Diagnostics initiates an SVC dump of the HZR
    address space along with an SVC dump of the JES2 address space.
    NOJES2 When NO JES2 events are found, Runtime Diagnostics
    dumps the HZR address space.
    
    In the section "Runtime Diagnostics messages", "Understanding
    the messages Runtime Diagnostics issues" adjust as follows:
    In the second paragraph, add JES2 to the bulleted list that
    starts with "z/OS UNIX file system latch contention" and ends
    with "Local Lock suspension.".  Additionally Adjust the Figure
    1.  Message output for target system.
    
    HZR0200I RUNTIME DIAGNOSTICS RESULT 593
    SUMMARY: SUCCESS - NO EVENTS FOUND
     REQ: 001 TARGET SYSTEM: SYS3     HOME: SY1      2010/12/21
     INTERVAL:  60 MINUTES
     EVENTS:
      FOUND: 00 - PRIORITIES: HIGH:00  MED:00  LOW:00
      PROCESSING BYPASSED:
       OMVS.......SPECIFIED TARGET SYSTEM IS NOT THE HOME SYSTEM.
       LATCHES....SPECIFIED TARGET SYSTEM IS NOT THE HOME SYSTEM.
       LOOP.......SPECIFIED TARGET SYSTEM IS NOT THE HOME SYSTEM.
       HIGHCPU....SPECIFIED TARGET SYSTEM IS NOT THE HOME SYSTEM.
       LOCK.......SPECIFIED TARGET SYSTEM IS NOT THE HOME SYSTEM.
       JES2.......SPECIFIED TARGET SYSTEM IS NOT THE HOME SYSTEM.
    ----------------------------------------------------------------
    
    In the introductory section for "Runtime Diagnostics", (Chapter
    4 in some formats) adjust as follows:
    For the bulleted list starting with "Reviewing critical messages
    in the log" and ending with "Analyzing various types..." add an
    additional entry of "Finding JES2 health exception events."
    

APAR Information

  • APAR number

    OA46531

  • Reported component name

    RUN TIME DIAGNO

  • Reported component ID

    5752SCRTD

  • Reported release

    790

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    YesSpecatt / New Function / Xsystem

  • Submitted date

    2014-11-12

  • Closed date

    2015-02-17

  • Last modified date

    2015-04-02

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UA76362

Modules/Macros

  • HZRINMTR HZRINPVT
    

Publications Referenced
SC23684401    

Fix information

  • Fixed component name

    RUN TIME DIAGNO

  • Fixed component ID

    5752SCRTD

Applicable component levels

  • R790 PSY UA76362

       UP15/03/06 P F503

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"790","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"790","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 April 2015