IBM Support

PK22696: APPLICATION TRACE STOP COMMAND: ATST NOT HONORED WITH LOW-VOLUME TRACE DATA

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Application trace stop command: ATST not honored with low-volume
    trace data.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of OMEGAMON XE for DB2 PE/DB2PM V310   *
    ****************************************************************
    * PROBLEM DESCRIPTION: -  WHEN ATTEMPTING TO VIEW RECORDS      *
    *                         WRITTEN BY THE ATF TO ITS OUTPUT DS, *
    *                         RECEIVE  PANEL MESSAGE "NO VSAM      *
    *                         RECORDS CRITERIA."                   *
    *                      -  ATF IS IGNORING STOP COMMAND.        *
    *                         UNIT OF WORK FLUSH INTERVAL IS       *
    *                         IGNORED WHEN NOT TRACING TO DATASET. *
    *                         EXISTING TRACE DATA IN OPX           *
    *                         BUFFER IS NOT CAPTURED AFTER USER    *
    *                         ISSUES MANUAL TRACE STOP COMMAND:    *
    *                         ATST.  DSNW133I MESSAGES IN DB2      *
    *                         MASTER ADDRESS SPACE.                *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF                                *
    ****************************************************************
    -  WHEN ATTEMPTING TO VIEW RECORDS WRITTEN BY THE ATF TO
       ITS OUTPUT DS, RECEIVE PANEL MESSAGE "NO VSAM RECORDS
       MATCHES SELECTED ,CRITERIA."
    -  A LOW-VOLUME APPLICATION TRACE IS IGNORING THE STOP COMMAND:
       ATST. THE TRACE REMAINS ACTIVE UNTIL THE SPECIFIED TIME HAS
       EXPIRED. THIS PROBLEM OCCURS IN BOTH CLASSIC AND CUA
       SESSIONS. THE UNIT OF WORK FLUSH INTERVAL IS NOT HONORED TO
       CONTROL FLUSHING OF THE OPX BUFFER IN THE CASE WHERE
       USER IS NOT CAPTURING TRACE DATA TO A DATASET. THE EXISTING
       CONTENT OF THE DB2 OPX BUFFER IS NOT CAPTURED AFTER A USER
       ISSUES THE ATST COMMAND TO STOP AN APPLICATION TRACE.  ATF
       WAS NOT CORRECTLY COMPUTING THE HIGH WATER MARK
       FOR DB2 OPX BUFFER SIZE.
    

Problem conclusion

  • -  THE PROBLEM MAY BE RESOLVED BY CHANGING THE INTERVAL
       TIME USED TO CONTROL FLUSHING APPLICATION TRACE DATA
       FROM THE INTERNAL BUFFERS TO THE VSAM DATASET.  THIS
       INTERVAL TIME MAY BE CHANGED BY USERMOD.  THE USERMOD IS
       FOUND IN HILEV.TKANSAM(KO2MOD01).  THE VALUE TO CHANGE
       WAS PREVIOUSLY NOT DOCUMENTED, BUT WITH THIS PTF,
       HILEV.TKANSAM(KO2MOD01) IS REPLACED BY A MEMBER
       CONTAINING THE NECESSARY DOCUMENTATION FOR THIS USER
       MODIFIABLE FIELD.  THE VALUE TO MODIFY IS REFERRED TO AS
       "17  CHANGE THE UNIT OF WORK FLUSH INTERVAL".
    -  THE ATF CODE WAS MODIFIED TO POST THE WAITING ECB WHENEVER
       A STOP COMMAND IS ISSUED.  CODE WAS CHANGED TO HONOR THE
       UNIT OF WORK FLUSH INTERVAL EVEN WHEN CAPTURING DATA TO
       STORAGE ONLY.  CODE WAS CHANGED TO FLUSH THE OPX BUFFER
       WHENEVER A USER USES THE ATST COMMAND TO MANUALLY STOP THE
       EXISTING APPLICATION TRACE.
       ADD CODE TO CORRECTLY COMPUTE OPX BUFFER SIZE.
    
    SYSMOD Title:
        ATF ABEND0C4 in module KO2ACAF2 Offset=001974
        Inconsistent output between panels ATD1 and ATSI
        ATF SCREENS DISPLAY ZERO INDB2 CPU.
        O21129 APPLICATION TRACE HAS BEEN TERMINATED
        IFCARLC and VSAMTSK values greater than zero
        APPLICATION TRACE FAILS TO STOP WHEN REQUESTED.
    Keywords:
        ATF ABEND0C4 KO2ACAF2 ATRQ UIFCIDS
        IN-DB2 TIME ATSI ATD1 STM# STMT# ZERO INCORROUT
        CPU APPLICATION TRACE ZATVW
        MSGO21129 UOW USERMOD KO2MOD01
        MSGO21152 O21152 IFCARLC VSAMTSK DSNW133I
        ATST ZATST KD2PSA2P STOP APPLICATION TRACE BUFFER
        UNIT OF WORK OP OPX MISSING TRACE DATA
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    PK22696

  • Reported component name

    OM XE DB2PE/PM

  • Reported component ID

    5655OPE00

  • Reported release

    310

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2006-04-03

  • Closed date

    2006-04-11

  • Last modified date

    2006-05-01

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

    OA15781

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

    UK13407

Modules/Macros

  •    KO2ACAFS KO2ACAF2 KO2ACAPS KO2ACAP2 KO2ASUBS
    KO2ASUB2 KO2ATRCB KO2ATRPB KO2ICAFS KO2ICAF2 KO2MOD01 KO2ODCNB
    

Publications Referenced
GC18963800    

Fix information

  • Fixed component name

    OM XE DB2PE/PM

  • Fixed component ID

    5655OPE00

Applicable component levels

  • R310 PSY UK13407

       UP06/04/14 P F604

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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSAV2B","label":"IBM Db2 Buffer Pool Analyzer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"310","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCT4H5","label":"IBM Tivoli OMEGAMON XE for Db2 PE \/ PM \/ BPA"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"310","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
01 May 2006