Use the VARY TCPIP,,OBEYFILE command to update TCP/IP profile configuration statements to make temporary dynamic changes to the system operation and network configuration without stopping and restarting the TCP/IP address space.
Before activating new configuration statements with the VARY TCPIP,,OBEYFILE command, use the VARY TCPIP,,SYNTAXCHECK command to verify that the configuration statements specified by the DSN= or datasetname parameter are free of syntax errors. For information about the VARY TCPIP,,SYNTAXCHECK command, see VARY TCPIP,,SYNTAXCHECK.
See the z/OS Communications Server: IP Configuration Reference for information about how different parameter updates take effect with Obeyfile processing.
- The identifier of the TCP/IP address space. When the procname value is not specified, there can be only one TCP/IP address space started. If more than one TCP/IP address space is available and no procname value is specified, the request will fail with an error message.
- CMD=OBEYFILE or OBEYFILE
- Specify this parameter to make temporary dynamic changes to the system operation and network configuration without stopping and restarting the TCP/IP address space. These changes are in effect until the TCP/IP cataloged procedure is started again or until another VARY OBEYFILE overrides them. Put your changes in the data set specified by the datasetname value. You can maintain different data sets that contain a subset of the TCP/IP configuration statements and activate them while TCP/IP is running.
- DSN=datasetname or datasetname
- The datasetname value is required after specifying the OBEYFILE parameter. The datasetname value is the name of a data set that contains TCP/IP profile configuration statements. The datasetname value must be a cataloged and fully-qualified data set name that is specified without any quotation marks. The datasetname value can be either a sequential data set or a member in a PDS. The datasetname value cannot be a z/OS® UNIX file. The DSN= parameter cannot be a z/OS UNIX file or a TCPIP.DATA data set. For more information about updating TCPIP.DATA configuration statements, see the information about dynamically changing TCPIP.DATA statements in z/OS Communications Server: IP Configuration Reference.
The following examples are about updating system operation and network configuration information without stopping and restarting the TCP/IP address space.
- The first example is directed to a TCP/IP address space started
by the identifier TCPPROC, and assumes the sequential data set USER99.TCPIP.OBEYFIL1
contains TCP/IP profile configuration statements:
- The next example assumes there is only one TCP/IP address space
and that OBEYFIL2 is a member of the PDS USER99.TCPIP and contains
TCP/IP profile configuration statements:
Users can be authorized to invoke the command by permitting their user IDs for CONTROL access to the RACF® profile name MVS™.VARY.TCPIP.OBEYFILE.