OA33043: IF2 ENHANCEMENTS TO ATF/NTH NAVIGATION AND CPU TIME, BATCH TRF, DBCTL DATA.

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as new function.

Error description

  • It is cumbersome to navigate between transaction instances when
    viewing ATF and NTH detail panels.  Allow navigation to the
    previous (PF5) and next (PF6) detail record from the ATF and NTH
    detail panels instead of having to return to the summary panel
    for the next transaction.
    
    More granularity is needed for CPU times displayed in ATF, NTH,
    and batch TRF.  ATF transaction level CPU times will be broken
    down by region type (control, dependent, and DLISAS), call type
    (DL/I, DB2, and MQ), and individual event.  NTH transaction
    level CPU times will be broken down by TCB, SRB, and individual
    DL/I database calls.  Batch TRF will include CPU metrics for
    DL/I and Fast Path databases.
    
    When no TRF records are found in the IMS log or SMF dataset
    input to the TRF batch extractor, there is no indication of this
    potential error and the job step has a zero condition code.  The
    batch extractor will output a WTO message for this condition and
    set the job step condition code based on a new NOTRF parameter
    value in the batch TRF JCL.
    
    Certain OMEGAMON IMS fixes require an IPL of z/OS to be run in
    order to complete installation of the fix.  A new KIPWIPER
    utility eliminates the need to run an IPL when applying OMEGAMON
    IMS maintenance.
    
    Monitoring the performance and throughput of DBCTL threads is
    difficult without unit-of-work (UOW) metrics.  Improve support
    for DBCTL threads in both the 3270 and TEP interfaces by
    providing UOW input and process rates as well as  thread
    occupancy percentage and elapsed thread time.
    
    When running ATF/NTH and archiving the trace data to  VSAM,
    there is no way to detect when the data has been completely
    written to a given VSAM dataset.  This would allow system
    automation to invoke any desired reporting or backup of the VSAM
    dataset.  A new ARCHAUTO parameter has been added for journaling
    which determines whether messages should be output during
    archival when switching VSAM datasets.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All OMEGAMON for IMS V4.2.0 on z/OS          *
    ****************************************************************
    * PROBLEM DESCRIPTION: V4.2.0 Interim Feature 2 - IF2          *
    ****************************************************************
    * RECOMMENDATION: Apply this PTF.                              *
    ****************************************************************
    1.  It is cumbersome to navigate between transaction
        instances when viewing ATF and NTH detail data.
    2.  More granularity is needed for CPU times displayed
        in ATF, NTH, and batch TRF.
    3.  When no TRF records are found in the IMS log or SMF
        dataset input to the TRF batch extractor, there is
        no indication of this potential error and the job
        step completes with a zero condition code.
    4.  Certain OMEGAMON IMS PTFs require an IPL of z/OS to be
        run in order to complete the installation of the PTF.
    5.  Monitoring the performance and throughput of DBCTL
        threads is difficult without unit-of-work (UOW) metrics.
    6.  When running ATF/NTH and archiving trace data to VSAM,
        there is no way to detect when the data has been
        completely written to a given VSAM dataset which
        would allow system automation to invoke any desired
        reporting or backup of the VSAM dataset.
    7.  In a high transaction volume environment, a JLF write
        error with RC=0000001E can be followed by several JLF
        write errors with RC=00000048.  Message KI2AT820E or
        KI2NT820E is issued when a JLF write error occurs.
    8.  Improve performance of ATF and NTH when collecting
        trace data.
    

Problem conclusion

Temporary fix

Comments

  • 1.  Allow navigation to the previous (PF5) and next (PF6)
        detail record from the ATF and NTH detail panels instead
        of having to return to the summary panel for the next
        transaction.
    2.  ATF transaction level CPU times will be broken down by
        region type (control, dependent, DLISAS), call type
        (DL/I, DB2, and MQ), and individual event.
        NTH transaction level CPU times will be broken down
        by TCB, SRB, and individual DL/I database calls.
        Batch TRF will include CPU time metrics for DL/I and
        Fast Path databases.
    3.  When no TRF records are input to batch TRF, a new
        message, KI2TR800I, will be output for this condition.
        In addition, a new NOTRF parameter has been added to
        the batch TRF JCL to indicate the job set condition
        code to be returned when no TRF records are input.
    4.  A new KIPWIPER utility has been provided to eliminate
        the need to run an IPL when applying OMEGAMON IMS
        maintenance.  Future PTFs will include, when necessary,
        HOLD instructions indicating that the KIPWIPER
        utility must be run to complete the installation of
        the PTF.
    5.  Support for DBCTL threads has been improved in both
        the 3270 and TEP interfaces by providing UOW input
        and process rates as well as thread occupancy and
        elapsed thread time.
    6.  A new ARCHAUTO parameter has been added for journaling
        which determines whether messages should be output
        during archival when switching VSAM datasets. The
        ARCHAUTO parameter is specified in member KOIJLF00
        member of RKANPARU and can have a value of YES or NO.
    7.  When an unexpected JLF write error occurs, journal
        logging will be disabled to prevent further write errors.
        In this case, message KI2AT821E or KI2NT821E will be
        issued indicating journal logging has been disabled due
        to the previous JLF write error.  In addition, a read
        operation to retrieve trace data will be pre-empted if a
        write operation is in progress, thus, allowing the Write
        to complete.  This should only occur when tracing a high
        volume of transactions and attempting to view the trace
        data during this high volume.  The pre-empted Read will
        result in a JLF busy message being returned to the
        OMEGAMON 3270 display and message KI2AT826W or KI2NTH826W
        output indicating the Journal Logging Facility is busy -
        unable to service the read request.
    
    8.  The ATF queueing mechanism has been modified to improve
        throughput and eliminate recursive chain errors, message
        ATF1030E.  TRF/NTH has been updated to properly handle
        incomplete UOWs, thereby, reducing storage and CPU
        consumption.
    
        New startup parameters have been added for ATF and NTH
        to improve performance and resource usage.
    
        New BUFFSIZE startup parameter for ATF and NTH specifies
        the number of bytes in KB that ATF or NTH will use to
        buffer data to the Journal Logging Facility (JLF).  A JLF
        buffer write is signaled when the buffer becomes full.
        Too many JLF buffer writes may cause performance
        degradation of the OMEGAMON address space.  Adjusting
        to a larger buffer size in higher volume transaction
        environments will allow fewer JLF buffer writes and
        better overall performance.  The value for BUFFSIZE can
        be from 4-16384; the default is 32 (32KB).
    
        New ECSAMAX startup parameter for ATF specifies the
        maximum number of bytes in KB that ATF can obtain in
        ECSA to buffer trace event records.  Caution should be
        used with this value not to over-allocate ECSA but also
        not to under-allocate it as ATF may need to suspend
        collection if not enough ECSA is available to handle the
        higher transaction volume environments.  ESCAMAX can
        range from 256-32768; the default is 8192 (8192KB).
    ž**** PE10/12/08 FIX IN ERROR. SEE APAR OA34982  FOR DESCRIPTION
    

