Chapter Contents
Previous
Next
SAS/CONNECT User's Guide

When a Host Message Interrupts SAS/CONNECT

As stated earlier, messages from the host will interrupt link processing. The interruption continues until the host message is resolved. Therefore, you must respond to host messages so that processing can resume.

There are several ways to handle host interruptions, but all of them involve

Reading the Host Message

If you have a TELNET or a TCP/IP connection, messages from the remote host are written to the SAS LOG window. To read them, go to the LOG window.

If you have an EHLLAPI connection, a message sent by the host is not automatically displayed in the LOG window of your local host. You may snap the message to your log by issuing the S command from the Communication Services Break Handler window (the window which appears when a message is detected), or you can "hot-key" to the 3270 session and read the message.

Responding to the Message

After the message from the remote host displays, you must respond to the message before link processing can resume.

For TELNET or TCP/IP connections, many of the messages from the remote host require no response. If you have a TELNET or a TCP/IP connection and the Communication Services Break Handler window displays, you can use the following commands to control the break window:
A aborts the link with the remote host.
C continues processing of command.
I invokes the application break window.
T types to the remote host.

If you have an EHLLAPI connection, switch to the 3270 session with which your local host is connected, and respond to the message in that session. For example, if you are running OS/2 on the local host, invoke the Task Manager, select the 3270 Terminal Emulation task, switch to the session to which you are linked, and respond to the message. In many cases, the only response necessary is to press the PA2 or ENTER key to clear the display.

Continuing SAS/CONNECT Processing

After you respond successfully to the host message, you can continue processing in one of the following ways:

Example

Suppose you write a program to execute on the remote host, but you misspell the name of a SAS data library that is referenced in a LIBNAME statement in the program. Without realizing your error, you issue the RSUBMIT command to execute your program. The remote host cannot find the library that is referenced in the program and issues an error message.

If you have an EHLLAPI connection, the host message brings up the Communication Services Break Handler window automatically. To respond, do the following:

  1. Use the S command in the break window to view the message from the remote host. The S command takes a snapshot and displays it in the LOG window. You can print the saved snapshot if you want to save it for later examination. Alternatively, you can read the message when you switch to the remote host session to respond to the message. In this example, the remote host tells you that the library you named in the LIBNAME statement does not exist and asks if you want to create it.

  2. Switch to the remote host session to respond to the message. For this example, type YES or NO and press ENTER. For many kinds of messages that you receive from the remote host, you can respond by simply pressing ENTER.

  3. Switch back to the local SAS session and select C from the break window. The remote host resumes processing.


Chapter Contents
Previous
Next
Top of Page

Copyright 1999 by SAS Institute Inc., Cary, NC, USA. All rights reserved.