A fix is available
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: * * - OMEGAMON Server * * - Classic Interface * **************************************************************** * PROBLEM DESCRIPTION: INCORROUT WHEN INVOKING ATF FROM * * THREAD DETAIL SCREEN. * **************************************************************** * RECOMMENDATION: Apply this PTF * **************************************************************** PLANNAME AND AUTHID FIELDS NOT INITIALIZED CORRECTLY
Problem conclusion
CORRECT INITIALIZATION OF THESE NEW FIELDS. KEYWORDS: ATRQ2 THREAD DETAIL ATF APPLICATION TRACE
Temporary fix
Comments
APAR Information
APAR number
PK51710
Reported component name
OM XE DB2PE/PM
Reported component ID
5655OPE00
Reported release
410
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2007-08-24
Closed date
2007-09-28
Last modified date
2017-02-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK29741 PK57706
Modules/Macros
KO2ASUBA KO2ASUBS KO2ASUB2 KO2ATRCB KO2OTHDB
Fix information
Fixed component name
OM XE DB2PE/PM
Fixed component ID
5655OPE00
Applicable component levels
R410 PSY UK29741
UP07/09/29 P F709
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":"410","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":"410","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
04 February 2017