This describes the MIB module for objects used to manage the TN3270E server. The TN3270E Configuration Table contains information about the general state of the server.
The TN3270 Configuration Table has two subtables:
· Status
· Activity/Timing
|
|
Figure 90. TN3270E Configuration Table
The fields on the TN3270E configuration table are:
Index |
This is the index into the configuration table. |
Functions |
This object indicates the functions supported by the TN3270E server. |
Session Term State
|
The current state for determining what a TN3270E server should do when a TN3270 Session terminates: Terminate => Terminate TCP connection LuSessionPend => Do not drop the TCP Connection associated with a client when their TN3270 Session ends. Processing should redrive session initialization as if the client was first connecting. QueueSession => QUEUESESSION deals with CLSDST-Pass. An example is the easiest explanation. Assume APPL1 does a CLSDST-Pass to APPL2. Then the client logs off APPL Without QUEUESESSION the connection would now be broken. With QUEUESESSION the TN3270E server keeps the LU around after getting the APPL2 unbind waiting for a bind from APPL1. |
Server Type |
This object indicates the type of TN3270E server. The existence of MIB tables and objects that will be defined by follow-on MIBs may be predicated on whether the TN3270E server can be local to the same host as a Target Application (host:1) or will always be remote (gateway:2). |
Contact |
This object provides a scratch pad for a TN3270E server administrator for storing information for later retrieval. |
STATUS subtable |
|
Index |
This is the index into the configuration table. |
Admin Status |
The desired state of the TN3270E server: Up (1) - Activate a TN3270E server. Down (2)- Informs the associating TN3270E server to gracefully terminate its processing. Stop Immediate (3) - Informs the associating TN3270E server to terminate immediately. Implementation as to the exact semantics of either down (2) or Stop Immediate (3) processing is left as implementation dependent. A TN3270E server that does not distinguish between down or Stop Immediate transitions should not support Stop Immediate. |
Oper Status |
The current operational state of a TN3270E server: Up - The corresponding TN3270E server is active. Down - The corresponding TN3270E server is inactive. |
Row Status |
This object allows entries to be created and deleted in the TN3270ESrvrConfTable. The values may be: 1 : Active 2 : Not In Service 3 : Not Ready 4 : Create And Go 5 : Create And Wait 6 : Destroy An entry in this table is deleted by setting this object to Destroy(6). |
ACTIVITY/ |
|
Inactivity Timeout |
The inactivity time-out specified in seconds. When a connection has been inactive for the number of seconds specified by this object it is closed. The default of 0 means no inactivity time-out. |
Activity Check |
This object is intended to enable either TIMEMARK or NOP processing. |
Activity Timeout |
The TIMEMARK or NOP processing time-out specified in seconds. Note that a value of 0 is not allowed for this object since the function that uses this object relies on TN3270ESrvrConfActivityCheck for function enablement. |
Activity Interval |
The scan interval to be used by a TN3270E server. TIMEMARK or NOP processing scans the Telnet sessions on the interval provided by this object looking for sessions that have been idle for more than the value provided by TN3270ESrvrConfActivityTimeout. Note that a value of 0 is not allowed for this object since the function that uses it relies on TN3270ESrvrConfActivityCheck for function enablement. |
See also: