Sample TCPIP.DATA data set (TCPDATA)
The following shows sample TCPIP.DATA statements that can be used to configure information used by the resolver and TCP/IP application programs. The sample is shipped as member TCPDATA in the z/OS® Communications Server SEZAINST data set.
;***********************************************************************
; *
; Name of Data Set: TCPIP.DATA *
; *
; COPYRIGHT = NONE. *
; *
; This data, TCPIP.DATA, is used to specify configuration *
; information required by TCP/IP client and server programs. *
; *
; *
; Syntax Rules for the TCPIP.DATA configuration data set: *
; *
; (a) All characters to the right of and including a ; or # will *
; be treated as a comment. *
; *
; (b) Blanks and <end-of-line> are used to delimit tokens. *
; *
; (c) The format for each configuration statement is: *
; *
; <SystemName||':'> keyword value *
; *
; where <SystemName||':'> is an optional label that can be *
; specified before a keyword; if present, then the keyword- *
; value pair will only be recognized if the SystemName matches *
; the name of the MVS system. *
; SystemName is derived from the MVS image name. Its value should*
; be the IEASYSxx parmlib member's SYSNAME= parameter value. *
; The SystemName can be specified by either restartable VMCF *
; or the subsystem definition of VMCF in the IEFSSNxx member of *
; PARMLIB. *
; *
; (d) There should be no sequence numbers in this dataset. If there *
; are they can be treated as invalid statement parameters. *
; *
;***********************************************************************
;
; TRACE RESOLVER statement
; ========================
; TRACE RESOLVER will cause a complete trace of all queries to and
; responses from the name server or site tables.
; This command is for debugging purposes only.
; It should be the first statement in the TCPIP.DATA statements to get
; the maximum trace output.
;
; TRACE RESOLVER
;
;
; OPTIONS statement
; =================
; Use the OPTIONS statement to specify the following:
; DEBUG
; Causes resolver debug messages to be issued. This is equivalent to
; TRACE RESOLVER. If used it should be the first statement in the
; TCPIP.DATA statements to get the maximum trace output.
; NDOTS:n
; Indicates the number of periods (.) that need to be contained in a
; domain name for it to be considered a fully qualified domain name
;
; OPTIONS NDOTS:1 DEBUG
;
;
; TCPIPJOBNAME statement
; ======================
; TCPIPJOBNAME specifies the name of the started procedure that was
; used to start the TCPIP address space. TCPIP is the default for
; most cases. However, for applications which use Language Environment
; services, the lack of a TCPIPJOBNAME statement causes applications
; that issue __iptcpn() to receive a jobname of NULL, and some of these
; applications will use INET instead of TCPIP. Although this presents
; no problem when running in a single-stack environment, this can
; potentially cause errors in a multi-stack environment.
;
; If multiple TCPIP stacks are run on a single system, each stack will
; require its own copy of this file, each with a different value for
; TCPIPJOBNAME.
;
TCPIPJOBNAME TCPIP
;
;
; HOSTNAME statement
; ==================
; HOSTNAME specifies the TCP host name of this system as it is known
; in the IP network. If not specified, the default HOSTNAME will be
; the name specified by either restartable VMCF or the subsystem
; definition of VMCF in the IEFSSNxx member of PARMLIB.
; If the VMCF name is not available then the IEASYSxx parmlib member's
; SYSNAME= parameter value will be used.
;
; For example, if this TCPIP.DATA data set is shared between 2
; systems, OURMVSNAME and YOURMVSNAME, then the following 2 lines
; will define the HOSTNAME correctly on each system.
;
; OURMVSNAME: HOSTNAME OURTCPNAME
; YOURMVSNAME: HOSTNAME YOURTCPNAME
;
; No prefix is required if the TCPIP.DATA file is not being shared.
;
; HOSTNAME THISTCPNAME
;
;
; NOTE - Use either DOMAINORIGIN/DOMAIN or SEARCH to specify your domain
; origin value
;
; DOMAINORIGIN or DOMAIN statement
; ================================
; DOMAINORIGIN or DOMAIN specifies the domain origin that will be
; appended to host names passed to the resolver. If a host name
; ends with a dot, then the domain origin will not be appended to the
; host name.
;
; DOMAINORIGIN YOUR.DOMAIN.NAME
;
;
; SEARCH statement
; ================
; SEARCH specifies a list of 1 to 6 domain origin values that will be
; appended to host names passed to the resolver. If a host name
; ends with a dot, then none of the domain origin values will be
; appended to the host name.
; The first domain origin value specified by SEARCH will be used as the
; DOMAINORIGIN/DOMAIN value.
;
; SEARCH YOUR.DOMAIN.NAME my.domain.name domain.name
;
;
; DATASETPREFIX statement
; =======================
; DATASETPREFIX is used to set the high level qualifier for dynamic
; allocation of data sets in TCP/IP.
;
; The character string specified as a parameter on
; DATASETPREFIX takes precedence over the default prefix of "TCPIP".
;
; The DATASETPREFIX parameter can be up to 26 characters long
; and the parameter must NOT end with a period.
;
; For more information please see "Dynamic Data Set Allocation" in
; the IP Configuration Guide.
;
DATASETPREFIX TCPIP
;
;
; MESSAGECASE statement
; =====================
; MESSAGECASE MIXED indicates to some servers, such as FTPD, that
; messages should be displayed in mixed case. MESSAGECASE UPPER
; indicates that all messages should be displayed in uppercase. Mixed
; case strings that are inserted in messages will not be uppercased.
;
; If MESSAGECASE is not specified, mixed case messages will be used.
;
; MESSAGECASE MIXED
; MESSAGECASE UPPER
;
;
; NOCACHE statement
; =================
; NOCACHE specifies that resolver cache processing should not be used.
; If NOCACHE is not specified, then the current system-wide level of
; resolver caching is used.
;
; NOCACHE
;
; NOCACHEREORDER statement
; =================
; NOCACHEREORDER specifies that the resolver should not reorder
; the list of cached IP addresses when responding to a resolution
; request for the associated host name. If NOCACHEREORDER is not
; specified, then the current system-wide setting for cache entry
; reordering is used.
;
; NOCACHEREORDER
;
;
; NSINTERADDR or NAMESERVER statement
; ===================================
; NSINTERADDR or NAMESERVER specifies the IP address of a name server.
;
; If you do not use name servers, then do not code any NSINTERADDR or
; NAMESERVER statements. If you do have name servers, then code the
; IPv4 or IPv6 address of the remote name servers to be contacted.
;
; The NSINTERADDR or NAMESERVER statement can be repeated up to sixteen
; times to specify alternate name servers. The name server listed first
; will be the first one attempted.
;
; IPv4 name server address:
; NSINTERADDR 10.0.0.1
;
; Ipv6 name server address:
; NSINTERADDR fc00::1
;
; NSPORTADDR statement
; ====================
; NSPORTADDR specifies the foreign port of the name server.
; 53 is the default value.
;
; NSPORTADDR 53
;
;
; RESOLVEVIA statement
; ====================
;
; RESOLVEVIA specifies how the resolver is to communicate with the
; name server. TCP indicates use of TCP connections. UDP indicates
; use of UDP datagrams. The default is UDP.
;
RESOLVEVIA UDP
;
;
; RESOLVERTIMEOUT statement
; =========================
; RESOLVERTIMEOUT specifies the time that the resolver will wait for
; a response from the name server when using RESOLVEVIA UDP.
; The default is 5 seconds.
;
RESOLVERTIMEOUT 5
;
;
; RESOLVERUDPRETRIES statement
; ============================
;
; RESOLVERUDPRETRIES specifies the number of times the resolver
; should try to connect to the name server when using UDP datagrams.
; The default is 1.
;
RESOLVERUDPRETRIES 1
;
;
; LOOKUP statement
; ================
; LOOKUP indicates the order of name and address resolution. DNS means
; use the DNSs listed on the NSINTERADDR and NAMESERVER statements.
; LOCAL means use the local host tables as appropriate for the
; environment being used (UNIX System Services or Native MVS).
;
; LOOKUP DNS LOCAL
;
;
; LOADDBCSTABLES statement
; ========================
; LOADDBCSTABLES indicates to the FTP server and FTP client which DBCS
; translation tables should be loaded at initialization time. Remove
; from the list any tables that are not required. If LOADDBCSTABLES is
; not specified, no DBCS tables will be loaded.
;
; LOADDBCSTABLES JIS78KJ JIS83KJ SJISKANJI EUCKANJI HANGEUL KSC5601
; LOADDBCSTABLES TCHINESE BIG5 SCHINESE
;
;
; SOCKDEBUG statement
; ===================
; Use the SOCKDEBUG statement to turn on the tracing of TCP/IP C and
; REXX socket library calls.
; This command is for debugging purposes only.
;
; SOCKDEBUG
;
;
; SOCKNOTESTSTOR statement
; ========================
; SOCKTESTSTOR is used to check socket calls for storage access errors
; on the parameters to the call. SOCKNOTESTSTOR stops this checking
; and is better for response time. SOCKNOTESTSTOR is the default.
;
; SOCKTESTSTOR
; SOCKNOTESTSTOR
;
;
; SORTLIST statement
; ==================
; Use the SORTLIST statement to specify the ordered list (maximum of 4)
; of network numbers (subnets or networks) for the resolver to prefer
; if it receives multiple addresses as the result of a name query.
;
; SORTLIST 128.32.42.0/24 128.32.42.0/255.255.0.0 9.0.0.0
;
;
; TRACE SOCKET statement
; ======================
; TRACE SOCKET will cause a complete trace of all calls to TCP/IP
; through the C socket library.
; This statement is for debugging purposes only.
;
; TRACE SOCKET
;
;
; ALWAYSWTO statement
; ===================
; ALWAYSWTO causes messages for some servers, such as LPD,
; to be issued as WTOs. Specifying YES can cause excessive operator
; console messages to be issued.
;
ALWAYSWTO NO
; ALWAYSWTO YES
;
; Obsolete statements
; ===================
; The following statements no longer have any effect when included in
; this file:
; SOCKBULKMODE
; SOCKDEBUGBULKPERF0
;
; End of file.
;