What's New in Communications Access Methods for SAS/CONNECT 9.1 and SAS/SHARE 9.1
Overview
SAS now supports:
- the TCP/IP communications access method for network connections
between these operating environments: OpenVMS Alpha, UNIX, Windows, and z/OS.
Also, the XMS communications access method can be used between address spaces
under z/OS.
- the network security protocol Secure Sockets Layer (SSL), which
encrypts connections between client and server.
- a new shell script for starting SAS is provided for the z/OS spawner.
- new instructions for
configuring TCP/IP that runs under the OS/390
and z/OS operating environments.
- the new Windows spawner option -NAME.
- new options for the OpenVMS spawner, UNIX spawner, Windows spawner,
and z/OS spawner are -OMRCONFIGFILE and -SASSPAWNERCN. The -INSTALLDEPENDENCIES
option is valid only in the Windows spawner.
Note:
- This section describes the features of the SAS communications
access methods that are new or enhanced since SAS 8.2.
- z/OS is the successor to the OS/390 operating system. Throughout
this document, any reference to z/OS also applies to OS/390, unless otherwise
stated.
Details
Access Methods and Operating Environments
- SAS now supports the TCP/IP and XMS communications
access methods.
- SAS now supports the OpenVMS Alpha, UNIX, Windows,
and z/OS operating environments.
- SAS no longer supports the APPC, DECnet, EHLLAPI, and NETBIOS
communications access methods or the CMS, OpenVMS VAX, OS/2, Windows 95, and
Windows 98 operating environments.
SSL Protocol
SAS/CONNECT and SAS/SHARE support the Secure Sockets
Layer (SSL) protocol, which provides network
security and protects the privacy of information by encrypting client/server
transfers under the UNIX and Windows operating environments.
OS/390 and z/OS Operating Environments
- A new Shell Script for
Starting SAS is provided for the z/OS spawner.
- New instructions are provided to configure TCP/IP that
runs under the OS/390 and z/OS operating environments.
Spawners
- The new -NAME option for the Windows spawner is
used
to assign a name to the spawner that is installed and started as a service.
A specified name overrides the default name that is automatically assigned
when the -INSTALL option is used.
- New options for the OpenVMS spawner,
UNIX spawner, Windows spawner, and
z/OS spawner are -OMRCONFIGFILE
and -SASSPAWNERCN. The new -INSTALLDEPENDENCIES option is valid only in the
Windows spawner.