3 Replies Latest reply on Dec 7, 2001 4:44 PM by 25386

    AS/400 ODBC agent not self-registering

    25386
      I've created identical MS SQL Server and AS/400 HS Generic
      Connectivity agents. The SQL Server agent self-registers and
      the DB Link works great.

      The AS/400 agent on the other hand does not sef-register and
      returns the following following error when I try the DB Link:

      1     1     40     ORA-28500: connection from ORACLE to a
      non-Oracle system returned this message:
      [Generic Connectivity Using ODBC]DRV_InitTdp: [IBM][Client
      Access ODBC Driver (32-bit)][DB2/400 SQL]Communication link
      failure. COMM RC=0x5 (SQL State: 08S01; SQL Code: -5)
      ORA-02063: preceding 2 lines from AS400UAT

      Are there extra steps in setting up the AS/400 agent?

      Thanks,

      Willy Vancrey
        • 1. re:AS/400 ODBC agent not self-registering
          3004
          Willy,

          The steps for connecting to SQL Server and AS/400 are the same,
          so if you can access SQL Server then you have setup Generic
          Connectivity correctly.

          This error probably occurs because of the ODBC driver. Check the
          documentation and verify that the ODBC driver meets the
          requirements for Generic Connectivity.

          You can also check the ODBC driver trace files for more
          information about the error.

          Vira
          • 2. re:re:AS/400 ODBC agent not self-registering
            25386
            Vira,

            Our production Oracle Server uses IBM ODBC driver ver. 5.00.00
            (5/2/98) and the DB Link works fine.

            The IBM ODBC driver that is not working is ver. 5.00.06
            (8/8/98). Since it is only slightly newer, I think the problem
            is with the IBM Client Access configuration.

            Thanks for the tip to check the ODBC logs. Any idea what would
            might cause this failure:


            hsodbcS1042214 12e-49     ENTER SQLAllocEnv
                      HENV * 021FD7E8

            hsodbcS1042214 12e-49     EXIT SQLAllocEnv with return code 0
            (SQL_SUCCESS)
                      HENV * 0x021FD7E8 ( 0x02201478)

            hsodbcS1042214 12e-49     ENTER SQLAllocConnect
                      HENV 02201478
                      HDBC * 0012E074

            hsodbcS1042214 12e-49     EXIT SQLAllocConnect with return code
            0 (SQL_SUCCESS)
                      HENV 02201478
                      HDBC * 0x0012E074 ( 0x02201520)

            hsodbcS1042214 12e-49     ENTER SQLDriverConnectW
                      HDBC 02201520
                      HWND 00000000
                      WCHAR * 0x1F7B2690 [      -
            3] "******\ 0"
                      SWORD -3
                      WCHAR * 0x1F7B2690
                      SWORD 8
                      SWORD * 0x00000000
                      UWORD 0
            <SQL_DRIVER_NOPROMPT>

            hsodbcS1042214 12e-49     EXIT SQLDriverConnectW with return
            code -1 (SQL_ERROR)
                      HDBC 02201520
                      HWND 00000000
                      WCHAR * 0x1F7B2690 [      -
            3] "******\ 0"
                      SWORD -3
                      WCHAR * 0x1F7B2690
                      SWORD 8
                      SWORD * 0x00000000
                      UWORD 0
            <SQL_DRIVER_NOPROMPT>

                      DIAG [08S01] [IBM][Client Access ODBC Driver (32-
            bit)][DB2/400 SQL]Communication link failure. COMM RC=0x5 (-5)


            Thanks,

            Willy
            wvancrey@global-com.com
            • 3. re:re:re:AS/400 ODBC agent not self-registering
              25386
              Vira,

              We found the following intructions from IBM, which fixed the
              problem:

              NOTE: when setting up NEW hosts in client access for ODBC use
              the following command to give the nt system account access.
              Otherwise you get a communication link falue 0x5.

              in dos:

              cwbcfg /host xxxx /ipaddr xxx.xxx.xxx.xxx /s


              Thanks,

              Willy Vancrey