IBM Support

PK57706: INCORROUT WHEN LAUNCHING APPL TRACE FROM ZTDTL

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When launching APPICATION TRACE specify trace panle ZATRQ2 from
    the Thread Detail panel ZTDTL in VTAM scrambled values are
    displayed (for example in the plan and authid fields).
    
    Sample screenshot:
    
     ________________ ZATRQ2   VTM     O2       V410./C D911
    08/24/07 13:05:06   2
    > Help PF1
    Back PF3
    
    >       THREAD INFORMATION:  Enter a selection letter on the top
    line.
    
    > A-THREAD DETAIL B-LOCK COUNTS C-LOCK WAITS     D-LOCKS OWNED
    E-GLOBAL LOCKS
    > F-CURRENT SQL   G-SQL COUNTS  H-DISTRIBUTED    I-BUFFER POOL
    J-GROUP BP
    > K-PACKAGES      L-RES LIMIT   M-PARALLEL TASKS N-UTILITY
    O-OBJECTS
    > P-CANCEL THREAD Q-DB2 CONSOLE R-DSN ACTIVITY   *-APPL TRACE
    T-ENCLAVE
    > U-LONG NAMES
    ================================================================
    >                          SPECIFY APPLICATION TRACE
     ATRQ
    + Type DB2 Plan name to be traced. Also, provide additional
    optional
    + selection information to limit trace output. To save trace
    records
    + for later viewing you must specify a data set name for DSN
    +
    :            DSN= ____________________________________________
    Data set name
    :           TIME= 0005     Number of mins to trace (0001-0060)
    :          FLUSH= 300      Number of seconds between VSAM writes
    :       PLANNAME= KO2PLAN    DB2CALL    D911DM4S       ....
    .&(.....         <--- can be scrambled
    :                          Plan name(s) or ALL for all active
    threads
    :         AUTHID= DB2PM                   <--- can be scrambled
    :                          DB2 authorization identifier(s)
    :        TSOUSER= ________ TSO USERID (TSO foreground app)
    :        JOBNAME= ________ Jobname (TSO batch app)
    :       CICSTRAN= ____     CICS trans id
    :       CICSCONN= ________ CICS connection id)
    :        PSBNAME= ________ IMS PSB name
    :          IMSID= ________ IMS ID of the IMS region
    :       LOCKDATA= Y        Collect DB2 lock trace recs? (Y/N)
    :       SCANDATA= Y        Collect DB2 scan trace recs? (Y/N)
    :        SQLDATA= Y     Collect DB2 sql  trace recs? (Y/N)
    :       THRDDATA= Y     Collect DB2 thread trace recs?  (Y/N)
    :       CONNDATA= Y     Collect DB2 connect trace recs? (Y/N)
    :            SMF= N     Write trace data to SMF? (Y/N)
    :            GTF= N     Write trace data to GTF? (Y/N)
    :        MEMSIZE= 02    Collection workarea memory size (01-04
    meg)
    ================================================================
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
    *                 users of component:                          *
    *                 -   Classic Interface                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: INCORROUT WHEN LAUNCHING APPL TRACE     *
    *                      FROM ZTDTL                              *
    ****************************************************************
    * RECOMMENDATION: APPLY THIS PTF                               *
    ****************************************************************
    PROBLEM SUMMARY:
    APPLICATION TRACE NOW ALLOWS UP TO FIVE
    PLANNAMES AND FIVE AUTHIDS TO BE SPECIFIED ON THE ATF REQUEST
    ENTRY PANEL.  WHEN ATF IS INVOKED FROM THREAD DETAIL, THE FOUR
    ADDITIONAL FIELDS WERE NOT PROPERLY INITIALIZED TO BLANKS.
    
    PROBLEM CONCLUSION:
    INITIALIZE ALL PLAN NAME AND AUTHID FIELDS PROPERLY.
    

Problem conclusion

  • INITIALIZE ALL PLAN NAME AND AUTHID FIELDS PROPERLY.
    
    KEYWORDS :
    ZATRQ2 INCORROUT APPLICATION ATRQ THREAD DETAIL DYNAMIC SQL
    HISTORY
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK57706

  • Reported component name

    OM XE DB2PE/PM

  • Reported component ID

    5655OPE00

  • Reported release

    310

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-12-05

  • Closed date

    2007-12-10

  • Last modified date

    2008-01-03

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

    PK51710

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

Modules/Macros

  • DUMM3KO2
    

Fix information

  • Fixed component name

    OM XE DB2PE/PM

  • Fixed component ID

    5655OPE00

Applicable component levels

  • R310 PSN UK32075

       UP07/12/12 P F712

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:
03 January 2008