Contacting IBM Software Support

IBM® Software Support provides assistance with product defects.

Before contacting IBM Software Support, your company must have an active IBM software maintenance contract, and you must be authorized to submit problems to IBM. The type of software maintenance contract that you need depends on the type of product you have:

If you are not sure what type of software maintenance contract you need, call 1-800-IBMSERV (1-800-426-7378) in the United States or, from other countries, go to the contacts page of the IBM Software Support Handbook at http://www14.software.ibm.com/webapp/set2/sas/f/handbook/contacts.html and under Worldwide contacts click the name of your geographic region for phone numbers of people who provide support for your location.

Follow the steps in this topic to contact IBM Software Support:

  1. Determine the business impact of your problem
  2. Describe your problem and gather background information
  3. Submit your problem to IBM Software Support

Determine the business impact of your problem

When you report a problem to IBM, you will be asked to supply a severity level. Therefore, you need to understand and assess the business impact of the problem you are reporting. Use the following criteria:

Severity Business impact
1 Critical: You are unable to use the program, resulting in a critical impact on operations. This condition requires an immediate solution.
2 Significant: The program is usable but is severely limited.
3 Some: The program is usable with less significant features (not critical to operations) unavailable.
4 Minimal: The problem causes little impact on operations, or a reasonable circumvention to the problem has been implemented.

Describe your problem and gather background information

When explaining a problem to IBM, be as specific as possible. Include all relevant background information so that IBM Software Support specialists can help you solve the problem efficiently. To save time, know the answers to these questions:

Gathering problem determination information

You might require assistance when determining the cause of HATS-related problems. To gather general information for HATS support personnel, on the HATS Toolkit menu bar, click HATS > Gather Problem Determination Information to launch the wizard.

When the wizard opens, all projects are listed within the window. You can select any combination of project types. Select the projects you want to include for diagnosis by selecting the check box beside them. Specify the location of the zip file you want to use to capture your information, then click Finish. The information contained in the zip file assists HATS support personnel in determining the cause of your problem.

For rich-client projects, click File > Preferences... > HATS > Troubleshooting from the menu bar. The Troubleshooting window opens and you can select tracing and logging settings. Click Gather to gather information required for diagnosing a problem. The contents of the selected applications, the runtime extension plug-in, and the .log file are copied into a zip file.

More specific information might be required for certain problem scenarios. To see what specific information to gather, go to the HATS support site at http://www.ibm.com/software/awdtools/hats/support/index.html. In the Additional search terms edit box enter mustgather and click Go. Read the technote titled MustGather: Read first for all Rational Host Access Transformation Services products. Then scan the other technotes for those that might be related to your problem scenario.

Displaying the Java Console

When using a Java™-enabled browser the Java Console or Java Log displays information about Java events. The Java console is useful when asynchronous update is configured. HATS messages and trace data can be shown here.

Displaying the Java Console in Internet Explorer

Display options for Internet Explorer vary according to how it is configured. The following are suggested ways to display the Java Console but they may not apply to your browser.

To display the Java Console while using the Internet Explorer browser, do the following:

  1. Select Tools > Internet Options from the main menu bar.
  2. Click the Advanced tab.
  3. Scroll down to the Microsoft® VM section and click in the checkbox next to Java console enabled to enable the Java Console. (This requires you to restart the browser.)
  4. Click Apply.
  5. Click OK.
  6. Stop Internet Explorer as well as any other open instances of the browser and restart it.
  7. Select View > Java Console from Internet Explorer's main menu to view the Java Console. The Java Console window appears.

If Internet Explorer browser does not provide the Microsoft VM selection on the Advanced tab, do the following:

  1. Select Tools > Sun Java Console option.
  2. The Java Console window appears.

Displaying the Java Console when running the Java 2 plug-in

To display the Java Console when running the Java 2 plug-in, click the Java Console option from the browser's Tools menu. Older versions of the plug-in might require the selection to be made in the plug-in's control panel.

Worksheet for preparing to call IBM Support

If you determine that you need IBM assistance to solve a problem with HATS, then complete this IBM support checklist for HATS. The following is a list of the information that the IBM Support Center might need to help diagnose your problem. You can print a copy of this list, and then fill in the blanks, before contacting IBM for support.

Description of the problem and the environment

  1. Problem Summary:

    _______________________________________________________________________

    _______________________________________________________________________

    _______________________________________________________________________

    _______________________________________________________________________

  2. HATS version, release, and refresh pack level: _______________________________________.

    To determine the HATS version, do the following:

  3. Rational Software Delivery Platform (Rational SDP) product, version, release, and refresh pack level: _________________________
  4. Type of connection being used: 3270____ 3270E____ 3270 print____ 5250____ 5250W ____ 5250 print____ VT____
  5. Steps to recreate:

    _________________________________________________

    _________________________________________________

    _________________________________________________

    _________________________________________________

    _________________________________________________

    _________________________________________________

  6. What type of security is being used? None_____ SSL _____
  7. If security is being used, describe the environment (for example, applicable servers, backend systems, Web servers)?

    Questions 8 through 19 apply to HATS Web or Portlet applications:

  8. Client operating system: __________________________________________

    On Windows®, open the Windows control panel and start the System application.

  9. Browser version used to run the HATS application:

    Internet Explorer: ________________

    Other: ________________

    To determine your browser version, select Help on the browser toolbar and then select About Internet Explorer or the appropriate selection for your particular browser.

  10. WebSphere® Application Server version: ____________________________
  11. WebSphere Application Server platform: ____________________________
  12. WebSphere Portal Server version (if applicable): ____________________________
  13. WebSphere Portal Server platform (if applicable): ____________________________
  14. Are there any messages posted in the Java Console? See Displaying the Java Console for instructions on how to display the Java Console in the Internet Explorer or other browsers.
  15. Are there any entries in your HATS log or trace files?
  16. Are there any messages in your WebSphere Application Server logs, Web server logs, or Rational SDP logs?
  17. Does the problem occur regularly ______ or only occasionally? _________
  18. If the problem occurs when the browser client is connected to a WebSphere Application Server, does it also occur when you use Run On Server in the HATS Toolkit? Yes _____ No _____
  19. Are your HATS connections configured to use Web Express Logon? No ___. Yes ___.

    If Yes:

    Network Security Plugin: ____________________________

    Credential Mapper Plugin: ____________________________

    Question 20 through 24 apply to HATS rich client applications:

  20. Client operating system and version: ____________________________
  21. Rich client platform and versions (for example, Eclipse Rich Client Platform V3.4, Lotus Notes® V8.5.1, or Lotus® Expeditor Client V6.2): ________________________________________________

    To determine the version, click Help>About from within the client environment.

  22. How was the application installed into the client environment (for example, installed using Eclipse Update Site, installed using a Lotus Notes widget, provisioned from Lotus Expeditor Server)? ________________________________________________
  23. Does the same problem occur when the application is run on a local test environment (that is, from within the development environment)? Yes_____ No _____
  24. Are there any entries in your HATS log or trace files? No ___. Yes ___.

Submit your problem to IBM Software Support

You can submit your problem in one of three ways:

If the problem you submit is for a software defect or for missing or inaccurate documentation, IBM Software Support will create an Authorized Program Analysis Report (APAR). The APAR describes the problem in detail. Whenever possible, IBM Software Support will provide a workaround for you to implement until the APAR is resolved and a fix is delivered.

IBM publishes resolved APARs on the IBM product support Web pages daily, so that other users who experience the same problem can benefit from the same resolutions. You can search for HATS related APARs on the HATS support site at http://www.ibm.com/software/awdtools/hats/support/index.html.