Use of Local Interface Gateways
Currently, Information Exchange utilizes IN Gateways
to process event notification dial-out requests. IBM(R)
is replacing the use of IN Gateways with Local Interface
Gateways (LIGs) as part of IBM's preparation for Year 2000.
Event Trail changes
As a result of the move from Gateways to LIGs, changes
will appear in the event trail for event notification dial-out
requests. Requests that result in any of the following conditions
will appear in the event trail as "CLIENT ERROR":
- The user's Event Notification Manager (ENM) picks up
but does not respond (Event trail currently reads NO PARTNER
RESPONSE)
- A connection was made with the user's ENM, however the
connection was lost prior to completion of the request
(Event trail currently reads LOST CONNECTION)
- The number dialed is not a modem (Event trail currently
reads WRONG NUMBER)
- The number dialed is busy (Event trail currently reads
NUMBER BUSY)
- The number dialed did not answer (Event trail currently
reads RING NO ANSWER)
There are limitations in the LIG node that prevent Information
Exchange from providing a more detailed event trail status
at this time.
In addition, two new event trail status codes may appear
in the event trail, as follows:
- NO SRVR CONNECT - A connection with the LIG could not
be established. A backup LIG was also tried.
- NO SRVR CONVRSE - A connection was established with
the LIG but Information Exchange could not send the request
via the connection.
Event trail status definitions in the Information Exchange
Administration Services Supplement (GN10-4073-00) that reference
a Gateway may also apply to the LIG. The definitions in
this publication will be updated with the next major release
of Information Exchange.
|