APAR Information

  • APAR number

    OA33043

  • Reported component name

    OM XE FOR IMS Z

  • Reported component ID

    5698A3900

  • Reported release

    420

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-05-13

  • Closed date

    2010-06-25

  • Last modified date

    2010-12-08

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

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

Modules/Macros

  • KIPAGENT KIPCMD00 KIPCOL00 KIPDCIF1 KIPDSPL1
    KIPICS00 KIPMCB00 KIPPLEX  KIPSCDI0 KIPSCDJ0 KIPSCDK0 KIPSCDL0
    KIPTHDI0 KIPTHDJ0 KIPTHDK0 KIPTHDL0 KIPTHSI0 KIPTHSJ0 KIPTHSK0
    KIPTHSL0 KIPWIPER KI2AHAI0 KI2AHAJ0 KI2AHAK0 KI2AHAL0 KI2AJI00
    KI2AJW00 KI2ARJ00 KI2AT000 KI2BS000 KI2BT0I0 KI2BT0J0 KI2BT0K0
    KI2BT0L0 KI2CF000 KI2DDR00 KI2DL0IQ KI2DL0JQ KI2DL0KQ KI2DL0LQ
    KI2DR000 KI2FLT00 KI2LL0IQ KI2LL0JQ KI2LL0KQ KI2LL0LQ KI2MN0I0
    KI2MN0J0 KI2MN0K0 KI2MN0L0 KI2MR000 KI2NJI00 KI2NJW00 KI2NRJ00
    KI2NR000 KI2PB0IQ KI2PB0JQ KI2PB0KQ KI2PB0LQ KI2PC0IQ KI2PC0JQ
    KI2PC0KQ KI2PC0LQ KI2PUT00 KI2RI0IQ KI2RI0JQ KI2RI0KQ KI2RI0LQ
    KI2SUMI0 KI2SUMJ0 KI2SUMK0 KI2SUML0 KI2SX000 KI2TC0I0 KI2TC0J0
    KI2TC0K0 KI2TC0L0 KI2TIA00 KI2TM000 KI2TP0I0 KI2TP0J0 KI2TP0K0
    KI2TP0L0 KI2TRA00 KI2TRD00 KOIAM000 KOIAV000 KOICMD00 KOIID0IQ
    KOIID0JQ KOIID0KQ KOIID0LQ KOIIP0I0 KOIIP0J0 KOIIP0K0 KOIIP0L0
    KOIIR0I0 KOIIR0J0 KOIIR0K0 KOIIR0L0 KOIIT000 KOIIU000 KOIIV00Q
    KOIJMP0Q KOIJMS00 KOIJMV0Q KOIMI0IQ KOIMI0JQ KOIMI0KQ KOIMI0LQ
    KOINC0IQ KOINC0JQ KOINC0KQ KOINC0LQ KOINM000 KOINV000 KOIPWIIQ
    KOIPWIJQ KOIPWIKQ KOIPWILQ KOIRG0IQ KOIRG0JQ KOIRG0KQ KOIRG0LQ
    KOISB000 KOISR0IQ KOISR0JQ KOISR0KQ KOISR0LQ KOITH0I0 KOITH0J0
    KOITH0K0 KOITH0L0
    

Fix information

  • Fixed component name

    OM XE FOR IMS Z

  • Fixed component ID

    5698A3900

Applicable component levels

  • R420 PSY UA55228

       UP10/07/06 P F007

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.



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli OMEGAMON XE for IMS on z/OS

Software version:

420

Reference #:

OA33043

Modified date:

2010-12-08

Translate my page

Machine Translation

Content navigation