Communications Access Methods for SAS/CONNECT and SAS/SHARE Software

OS/390: APPC Access Method

SAS/CONNECT

Until the configuration is properly specified, it can be difficult to establish communications within an SNA network, especially for a host subarea peripheral node. To simplify troubleshooting, SAS/CONNECT uses a convention for error handling that passes information to you to help you debug your configuration. This information includes operation codes, return codes, and sense data, which is framed within the context of the function the software is trying to perform. SAS/CONNECT does not attempt to interpret this information. Use this information to work with network systems and SAS support personnel at your site to resolve the problem.

ERROR: VTAM Communications Failure:
 ACB initialization error.  Verify pooling options 
(LUPOOL, LUPREFIX, LUFIRST, LULAST) or that the target ACD 
is not already in use. 
IEF170I SAS ABEND 0999.

This error occurs during a SIGNON to SAS on a remote OS/390 host if the SRBEXIT parameter of the OS/390 LU APPL definition is set to YES.

SRBEXIT=YES uses SRB-enablement. This is a privileged and optimized method by which VTAM can deliver asynchronous event notification to an application. To do this, the VTAM application must be running in supervisor state or authorized through APF (Authorized Program Facility). This mode is generally reserved for operating system services. SAS is not an application of this class and does not support SRBEXIT enablement. By setting SRBEXIT=NO or deleting the parameter so that it defaults to NO, VTAM is informed that SAS is a problem-state program with no special privilege authorization.

ERROR: VTAM Communications Failure:  
ACB initialization error when using the 
APPC access method and SAS/CONNECT software.

This error occurs if all of the available LUs are defined to APPC/MVS using LUADD ACBNAME. To avoid this problem, verify that all LUs are not defined to APPC/MVS.

ERROR: VTAM Communications Failure:  
ACB initialization error.  Verify LU options.
ERROR: The target ACB is not already in use.

This error occurs in SAS/CONNECT sessions between two OS/390 hosts if the LU_NAME parameter is defined in the local session instead of using LU pools.

Communication partner has terminated
the conversation.

When signing on to a remote APPC/MVS system, you can avoid this error by adding REMOTE=ACBname to the SAS configuration file on the OS/390 host, where ACBname is the LU defined to the APPC/MVS scheduler.

USER1701 ABEND

This error occurs under OS/390 when an ACB associated with a pool of LUs fails to open. Many events can cause this ABEND. Follow these guidelines to resolve the problem:

Verify that all required zaps and maintenance are applied.
Check pool definitions: LUFIRST, LULAST, and LUPREFIX, and refer to the installation and administration documentation for SAS software under OS/390, Release 6.08 and later.
Verify that the value for the REMOTE= option is the logical unit that is defined to the APPC/OS/390 scheduler through APPCPMxx in SYS1.PARMLIB.
Verify that the REMOTE= logical unit that is defined to APPC/MVS is defined to SAS through your OS/390 SAS configuration file.
Query VTAM to verify that the logical units are active.
```
You cannot connect to remote host <name> because ERROR:
APPC CNOS failure: RC = 00080000 SENSE = 087D0002
```
The remote host whose name was specified has not been defined as a VTAM LU6.2 application.
```
APPC transaction program failure: RC = 00480000 SENSE = 080F6051
```
The remote host is running secured, and the user's APPCSEC= option does not represent a valid userid and password combination for the remote host.

If you cannot resolve a problem from the explanations given here or by using the cited resources, call SAS Technical Support for assistance. You will probably be asked to generate traces that document the problem, so be sure that you or your site support personnel are familiar with the tracing services available through OS/2 Extended Services and VTAM.

SAS/SHARE

VTAM communication failure: ACB initialization error.

Verify that the pooling options (LUPOOL, LUPREFIX, LUFIRST, and LULAST) or the target ACB is not already in use.

The server whose name was specified was unable to initialize itself as a VTAM LU6.2 application, or a server with that name is already active.

VTAM communication failure: 
ACB initialization error. Verify pooling options 
(LUPOOL, LUPREFIX, LUFIRST, and LULAST) 
or that the target ACB is not already in use.

The LUPREFIX= option was specified incorrectly. Either the value given does not correctly represent the user pool as defined, or it is blank.

You cannot connect to server <name> because
ERROR: APPC CNOS failure:  RC = 00080000 SENSE = 087D0002

The server whose name was specified has not been defined as a VTAM LU6.2 application.

You cannot connect to server <name> because 
ERROR: VTAM communication failure:
ACB initialization error. verify pooling options 
(LUPOOL, LUPREFIX, LUFIRST, and LULAST) 
or that the target ACB is not already in use.

The LUPREFIX= option was specified incorrectly. Either the value given does not correctly represent the user pool as defined, or it is blank.

APPC transaction program failure:
RC = 00480000 SENSE = 080F6051

The server is running secured, and the user's APPCSEC= option does not represent a valid userid and password combination.

APPC CNOS failure: RC = 00900000
SENSE = 00000000

The LUPREFIX= option was specified incorrectly. The value given is for a valid LU0 application.

You cannot connect to server <name>
because ERROR: APPC CNOS failure:  RC = 00080000 SENSE = 08570003

The server whose name was specified has been defined as a VTAM LU6.2 application, but that server is not currently running.

Chapter Contents
Previous
Next
Top of Page