Chapter 7. Reporting graPHIGS API Program Failures

This chapter describes the steps involved in reporting a suspected graPHIGS API failure to IBM.

Central Service is available for the graPHIGS API until discontinued by IBM upon six months notice. However, IBM does not guarantee that all errors or program defects will be corrected.

Each licensee's access to program service is determined by the marketing channel through which the product was obtained.

In the United States and Puerto Rico

If obtained through one of the IBM Authorized Personal Computer Dealers or IBM Authorized Industry Remarketers, requests for program service should be made through your dealer/remarketer.

If obtained through the U.S. Marketing and Services (M) -- Market Operations, requests for program service should be made to IBM Central Service. Your IBM Representative can assist you in completing the request.

Outside the United States and Puerto Rico

Contact your local IBM Representative or your Authorized IBM Supplier for information on program services.

In all cases, the licensee may report problems directly to IBM by sending appropriate information to the address given below.

Obtain an Authorized Problem Analysis Report (APAR) form and complete it. See the Programming System General Information Manual for additional information that will help you in completing the form.

Once the APAR form is complete, send it and all supporting documentation to:

      IBM Corporation
      11400 Burnet Road
      Austin, TX 78758 U.S.A.
 
      Attention:  IBM graPHIGS API Programming Interface APAR Coordinator
                  Department 997

Filling Out the APAR Form

The APAR form enables you to provide IBM with a description of your problem and your system environment. It must be completed and sent, with accompanying documentation, to the address shown above. The information requirements are explained further in the Programming System General Information Manual

graPHIGS API Product Information

Field "N": Component or Program in Error/Suspected, identifies the graPHIGS API product that you are using. The three areas are entered as follows:

• Component ID Number The graPHIGS API Component ID Number is always 5601-257
• Component Level/SU This field identifies the level of the graPHIGS API that you are using. The format is XYZ, where:

  X

  is the Version Number (e.g., 2)

  Y

  is the Release Number (e.g., 2)

  Z

  is the Modification Level (e.g., 4)

  This can be obtained from the BUILDID value found in the second line of a trace file. For example, a BUILDID value of V2R2.4 would be entered in the Component Level/SU field as 224

• SCP-CSP Level Enter AIX into this field.

Problem Symptom Reporting

Use the following information to describe the symptoms of your problem. Use this information when completing fields "R," "S," "T," and "V" of the APAR form. Be sure to include ALL available supporting documentation for the problem you are describing. For fields "R" and "S," refer to the keyword chart, "Symptoms and Failure Keywords"

Record the following information:

R

The symptom code that corresponds to the Failure Keyword.

S

A Failure Keyword that best describes the failure.

T

A problem abstract that summarizes the failure.

V

A description of the details and circumstances surrounding the failure.

Note:

Refer to the Programming System General Information Manual for additional information.

Symptoms and Failure Keywords

Select the type-of-failure keyword and symptom code for fields "R" and "S" of the APAR form from the following list:

Figure 7-1. Symptoms and Failure Keywords

Descriptions of Type-of-Failure Keywords

The following descriptions will help you narrow down your choice of keywords. Select the word that describes your problem most accurately.

Some keywords also require qualifiers. If a qualifier is required, select it from the list that accompanies the keyword. The qualifier should be entered in "T", the abstract field, along with the summary of the problem.

Problem Abstract

Use field "T" of the APAR form to provide a summary of the failure. Where failures involve messages or ABORTs, use the format shown for field "S," Failure Keyword (e.g. ABORT806). Where a failure keyword has a qualifier list, include the qualifier in the abstract.

Problem Description

Use field "V" of the APAR form to provide the details of the failure. Include the following items:

• Sequence of actions and observations at the device, including expected results

• The graPHIGS API subroutine calls made prior to the failure

• Description of the processing of the application.

Supporting Information

Some of the information needed to describe a problem is generic, while some information depends on the problem you are experiencing.

General information required

• Application program - a copy of the application program so that the operations of the application can be reviewed .

• Maintenance list - a list of all service that has been applied.

Specific problems

In general, the following items might be required to solve a problem:

• A copy of the application program in which the failure occurs. This may be in the form of an executable module or the source code to an application.

• A core file. If one is sent in as supporting documentation, then the failing executable module must also be sent in.

• A synchronized graPHIGS API component trace.

• For incorrect output, a description of the calls, the data values used, and the expected output must be given.

• For a graPHIGS API message that does not result in termination, a full description of the calls used and the expected output must be given.