If you encounter a problem when attempting to run a graPHIGS API application or connect to a graPHIGS API gateway, follow this procedure:
Figure 5-1. Messages and Appropriate Actions
|lsgPcon AFM0602 No connection exists on path hostname:nucid||go to Step 2|
|device address hostname:nucid DEFINED||Verify that this is the run time connection profile entry desired. If so, go to Step 3 If not, go to Step 2|
|device address hostname:nucid OPEN||This device address is in use. You may wish to try another device address.|
|lsgPcon unknown hostname hostname||go to Step 4|
|lsgPcon AFM0604 gPgated hostname NOT STARTED OR NOT RESPONDING||go to Step 5|
|gPhost AFM0604 NUCLEUS gP xxx NOT STARTED OR NOT RESPONDING||go to Step 6|
If the host on which the graPHIGS API gateway daemon is running is not in the list returned by gPhost, use the gPhost command to add the host. (See The graPHIGS Programming Interface: Technical Reference for more information on the gPhost command.)
Then go to Step 7
Then go to Step 3
Under problem conditions, several types of system failures are possible. Following is a list of potential problems and the expected default system behavior:
This failure does not affect the graPHIGS API gateway daemon or any connections. If a 'system reset' is required, warning messages are recorded at the host where the graPHIGS API gateway daemon is running.
Depending on the kind of failure, there may be no greater impact than an IBM S/370 failure, as described above. Run the utility program panel20 at the host where the graPHIGS API gateway daemon is running. (See the IBM RISC System/6000 5080 Graphics System Installation, Operation, and Problem Determination for more information about the panel20 command.)
If the link status code is 0, no action is required. If the status for a connection is not as expected, the graPHIGS API gateway daemon may need to be restarted with the gPated command. (See The graPHIGS Programming Interface: Technical Reference for more information on the gPgated command.)
If the IBM 5088 or 6098 is restarted, not-ready-to-ready interrupts are received at the IBM S/370.
This is indicated by a link status of 2 (adapter error) in the utility program panel20 This is a terminating error and requires the graPHIGS API gateway daemon to be terminated and the adapter to be reconfigured. This may be done simply by shutting down, or by the following command sequence:
rmdev -l hia0 mkdev -l hia0
Error log information from the errpt command should be reported to your service representative. Once the graPHIGS API gateway daemon is restarted and the connections are re-established, not-ready-to-ready interrupts are received at the IBM S/370.
In the event of a graPHIGS API gateway daemon abend, there is a "warmstart" option that allows the gateway to be restarted with the same run time connection profile that existed at the time of failure. Once the connections are re-established, not-ready-to-ready interrupts are received at the IBM S/370.
Depending on the nature of the failure, one of two things may occur:
AFM0593 COMMUNICATION ERROR: MAJOR 7, MINOR errno
In either case, the IBM S/370 device address associated with the connection receives an asynchronous error (Attention-UC).
The following error may be logged in the gateway transaction file:
AFM0204 NUCLEUS CONNECTION FAILED DEVICE ADDRESS xxx, NUCLEUS ':0' MAJOR 7, MINOR errno ABNORMALLY terminated
The associated IBM S/370 device address receives an asynchronous error (Attention-UC) and the connection remains OPEN At this point, the application should react to the error and disconnect the nucleus.
The graPHIGS API gateway daemon is capable of using the AIX system trace facility. If detailed problem determination is required, your support representative may ask you to generate a trace file.
To generate a trace file, follow these steps:
trcrpt -o trace.file
See "The graPHIGS API Trace Facility" for more information on the graPHIGS API trace facility.