3270 server does not start

When an OpenHostServerLink action fails to start the specified 3270 server, check the following:

Does the calling state table correctly specify the 3270 server name?

Use the State Tables option on the Development menu to open the state table that calls the 3270 server and ensure that the name of the 3270 server specified in the OpenHostServerLink action is correct.

For information about OpenHostServerLink, see the Blueworx Voice Response for AIX: Application Development using State Tables information.

Has SNA been configured and started?

For the server to communicate with a remote 3270 host, SNA must be installed, SNA profiles must be created on the Power System, and SNA (with all the network connections) must be started.

Blueworx Voice Response for AIX: Installation describes how to determine whether SNA is ready. Use this information to make ensure that the correct profiles have been created, and to start SNA and the connection if necessary.

Are configured 3270 sessions available?

Servers can only communicate with the 3270 host via 3270 sessions that have been configured for them. Use the information provided in Blueworx Voice Response for AIX: Configuring the System to review the status of 3270 sessions.

If all of the sessions configured for the server are initializing or allocated, you need additional sessions. Use the information provided in Blueworx Voice Response for AIX: Configuring the System to configure additional sessions.

If a session that would otherwise be available is disabled, use the information provided in Blueworx Voice Response for AIX: Configuring the System to restart the disabled session (or sessions).

If no sessions have been configured for the server, use the information in Blueworx Voice Response for AIX: Configuring the System to configure sessions.

If all else fails, recycle Blueworx Voice Response (shut it down and restart it). Be sure to quiesce any active sessions first.