PK65347: KO2I1001W CONNECTION OMPE SERVER LOST RC24 RC14 RC18 RSN28 RSN36RSN6C ALSO KO2I1002E

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Customer gets these failed connection messages:
  KO2I1001W Connection to OMPE ServerOMDB2CI  for DB2 D1AN lost.
     Return=00000018 Reason=00000028
  (0001-E0ED7383:kdp05agt,374,"ProcessAVT") Error in d5api()
     for kdp05agt, rc = 24
  (0000-E0D96573:kdpd5api,214,"d5api_connect")
     Problem with connect DB2 DBAW RC 24 RSN 36
  (0002-E0ED7383:kdp05agt,374,"ProcessAVT") Error in d5api()
     for kdp05agt, rc = 20
  (0001-E0D96573:kdpd5api,214,"d5api_connect")
     Problem with connect DB2 DBAW RC 20 RSN 108.
  (0003-E0D96573:kdpd5api,278,"d5api_connect")
     KO2I1002E Connection to OMPE Server OMDB2CI Failed Subsystem
     DBA
     Return=00000014 Reason=0000006C Not Retrying
  

Local fix

• Please apply PTF when available.
  .
  Possible circumvention is to change the STIMER value to
  something higher.  In customer's case it was set to 00010000
  and changed to 00020000, and recycle OMDB2CI.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
  *                 users of component:                          *
  *                 -   Tivoli Enterprise Monitoring Agent       *
  ****************************************************************
  * PROBLEM DESCRIPTION: DB2 systems will not be monitored by XE *
  *                      if the OMPE Server is too busy during   *
  *                      the agent's attempts to establish       *
  *                      connections for those DB2 systems.  The *
  *                      agent and/or OMPE Server has to be      *
  *                      recycled or the COMMCOLL has to be      *
  *                      stopped and restarted.                  *
  *                                                              *
  *                      Also, better filtering of diagnostic    *
  *                      data in the RKLVLOG is desirable.       *
  ****************************************************************
  * RECOMMENDATION: Apply this PTF                               *
  ****************************************************************
  PROBLEM SUMMARY:
  If the OMPE Server is very busy during an agent's attempt to
  establish a connection for a DB2 subsystem, that
  connection will never be established until the agent and/or
  OMPE Server is recycled or the COMMCOLL is stopped and
  restarted.
  
  Also, better filtering of diagnostic data in the RKLVLOG is
  desirable.
  
  PROBLEM CONCLUSION:
  Internally, separate the COMMCOLL STIMER value such that it
  only governs data collection time, not agent connection time.
  
  Make very minor updates to agent modules to allow filtering
  of RKLVLOG data.
  

Problem conclusion

• Internally, separate the COMMCOLL STIMER value such that it
  only governs data collection time, not agent connection time.
  
  Make very minor updates to agent modules to allow filtering
  of RKLVLOG data.
  
  KEYWORDS : COMMCOLL STIMER RKLVLOG
  

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:

  UK38805

Modules/Macros

•    KD5AGENT KD5ATC00 KD5AUTO1 KO2AINIB
  

Fix information

• Fixed component name

  OM XE DB2PE/PM

• Fixed component ID

  5655OPE00

Applicable component levels

• R410 PSY UK38805

     UP08/08/12 P F808

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.