A fix is available
APAR status
Closed as program error.
Error description
*** Original APAR text *** ABEND0C4 DSNWAAPI+1AD0 (at UK38867 level), R8 which should have pointed to the IFCA, did not. A bit earlier another ABEND0C4-11 is seen and occurs in DSNWACMD+282 (at UK36546 level) trying to access the return area in the ALLIED ADDRESS SPACE (Omegamon's). A DISPLAY UTILITY(*) command is queued to FPEVDB2I for execution in DB2. FPEVDB2I did not respond within 10 seconds which Omegamon's Exchange Layer detected as a timeout and freed the return area. DB2 however tries to use this now freed return area and program checks. While READS requests are protected on FPEVDB2I side from writing to freed return areas, the command requests are not and must be changed to do so. This will prevent the ABENDs from occurring. *** Modified (more generic) APAR text *** This APAR now covers all exchange layer call issues of the form: KO2O1942E EXCHANGE LAYER CALL - REASON CODE 000000xx where xx can be at least one of: 64 7B 80 85 00000064 0000007B 00000080 00000085 This message can simply be due to timeouts caused by local system and network problems. This APAR deals with very frequent occurrence of the messages. KO2O1941E DSNT EXCHANGE LAYER CALL - RETURN CODE
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM * * users of component: * * - PE Server subtask * * - Classic Interface * **************************************************************** * PROBLEM DESCRIPTION: Data retrieval requests issued from * * the Classic Interface (VTAM) return * * with bad return and reason codes * * because of timeout conditions * * experienced during data retrieval and * * processing in the PE Server subtask. * * Messages KO2O1941E and KO2O1942E are * * issued with return code 8 and * * hexadecimal reason codes 64,7B,80 and * * 85. * * When internal DB2 commands issued by * * the PE Server subtask experience a * * timeout, the corresponding DB2 module * * causes an Abend 0C4 when it tries to * * return the response to the issued * * command. * * * **************************************************************** * RECOMMENDATION: Apply this PTF * **************************************************************** PROBLEM SUMMARY: A maximum elapsed time of 10 seconds is allowed for the completion of requests submitted from the Classic Interface to the PE Server subtask. When the maximum elapsed time expires, a timeout condition is reported. In case of timeouts resources allocated to handle data retrieval requests remain allocated until DB2 IFI returns data while resources allocated to handle internal DB2 commands are freed before DB2 IFI returns response issued command and cause Abend 0C4. to the issued command and cause Abend 0C4. PROBLEM CONCLUSION: When internal DB2 commands issued by the PE Server subtask experience a timeout, the corresponding resources remain allocated until DB2 IFI completes the response to the issued command. The majority of the elapsed time is caused by wait times while the processing task is not dispatched. The processing of requests in the PE Server subtask was improved to reduce CPU consumption and decrease the likelihood of timeouts. The OMEGAOMON Collector should be run at the same or higher priority as the monitored DB2 subsystem to get enough CPU cycles to complete data retrieval requests in time.
Problem conclusion
When internal DB2 commands issued by the PE Server subtask experience a timeout, the corresponding resources remain allocated until DB2 IFI completes the response to the issued command. The majority of the elapsed time is caused by wait times while the processing task is not dispatched. The processing of requests in the PE Server subtask was improved to reduce CPU consumption and decrease the likelihood of timeouts. The OMEGAOMON Collector should be run at the same or higher priority as the monitored DB2 subsystem to get enough CPU cycles to complete data retrieval requests in time. KEYWORDS : KO2O1941E KO2O1942E RETURN CODE 8 REASON CODE 00000080'x TIMEOUT ABEND 0C4 DSNWAAPI
Temporary fix
Comments
APAR Information
APAR number
PK83539
Reported component name
OM XE DB2PE/PM
Reported component ID
5655OPE00
Reported release
410
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-03-27
Closed date
2009-05-28
Last modified date
2009-07-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK46961 PK89574
Modules/Macros
DGO@CRDP DGOVISI DGOVMSTR DGOVM001 DGOVM002 DGOZCRDC DGOZCRDP DGOZCRDS DGOZCRDW DGOZPRSE DGOZUAUT FPE@DB2I FPEVDB2I FPEVRACF FPEZCRD
Fix information
Fixed component name
OM XE DB2PE/PM
Fixed component ID
5655OPE00
Applicable component levels
R410 PSY UK46961
UP09/06/03 P F906
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:
01 July 2009