Logging off and on 3270 sessions

Use the run_script command to log 3270 sessions on or off. This command can be invoked by any suitable method, but probably the most reliable and sensible would be the crontab. The effective userid must be the Blueworx Voice Response AIX account (dtuser). Typically, run_script command is used before or after a network shutdown, to prevent Blueworx Voice Response from continually attempting to restart the sessions.

Note: Because the time taken to log on or log off all the sessions can vary, you should allow adequate time to ensure the sessions are in the correct state both before and after the host outage. For example, if the host is to be shut down at 02:00 am, you may need to run the logoff script at 01:30 am. You should select an appropriate time based on observations of your own systems.

While the script is logging off sessions, attempts to invoke the action OpenHostServerLink may fail. You can account for this in your voice application using logic in the state table which, for example, could speak the phrase “The database is not available between one thirty and six thirty a.m.”

Logging off

Use the run_script command to log off any session that is in the Ready state (for example, if you need to close sessions cleanly before a host shutdown). The sessions are disabled in such a way that the recovery logic within Blueworx Voice Response is bypassed, thereby preventing unnecessary interactions with the host session. To log off all sessions in the Ready state that belong to a specified server, the syntax is:

run_script LOGOFF 3270_server_name [logoff_script_name]

You must specify the application name (3270_server_name). This allows different applications to be logged off at different times.

The logoff script (logoff_script_name) is optional. Without it, the sessions are just disabled in order.

A logoff script allows you to specify actions to be performed before the sessions are disabled. It is recommended that the logoff script be reasonably short, otherwise some problems can occur when using this script. Therefore, do not put very complicated logic in the script: just use the most effective way to cause the session to log off from the host application as soon as possible.

After the script has finished, all sessions are disabled as if they had been disabled from the 3270 Session Manager.

Logging on

Use the run_script utility to log on any session that is in the Disabled state. To log on all such sessions that belong to a specified server:

run_script LOGON 3270_server_name

You must specify the application name (3270_server_name). This allows different applications to be logged on at different times. As is usual when starting a 3270 server, the initial script is run.