PK57152: ERROR MESSAGE KO2I0212U UNABLE TO LOCATE A CONNECTION TO DB2 - ISSUED WITH ALLOWUSERKEYCSA SET TO NO.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• With ALLOWUSERKEYCSA (NO) or ALLOWUSERKEYCSA ( YES ), the
  following error messages are seen in the AGENT:
  KO2I0212U UNABLE TO LOCATE A CONNECTION TO DB2=.... IN OM SERVER
  DBSOMEG  - COLLECT    CALL FAILED .
   In the SERVER:
  KO2O0452I TERMINATING COMMON SERVICES
  KO2X0453I UNSUBSCRIBING COMMON SERVICES
  KO2O1920I DB1S+ IFI COLLECTOR (CAF) CONNECTION TERMINATED
  KO2I0157I D5API COLLECTOR DISCONNECTED FROM DB2 DB1S AS
                                   REQUESTED BY AGENT DBSOMEA
  KO2O0450I INITIALIZING COMMON SERVICES
  KO2X0451I SUBSCRIBING COMMON SERVICES
  *
  PTF UK30718 is applied
  
  Additional symptoms:
  Found the following on the Agent Log:
  IEA848I NO DUMP WAS PRODUCED FOR THIS ABEND, DUE TO SYSTEM OR
  INSTALLATION REQUEST
  IEA848I NO DUMP WAS PRODUCED FOR THIS ABEND, DUE TO SYSTEM OR
  INSTALLATION REQUEST
  IEA848I NO DUMP WAS PRODUCED FOR THIS ABEND, DUE TO SYSTEM OR
  INSTALLATION REQUEST
  KLXI@USE WAITING FOR TCP/IP TO INITIALIZE
  IEA848I NO DUMP WAS PRODUCED FOR THIS ABEND, DUE TO SYSTEM OR
  INSTALLATION REQUEST
  LSCX013 Improper use of C subordinate load module.
  LSCX041 **** ERROR ****
          C run-time storage has been overlaid by the program
          Unable to determine location of failure
          Program terminated by operating system. ABEND code =
  U1213
          A non-C or system routine was running at the time of
  ABEND
  Actual ABEND location = C8ACDB04
  *(PSW-6) = 5020 C060 0A01
  *(PSW)   = 9200 C04D 4190
  Registers at time of ABEND:
       00000001 FFA3FE84 C8ACDAFE 00000000
       48ACEB10 48ACD75C 48B1F958 46A4CEC8
       48ACECF0 46A4CEF8 46A4CED4 48ACECF0
       805BD030 005C00B8 C8ACDA86 806FF050
  BPXP018I THREAD 3DAEB11000000001, IN PROCESS 68, ENDED  196
  WITHOUT BEING UNDUBBED WITH COMPLETION CODE 040C4000, AND REASON
  CODE
  00000010.
  BPXP018I THREAD 3DAEC02000000002, IN PROCESS 68, ENDED  200
  WITHOUT BEING UNDUBBED WITH COMPLETION CODE 040C4000, AND REASON
  CODE
  00000010.
  BPXP018I THREAD 3DAEA20000000000, IN PROCESS 68, ENDED  201
  WITHOUT BEING UNDUBBED WITH COMPLETION CODE 940C4000, AND REASON
  CODE
  00000010.
  
  According to the Agent log, there are several abends here, the 3
  S0C4's
  at the end of the log look to be different than the S0C4 from
  the dump
  (Reason Code 10 in the above log, the RC was 4 in the dump).
  Only one
  true S0C4 in the System Trace table:  offset X'3900' in D5AINI
  (eyecatcher V41051007/31/07 14:13..PK47760 DB2810 COMCOM).
  Checked in dump for address C8ACDB04 (where according to the
  Agent log a
  U1213 was issued), this storage wasn't in the dump.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
  *                 users of component:                          *
  *                 -   Tivoli Enterprise Monitoring Agent       *
  ****************************************************************
  * PROBLEM DESCRIPTION: 1. KO2I0212U UNABLE TO LOCATE A         *
  *                      CONNECTION TO DB2=    IN OM SERVER      *
  *                      nnnnnnnn - COLLECT CALL FAILED          *
  *                      2.No data for Global Lock Conflicts     *
  *                      under DB2Plex node in TEP               *
  ****************************************************************
  * RECOMMENDATION: Apply this PTF.                              *
  ****************************************************************
  PROBLEM SUMMARY:
  The DB2 ID was not set correctly for D5API call resulting in
  connecting to an invalid DB2
  
  PROBLEM CONCLUSION:
  Set the DB2 id correctly for D5API call
  

Problem conclusion

• Set the DB2 id correctly for D5API call
  
  KEYWORDS :
  KO2I0212U UNABLE LOCATE CONNECTION COLLECT FAILED GLOBAL LOCK
  CONFLICTS DB2PLEX
  

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:

  UK31791 UK31790

Modules/Macros

• KD5AGENT
  

Fix information

• Fixed component name

  OM XE DB2PE/PM

• Fixed component ID

  5655OPE00

Applicable component levels

• R310 PSY UK31790

     UP07/12/04 P F712

• R410 PSY UK31791

     UP07/12/04 P F712

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.