
APAR= II09605
ODBC TROUBLESHOOTING - CA400WIN95 CA400WIN CA400OS2OPT  V2.0

*** This is a continuation of II09604 ***

 ODBC Troubleshooting - CA400WIN95 CA400WIN CA400OS2OPT  V2.0
 ============================================================
                                          LAST UPDATE 7/18/96

 CONTENTS
 ========
 1.0 ........................ Unable to connect to the AS/400
 2.0 ............................. How to locate the ODBC job
 3.0 .......................................... Common Errors
     3.1 .................................. Connection Errors
     3.2 ........................ Application Specific Errors
     3.3 ............................ Stored Procedure Errors
     3.4 ........................................ Misc Errors
 4.0 ...................... Reporting problems to IBM Support
 5.0 ....................... Diagnostic and Performance Tools
 6.0 ............................................... Security
 7.0 ....................................... Other References

 4.0 Gathering Information for IBM Support
 =========================================

 When opening a problem record to IBM Support please have
 the following information available when you place the call.

 The AS/400 Cumulative PTF level
 -------------------------------
 Issue the display PTF command on an AS/400 terminal emulation
 command line:
     DSPPTF
 Record the first
 PTF ID in the list.  It will have the format Tzxxyyy
 where xx is the year, yyy the julian date and z is either
 L or C.

 The OS/400 version
 ------------------
 This can also be found from the DSPPTF screen.  Record the
 Release field at the top of the screen.

 The version of the Client Access ODBC driver.
 ---------------------------------------------
  - Client Access for Windows 3.1

    o EDIT CAWIN QPTFIDX

    o Record the version listed in the first line of the file.
      Now search for EHNODBC3.DLL.  Record the PTF number
      which is found in the left column (it will begin with SF).

    o Record the date and time stamp on the EHNODBC3.DLL file
      located in C: CAWIN where X: CAWIN is the location client
      access was install to.

  - Client Access for Windows 95

    o Record the service pack level of Client Access
      - Open the "My Computer" folder
      - Double Click on Control Panel
      - Double Click on Client Access
      - Record the version and service pack levels displayed
       on the General Tab (default).

    o Record the version of the Client Access odbc driver
      - From the Task bar: Select Start, Find, Files or
        Folders
      - Enter cwbodbc.dll for the name and click Find
      - Note the size and date of the file
      - Right click on the name and select properties
      - Select the Version tab and note the file version

 The version of the ODBC driver manager.
 ---------------------------------------
  -  Client Access for Windows 3.1
     o C: WINDOWS SYSTEM
     o Record the date and size of ODBC.DLL.  Search your
       hard drive for duplicate copies of the dll:
       CD C: DIR ODBS.

  -  Client Access for Windows 95
     o From the Task bar: Select Start, Find, Files or
       Folders
     o Enter odbc32.dll for the name and click Find
     o Note the size and date of the file
     o Right click on the name and select properties
     o Select the Version tab and note the file version

 -   Client Access for Windows 95 16 bit applications
     Repeate steps above for ODBC.DLL.

 The version and type of communication software used.
 ----------------------------------------------------
 This might include:
  - An OEM router, if applicable.  These include:
     o Novell Netware for SAA
     o NetSoft (purchased direct from Netsoft)
     o Microsoft SNA Server

  - Client Access/400 for Windows 3.1 connection router

  - Client Access/400 for Extended DOS connection router

  - Client Access/400 for Windows 95 connection router
    o Netsoft 802.2 (SNA), Async, Twinax, or SDLC
    o Native TCP/IP or IPX
    o Netsoft Microsoft SNA server
    o Microsoft SNA server
    o Novell SAA Gateway
    o Other: winappc32 compatible

 Communication Protocols and Drivers
 -----------------------------------

  - Client Access for Windows 3.1
    o Windows for Workgroups' MSDLC
    o IBM Lan Support Program
    o IBM TCP/IP Stack
    o OEM TCP/IP Stack (note which stack)

 - Client Access for Windows 95

   o Windows 95 32 bit MSDLC (note version)
   o TCP/IP (note which stack)
   o IPX (note which stack)
   o Async (note the modem)

 Communication Adapter
 ---------------------
 - Token-Ring (Manufacturer and Model)
 - Ethernet   (Manufacturer and Model)
 - Twinaxial (TDLC)  (Manufacturer and Model)
 - Synchronous Data Link Control (SDLC)
 - Asynchronous (ASYNC)  (Manufacturer and Model of modem)

 The PC application
 ------------------
 Name and version of the PC application.

 Error Description
 -----------------
 A description of what you were attempting when the failure
 occurred.  If possible, the steps needed to recreate the
 problem.
  - Error message
    The exact text and error numbers of any error message
    produced by the PC application.

    Even if there is no printer direct attached to the PC
    the image can be captured by pressing the print screen
    key to copy a bitmap of the current screen
    to the clip board.  Open the Microsoft Windows applet
    Paintbrush or Write under the ACCESSORIES group.  Select
    EDIT, PASTE and save this 'print screen' in a file for
    future reference.

 ODBC joblog
 -----------
 The QZDAINIT joblog if it was produced.  See above for
 details on how to generate and find your joblog.

 VLOGs
 -----
 For internal server errors, service personnel may request
 VLOGs generated at the time the error.  These VLOGs
 have a major code of 0700 and a minor code of either F230
 or F299.


*** Please see II09606 for the continuation of this APAR ***

