Modifying a TCP/IP/NJE Network Server *MODIFY,NETSERV=

Function

Use the *MODIFY,NETSERV=ntsvname command to modify an existing Netserv definition.

Syntax


                                    (1)   
>>-+-*MODIFY-+--,NETSERV=--ntsvname----------------------------->
   '-*F------'                            

>--+----------------------+--+-------------------+-------------->
   '-,HOSTNAME=--hostname-'  '-,PORT=--+-0-----+-'   
                                       '-nnnnn-'     

>--+-------------------+--+--------------------+---------------->
   '-,SYSTEM=--sysname-'  '-,STACK=--stackname-'   

>--+-------------------+--+-------------------+----------------->
   '-,ITRACE=--+-NO--+-'  '-,JTRACE=--+-NO--+-'   
               '-YES-'                '-YES-'     

>--+-------------------+---------------------------------------><
   '-,VTRACE=--+-NO--+-'   
               '-YES-'

Notes:

More than one parameter can be specified at a time and in any order.

Parameters

NETSERV=ntsvname

Specifies a 1-8 character name that uniquely identifies this socket. The name must contain only A-Z, @, $, #, or 0-9 and cannot start with a digit.

HOSTNAME=hostname

Specifies the IP host name or IP address that the Netserv uses to listen over TCP/IP for incoming data. Multiple Netservs can listen over the default, but only one Netserv can listen over a specific host name and port combination if a host name is specified.

The host name can consist of up to 60 characters and must be a legal TCP/IP IP address or host name defined to the TCP/IP resolver. The host name can be in IPV4 or IPV6 format.

HOSTNAME=* can be specified to remove any existing HOSTNAME assignment.

PORT=0|nnnnn

Specifies a port number that the Netserv uses, in combination with the host name, to listen over TCP/IP for incoming data. The port must be a number from 0 to 65,535. A port of 0 indicates that when the Netserv starts, a standard service name of VMNET will be used instead of a numeric port. The service of VMNET corresponds to port 175. Although there is a corresponding port for the service NJENET-SSL, it is suggested that you use the TLS=YES parameter on the NJERMT statement or the *MODIFY,NJE command instead.

SYSTEM=sysname

Specifies the name of the system that the Netserv runs on.

SYSTEM=* can be specified to remove any existing SYSTEM assignment. If this is done, the Netserv will start on the current global the next time it is started. If a DSI is done while a Netserv is active, it will continue to run on the system where it is currently defined. If the Netserv is subsequently brought down and back up, it will run on the new global.

STACK=stackname

Specifies the name of the stack that TCP/IP uses to get its definitions when the Common INET (CINET) configuration is being used.

STACK=* can be specified to remove any existing STACK assignment.

When only an INET configuration is being used, any specification of a stack name is ignored.

ITRACE=NO|YES

Indicates whether internal tracing in the Netserv address space is to be active. Internal tracing shows TCP/IP data records that are sent and received between IAZNJTCP and TCP/IP.

JTRACE=NO|YES

Indicates whether JES tracing is to be active. JES tracing occurs during JES specific exit points in the Netserv during which data records, headers, and trailers are transmitted and received.

VTRACE=NO|YES

Indicates whether verbose tracing is to be active. Verbose tracing involves various diagnostic messages being written to the console and job log from the Netserv address space.

Rules

HOSTNAME= can be abbreviated to HOST=.
Active Netservs cannot be modified, except for ITRACE, JTRACE, and VTRACE.

The following information applies to all *MODIFY,NETSERV command variants. The state of a Netserv after a JES3 start depends on the type of start that was requested:

Cold start: The initialization statements are read and used as the source of the Netserv state. The starting state is checkpointed.
Warm start: The initialization statements are read and used as the source of the Netserv state. The starting state is checkpointed, replacing checkpointed information from previous starts.
Hot start: The checkpointed information is the source for all Netservs. Because checkpoint includes the state and modifications from previous JES3 starts, that state is preserved across the hot start.
Hot start with refresh: The initialization statements are read and used as the source for inactive Netservs. Checkpointed information is used for active Netservs. The checkpoint includes state and modifications from previous JES3 starts, and that state is preserved across the start.

These rules dictate the outcome of each specific JES3 start situation. For example, if an initialization statement is changed and the system is hot started, the change will not be applied because a hot start does not read the initialization statements and preserves the checkpointed state. To apply such a change, the NETSERV statements must be read, which requires a cold, warm or hot start with refresh. Choosing hot start with refresh also means that the changed Netserv must be inactive across the restart. Likewise, if an inactive Netserv is modified by command and it remains inactive, the change will be lost across a hot start with refresh because this restart preserves changes only for active Netservs.

Results

The Netserv is modified and the changes take effect immediately.

Example

*F,NETSERV=JES3S1,JTRACE=YES

*F,NETSERV=JES3S1,SYSTEM=SY1