A fix is available
APAR status
Closed as program error.
Error description
During PE Server start up the Application Services subtask executes SQL SELECT COUNT(*) FROM SYSIBM.SYSDATABASE, gets SQL code -913 (UNSUCCESSFUL EXECUTION CAUSED BY DEADLOCK OR TIMEOUT) and thus issues FPEV1205S and terminates as response to the unavailable DB2 resource. The problem indicated by error message FPEV1205S does not justify the termination of the whole OMEGAMON collector started task because the problem might affect only one DB2 subsystem out of a list of DB2 subsystems desired to be monitored. Therefore PE Server subtasks which could successfully be started for other DB2 subsystems remain up and running. Message FPEV1205S is issued at the time the PE Server subtask is started for a DB2 subsystem to be monitored and is issued at exactly one place in the code. The corresponding action could either be to stop and restart the OMEGAMON collector stated task or to just re-start the PE Server subtask for the DB2 subsystem mentioned in message FPEV1205S. The appropriate modify command to start the monitoring PE Server subtask is /F <STC>, F PESERVER,S <DB2SSID> where <STC> is the name of the OMEGAMON started task and <DB2SSID> is the DB2 subsystem ID e.g. DB2 subsystems DB2A and DB2B are configured. DB2B can not be monitored using the GUI (PE Client) because the application services main task ended. For DB2A the monitoring PE Server subtask inclusive the application services started successfully and thus monitoring with the GUI is enabled and must work. The customer mentioned that the GUI does not work for any of the subsystems in such scenario. That would be a bug. The application server mentioned in message FPEV1205S as APPL SERVICES MAIN TASK is the component of a monitoring PE Server subtask which manages the connections to PE Clients. Currently only the Application Services task ends but the monitoring PE Server subtask remains up and running. This behavior could be changed such that the monitoring PE Server subtask ends as well.
Local fix
You can try to re-start the PE Server subtask for the DB2 subsystem mentioned in message FPEV1205S. The appropriate modify command to start the monitoring PE Server subtask is /F <STC>, F PESERVER,S <DB2SSID> where <STC> is the name of the OMEGAMON started task and <DB2SSID> is the DB2 subsystem ID The PE Client no longer works without recycling the collector. Restarts on both address spaces are usually required to get things working again. NOTE: 1. Optimize the specific SQL clause to minimize locking and thus reduce the likelihood of deadlocks/timeouts. 2. If the application server terminates, the whole monitoring PE Server subtask terminates but monitoring PE Server subtasks which could be started successfully for other DB2 subsystems remain up and running.
Problem summary
**************************************************************** * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM * * users of component: * * - PE Server subtask * **************************************************************** * PROBLEM DESCRIPTION: During start up of a monitoring PE * * Server subtask the component * * 'Application Services' detects an * * error condition, issues message * * FPEV1205S and terminates. The * * monitoring PE Server subtask remains * * up and running instead of being * * stopped. * * * **************************************************************** * RECOMMENDATION: Apply this PTF * * * **************************************************************** PROBLEM SUMMARY: When a PE Server subtask is started to monitor a DB2 subsystem and the component 'Application Services' (task FPEVSERV) terminates during start up, the PE Server subtask remains up and running although data retrieval requests will fail. PROBLEM CONCLUSION: When a PE Server subtask is started to monitor a DB2 subsystem and the component 'Application Services' (task FPEVSERV) terminates during start up, the PE Server subtask stops. Depending on the error causing the termination of task FPEVSERV either message FPEV1203S, FPEV1204S or FPEV1205S is issued followed by message FPEV0027E to indicate termination of task FPEVSERV. Message FPEV0224I is issued followed by message FPEV0169E to indicate that the PE Server subtask stopped with error.
Problem conclusion
When a PE Server subtask is started to monitor a DB2 subsystem and the component 'Application Services' (task FPEVSERV) terminates during start up, the PE Server subtask stops. Depending on the error causing the termination of task FPEVSERV either message FPEV1203S, FPEV1204S or FPEV1205S is issued followed by message FPEV0027E to indicate termination of task FPEVSERV. Message FPEV0224I is issued followed by message FPEV0169E to indicate that the PE Server subtask stopped with error. KEYWORDS : FPEV1205S APPLICATION SERVICES
Temporary fix
Comments
APAR Information
APAR number
PM87862
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
2013-04-25
Closed date
2013-08-29
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:
UK97122 UK97123
Modules/Macros
DGO@SDOB DGOVMSTR DGOVSDOB FPEVM000 FPEVSERV
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.
[{"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":"5.1.0","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":"5.1.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
04 February 2017