A fix is available
APAR status
Closed as program error.
Error description
ISPF online monitor OLM CRD to handle multiple start trace sequences. . The problem can be recreated by using the OMPE V510 ISPF OLM function "DB2 command input" only, by using 2 TSO sessions. - In TSO session 1 start OLM and use DB2 cmd input panel - Stop all traces - DISPLAY TRACE(*) will show: DSNW137I -D911 SPECIFIED TRACE NOT ACTIVE DSN9022I -D911 DSNWVCM1 '-DISPLAY TRACE' NORMAL COMPLETION - Start a 1st PERFM trace: START TRACE(PERFM) DEST(OPX) CLASS(18) DSNW130I -D911 PERFM TRACE STARTED, ASSIGNED TRACE NUMBER 01 DSN9022I -D911 DSNWVCM1 '-START TRACE' NORMAL COMPLETION - DISPLAY TRACE(*) will show: DSNW127I -D911 CURRENT TRACE ACTIVITY IS - TNO TYPE CLASS DEST QUAL IFCID 01 PERFM 18 OP1 NO *********END OF DISPLAY TRACE SUMMARY DATA********* DSN9022I -D911 DSNWVCM1 '-DISPLAY TRACE' NORMAL COMPLETION . - In TSO session 2 start OLM and use DB2 cmd input panel - DISPLAY TRACE(*) will show the same as in session 1: DSNW127I -D911 CURRENT TRACE ACTIVITY IS - TNO TYPE CLASS DEST QUAL IFCID 01 PERFM 18 OP1 NO *********END OF DISPLAY TRACE SUMMARY DATA********* DSN9022I -D911 DSNWVCM1 '-DISPLAY TRACE' NORMAL COMPLETION - Start a 2nd ACCTG trace: START TRACE(A) D(OPX) BUFSIZE(1024) C(03) DSN9022I -D911 DSNWVCM1 '-DISPLAY TRACE' NORMAL COMPLETION DSNW130I -D911 A TRACE STARTED, ASSIGNED TRACE NUMBER 02 DSN9022I -D911 DSNWVCM1 '-START TRACE' NORMAL COMPLETION - DISPLAY TRACE(*) will show that OP1 is used. DSNW127I -D911 CURRENT TRACE ACTIVITY IS - TNO TYPE CLASS DEST QUAL IFCID 01 PERFM 18 OP1 NO 02 ACCTG 03 OP1 NO *********END OF DISPLAY TRACE SUMMARY DATA********* DSN9022I -D911 DSNWVCM1 '-DISPLAY TRACE' NORMAL COMPLETION - Start a 3rd RERFM trace using the same OPn from 2nd ACCTG trace: START TRACE(P) D(OP1) BUFSIZE(1024) C(06,07,17,20,21) DSN9022I -D911 DSNWVCM1 '-DISPLAY TRACE' NORMAL COMPLETION DSNW184I -D911 OP BUFFER OP1 NOT AVAILABLE DSN9023I -D911 DSNWVCM1 '-START TRACE' ABNORMAL COMPLETION =============================================================== DB2 development informed the following rules, ie. "The rules are this: 1. The same OP buffer can be shared if the starter of the trace is the same agent. This agent already owns the buffer and can presumably make a decision to add addtional trace data to that buffer OR 2. If the trace does not produce real output (i.e., is just a bunch of internal switches), it will pick OP1 even if from a different agent. Since the trace isn't going to generate IFCID records, the OP buffer doesn't matter." ================================================================
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM * * users of component * * - ISPF Monitoring dialogs * **************************************************************** * PROBLEM DESCRIPTION: Some tasks are using the DB2 OP * * buffers. The ISPF Collect Report Data * * task is just one of these tasks. * * Sometimes the error message * * "DSNW184I ssid OP BUFFER OPn NOT * * AVAILABLE" occurs for DB2 V9 or V10. * **************************************************************** * RECOMMENDATION: Apply this PTF * **************************************************************** PROBLEM SUMMARY: Some tasks are using the DB2 OP buffers. The ISPF Collect Report Data task is just one of these tasks. Sometimes the error message "DSNW184I ssid OP BUFFER OPn NOT AVAILABLE" occurs for DB2 V9 or V10. PROBLEM CONCLUSION: The logic to get a free OP buffer number was changed from "START TRACE DEST(OPX)" to "DISPLAY TRACE output analysis". KEYWORDS: OMPE-OLM CRD-6A-TASK OP-BUF-NOT-AVAILABLE DSNW184I
Problem conclusion
PROBLEM CONCLUSION: The logic to get a free OP buffer number was changed from "START TRACE DEST(OPX)" to "DISPLAY TRACE output analysis". KEYWORDS: OMPE-OLM CRD-6A-TASK OP-BUF-NOT-AVAILABLE DSNW184I
Temporary fix
Comments
APAR Information
APAR number
PM56530
Reported component name
OM XE DB2PE/PM
Reported component ID
5655OPE00
Reported release
510
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2012-01-23
Closed date
2012-04-30
Last modified date
2012-06-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK78385
Modules/Macros
DGOMAOPN DGOMASTA DGOMAXA0 FPEUU120 HKDB510J KDB510J
Fix information
Fixed component name
OM XE DB2PE/PM
Fixed component ID
5655OPE00
Applicable component levels
R510 PSY UK78385
UP12/05/02 P F205
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.
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSZJXP","label":"DB2 Tools for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.1.0"}]
Document Information
Modified date:
30 March 2021