 necessary unless SAS is running under a multiple TCP/IP stack system (CINET). If SAS is running under a multiple TCP/IP stack system, the SAS TCP/IP library will need to set the TCP/IP stack affinity. Specify this SAS environment variable:
TCPIPMCH is a SAS environment variable that is used to specify the name for the TCP/IP stack, which is also known as a started task. TCPIPMCH is equivalent to the TCPIPJOBNAME and TCIPPUSERID configuration keywords that are used in the IBM TCPIP.DATA file.
If a value is not specified for TCPIPMCH, the SAS TCP/IP library will use the first TCP/IP stack name that is returned by a call to the UNIX System Service, pfsctl(), which might not be the appropriate TCP/IP stack. For information, see TCIPMCH Environment Variable.
|The Services File|
The SERVICES file defines port resources that are used when TCP/IP is used to connect client/server sessions. Examples of configured port services include the Telnet port, spawner ports, MP CONNECT pipes, and SAS/SHARE servers. For more information, see Configuring the SERVICES File.
A service for each SAS server session (SAS/CONNECT or SAS/SHARE) must be defined in the SERVICES file on each computer that a SAS client session runs on.
Note: Some TCP/IP stacks can restrict the range of ports that can be used. For details, see TCP/IP Stack Configuration Files.
The z/OS Name Resolver searches for the SERVICES file, using this order:
value of the ETC_SERVICES environment variable
tso-prefix.ETC.SERVICES under TSO or user-ID.ETC.SERVICES under batch execution
Albitz, Paul and Cricket Liu. 2001. DNS and BIND. 4th ed. Cambridge, MA: O'Reilly Media.
z/OS V1R9.0 Communication Server: IP Configuration Guide, IBM SC31-8775-11
z/OSV1R9.0 Communication Server: IP Configuration Reference, IBM SC31-8776-12
z/OS V1R9.0 UNIX System Services Planning, IBM GA22-7800-12
The IBM documentation is also available from http: publibz.boulder.ibm.com.