Problem
You are signing on to a 3270 connection by means of an IBM 3174
control unit, and you receive the following message:
Received host T packet reason ?
M outbound packet failure
Explanation
The File Transfer Aid option (option 125) of the 3174
control unit must have digit 6 set to 1. Refer to pages 316 through 317 of
the IBM 3174 Subsystem Control Unit Customizing Guide (order
number GA23-0214) for information about setting this option.
|
| Absence of SAS Software Start-up Messages |
Problem
While signing on to a remote session, you receive the following
message:
ERROR: Did not get SAS software startup messages
Explanation
This message occurs if the command to invoke SAS software
on the remote host is not correct in the script file that is being used for
signing on. Look at your script file and make sure that the TYPE statement
that invokes SAS software on the remote host uses the correct SAS command
for your site. At some sites, the command to invoke SAS software is not the
default command name SAS.
Problem
While signing on to a remote session, you receive the following
message:
ERROR: Did not get Host prompt.
Host not active.
Explanation
If you are signing on to a 3270 connection, one of the
following actions may overcome the problem:
- If you are using OS/2, Windows 3.x,
or Windows 32s on the local host, switch to your remote host session and look
for any terminal error messages that may appear there. Respond to these messages
and switch back to the local SAS session.
- Make sure you are at the remote prompt before
attempting to sign on. For example, if the remote host is running TSO, you
must not be in an ISPF session. SAS/CONNECT expects the TSO READY prompt.
- Look at the script that you used for signing on,
to ensure that the character string in the WAITFOR statement that tests for
the remote system prompt, exactly matches a character string that normally
appears on the remote screen. The WAITFOR statement is case sensitive.
- If you do not find any errors after checking the
previous items in this list, modify the script file at the location where
the error message appears in the file. Add a SNAPSHOT statement before the
LOG statement that produces the error message. The SNAPSHOT statement sends
a copy of the remote screen to the Log window or the file on the local host.
You can examine the SAS log on the local host to see what is displayed by
the remote host at the time that the WAITFOR statement executes.
If you are signing on to a TELNET or a TCP/IP connection,
one of the following actions may overcome the problem:
- Look at the script that you used for signing on,
to ensure that the character string in the WAITFOR statement that tests for
the remote system prompt, exactly matches a character string that normally
appears on the remote system. The WAITFOR statement is case sensitive.
- Look at the value of the REMOTE= option on the
local host to be sure it specifies the correct IP address.
- If you do not find any errors after checking the
two preceding items, modify the script file by adding a TRACE ON statement
and an ECHO ON statement at the beginning of the script file. These statements
send a copy of the remote screen to the Log window or to a file on the local
host. You can examine the SAS log on the local host to see what is displayed
by the remote host at the time the WAITFOR statement executes.
|
| Requested-Link-Not-Found Message |
Problem
While signing on to a remote session from a local OS/390 host,
you receive the following message:
ERROR: XMS Communication Failure:
requested-link XVT not found.
Explanation
This error occurs if the COMAMID= value is not submitted
on the local OS/390 host when a SIGNON is initiated from OS/390. To resolve
this error, submit the COMAMID= option before attempting the SIGNON.
Copyright 1999 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
