Naming conventions for dynamically allocated data sets

A data set that you allocate explicitly (with a DD statement in JCL) can have any valid MVS™ data set name or z/OS® UNIX file name. A data set that you create for the purpose of being allocated dynamically by TCP/IP must use the following naming conventions.

Note: In these examples, xxxx indicates an appropriate high-level qualifier, yyyy indicates an appropriate middle-level qualifier, and zzzz indicates an appropriate low-level qualifier.

userid.yyyy.zzzz
userid is the user ID of the logged on TSO user.
TSOprefix.yyyy.zzzz
TSOprefix is the data set prefix established by the TSO PROFILE command. userid is the default value of TSOprefix.
jobname.yyyy.zzzz
jobname is the job name specified on the JOB statement for a job stream or the procedure name for a started procedure.
hlq.yyyy.zzzz
hlq is the TCP/IP HLQ distributed as the system default, which can be overridden by the value in the DATASETPREFIX statement.
xxxx.nodename.zzzz
nodename is an MLQ that is used to define the data set name for the TCP/IP stack profile data set.
xxxx.function_name.zzzz
function_name denotes an acronym specifying a particular TCP/IP server (for example SRVRFTP for the FTP server) and is used as an MLQ for the translation table data set for that application.
xxxx.private_name.zzzz
private_name is a user-specified private qualifier that can be specified as an option on some TCP/IP commands.
SYS1.TCPPARMS(TCPDATA)
The member of a system data set used to find the configuration file TCPIP.DATA.