HOST013

Alarm level

Major.

Description

The application cannot access the host to get data for the call. One of these problems exists:

• The voice system was stopped before all sessions were logged out.
• The application running on the host (for example, CICS or TSO) is down.
• The connection to the host is down, or the host is down.
• There is a logic problem in the host application.

Repair procedures

If the voice system was stopped before all sessions logged out, take these actions:

1. Enter hfree application, session_number, range, or all to free all sessions assigned to the application or the card.

The system displays a message reporting the success or failure of the hfree command.

2. Enter sb_te session_numbers to use the terminal emulator on all of the recovering sessions and manually move the sessions to the Login Base screen with the screens and keys.

The current screen on the sessions is displayed.

3. Use the hassign command to reassign the application to all the sessions and verify that all sessions become logged in.

If the application is down, take these actions:

1. Enter hfree session_number to free a session of the card.

The system displays a message reporting the success or failure of the hfree command.

2. Enter sb_te session_numbers.

The Terminal Emulator (TE) displays the current screen of the LU. The 3270 status line appears at the bottom of the screen to inform you whether or not the host is active.

If the problem persists:

• Check that configuration settings in both systems are correct and make any required changes.
• Check with your LAN administrator to ensure that the connection between the host and the IR system is operating, and that the host is not down.

If the problem still persists, check the logic in the voice response application. See the Avaya IVR Designer Help for TAS Applications or the Avaya IVR Designer Help for VXML Applications for more information.

� 2002 Avaya Inc. All Rights Reserved.