TNSACONFIG statement

Use the optional TNSACONFIG statement to configure the SNMP TN3270E Telnet subagent.

The Telnet defaults are:

DISABLED
AGENT 161
COMMUNITY PUBLIC
NOTNSATRACE
CACHETIME 30

Restrictions:

The TNSACONFIG statement can be coded only in the TELNETGLOBALS statement block.
No parameters can change while the Telnet subagent is active. To make a change, the Telnet subagent must be disabled and then enabled again with the new parameter values.

Syntax


>>-+----------------------------------------------------+------><
   |             .------------------------------------. |   
   |             V                                    | |   
   '-TNSACONFIG----+--------------------------------+-+-'   
                   | .-DISABLED-.                   |       
                   +-+----------+-------------------+       
                   | '-ENABLED--'                   |       
                   | .-AGENT 161---------------.    |       
                   +-+-------------------------+----+       
                   | '-AGENT agent_port_number-'    |       
                   | .-CACHETIME 30--------.        |       
                   +-+---------------------+--------+       
                   | '-CACHETIME cachetime-'        |       
                   | .-NOTNSATRACE-.                |       
                   +-+-------------+----------------+       
                   | '-TNSATRACE---'                |       
                   | .-COMMUNITY public-----------. |       
                   '-+----------------------------+-'       
                     '-COMMUNITY community_string-'

Parameters

AGENT: A port number in the range 1 - 65 535 used in establishing communication with the SNMP agent. For the Telnet SNMP subagent to communicate with the z/OS® CS SNMP agent, the port number specified must match the port number specified on the -p parameter when the SNMP agent is started. See OSNMPD parameters for a description of how to specify the port when the SNMP agent is started.
CACHETIME: Amount of time in seconds to elapse before rebuilding the MIB object tables. The valid range is 0 - 99 999 999.
COMMUNITY: A character string 1- 32 characters in length used as the community name (or password) in establishing contact with the SNMP agent. Because the community name is case sensitive, it is not converted to uppercase by profile processing. It cannot contain any imbedded white space or control characters (such as blank, tab, end of line, or end of file) and cannot contain any imbedded semicolons (semicolons are treated as comment delimiters). For the Telnet SNMP subagent to communicate with the z/OS Communications Server SNMP agent, the community name specified on the COMMUNITY keyword must match one that is defined in the PW.SRC or SNMPD.CONF data set used by the SNMP agent or specified on the -c parameter when the SNMP agent is started.
For more information about how the community name is used to permit access to the SNMP agent, see Step 1: Configure the SNMP agent (OSNMPD), in z/OS Communications Server: IP Configuration Guide.
DISABLED|ENABLED: DISABLED specifies that you do not require any of the SNMP MIB data supported by the Telnet subagent. By default, the Telnet SNMP subagent is not started during Telnet initialization. If specified using the VARY TCPIP,,OBEYFILE command, this statement indicates that the currently active Telnet subagent task should be terminated. SNMP MIB objects supported by the z/OS CS SNMP agent and subagents other than the Telnet SNMP subagent are still available. For information about which MIB objects are supported by the SNMP agent and subagent, see z/OS Communications Server: IP User's Guide and Commands.
ENABLED indicates that the Telnet SNMP subagent should be started at the completion of profile processing, either of the initial profile or of the data set referenced on a VARY TCPIP,,OBEYFILE command.
NOTNSATRACE|TNSATRACE: TNSATRACE generates trace points throughout Telnet subagent processing in addition to tracing data passed between the Telnet subagent and the agent, Telnet, and TCP/IP stack. The trace data is written to the syslog daemon.