PK41645: WS CLIENT INDICATES FALSE STATUS OF THE AGENT OR SHOWS MESSAGE DGOK7000

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• getting dgok7000 when trying to access the AGENT information
  from the PE client.
  table DB2PM.DB2C_GATEWAY and the status says "INACTIVE".
  And the AGENTS are actively running.
  .
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
  *                 users of component:                          *
  *                 -   Performance Expert Client                *
  ****************************************************************
  * PROBLEM DESCRIPTION: 1. The pop-up message DGOK7000 "The     *
  *                      selected DB2 Connect gateway is         *
  *                      currently not active. Switch to history *
  *                      mode and select a date and time at      *
  *                      which the DB2 Connect gateway was       *
  *                      active. " appears when the Performance  *
  *                      Expert client user tries to monitor     *
  *                      statistics for the DB2 Connect/Gateway. *
  *                      The agent is actively running but the   *
  *                      DB2PM.DB2C_GATEWAY table indicates      *
  *                      status "INACTIVE" for the agent.        *
  *                                                              *
  *                      2. The pop-up message DGOK3610          *
  *                      "The selected DB2PM database is not     *
  *                      receiving DB2 Connect/gateway           *
  *                      information" appears when the           *
  *                      PE Client user tries to create          *
  *                      a new DB2 Connect/Gateways view         *
  *                                                              *
  *                                                              *
  *                      For V310:                               *
  *                      The service level of the                *
  *                      OMEGAMON server subtask PESERVER        *
  *                      FPEV0000I  DATA SERVER INITIALIZATION   *
  *                      FPEV0114I  PTF BUILD IS 07.184          *
  *                                                              *
  *                      For V410:                               *
  *                      The service level of the                *
  *                      OMEGAMON server subtask PESERVER        *
  *                      FPEV0000I  DATA SERVER INITIALIZATION   *
  *                      FPEV0114I  PTF BUILD IS 07.183          *
  ****************************************************************
  * RECOMMENDATION: Apply this PTF.                              *
  *                 See additional recommendations and           *
  *                 explanations in the technote "Explanation    *
  *                 of the APAR PK41645 and dealing with any     *
  *                 unexpected remaining issues with DB2         *
  *                 Connect data monitoring".                    *
  ****************************************************************
  The problem might be caused by the following reasons:
  
  1. Two PESERVERS are running on two different LPARs and
  monitoring the same DB2 instances being members of a data
  sharing group and these PESERVERS have not correspondingly
  identical values set for the one or some the following
  start-up parameters: SHTHREAD, SHSTATISTICS,
  SHDB2CONNECTSYSTEM, SHDB2CONNECTAPPLICATION.
  2. Z/OS operator issued a MODIFY command changing one or
  some of the following snapshot history intervals:
  SHTHREAD, SHSTATISTICS, SHDB2CONNECTSYSTEM,
  SHDB2CONNECTAPPLICATION.
  
  Each of these cases might cause mistiming in PESERVER and
  DB2 Connect Server interactions when the mentioned above
  history snapshot intervals become different in the PDA, HDA
  internal control blocks of PESERVER and in the corresponding
  rows of the DB2PM.HISTORYDATA DB2 table used for collecting
  DB2 Connect data.
  

Problem conclusion

• The PESERVER code is modified to prevent the cases of
  mistiming described in the Problem Summary section.
  
  KEYWORDS : DGOK7000 DGOK3610
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

•    DUMM2KO2
  

Fix information

• Fixed component name

  OM XE DB2PE/PM

• Fixed component ID

  5655OPE00

Applicable component levels

• R310 PSN UK26908

     UP07/07/12 P F707

• R410 PSN UK26909

     UP07/07/12 P F707

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.