A fix is available
APAR status
Closed as program error.
Error description
Server started task produces the following messages: FPEV0158W DB2C 15:50:17.15 DATA SERVER DETECTED HIGH CPU USAGE (75%) OF TASK DGOVSERV FPEV0162W DB2C 15:50:17.15 TRACES ARE STARTED FOR FURTHER ANALYSIS OF HIGH CPU USAGE FPEV9999I DB2C DGOVWDOG TCB=008A4088 TCB_ttime=000000B1AFF17EC0 FPEV9999I DB2C DGOVWDOG Elapsed time = 0000003C FPEV9999I DB2C DGOVWDOG DGOVTCPL 008C8340 000000000E5B74C0 000000000EABAC00 00000000 FPEV9999I DB2C DGOVWDOG DGOZPMS 0089E088 00000007AD89FB00 00000007B8C15120 00000000 FPEV9999I DB2C DGOVWDOG DGOVEE00 00898088 00000000267B7720 0000000026D21B80 00000000 . Looks like an 'invalid' return area has caused the high CPU consumption when the return area is screened for desired IFCIDs because we may have passed the normal end of the return area. Base on the job output the data server reported an invalid return area and an SDUMP with the name of 'INCORRECT RETURN AREA - SCO1'. is produced.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM * * users of component: * * - PE Server * **************************************************************** * PROBLEM DESCRIPTION: hen performance data are requested * * from the PE Client and the data server * * detects invalid data to be returned, * * the data server initiates an SDUMP with * * title 'INCORRECT RETURN AREA - SCO1' to * * save the invalid return area for later * * analysis. * * In some instances the invalid data may * * cause a loop in the data processing * * module DGOVSERV causing high CPU * * consumption. * * The high CPU consumption is detected by * * the data server which issues message * * FPEV0158W, starts the internal server * * traces and will finally reattach the * * causing subtask if the high CPU * * consumption persists. * * --------------------------------------- * * The service level of the * * OMEGAMON Server is: * * FPEV0000I DATA SERVER INITIALIZATION * * FPEV0114I PTF BUILD IS 2007.016 * * --------------------------------------- * **************************************************************** * RECOMMENDATION: APPLY this PTF * **************************************************************** When suspect data are detected by the data server further processing of such data is immediately discontinued.
Problem conclusion
When performance data are requested from the PE Client and the data server detects invalid data to be returned, the data server initiates an SDUMP with title 'DGOVSCO1 - INCORRECT RETURN AREA xxxxxxxx' to save the invalid return area for later analysis. The dump title contains the address xxxxxxxx of the data area which contains the invalid data. When invalid data are detected further processing is immediately discontinued and the error condition is returned to the PE Client. The data server and PE Client will be available thereafter for normal operation. ------------------------------------------------ Keywords: FPEV0158W FPEV0162W 'INCORRECT RETURN AREA - SCO1' HIGH CPU DGOVSERV
Temporary fix
Comments
APAR Information
APAR number
PK37096
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-01-09
Closed date
2007-01-17
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:
UK21301 UK21302
Modules/Macros
DGOVMSTR DGOVSCON DGOVSCO1
Fix information
Fixed component name
OM XE DB2PE/PM
Fixed component ID
5655OPE00
Applicable component levels
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":"410"}]
Document Information
Modified date:
31 March 2021