TN3270 Server Commands

Note Unless otherwise specified, all commands in this chapter are supported on the Cisco 7000 with RSP7000, Cisco 7500 and the Cisco 7200 series routers.

For interface configuration information and examples, refer to the "Configuring the TN3270 Server" chapter of the Cisco IOS Bridging and IBM Networking Configuration Guide.

For a conversion table of the modular products and Cisco 7000 family processors, refer to the "Platform Support" appendix of the Cisco IOS Configuration Fundamentals Command Reference.

Syntax Description

lu-address	Starting number of the LOCADDR to which a cluster of LUs are to be allocated.
pool poolname	Pool name to which you want to allocate LUs. The pool name cannot exceed 8 characters.
clusters count	Range of LUs in a cluster that are allocated to the specified pool. For example, if the lu keyword specifies the beginning of the LOCADDR number, the cluster keyword specifies the number of clusters to be included in the pool.

Defaults

No default behavior or values.

Command Modes

Listen-point PU configuration

Command History

Release	Modification
11.2(18)BC	This command was introduced.
12.0(5)T	This command was migrated to the T-train

Usage Guidelines

The following guidelines apply to the allocate lu command:

• The LUs assigned to a pool constitute a cluster. When multiple pools are configured, the LU ranges for different pools on the same PU must not overlap.

• A maximum of 255 LOCADDRs can be allocated to a pool. Configurations with invalid LOCADDRs are deleted. Overlapping LU ranges between different pools are invalid.

• The LOCADDR ranges must not overlap for multiple allocation statements and with existing ranges specified for client nailing statements.

• When LUs are allocated while LUs are in use, existing clients are allowed to complete their sessions unaffected.

Examples

In the following example, the starting LOCADDR is 10. Each cluster has 10 LOCADDRs, therefore 50 LOCADDRs are allocated to the pool name LOT1.

interface channel 0/2
 tn3270-server
  pool LOT1 cluster layout 4s1p
  listen-point 10.20.30.40
   pu PU1
    allocate lu 10 pool LOT1 clusters 5
 

As a result of this configuration, the following LOCADDRs are created in each cluster:

• Cluster 1

  • LOCADDR 10---Screen

  • LOCADDR 11---Screen

  • LOCADDR 12---Screen

  • LOCADDR 13---Screen

  • LOCADDR 14---Printer

• Cluster 2

  • LOCADDR 15---Screen

  • LOCADDR 16---Screen

  • LOCADDR 17---Screen

  • LOCADDR 18---Screen

  • LOCADDR 19---Printer

All of the LUs in these clusters are allocated to pool LOT1.

Related Commands

Command	Description
pool	Defines pool names for the TN3270 server and specifies the number of screens and printers in each logical cluster.
tn3270-server	Starts the TN3270 server on a CMCC adapter or enters TN3270 configuration mode.
pu (TN3270)	Creates a PU entity that has its own direct link to a host, or enters PU configuration mode.
pu dlur (listen-point)	Creates a PU entity that has no direct link to a host, or enters listen-point PU configuration mode.

Syntax Description

ip-address	IP subnet being added to the response-time group.
ip-mask	(Optional) Mask applied to a client IP address to determine the client's membership in a client subnet group. When the mask is applied to a connecting client's IP address and the resulting address is equal to the defined IP address, the client becomes a member of the client group. The default mask is 255.255.255.255.

Defaults

No default behavior or values.

Command Modes

Response-time configuration

Command History

Release	Modification
11.2(18)BC	This command was introduced.
12.0(5)T	This command was migrated to Cisco IOS Release 12.0 T.

Examples

Following is an example of the client ip command:

tn3270-server
response-time group acctg
 client ip 10.1.2.3 255.0.0.0

Related Commands

Command	Description
response-time group	Configures a client subnet group for response-time measurements.
show extended channel tn3270-server response-time application	Displays information about Application response-time client groups.
show extended channel tn3270-server response-time global	Displays information about the Global response-time client group.
show extended channel tn3270-server response-time link	Displays information about Host Link response-time client groups.
show extended channel tn3270-server response-time listen-point	Displays information about Listen-point response-time client groups.
show extended channel tn3270-server response-time subnet	Displays information about Subnet response-time client groups.
tn3270-server	Starts the TN3270 server on a CMCC adapter or enters TN3270 configuration mode.

Syntax Description

printer	(Optional) Specifies that a client connection from the nailed IP addresses will be nailed to one of the specified LUs only if the client-session negotiates a model type of 328n, where n is any alphanumeric character. Moreover, it ensures that a printer matching the IP address condition can only use an LU nailed as a printer LU. If the printer keyword is not specified for any client statement that has this IP address set, all model types can use this range of LUs.
ip-address	Specifies remote client IP address.
ip-mask	(Optional) The mask applied to the remote device address. Multiple client IP addresses in the same subnet can be nailed to the same range of locaddrs.
first-locaddr	Defines a single locaddr to nail.
last-locaddr	(Optional) Defines the end range of inclusive locaddrs to be nailed from first-locaddr to last-locaddr.

Defaults

No LUs are nailed. They are all available to any client.

Command Modes

TN3270 PU configuration mode

Command History

Release	Modification
11.3	This command was introduced.

Usage Guidelines

This command is valid only on the virtual channel interface. Multiple statements can be configured for one IP address or nail type either on one PU or multiple PUs. But each LU can only appear in one client statement.

A client with a nailed IP address can request one of the nailed LUs via the TN3270 device name. If the requested LU is not available then the connection is rejected.

A client with a nailed IP address cannot request an LU outside the range of nailed LUs for its type (screen or printer).

A client with a nonnailed IP address cannot request an LU that is configured as nailed.

The command will be rejected if some of the locaddrs are already nailed. If the locaddrs are currently in use by other remote clients, the nailing statement will take effect only when the locaddr is made available.

To cancel the definition, the no client form of the command must be entered exactly as the client command was originally configured. If a range of locaddrs was specified, to cancel this definition the whole range of locaddrs must be specified. There is no way to cancel only one locaddr if a whole range of locaddrs was configured.

Examples

In the following example, locaddrs 1 to 50 are reserved for remote devices in the 171.69.176.0 subnet:

interface channel 2/2
 tn3270-server
 pu BAGE4
  client ip 171.69.176.28 255.255.255.0 lu 1 50
 

In the following example, locaddrs 1 to 40 are reserved for screen devices in the 171.69.176.0 subnet, while 41 to 50 are reserved for printers in that subnet:

interface channel 2/2
 tn3270-server
 pu BAGE4
  client ip 171.69.176.28 255.255.255.0 lu 1 40
  client printer ip 171.69.176.28 255.255.255.0 lu 41 50
 

In the following example, there is an attempt to cancel a definition but this is rejected because it does not specify the full range of locaddrs and the second attempt fails to specify the correct nail type:

interface channel 2/2
 tn3270-server
  pu BAGE4
  client printer ip 171.69.176.50 255.255.255.0 lu 1 100
  no client printer ip 171.69.176.50 255.255.255.0 lu 1
  %Invalid LU range specified
  no client ip 171.69.176.50 255.255.255.0 lu 1 100
  %client ip 171.69.176.50 nail type not matched with configured nail type printer 

Related Commands

Command	Description
pu (DLUR)	Creates a PU entity that has no direct link to a host, or enters DLUR PU configuration mode.

Syntax Description

ip-address	Remote client IP address.
ip-mask	(Optional) Mask applied to the remote device address. The mask is part of the matching function that determines whether a client is governed by the nailing statement. The default is 255.255.255.255. Multiple client IP addresses in the same subnet can be nailed to the same range of LOCADDRS.
poolname	Specifies a unique pool name. The pool name cannot exceed 8 characters.

Defaults

No default behavior or values.

Command Modes

Listen-point configuration

Command History

Release	Modification
11.2(18)BC	This command was introduced.
12.0(5)T	This command was migrated to Cisco IOS Release 12.0 T.

Usage Guidelines

If the pool is configured while LUs are in use, existing clients are allowed to complete their sessions. A pool name can be identical to an LU name. When assigning an LU, the TN3270 server searches the LU name space first for specific requests, such as connections that specify a device name on CONNECT or LU name in the terminal type negotiation. The request is assumed to be directed to the specific LU rather than to the pool. Make sure the name spaces do not clash.

Examples

The following is an example of the client ip pool command that nails the client at IP address 10.1.2.3 with an IP mask of 255.255.255.0 to the pool named OMAHA:

tn3270-server
 pool OMAHA cluster layout 10s1p
 listen-point 172.18.4.18
  client ip 10.1.2.3 255.255.255.0 pool OMAHA

Related Commands

Command	Description
listen-point	Defines an IP address for the TN3270 server.
pool	Defines pool names for the TN3270 server and specifies the number of screens and printers in each logical cluster.
pu dlur (listen-point)	Creates a PU entity that has no direct link to a host, or enters listen-point PU configuration mode.
pu (listen-point)	Creates a PU entity that has a direct link to a host, or enters listen-point PU configuration mode.
tn3270-server	Starts the TN3270 server on a CMCC adapter or enters TN3270 configuration mode.

Syntax Description

ip	(Optional) IP address of the client. The value for the ip argument is optional when setting the maximum number of LU sessions. If no IP address is specified then the limit is applied to all clients.
ip-mask	(Optional) IP network mask for the client. The default is 255.255.255.255
number	(Optional) Maximum number of LU sessions. The allowed value is from 0 to 65535.

Defaults

The default is that there is no limit on the number of concurrent sessions from one client IP address.

The default value for the ip-mask argument is 255.255.255.255.

In the no form of this command, the default value for the number argument is 65535.

Command Modes

TN3270 server configuration

Command History

Release	Modification
12.0	This command was introduced.

Usage Guidelines

This command is valid only on the virtual channel interface. An instance of the client (lu limit) command on a given tn3270-server is uniquely identified by the ip-mask and the logical AND of the ip-address with that mask. For example, if the command is entered as the following:

client 10.1.1.62 255.255.255.192 lu maximum 2
 

Then it will be stored (and subsequently displayed by write term) as:

client 10.1.1.0 255.255.255.192 lu maximum 2
 

The maximum specified on the command can be changed simply by reissuing the command with the new value. It is not necessary to remove the command first.

When you use the no client command, only the corresponding client lu maximum statement is removed, as identified by the IP address and IP address mask combination. You cannot use no client to specify an unlimited number of LU sessions. The lu number keyword is optional in the no form of the command.

For example, if a service bureau has 8000 clients and each client IP address is limited to four LU sessions, you will never need more than 32000 concurrent LU definitions even when the service is running at 100 percent capacity.

Examples

The following example limits all clients to a maximum of two LU sessions:

client lu maximum 2
 

The following example limits a client at IP address 10.1.1.28 to a maximum of three LU sessions:

client 10.1.1.28 lu maximum 3
 

The LU limit can be applied to different subnets as shown in the following example. The most exact match to the client IP address is chosen. Clients with IP addresses that reside in the subnet 10.1.1.64 (those with IP addresses in the range of 10.1.1.64 through 10.1.1.127) are limited to a maximum of 5 LU sessions while other clients with IP addresses in the subnet 10.1.1.0 are limited to a maximum of 4 LU sessions.

client 10.1.1.0  255.255.255.0 lu maximum 4
client 10.1.1.64 255.255.255.192 lu maximum 5
 

The following example prevents an LU session for the client at IP address 10.1.1.28:

client 10.1.1.28 lu maximum 0

Related Commands

Command	Description
maximum-lus	Limits the number of LU control blocks that will be allocated for TN3270 server use.

Syntax Description

fq-cpname	(Optional) Fully qualified control point (CP) name used by the SNA session switch and the logical unit (LU) name for the DLUR function. This name must be unique among APPN nodes in the network including other values for the fq-cpname argument specified on all other TN3270 servers running under the Cisco IOS software.
fq-dlusname	(Optional) Fully qualified name of the primary choice for the dependent LU server (DLUS). This is the name of an LU, usually a CP, in an APPN host. The value for the fq-dlusname argument can be repeated and shared across servers.

Defaults

No DLUR function is enabled.

Command Modes

TN3270 server configuration

Command History

Release	Modification
11.2	This command was introduced.

Usage Guidelines

This command is valid only on the virtual channel interface. If the SNA session switch function is already enabled, the dlur command with no arguments puts you in DLUR configuration mode. The session switch function implements an End Node DLUR.

Several parameters in the DLUR configuration mode consist of fully qualified names, as defined by the APPN architecture. Fully qualified names consist of two case-insensitive alphanumeric strings, separated by a period. However, for compatibility with existing APPN products, including VTAM, the characters "#" (pound), "@" (at), and "$" (dollar) are allowed in the fully qualified name strings. Each string is from one to eight characters long; for example, RA12.NODM1PP. The portion of the name before the period is the NETID and is shared between entities in the same logical network.

The no dlur command hierarchically deletes all resources defined beneath it.

Examples

The following example performs two functions: it enters DLUR configuration mode; and it enables the DLUR function and defines the LU name for the DLUR as SYD.TN3020 and the primary choice for DLUS as SYD.VMG. Note that the NETID portion of both names is the same:

dlur SYD.TN3020 SYD.VMG

Related Commands

Command	Description
lsap	Creates a SAP in the SNA session switch, or enters DLUR SAP configuration mode.
preferred-nnserver	Specifies a preferred NN as server.
pu (DLUR)	Creates a PU entity that has no direct link to a host, or enters DLUR PU configuration mode.

Syntax Description

dlusname2

Fully qualified name of the backup DLUS for the DLUR.

Defaults

No backup DLUS is specified.

Command Modes

DLUR configuration

Command History

Release	Modification
11.2	This command was introduced.

Usage Guidelines

This command is valid only on the virtual channel interface. Only one backup DLUS can be specified per CMCC adapter. If the backup DLUS specified in the dlus-backup command is in use when a no dlus-backup command is issued, the connection is not torn down.

Several parameters in the DLUR configuration mode consist of fully qualified names, as defined by the APPN architecture. Fully qualified names consist of two case-insensitive alphanumeric strings, separated by a period. However, for compatibility with existing APPN products, including VTAM, the characters "#" (pound), "@" (at), and "$" (dollar) are allowed in the fully qualified name strings. Each string is from one to eight characters long; for example, RA12.NODM1PP. The portion of the name before the period is the NETID and is shared between entities in the same logical network.

Examples

The following example specifies SYD.VMX as the backup DLUS:

dlus-backup SYD.VMX

Related Commands

Command	Description
dlur	Enables the SNA session switch function on the CMCC adapter, or enters DLUR configuration mode.

Syntax Description

permit	Leftover LUs should be made available to TN3270 users wanting generic sessions. This value is the default.
deny	Leftover LUs should not be given to a generic pool. The physical unit (PU) is not automatically fully populated with 255 LOCADDR definitions. The default is the value configured in TN3270 server configuration mode.

Defaults

In TN3270 server configuration mode, generic pool use is permitted.

In PU configuration mode, the default is the value currently configured in TN3270 server configuration mode.

Command Modes

TN3270 server configuration---The generic-pool command at this level applies to all PUs supported by the TN3270 server.

Listen-point configuration---The generic-pool command at this level applies to all PUs defined at the listen point.

Listen-point PU configuration---The generic-pool command at this level applies only to the specified PU.

DLUR PU configuration---The generic-pool command at this level applies to all PUs defined under DLUR configuration mode.

PU configuration---The generic-pool command at this level applies only to the specified PU.

Command History

Release	Modification
11.2	This command was introduced.

Usage Guidelines

This command is valid only on the virtual channel interface.

A leftover LU is defined as one for which all of the following conditions are true:

• The system services control point (SSCP) did not send an ACTLU during PU start-up; and

• The PU controlling the LU is capable of carrying product set ID (PSID) vectors on network management vector transport (NMVT) messages, thus allowing dynamic definition of dependent LU (DDDLU) operation for that LU.

All LUs in the generic pool are, by definition, DDDLU capable.

Values entered for generic-pool in TN3270 server configuration mode apply to all PUs for that TN3270 server but can be changed in PU configuration mode.

In PU configuration mode, a no generic-pool command will restore the generic-pool value entered in TN3270 command mode.

In TN3270 server configuration mode, the no generic-pool command reverts to the default, which permits generic pool use.

The command takes effect immediately. If generic-pool deny is specified on a PU, no further dynamic connections to it will be allowed. Existing sessions are unaffected, but as they terminate the LUs will not become available for dynamic connections.

Similarly, if generic-pool permit is specified, any inactive LUs are immediately available for dynamic connections. Moreover, any active LUs that were dynamic previously (before generic-pool deny was issued) return to being dynamic.

Examples

The following example permits generic LU pool use:

generic-pool permit

Related Commands

Command	Description
client ip lu	Defines a range of locaddrs to be reserved for remote devices.

Syntax Description

seconds

Idle time in seconds, from 0 to 65535. A value of 0 means the session is never disconnected.

Defaults

The default in TN3270 server configuration mode is that the session is never disconnected (0).

The default in PU configuration mode is the value currently configured in TN3270 server configuration mode.

Command Modes

TN3270 server configuration---The idle-time command at this level applies to all PUs supported by the TN3270 server.

Listen-point configuration---The idle-time command at this level applies to all PUs defined at the listen point.

Listen-point PU configuration---The idle-time command at this level applies only to the specified PU.

DLUR PU configuration---The idle-time command at this level applies to all PUs defined under DLUR configuration mode.

PU configuration---The idle-time command at this level applies only to the specified PU.

Command History

Release	Modification
11.2	This command was introduced.

Usage Guidelines

The idle-time command is valid only on the virtual channel interface, and can be entered in either TN3270 server configuration mode or PU configuration mode. A value entered in TN3270 mode applies to all PUs for that TN3270 server, except as overridden by values entered in PU configuration mode.

A no idle-time command entered in PU configuration mode will restore the idle-time value entered in TN3270 command mode.

The idle-time command affects currently active and future TN3270 sessions. For example, if the idle-time value is reduced from 900 seconds to 600 seconds, sessions that have been idle for between 600 and 900 seconds are immediately disconnected.

Note For the purposes of idle-time logic, TIMING-MARKs generated by the keepalive logic do not constitute "activity."

Examples

The following command sets an idle-time disconnect value of 10 minutes:

idle-time 600
 

The following command entered in TN3270 server configuration mode sets the default idle-time disconnect value to 0, or never disconnect:

no idle-time

Related Commands

Command	Description
keepalive (TN3270)	Specifies how many seconds of inactivity elapse before transmission of a DO TIMING-MARK or Telnet no operation (nop) to the TN3270 client.
timing-mark	Selects whether a WILL TIMING-MARK is sent when the host application needs an SNA response (definite or pacing response).

Syntax Description

screen	Specifies the precedence is for screen devices.
printer	Specifies the precedence is for printer devices.
value	Sets the precedence priority. A value between 0 and 7, with 7 being the highest priority. The default is 0.

Defaults

The default is a precedence value of 0 for both screens and printers.

Command Modes

TN3270 server configuration---The ip precedence (TN3270) command at this level applies to all PUs supported by the TN3270 server.

Listen-point configuration---The ip precedence (TN3270) command at this level applies to all PUs defined at the listen point.

DLUR PU configuration---The ip precedence (TN3270) command at this level applies to all PUs defined under DLUR configuration mode.

PU configuration---The ip precedence (TN3270) command at this level applies only to the specified PU.

Command History

Release	Modification
11.3	This command was introduced.

Usage Guidelines

This command is valid only on the virtual channel interface. Precedence values applied in TN3270 PU configuration mode override values applied in TN3270 server configuration mode.

You can enter new or different values for IP precedence without first using the no form of this command.

During initial Telnet negotiations to establish, or bind, the session an IP precedence value of 0 and IP TOS value of 0 is used. These values are used until the bind takes place. When the session is a type 2 bind, the TN3270 client is assumed to be a screen; otherwise the client is assumed to be a printer.

Examples

The following example assigns a precedence value of 3 to printers:

ip precedence printer 3

Related Commands

Command	Description
ip tos	Specifies the TOS level for IP traffic in the TN3270 server.

Syntax Description

screen	Specifies the TOS is for screen devices.
printer	Specifies the TOS is for printer devices.
value	Sets the TOS priority. A value between 0 and 15. The default is 0.

Defaults

The default is a TOS value of 0 for both screens and printers.

Command Modes

TN3270 server configuration---The ip tos command at this level applies to all PUs supported by the TN3270 server.

Listen-point configuration---The ip tos command at this level applies to all PUs defined at the listen point.

DLUR PU configuration---The ip tos command at this level applies to all PUs defined under DLUR configuration mode.

PU configuration---The ip tos command at this level applies only to the specified PU.

Command History

Release	Modification
11.3	This command was introduced.

Usage Guidelines

This command is valid only on the virtual channel interface. TOS values applied in TN3270 PU configuration mode override values applied in TN3270 server configuration mode.

The default TOS values for screen and printer are 0. However, RFC 1349 recommends different default values. Specifically, the RFC recommends a default minimize screen delay value of 8 and a default maximize printer throughput value of 4. You must configure these values using the ip tos command if you want to comply to the defaults as stated in the RFC.

During initial Telnet negotiations to establish, or bind, the session, an IP precedence value of 0 and IP TOS value of 0 is used. These values are used until the bind takes place. When the session is a type 2 bind, the TN3270 client is assumed to be a screen; otherwise the client is assumed to be a printer.

When you use the no form of the command, the TOS value is either set to 0 for that configuration mode or the value set at a previous (higher) configuration mode is used. For example, if you are at the TN3270 PU configuration mode and issue a no ip tos screen command, any value you configured previously at the TN3270 server configuration mode will take effect.

You can enter new or different values for TOS without first using the no form of this command.

Examples

In the following example, the TN3270 server TOS screen value is set to 10 and a specific PU TOS screen value is set to 0:

interface channel 3/2
  tn3270-server
   ip tos screen 8
   ip tos printer 4
  pu PUS2
   ip tos screen 0

Related Commands

Command	Description
ip precedence (TN3270)	Specifies the precedence level for IP traffic in the TN3270 server.

Syntax Description

seconds	Number of elapsed seconds (from 0 to 65535) before the TN3270 server transmits a DO TIMING-MARK or Telnet nop command to the TN3270 client. A value of 0 means no keepalive signals are sent. The default is 1800 seconds (30 minutes).
send nop	(Optional) Sends the Telnet command for no operation to the TN3270 client to verify the physical connection. No response is required by the client.
send timing-mark [max-response-time]	(Optional) Number of seconds (from 0 to 32767) within which the TN3270 server expects a response to the DO TIMING-MARK from the TN3270 client. The default is 30 seconds if the keepalive interval is greater than or equal to 30 seconds. If the value of the keepalive interval is less than 30 seconds, then the default max-response-time is the value of the interval. The value of the max-response-time should be less than or equal to the interval.

Defaults

The default behavior is to send timing marks with a keepalive interval of 1800 seconds (30 minutes). If you specify only the keepalive interval, the TN3270 server sends timing-marks.

The default value of the send timing-mark max-response-time command is 30 seconds if the keepalive interval is greater than or equal to 30 seconds. If the value of the keepalive interval is less than 30 seconds, then the default max-response-time is the value of the interval.

Command Modes

TN3270 server configuration---The keepalive command at this level applies to all PUs supported by the TN3270 server.

Listen-point configuration---The keepalive command at this level applies to all PUs defined at the listen point.

Listen-point PU configuration---The keepalive command at this level applies only to the specified PU.

DLUR PU configuration---The keepalive command at this level applies to all PUs defined under DLUR configuration mode.

PU configuration---The keepalive command at this level applies only to the specified PU.

Command History

Release	Modification
11.2	This command was introduced.
12.0(5)T	The send {nop | timing-mark [max-response-time]} keywords were added.

Usage Guidelines

The keepalive command is valid only on the virtual channel interface. This command can be entered in one of four command modes (TN3270 configuration, Listen-point configuration, Listen-point PU configuration, or PU configuration mode). A value entered in TN3270 mode applies to all PUs for that TN3270 server, except as overridden by values entered in the other supported configuration modes. A no keepalive command entered in a subsequent configuration mode will restore the keepalive value entered in the previous command mode.

In Cisco IOS releases prior to 12.0(5)T in which the keepalive command is supported, you cannot specify the period of time in which the client must respond to the DO TIMING-MARK before the TN3270 server disconnects the session. By default in prior releases, if the client does not reply within 30 minutes of the transmission of the DO TIMING-MARK, the TN3270 server disconnects the TN3270 session. (The DO TIMING-MARK is a Telnet protocol operation that does not affect the client operation.)

With the addition of the send timing-mark max-response-time keywords in Cisco IOS release 12.0(5)T, you can specify the period of time in which the client must respond to the DO TIMING-MARK before being disconnected by the server. If you do not specify the max-response-time argument, the default value is determined by the size of the keepalive interval. The default is 30 seconds if the keepalive interval is greater than or equal to 30 seconds. If the value of the keepalive interval is less than 30 seconds, then the default max-response-time is the value of the interval.

If the IP path to the client is broken, the TCP layer will detect the failure to acknowledge the DO TIMING-MARK and initiate disconnection. This action usually takes much less than 30 seconds.

The keepalive command affects currently active and future TN3270 sessions. For example, reducing the keepalive interval to a smaller nonzero value causes an immediate burst of DO TIMING-MARKs on those sessions that have been inactive for a period of time greater than the new, smaller value.

Use the keepalive send nop command when you are using older TN3270 clients that do not support TIMING-MARK or are DOS-based clients. When you use the keepalive send nop command to monitor the client connection, no response is required by the client to the TN3270 server. However, the TCP/IP stack can detect that the physical connection still exists. This command is useful for those clients that can be swapped out when a DO TIMING-MARK has been sent by the TN3270 server. If the client is swapped out and cannot respond to the DO TIMING-MARK from the TN3270 server, the session is disconnected. However, if the client is swapped out and the Telnet nop command is sent by the server, the physical connection is still verifiable by the TCP/IP stack and the client remains connected to the server.

If your client supports the use of timing-marks and is not subject to being swapped out, then using timing-marks is preferable to the Telnet nop command for keepalive monitoring. The required response by TN3270 clients to timing-marks sent by the server provides a better indication of the health of the client-server connection.

Examples

The following example specifies that the TN3270 server transmits a DO TIMING-MARK in 15-minute (900-second) intervals and the client must respond within 30 seconds (the default value for the timing-mark max-response-time command when not specified):

keepalive 900
 

The following example entered in TN3270 configuration mode specifies that the TN3270 server transmits a DO TIMING-MARK in 30-minute (1800-second) intervals (the default interval) and the client must respond within 30 seconds (the default for the timing-mark max-response-time command when not specified):

no keepalive
 

The following example specifies that the TN3270 server transmits a DO TIMING-MARK in 40-minute (2400-second) intervals and the client must respond within 1 minute (60 seconds):

keepalive 2400 send timing-mark 60
 

Consider the following example in which the keepalive command is configured in more than one command mode. In this example the keepalive command is first configured in TN3270 server configuration mode, followed by Listen-point PU configuration mode. The keepalive command values specified under the listen-point PU overrides the keepalive 300 value specified under the tn3270-server for PU1. In this example, all other PUs except PU1 use the value of the keepalive 300 command specified in TN3270 configuration mode.

tn3270-server
keepalive 300
listen-point 10.10.10.1 tcp-port 40
  pu PU1 94223456 tok 1 08
    keepalive 10 send timing-mark 5
  pu PU2 94223457 tok 2 12

Related Commands

Command	Description
idle-time	Specifies how many seconds of LU inactivity, from both host and client, before the TN3270 session is disconnected.
timing-mark	Selects whether a WILL TIMING-MARK is sent when the host application needs an SNA response (definite or pacing response).

Syntax Description

name	Link name, from one to eight alphanumeric characters. The first character must be alphabetic. The name must be unique within the DLUR function.
rmac rmac	(Optional) Remote MAC address of the form xxxx.xxxx.xxxx in hexadecimal. If not specified, a loopback link to another SAP on the same internal LAN adapter is assumed.
rsap rsap	(Optional) Remote SAP address, 04 to FC in hexadecimal. The rsap value must be even and should be a multiple of 4, but this requirement is not enforced. The default value for the rsap argument is 04.

Defaults

No DLUR link is defined.

The default remote SAP address is 04 (hexadecimal).

Command Modes

DLUR SAP configuration

Command History

Release	Modification
11.2	This command was introduced.

Usage Guidelines

This command is valid only on the virtual channel interface. The combination of rmac and rsap must be unique within the DLUR SAP function. These values can only be changed by deleting the link definition, using the no link command, and recreating the link definition.

For a link via a channel on this CMCC adapter, the TN3270 server and the hosts should open different adapters. Using different adapters avoids any contention for SAP numbers, and is also necessary if you configure duplicate MAC addresses for fallback CSNA or CMPC access to the host.

Examples

The following example defines a link name and a remote SAP address:

link LINK5 rsap 08
 

The following example shows different adapter numbers configured on the same internal LAN to avoid SAP contention. The host uses SAP 4 on Token Ring adapter 0.

lan tokenring 0
 adapter 0 4000.0000.0001
 adapter 1 4000.0000.0002
tn3270-server
 dlur ...
 lsap token-adapter 1
  link HOST rmac 4000.0000.0001 rsap 4

Related Commands

Command	Description
adapter	Configures internal adapters.
dlur	Enables the SNA session switch function on the CMCC adapter, or enters DLUR configuration mode.
lsap	Creates a SAP in the SNA session switch, or enters DLUR SAP configuration mode.

Syntax Description

ip-address	IP address that the clients should use as the host IP address to map to LU sessions under this PU and listen point.
tcp-port number	(Optional) Port number used for the listen operation. The default value is 23.

Defaults

The default tcp-port number is 23.

Command Modes

TN3270 server configuration

Command History

Release	Modification
11.2(18)BC	This command was introduced.
12.0(5)T	This command was migrated to Cisco IOS Release 12.0 T.

Usage Guidelines

Use the listen-point command to create a unique listen point for every IP address and TCP-port pair. In this mode, the IP address and the TCP port are no longer configured in the PU. Configure the PUs under the appropriate listen point. The other siftdown configuration commands remain the same.

For example, in the old configuration the following statements were used to configure the IP address and TCP port in the PU:

tn3270-server
  pu PU1 94223456 10.10.10.1 tok 1 08
   tcp-port 40
   keepalive 10
 

In the new listen-point configuration, the following statements are used to configure the IP address and TCP port at the listen point:

tn3270-server
  listen-point 10.10.10.1 tcp-port 40
   pu PU1 94223456 tok 1 08
    keepalive 10
 

You can also use the listen-point configuration to assign the same IP address to multiple PUs. In the old configuration the following statements were used:

tn3270-server
  pu PU1 94201231 10.10.10.2 tok 1 10
  pu PU2 94201232 10.10.10.3 tok 1 12
  pu PU3 94201234 10.10.10.3 tok 1 14
  pu PU4 94201235 10.10.10.4 tok 1 16
   tcp-port 40
  pu PU5 94201236 10.10.10.4 tok 2 08
 

In the new listen point configuration, the old statements are replaced by the following configuration commands. In this example, PU2 and PU3 are grouped into one listen point because they have the same IP address. Note that even though PU4's IP address is identical to PU5's IP address, they are not configured within the same listen point because the listen point indicates a unique IP address and TCP port pair. If you do not specify the TCP port, the default port value is 23.

tn3270-server
 listen-point 10.10.10.2
  pu PU1 94201231 tok 1 10
 listen-point 10.10.10.3
  pu PU2 94201232 tok 1 12
  pu PU3 94201234 tok 1 14
 listen-point 10.10.10.4
  pu PU5 94201236 tok 2 08
 listen-point 10.10.10.4 tcp-port 40
  pu PU4 94201235 tok 1 16
 

The next example shows how the configuration changes for a DLUR PU. In this mode, the DLUR PU is no longer configured under DLUR, but is configured in the listen point.

In the old configuration, the following statements were used:

tn3270-server
 dlur NETA.RTR1 NETA.HOST
  dlus-backup NETA.HOST
  lsap token-adapter 15 08
   link MVS2TN rmac 4000.b0ca.0016
  pu PU1 017ABCDE 10.10.10.6
 

These statements are replaced by the following statements in the new listen-point configuration. The keyword dlur differentiates the listen-point direct PU from the listen point DLUR PU. The DLUR configuration must be completed before configuring the PU in the listen-point. Any siftdown commands configured within the scope of the listen point are automatically inherited by the PUs that are configured within the scope of that listen point. To override the siftdown configurations, you can explicitly configure the siftdown configuration commands within the scope of the listen-point PU.

tn3270-server
 dlur NETA.RTR1 NETA.HOST
  dlus-backup NETA.HOST
  lsap token-adapter 15 08
   link MVS2TN rmac 4000.b0ca.0016
 listen-point 10.10.10.6
  pu PU1 017ABCDE dlur

Examples

Following is an example of the listen-point command showing PU7 grouped into the listen point at IP address 10.10.10.1 and TCP port 40:

tn3270-server
listen-point 10.10.10.1 tcp-port 40
 pu PU7 94201237 tok 1 17

Related Commands

Command	Description
tn3270-server	Starts the TN3270 server on a CMCC adapter or enters TN3270 configuration mode.
pu dlur (listen-point)	Creates a PU entity that has no direct link to a host, or enters listen-point PU configuration mode.
pu (listen-point)	Creates a PU entity that has a direct link to a host, or enters listen-point PU configuration mode.

Syntax Description

type	Internal adapter type on the CIP card, which corresponds to the value specified in the lan internal LAN configuration command. The currently supported value for the type argument is token-adapter.
adapter-number	Internal adapter interface on the CIP card, which is the same value specified in the adapter internal LAN configuration command.
lsap	(Optional) Local SAP number, 04 to FC, in hexadecimal. The value must be even and should normally be a multiple of four. It must be unique within the internal adapter in that no other 802.2 clients of that adapter, in the router or in a host, should be allocated the same SAP. The default value is C0.

Defaults

The default value for the lsap argument is hexadecimal C0.

Command Modes

DLUR configuration

Command History

Release	Modification
11.2	This command was introduced.

Usage Guidelines

The lsap command is valid only on the virtual channel interface. If the SAP in the SNA session switch function is already created, the lsap command with no arguments puts you in DLUR SAP configuration mode.

The lsap command can be entered only in DLUR configuration mode.

The lsap command uses values that are defined in two other commands: the lan internal LAN configuration command and the adapter internal LAN configuration command. The lan type and adapter adapter-number values configured on the CMCC internal LAN interface are used in the lsap command. However, the lan type keyword is a little different. Where the value for the type argument on the lan command is tokenring, the corresponding value for the type argument on lsap is token-adapter. This emphasizes that the number that follows is an adapter number, not a lan number.

The no lsap command hierarchically deletes any links using it. Any sessions using those links are lost.

Examples

The following example defines an adapter type, an adapter number, and a local SAP:

lsap token 0 B0

Related Commands

Command	Description
adapter	Configures internal adapters.
dlur	Enables the SNA session switch function on the CMCC adapter, or enters DLUR configuration mode.
link (TN3270)	Defines and activates a link to a host.

Syntax Description

always	Always delete dynamic LUs upon disconnect.
normal	Delete screen LUs only upon disconnect.
non-generic	Delete only specified LUs upon disconnect.
never	Never delete LUs upon disconnect.

Defaults

The default keyword is never.

Command Modes

TN3270 server configuration---The lu deletion command at this level applies to all PUs supported by the TN3270 server.

Listen-point configuration---The lu deletion command at this level applies to all PUs defined at the listen point.

Listen-point PU configuration---The lu deletion command at this level applies only to the specified PU.

DLUR PU configuration---The lu deletion command at this level applies to all PUs defined under DLUR configuration mode.

PU configuration---The lu deletion command at this level applies only to the specified PU.

Note The lu deletion command is a siftdown command, so it can be used at any of the configuration command modes shown. The most recent lu deletion command in the PU configuration takes precedence.

Command History

Release	Modification
11.2(18)BC	This command was introduced.
12.0(5)T	This command was migrated to Cisco IOS Release 12.0 T.

Usage Guidelines

Use the always keyword of the lu deletion command when you have only screen LUs, but they are all of different sizes. This prevents screen LUs from attaching to a previously used LU with an incompatible screen size designated by a previous session.

Use the normal keyword of the lu deletion command when you have both screen and printer LUs. This is important because printers are acquired by the host application and are not logged on manually. If VTAM deletes the LU, then there is nothing for a host application (such as CICS) to acquire.

You can use the non-generic mode of LU deletion if VTAM can support deletion of specifically-named LUs. (The support of this mode is not currently available in VTAM, as of VTAM version 4.4.1.)

Use the never mode of LU deletion when you have only screen LUs and they all use the same screen size.

Examples

Following is an example of the lu deletion command specifying that the TN3270 server sends a REPLY-PSID poweroff request to delete only screen LUs upon session disconnect for any PUs supported by the TN3270 server:

tn3270-server
 lu deletion normal

Syntax Description

termself	Orders termination of all sessions and session requests associated with an LU upon disconnect.
unbind	Requests termination of the session by the application upon LU disconnect. This value is the default.

Defaults

Unbind is the default.

Command Modes

TN3270 server configuration---The lu termination command at this level applies to all PUs supported by the TN3270 server.

Listen-point configuration---The lu termination command at this level applies to all PUs defined at the listen point.

Listen-point PU configuration---The lu termination command at this level applies only to the specified PU.

DLUR PU configuration---The lu termination command at this level applies to all PUs defined under DLUR configuration mode.

PU configuration---The lu termination command at this level applies only to the specified PU.

Note The lu termination command is a siftdown command, so it can be used at any of the configuration command modes shown. The most recent lu termination command in the PU configuration takes precedence.

Command History

Release	Modification
11.2(18)BC	This command was introduced.
12.0(5)T	This command was migrated to the T-train

Usage Guidelines

Use the termself keyword when you want to be sure that the application terminates the session when the LU disconnects. This is important for certain applications such as CICS.

If you use the unbind keyword for session termination with applications such as CICS, VTAM security problems can arise. When CICS terminates a session from an UNBIND request, the application may reestablish a previous user's session with a new user, who is now assigned to the same freed LU.

Examples

Following is an example of the lu termination configuration command to force termination of the session when an LU disconnects for any PUs supported by the TN3270 server:

tn3270-server
 lu termination termself

Syntax Description

number

Maximum number of LU control blocks allowed. The allowed range is 0 to 32000. However, the practical upper limit for concurrently operating TN3270 sessions depends on the hardware and usage characteristics. The default is 2100.

Defaults

Because of the license structure, the default is 2100, which represents the limit of the lower-priced license (2000) plus a five percent buffer. If you configure a value greater than the default, a license reminder is displayed.

Command Modes

TN3270 server configuration

Command History

Release	Modification
11.2	This command was introduced.

Usage Guidelines

The maximum-lus command is valid only on the virtual channel interface. Although the value may be varied at any time, reducing it below the current number of LU control blocks will not release those blocks until a PU is inactivated by DACTPU or by using the no pu command.

If the number of LUs in use reaches 94% of the current setting of maximum-lus, a warning message is displayed on the console. To prevent redundant messages, the threshold for generating such messages is raised for a period.

The TN3270 server attempts to allocate one LU control block for each LU activated by the hosts. In the case of dynamic definition of dependent LU (DDDLU) the control block is allocated when the client requests the LU, in anticipation of an ACTLU from the SSCP host.

By limiting the number of LU control blocks allocated, you can make sure enough memory is available to support other CMCC functions. The control blocks themselves take about 1K bytes per LU. During session activity, a further 2K per LU may be needed for data. On a CIP, 32 MB of memory will support 4000 LUs. To support more than 4000 LUs, we recommend 64 MB of memory. On an XCPA, 8 MB of memory supports 1000 LUs.

Examples

The following example allows 5000 LU control blocks to be allocated:

maximum-lus 5000

Related Commands

Command	Description
client ip	Adds an IP subnet to a client subnet response-time group.
pu (TN3270)	Creates a PU entity that has its own direct link to a host, or enters PU configuration mode.
pu (DLUR)	Creates a PU entity that has no direct link to a host, or enters DLUR PU configuration mode.

Syntax Description

poolname	Unique pool name which cannot exceed eight characters. Valid characters are (alphabetic characters are not case sensitive): 1st character---Alphabetic (A-Z) and national characters `@', `#', and `$' 2nd-8th characters---Alphabetic (A-Z), numeric (0-9), and national characters `@', `#', and `$'
cluster layout layout-spec-string	(Optional) Name for the cluster and to indicate a cluster of LUs such as printers. The sum of the numbers must be less than or equal to 255. No spaces are used between the entries in the layout-spec-string. The default value is 1a.

Defaults

The default value for the layout-spec-string argument is "1a."

Command Modes

TN3270 server configuration

Command History

Release	Modification
11.2(18)BC	This command was introduced.
12.0(5)T	This command was migrated to Cisco IOS Release 12.0 T.

Usage Guidelines

The pool and allocate lu commands enable the TN3270 server to know the relationships between screen and printer LUs. These commands are an alternative to the LU nailing feature that allows clients to be nailed to LUs.

The pool command is configured in the TN3270 scope. The pool command provides the pool names and the definitions of the number of screens and printers in one logical cluster. Each pool statement must have a unique pool name.

The TN3270 server validates pool names when configuring a pool name and when processing the name received on a CONNECT request from the client. The TN3270 server rejects an invalid name and truncates the name received in the CONNECT request from the client to eight characters or at an invalid character (whichever comes first) when processing the CONNECT request.

When using a pool command to create a cluster, a combination of the following values is used in the layout-spec-string:

• s (screen)

• p (printer)

• a (any, or wildcard) [Refers to a printer or a screen]

Use the following format to define the layout-spec-string, where decimal_num is a decimal number between 1 and 255:

pool poolname cluster layout {decimal_nums}{decimal_nump}{decimal_numa}
 

The total sum of the numbers must be less than or equal to 255. No spaces are used between the entries in the layout-spec-string. The default is 1a, which defines 1 screen or 1 printer. A screen, printer, or a wildcard definition cannot be followed by a definition of the same type. A screen definition can only be followed by a printer or wildcard. Similarly, a printer definition can be followed only by a wildcard or a screen definition.

The following are examples of invalid layout-spec-string values, and the corresponding corrected specification:

• A layout-spec-string of 3s6s is invalid. The correct specification is 9s.

• A layout-spec-string of 3s6p7a8a is invalid. The correct specification is 3s6p15a.

• A layout-spec-string of 255s10p is invalid. Although the decimal number for any portion of the layout-spec-string can be between 1 and 255, the total number across all parameters cannot exceed 255. To correct this example, you can reduce the screens to 245 as 245s10p.

The combination of a screen, printer, and wildcard constitute a group. The layout-spec-string can support a maximum of 4 groups.

Consider the following example:

pool CISCO cluster layout 2s3p4a5s6a7s8p9s
 

There are 4 groups in this definition: 2s3p4a, 5s6a, 7s8p and 9s.

Pools must be defined before any pool references under the listening points are defined. Also, pools must be defined before they are referenced by other statements in the configuration. Failure to define the pool before it is referenced will cause the referencing configuration to be rejected.

Pools that are deleted (using the no form of the command) will cause all statements referencing the pool to be deleted.

The following criteria apply to the creation of pool names and LOCADDRs:

• Pool and LU names must be unique; they cannot be identical.

• LOCADDR ranges for pools must not overlap.

• LOCADDR ranges for LU pools must not overlap with the existing client nailing configuration.

• Pool configurations made while LUs are in use do not affect the current LU configuration.

The following example uses the pool command to create two pools, pcpool and unixpool:

tn3270-server
 pool pcpool cluster layout 4s1p
 pool unixpool cluster layout 49s1p
listen-point 10.20.30.40
 client ip 10.10.10.2 pool pcpool
 pu PU1 91903315 dlur
  allocate lu 1 pool pcpool clusters 50
 pu PU2 91903345 dlur
  allocate lu 1 pool unixpool clusters 5
 

In this example, the pcpool contains a cluster of 4 screens and 1 printer per cluster. The total number of devices in a cluster cannot exceed 255, therefore the pcpool contains a total of 50 clusters with each cluster containing 5 LUs. Note that the remaining 5 LUs automatically go to the generic pool.

The unixpool contains 49 screens and 1 printer per cluster. The total number of devices in a cluster cannot exceed 255, therefore the unixpool contains a total of 5 clusters with each cluster containing 50 LUs. Again, note that the last 5 LUs automatically go to the generic pool.

Related Commands

Command	Description
tn3270-server	Starts the TN3270 server on a CMCC adapter or enters TN3270 configuration mode.

Syntax Description

name	Fully qualified name of an NN.

Defaults

No default behavior or values.

Command Modes

DLUR configuration

Command History

Release	Modification
11.2	This command was introduced.

Usage Guidelines

The preferred-nnserver command is valid only on the virtual channel interface. Fully qualified names consist of two case-insensitive alphanumeric strings, separated by a period. However, for compatibility with existing APPN products, including VTAM, the characters "#" (pound), "@" (at), and "$" (dollar) are allowed in the fully qualified name strings. Each string is from one to eight characters long; for example, RA12.NODM1PP. The portion of the name before the period is the NETID and is shared between entities in the same logical network.

When no preferred server is specified, the DLUR will request NN server support from the first suitable node with which it makes contact. If refused, it will try the next one, and so on.

If a preferred server is specified, then DLUR will wait a short time to allow a link to the preferred server to materialize. If the preferred server is not found in that time, any suitable node can be used, as above.

DLUR will not relinquish the current NN server merely because the preferred server becomes available.

Examples

The following example selects SYD.VMX as the preferred NN server:

preferred-nnserver SYD.VMX

Related Commands

Command	Description
dlur	Enables the SNA session switch function on the CMCC adapter, or enters DLUR configuration mode.

Syntax Description

pu-name	Name that uniquely identifies this PU.
idblk-idnum	Value of this argument must match the IDBLK-IDNUM value defined at the host. The value must be unique within the subarea; however, the TN3270 server cannot tell which remote hosts are in which subareas and does not enforce the unique value requirement.
type	Internal adapter type on the CIP card, which corresponds to the value specified in the lan internal LAN configuration command. The currently supported type is token-adapter.
adapter-number	Internal adapter interface on the CIP card, which is the same value specified in the adapter internal LAN configuration command.
lsap	Local SAP number in hexadecimal, ranging from 04 to DE. The value must be even, and must be unique within the internal adapter so that no other 802.2 clients of that adapter, in the router or in a host, are allocated the same SAP. Other direct links from TN3270 server direct PUs may use the same value on the internal adapter as long as the remote MAC or SAP is different.
rmac rmac	(Optional) Remote MAC address. The remote MAC address in the form xxxx.xxxx.xxxx hexadecimal, specifying the MAC address of the remote host. If not specified, a loopback link to another SAP on the same internal LAN adapter is assumed.
rsap rsap	(Optional) Remote SAP address. The remote SAP address is a one- or two-character hexadecimal string, ranging from 04 to FC, that specifies the SAP address of the remote host. The default is 04.
lu-seed lu-name-stem	(Optional) LU name that the client uses when a specific LU name request is needed. The format is x...x## or x...x### where x...x is an alphanumeric string. When ## is specified, it is replaced with the LU LOCADDR in hexadecimal digits to form the complete LU name. When ### is specified, decimal digits are used, padded with leading zeroes to make three characters. The first x must be alphabetic and the entire string, including the # symbols, must not exceed 8 characters.

Defaults

The default remote SAP address is 04 (hexadecimal).

Command Modes

Listen-point configuration

Command History

Release	Modification
11.2	This command was introduced.
11.2(18)BC	Listen-point PU configuration was added.
12.0(5)T	This command was migrated to Cisco IOS Release 12.0 T.

Usage Guidelines

The pu pu-name command is valid only on the virtual channel interface. If the PU is already created, the pu pu-name command with no arguments puts you in listen-point PU configuration mode, where you can modify an existing PU entity.

The pu listen-point command uses values that are defined in two other commands: the lan internal LAN configuration command and the adapter internal LAN configuration command. The lan type and adapter adapter-number values configured on the CIP internal LAN interface are used in the pu command.

For a link via a channel on this CMCC adapter, the TN3270 server and the hosts should open different adapters. Using different adapters avoids contention for SAP numbers and is also necessary if you configure duplicate MAC addresses for fallback CSNA or CMPC access to the host.

Examples

The following example configures the TN3270 server to be active and has one PU, CAPPU1, trying to connect. An LU seed using hexadecimal digits is defined.

tn3270-server
pu CAPPU1 05D18101 token-adapter 3 04 rmac 4000.0501.0001 lu-seed CAP01L##
 

The following example shows different adapter numbers configured on the same internal LAN to avoid SAP contention. The host uses SAP 4 on Token Ring adapter 0.

lan tokenring 0
 adapter 0 4000.0000.0001
 adapter 1 4000.0000.0002
tn3270-server
 listen-point 10.20.30.40
  pu PU1 05d00001 token-adapter 1 8 rmac 4000.0000.0001 rsap 4

Related Commands

Command	Description
adapter	Configures internal adapters.
lan	Configures an internal LAN on a CMCC adapter interface and enters internal LAN configuration mode.
listen-point	Defines an IP address for the TN3270 server.
show extended channel tn3270-server	Displays current server configuration parameters and the status of the PUs defined for the TN3270 server.

Syntax Description

pu-name	Name that uniquely identifies this PU.
idblk-idnum	The value for this argument must match the IDBLK-IDNUM value defined at the host. The value must be unique within the subarea; however, the TN3270 Server cannot tell which remote hosts are in which subareas and does not enforce the unique value requirement.
ip-address	IP address that the clients should use as host IP address to map to LU sessions under this PU.
type	Internal adapter type on the CIP card, which corresponds to the value specified in the lan internal LAN configuration command. The currently supported type is token-adapter.
adapter-number	Internal adapter interface on the CIP card, which is the same value specified in the adapter internal LAN configuration command.
lsap	Local SAP number in hexadecimal, ranging from 04 to FC. The value must be even, and must be unique within the internal adapter so that no other 802.2 clients of that adapter, in the router or in a host, should be allocated the same SAP. Other direct links from TN3270 server direct PUs may use the same value on the internal adapter as long as the remote MAC or SAP is different.
rmac rmac	(Optional) Remote MAC address. The remote MAC address of the form xxxx.xxxx.xxxx hexadecimal, specifying the MAC address of the remote host. If not specified, a loopback link to another SAP on the same internal LAN adapter is assumed.
rsap rsap	(Optional) Remote SAP address. The remote SAP address is a one- or two-character hexadecimal string, ranging from 04 to FC, specifying the SAP address of the remote host. The default is 04.
lu-seed lu-name-stem	(Optional) Provides an LU name that the client can use when a specific LU name request is needed. The format can be x...x## or x...x### where x..x is an alphanumeric string. When ## is specified, it is replaced with the LU LOCADDR in hexadecimal digits to form the complete LU name. When ### is specified, decimal digits are used, padded with leading zeroes to make three characters. The first x must be alphabetic and the entire string, including the # symbols, must not exceed 8 characters.

Defaults

No PU is defined.

The default remote SAP address is 04 (hexadecimal).

Command Modes

TN3270 server configuration

Command History

Release	Modification
11.2	This command was introduced.

Usage Guidelines

The pu pu-name command is valid only on the virtual channel interface. If the PU is already created, the pu pu-name command with no arguments puts you in PU configuration mode, where you can modify an existing PU entity.

The pu (TN3270) command uses values that are defined in two other commands: the lan internal LAN configuration command and the adapter internal LAN configuration command. The lan type and adapter adapter-number values configured on the CIP internal LAN interface are used in the pu command.

For a link via a channel on this CMCC adapter, the TN3270 server and the hosts should open different adapters. Using different adapters avoids any contention for SAP numbers, and is also necessary if you configure duplicate MAC addresses for fallback CSNA or CMPC access to the host.

Examples

The following example configures the TN3270 server to be active, and has one PU, CAPPU1, trying to connect in. An LU seed using hexadecimal digits is defined.

tn3270-server
pu CAPPU1 05D18101 10.14.20.34 token-adapter 3 rmac 4000.0501.0001 lu-seed CAP01L##
 

The following example shows different adapter numbers configured on the same internal LAN to avoid SAP contention. The host uses SAP 4 on token ring adapter 0.

lan tokenring 0
 adapter 0 4000.0000.0001
 adapter 1 4000.0000.0002
tn3270-server
 pu PU1 05d00001 10.0.0.1 token-adapter 1 8 rmac 4000.0000.0001 rsap 4

Related Commands

Command	Description
adapter	Configures internal adapters.
link (TN3270)	Defines and activates a link to a host.
tn3270-server	Starts the TN3270 server on a CMCC adapter or enters TN3270 server configuration mode.

Syntax Description

pu-name	Name that uniquely identifies this PU.
idblk-idnum	Value for this argument must match the IDBLK-IDNUM value defined at the host. The value must be unique within the subarea; however, the TN3270 server generally cannot tell which remote hosts are in which subareas, so the server only enforces uniqueness within the set of DLUR PUs.

Defaults

No PU is defined.

Command Modes

Listen-point configuration

Command History

Release	Modification
11.2	This command was introduced.
11.2(18)BC	Listen-point PU configuration was added.
12.0(5)T	This command was migrated to Cisco IOS Release 12.0 T.

Usage Guidelines

If the PU is already created, the pu dlur command without any arguments starts listen-point PU configuration mode. In this mode you can modify an existing listen-point DLUR PU entity.

You should define the DLUR before you configure the listen-point DLUR PU.

A typical usage for the IP address is to reserve an IP address for each application. For example, clients wanting to connect to TSO specify an IP address that is defined with PUs that have LOGAPPL=TSO.

Examples

The following example defines three PUs in the listen point with an IP address of 172.18.4.18:

tn3270-server
listen-point 172.18.4.18
 pu p0  05D99001 dlur
 pu p1  05D99002 dlur
 pu p2  05D99003 dlur

Related Commands

Command	Description
dlur	Enables the SNA session switch function on the CMCC adapter, or enters DLUR configuration mode.
listen-point	Defines an IP address for the TN3270 server.

Syntax Description

name	Alphanumeric string for the response-time group name. The maximum length of the name is 24 characters. Lower or uppercase letters can be used.
bucket boundaries t1 t2 t3 t4	(Optional) Unsigned 32-bit quantity that defines a bucket boundary in tenths of seconds. For other types of client groups, the bucket boundaries and multiplier values are fixed to the following defaults: Bucket boundaries---10, 20, 50, 100 Multiplier---30
multiplier m	(Optional) Number in the range of 1 to 5760, which when multiplied by the sample interval of 20 seconds, determines the collection interval.

Defaults

Bucket boundaries and the multiplier value are fixed to the following defaults:

• Bucket boundaries---10, 20, 50, 100

• Multiplier---30

Command Modes

TN3270 server configuration

Command History

Release	Modification
11.2(18)BC	This command was introduced.
12.0(5)T	This command was migrated to Cisco IOS Release 12.0 T.

Usage Guidelines

Multiple response-time groups can be configured within the scope of available memory. When using this command, up to 1024 IP subnets can be defined per response-time group with the client ip command. All TN3270 clients belonging to subnets configured within a specific response-time group are added to the response-time group when they connect as clients.

If the IP address and mask combination already exists within any response-time group, the following error message is displayed:

Subnet 10.1.1.0 255.255.255.248 already exists in client group MYSUBNET 

In the following example, the response-time group MYSUBNET is configured:

tn3270-server
response-time group MYSUBNET bucket boundaries 15 25 60 120 multiplier 35
 client ip 10.1.1.0 255.255.255.248
 client ip 10.1.2.0 255.255.255.248

Related Commands

Command	Description
client ip	Adds an IP subnet to a client subnet response-time group.
show extended channel tn3270-server response-time application	Displays information about Application response-time client groups.
show extended channel tn3270-server response-time global	Displays information about the Global response-time client group.
show extended channel tn3270-server response-time link	Displays information about Host Link response-time client groups.
show extended channel tn3270-server response-time listen-point	Displays information about Listen-point response-time client groups.
show extended channel tn3270-server response-time subnet	Displays information about Subnet response-time client groups.

Syntax Description

slot	Specifies a particular CMCC adapter in the router where slot is the slot number.
port	Port value for a TN3270 server will always be 2.

Defaults

No default behavior or values.

Command Modes

EXEC

Command History

Release	Modification
11.2	This command was introduced.
12.0(5)T	The following fields were added to the output display: lu-termination lu-deletion

Examples

The following is sample output from the show extended channel tn3270-server command:

Router# show extended channel 3/2 tn3270-server
 
<current stats> < connection stats >  <response time(ms)>
server-ip:tcp        lu in-use   connect disconn fail   host     tcp
172.28.1.106:23     510     1       12       11     0     54     40
172.28.1.107:23     511     0        0        0     0      0      0
172.28.1.108:23     255     0        0        0     0      0      0
total              1276     1
configured max_lu 20000
idle-time    0           keepalive 1800      unbind-action disconnect  
tcp-port   23            generic-pool permit no timing-mark
lu-termination unbind lu-deletion never
dlur MPX.GOANCP                              status SHUT    
dlus MPX.NGMVMPC      
 
name(index)    ip:tcp               xid   state     link   destination   r-lsap
EXT2(1)      172.28.1.106:23     05D18092 ACTIVE    tok 0  4000.7470.00e7 08 04
PUS10(2)     172.28.1.107:23     05D19010 ACTIVE    tok 0  4000.7470.00e7 08 2C
PUS11(3)     172.28.1.107:23     05D19011 ACTIVE    tok 0  4000.7470.00e7 08 28
PUS12(4)     172.28.1.108:23     05D19012 ACTIVE    tok 0  4000.7470.00e7 08 24
PUS9(5)      172.28.1.109:23     05D18509 SHUT      tok 0  4001.3745.1088 04 40
SDTF(7)      172.28.1.107:23     12345678 ACTIVE    tok 0  0800.5a4b.1cbc 04 08
TEST(8)      172.28.1.106:23     05D18091 ACTIVE    tok 0  4000.7470.00e7 08 30
INT1(6)      172.28.1.106:23     05D18091 SHUT      dlur   
 

Syntax Description

slot	Slot number.
port	Port number.
ip-address	IP address of the client.
disconnected	(Optional) Shows all clients with ip-address in disconnected state. Disconnected state refers to an LU session state of ACTIVE or INACTIVE. In this case, the ip-address refers to the client that last used the LU.
in-session	(Optional) Shows all clients with ip-address in active session state. Active session state refers to an LU session state of ACT/SESS.
pending	(Optional) Shows all clients with ip-address in pending state. Pending session state refers to an LU session state of P-SDT, P-ACTLU, P-NTF/AV, P-NTF/UA, P-RESET, P-PSID, P-BIND, P-UNBIND, WT-UNBND, WT-SDT or UNKNOWN.

Command Modes

EXEC

Command History

Release	Modification
11.2	This command was introduced.

Usage Guidelines

The show extended channel tn3270-server client-ip-address command is valid only on the virtual channel interface. Note that this command does not show information about LUs that have never been connected.

Examples

The following is sample output from the show extended channel tn3270-server client-ip-address command. The example shows only active sessions because no other session types exist at this client IP address.

Router# show extended channel 3/2 tn3270-server client-ip 192.195.80.40
 
lu    name   client-ip:tcp        nail state    model   frames in out   idle for
1   PUS11001 192.195.80.40:3169    Y   ACT/SESS 327804   5       5       0:5:47
 
pu is PUS11, lu is DYNAMIC type 2, negotiated TN3270
bytes 155 in, 1758 out; RuSize 1024 in, 3840 out; NegRsp 0 in, 0 out
pacing window 0 in, 1 out; credits 0 in, queue-size 0 in, 0 out
 

The following is sample output using the disconnected keyword:

Router# show extended channel 2/2 tn3270 client-ip 10.14.1.21 disconnected
 
Total 2 clients found using 10.14.1.21
 

The following is sample output using the in-session keyword:

Router# show extended channel 2/2 tn3270 client-ip 10.14.1.21 in-session
 
Note: if state is ACT/NA then the client is disconnected
 
lu    name   client-ip:tcp       nail state    model   frames in out   idle for
3    PU1L03 10.14.1.21:35215      N   ACT/SESS 327804    317     316     0:0:1
 
pu is PU1, lu is DYNAMIC type 2, negotiated TN3270
bytes 12167 in, 225476 out; RuSize 2048 in, 1536 out; NegRsp 0 in, 0 out
pacing window 0 in, 1 out; credits 0 in, queue-size 0 in, 0 out
Note: if state is ACT/NA then the client is disconnected
 
lu    name   client-ip:tcp       nail state    model   frames in out   idle for
4    PU1L04 10.14.1.21:35216      N   ACT/SESS 327804   317     316     0:0:1
 
pu is PU1, lu is DYNAMIC type 2, negotiated TN3270
bytes 12167 in, 225476 out; RuSize 2048 in, 1536 out; NegRsp 0 in, 0 out
pacing window 0 in, 1 out; credits 0 in, queue-size 0 in, 0 out
Note: if state is ACT/NA then the client is disconnected
Total 2 clients found using 10.14.1.21
 

The following is sample output using the pending keyword:

Router# show extended channel 2/2 tn3270 client-ip 10.14.1.21 pending
 
Total 2 clients found using 10.14.1.21
 

Related Commands

Command	Description
client ip lu	Defines a range of locaddrs to be reserved for remote devices.

Syntax Description

slot	Slot number.
port	Port number.

Command Modes

EXEC

Command History

Release	Modification
11.2	This command was introduced.

Usage Guidelines

The show extended channel tn3270-server dlur command is valid only on the virtual channel interface.

Examples

The following is sample output from the show extended channel tn3270-server dlur command:

Router# show extended channel 3/2 tn3270-server dlur
 
dlur MPX.GOANCP
current dlus MPX.NGMVMPC                dlur-dlus status ACTIVE
preferred dlus MPX.NGMVMPC              backup dlus MPX.NGMVMPB
preferred server MPX.NGMVMPA
lsap token-adapter   0 5C     vrn MPX.LAN4           status ACTIVE
link P390                 remote 4000.7470.00e7 08  status ACTIVE
 

Syntax Description

slot	Specifies a particular CMCC adapter in the router where slot is the slot number.
port	Port number.
name	Name of the SNA session switch link to be displayed.

Command Modes

EXEC

Command History

Release	Modification
11.2	This command was introduced.

Usage Guidelines

The show extended channel tn3270-server dlurlink command is valid only on the virtual channel interface.

Examples

The following is sample output from the show extended channel tn3270-server dlurlink command:

Router# show extended channel 3/2 tn3270-server dlurlink P390
 
lsap token-adapter  0 5C  vrn MPX.LAN4              status ACTIVE
link P390                 remote 4000.7470.00e7 08  status ACTIVE
partner MPX.NGMVMPC       tgn 1                     maxdata   1033
 

Related Commands

Command	Description
dlur	Enables the SNA session switch function on the CMCC adapter, or enters DLUR configuration mode.

Syntax Description

slot	Slot number.
port	Port number.
ip-address	Remote client IP address.

Command Modes

EXEC

Command History

Release	Modification
12.0	This command was introduced.

Usage Guidelines

The show extended channel tn3270-server nailed-ip command is valid only on the virtual channel interface.

Examples

The following is sample output from the show extended channel tn3270-server nailed-ip command:

Router# show extended channel 3/2 tn3270-server nailed-ip 172.28.0.0
172.28.1.0  255.255.255.192    pu BAGE1  lu 1     50
172.28.1.80 255.255.255.248    pu BAGE2  lu 100  200    printer
172.28.1.83                    pu BAGE3  lu 1     60    printer
172.28.1.82                    pu BAGE1  lu 100  200
 

Related Commands

Command	Description
client ip lu	Defines a range of locaddrs to be reserved for remote devices.

Syntax Description

slot	Specifies a particular CMCC adapter in the router where slot is the slot number.
virtual channel	Virtual channel number.
pu-name	Name that uniquely identifies this PU.
cluster	(Optional) Display cluster information for the LUs within the pool.

Defaults

No default behavior or values.

Command Modes

EXEC

Command History

Release	Modification
11.2	This command was introduced.
11.2(2.1)	ACT/NA replaced ACTIVE status for LU states. A note was added to the output to describe its meaning.
11.2(18)BC	The cluster keyword was added.
12.0(5)T	The following fields were added to the output display: lu-termination lu-deletion

Usage Guidelines

The show extended channel tn3270-server pu command is valid only on the virtual channel interface. The display shown depends on whether the PU is a direct PU or a SNA session switch PU.

The output for the show extended channel tn3270-server pu command also varies by whether you are using the optional cluster keyword. Without the cluster keyword, the output column headings for the LU information appear as "model," "frames in out," and "idle for."

When you use the cluster keyword, the output column headings for the LU information appear as "cluster," "pool," and "count." The cluster heading lists the specific cluster within the pool to which the LU belongs along with the specific cluster layout after the slash.

The pool heading identifies the corresponding pool name, and the count heading identifies the cluster number out of the total number of clusters in the pool.

Examples

This example shows a sample router configuration and the corresponding output using the show extended channel tn3270-server pu command:

interface Channel6/1
 no ip address
 no keepalive
 csna E160 40
!
interface Channel6/2
 ip address 172.18.4.17 255.255.255.248
 no keepalive
 lan TokenRing 15
  source-bridge 15 1 500
  adapter 15 4000.b0ca.0015
 lan TokenRing 16
  source-bridge 16 1 500
  adapter 16 4000.b0ca.0016
 tn3270-server
  pool PCPOOL   cluster layout 4s1p
  pool SIMPLE   cluster layout 1a
  pool UNIXPOOL cluster layout 49s1p
  dlur NETA.SHEK NETA.MVSD
   lsap token-adapter 15 04
    link SHE1     rmac 4000.b0ca.0016
  listen-point 172.18.4.18 tcp-port 23
   pu PU1      91903315 dlur
    allocate lu 1 pool PCPOOL   clusters 10
    allocate lu 51 pool UNIXPOOL clusters 2
    allocate lu 200 pool SIMPLE   clusters 50
  listen-point 172.18.4.19 tcp-port 2023
   pu PU2      91913315 token-adapter 16 08
    allocate lu 1 pool UNIXPOOL clusters 2
    allocate lu 101 pool SIMPLE   clusters 100
    allocate lu 201 pool PCPOOL   clusters 10
 

Following is an example of output for the show extended channel tn3270-server pu command without the cluster keyword for a PU named PU1:

Router# show extended channel 6/2 tn3270-server pu pu1
 
name(index)    ip:tcp               xid   state     link   destination r-lsap
PU1(1)       172.18.4.18:23      91903315 ACTIVE    dlur   NETA.SHPU1
 
idle-time    0      keepalive 1800      unbind-act discon   generic-poolperm
ip-preced-screen 0 ip-preced-printer 0 ip-tos-screen  0 ip-tos-printer 0
lu-termination unbind lu-deletion never
bytes 27019 in, 73751 out; frames 1144 in, 869 out; NegRsp 0 in, 0 out
actlus 5, dactlus 0, binds 5
Note: if state is ACT/NA then the client is disconnected
 
lu    name   client-ip:tcp       nail state    model   frames in out  idle for
1   SHED1001 161.44.100.162:1538   N   ACT/SESS 3278S2E  228     172    0:0:2
51  SHED1051 161.44.100.162:1539   N   ACT/SESS 3278S2E  240     181    0:0:2
151 SHED1151 161.44.100.162:1536   N   ACT/SESS 327802E  212     160    0:0:5
152 SHED1152 161.44.100.162:1537   N   ACT/SESS 3278S2E  220     166    0:0:4
200 SHED1200 161.44.100.162:1557   N   ACT/SESS 3278S2E  244     184    0:0:2

Following is an example of output for the show extended channel tn3270-server pu command with the cluster keyword for a PU named PU1. In the example below, 1/1a identifies cluster 1 with a layout of 1a, which contains 1 LU of any type.

Router# show extended channel 6/2 tn3270-server pu pu1 cluster
 
name(index)    ip:tcp               xid   state     link   destination  r-lsap
PU1(1)       172.18.4.18:23      91903315 ACTIVE    dlur   NETA.SHPU1
 
idle-time    0      keepalive 1800      unbind-act discon   generic-poolperm
ip-preced-screen 0 ip-preced-printer 0 ip-tos-screen  0 ip-tos-printer 0
lu-termination unbind lu-deletion never
bytes 27489 in, 74761 out; frames 1164 in, 884 out; NegRsp 0 in, 0 out
actlus 5, dactlus 0, binds 5
Note: if state is ACT/NA then the client is disconnected
 
lu    name   client-ip:tcp       nail state    cluster   pool  count
1   SHED1001 161.44.100.162:1538   N   ACT/SESS 1/4s1p  PCPOOL   1/5
51  SHED1051 161.44.100.162:1539   N   ACT/SESS 1/49s1p UNIXPOOL 1/50
151 SHED1151 161.44.100.162:1536   N   ACT/SESS 1/1a    :GENERIC 1/1
152 SHED1152 161.44.100.162:1537   N   ACT/SESS 1/1a    :GENERIC 1/1
200 SHED1200 161.44.100.162:1557   N   ACT/SESS 1/1a    SIMPLE   1/1

Note If the cluster layout is very long, only the first 8 bytes are displayed under the cluster column. The pool called :GENERIC is shown for all LUs that are not allocated to any specific pool name.

Related Commands

Command	Description
pu (listen-point)	Creates a PU entity that has a direct link to a host, or enters listen-point PU configuration mode.
pu dlur (listen-point)	Creates a PU entity that has no direct link to a host, or enters listen-point PU configuration mode.
allocate lu	Assigns LUs to a pool.

Syntax Description

slot	Specifies a particular CMCC adapter in the router where slot is the slot number. The port value for a TN3270 server will always be 2.
port	Port value for a TN3270 server will always be 2.
pu-name	PU name that uniquely identifies this PU.
locaddr	LU LOCADDR that uniquely identifies the LU.
history	(Optional) Displays the LU trace history.

Defaults Defaults

No default behavior or values.

Command Modes

EXEC

Command History

Release	Modification
11.2	This command was introduced.
11.2(2.1)	ACT/NA replaced ACTIVE status for LU states. A note was added to the output to describe its meaning.
11.2(18)BC	The response time buckets, average total response time, average IP response time, and the number of transactions fields were added to the output display.
12.0(5)T	This command was migrated to Cisco IOS Release 12.0 T.

Usage Guidelines

The show extended channel tn3270-server pu lu command is valid only on the virtual channel interface.

Examples

The following is sample output from the show extended channel tn3270-server pu lu command for a SNA session switch PU:

Router# show extended channel 3/2 tn3270 pu int1 lu 1
Note: if state is ACT/NA then the client is disconnected
 
lu    name   client-ip:tcp       nail  state      model   frames in out   idle for
1   GOAN1X01 171.69.176.77:3828    N    ACT/NA              4       4       0:4:51
 
pu is INT1, lu is STATIC type 0, negotiated TN3270E
bytes 74 in, 1219 out; RuSize 0 in, 0 out; NegRsp 0 in, 0 out
pacing window 0 in, 0 out; credits 0 in, queue-size 0 in, 0 out
 

The following is sample output from the show extended channel tn3270-server pu lu history command:

Router# show extended channel 3/2 tn3270 pu pus20 lu 1 history
Note: if state is ACT/NA then the client is disconnected
 
lu    name   client-ip:tcp       nail  state      model   frames in out   idle for
1   PUS20001 192.195.80.40:2480    N    ACT/SESS  327804    5       4       0:0:8
 
pu is PUS20, lu is DYNAMIC type 2, negotiated TN3270
bytes 155 in, 1752 out; RuSize 1024 in, 3840 out; NegRsp 0 in, 0 out>pacing window 0 in, 1 out; credits 0 in, queue-size 0 in, 0 out
traces:
         Client connect req
         Reply PSID pos rsp
         actlu req
         bind req
         sdt req
OUT len=12   2Dxxxxxxxx456B80000D0201
IN  len=25   xxxxxxxxxx45EB80000D0201000000
OUT len=53   2Dxxxxxxxx466B800031010303B1
IN  len=10   2D0001010646EB800031
OUT len=10   2D00010106476B8000A0
IN  len=10   2D0001010647EB8000A0
OUT len=1677 2Cxxxxxxxx010381C07EC7114040
IN  len=9    2C0001010001838100
 

This example shows the response-time information using the show extended channel tn3270-server pu lu command for the LU at LOCADDR 1 associated with the PU named vincdpu:

sydney# show extended channel 1/2 tn3270-server pu vincdpu lu 1
Note: if state is ACT/NA then the client is disconnected
 
lu    name   client-ip:tcp       nail   state    model frames in out   idle for
1   VINDG001 161.44.100.210:1315   N   ACT/NA   3278S2E  12      11      0:0:18
 
pu is VINCDPU, lu is DYNAMIC unbound, negotiated TN3270E
bytes 253 in, 954 out; RuSize 0 in, 0 out; NegRsp 1 in, 0 out
pacing window 0 in, 1 out; credits 0 in, queue-size 0 in, 0 out
response time buckets 14 31 15 3 1
average total response time 19 average IP response time 8
number of transactions 64
 

Related Commands

Command	Description
pu (listen-point)	Creates a PU entity that has a direct link to a host, or enters listen-point PU configuration mode.
pu dlur (listen-point)	Creates a PU entity that has no direct link to a host, or enters listen-point PU configuration mode.
response-time group	Configures a client subnet group for response-time measurements.

Syntax Description

slot	Slot number.
virtual channel	Virtual channel number.
appl-name	(Optional) Display only the client group corresponding to the VTAM application name.
detail	(Optional) List client members and their response-time statistics following the client group entry.

Defaults

No default behavior or values.

Command Modes

Privileged EXEC

Command History

Release	Modification
11.2(18)BC	This command was introduced.
12.0(5)T	This command was migrated to Cisco IOS Release 12.0 T.

Usage Guidelines

If optional keywords are not used for the show extended channel tn3270-server response-time application command, a complete list of currently existing per-application client groups is displayed along with their collection control parameters. If you specify the appl-name keyword, only the client group corresponding to that application is displayed. If you specify the detail keyword, the client group entry is followed by a list of its client members and their response-time statistics.

Examples

Following is an example of output for the show extended channel tn3270-server response-time application:

Router# show extended channel 3/2 tn3270-server response-time application MYAPPL
group APPL MYAPPL
  aggregate NO excludeip NO dynamic definite response NO
  sample period multiplier 30
  bucket boundaries 10 20 50 100
 

Related Commands

Command	Description
response-time group	Configures a client subnet group for response-time measurements.
show extended channel tn3270-server response-time global	Displays information about the Global response-time client group.
show extended channel tn3270-server response-time link	Displays information about Host Link response-time client groups.
show extended channel tn3270-server response-time listen-point	Displays information about Listen-point response-time client groups.
show extended channel tn3270-server response-time subnet	Displays information about Subnet response-time client groups.

Syntax Description

slot	Slot number.
virtual channel	Virtual channel number.

Defaults

No default behavior or values.

Command Modes

Privileged EXEC

Command History

Release	Modification
11.2(18)BC	This command was introduced.
12.0(5)T	This command was migrated to Cisco IOS Release 12.0 T.

Usage Guidelines

The show extended channel tn3270-server response-time global command displays collection control parameters for the global client group.

Examples

Following is an example of output for the show extended channel tn3270-server response-time global command:

Router# show extended channel 3/2 tn3270-server response-time global
group CLIENT GLOBAL
  aggregate YES excludeip NO dynamic definite response NO
  sample period multiplier 30
  bucket boundaries 10 20 50 100
  buckets 105 118 211 109 104
  average total response time 33 average IP response time 24
  number of transactions 647
 

Related Commands

Command	Description
response-time group	Configures a client subnet group for response-time measurements.
show extended channel tn3270-server response-time application	Displays information about Application response-time client groups.
show extended channel tn3270-server response-time link	Displays information about Host Link response-time client groups.
show extended channel tn3270-server response-time listen-point	Displays information about Listen-point response-time client groups.
show extended channel tn3270-server response-time subnet	Displays information about Subnet response-time client groups.

Syntax Description

slot	Slot number.
virtual channel	Port number.
link-name	(Optional) PU name for a direct PU or link name for a DLUR PU.

Defaults

No default behavior or values.

Command Modes

Privileged EXEC

Command History

Release	Modification
11.2(18)BC	This command was first introduced.
12.0(5)T	This command was migrated to Cisco IOS Release 12.0 T.

Usage Guidelines

This command displays information clients groups by host link. If no optional keywords are specified, a complete list of currently existing client groups by host link is displayed along with their collection control parameters and aggregate response-time statistics. If a value for the link-name argument is specified, only the client group corresponding to that link is displayed.

Examples

Following is an example of the output for the show extended channel tn3270-server response-time link command without optional keywords, which shows all current client groups by host link:

Router# show extended channel 3/2 tn3270-server response-time link
group DIRECT LINK MYLINK
  aggregate YES excludeip YES dynamic definite response NO
  sample period multiplier 30
  bucket boundaries 10 20 50 100
  buckets 10 18 21 10 10
  average total response time 37 average IP response time 23
  number of transactions 69
group DLUR LINK HISLINK
  aggregate YES excludeip YES dynamic definite response NO
  sample period multiplier 30
  bucket boundaries 10 20 50 100
  buckets 14 31 15 3 1
  average total response time 19 average IP response time 8
  number of transactions 64
 

Following is an example of the output for the show extended channel tn3270-server response-time link command for the link named DIRECT LINK MYLINK:

Router# show extended channel 3/2 tn3270-server response-time link direct link mylink
group DIRECT LINK MYLINK
  aggregate YES excludeip YES dynamic definite response NO
  sample period multiplier 30
  bucket boundaries 10 20 50 100
  buckets 10 18 21 10 10
  average total response time 37 average IP response time 23
  number of transactions 69
 

Related Commands

Command	Description
response-time group	Configures a client subnet group for response-time measurements.
show extended channel tn3270-server response-time application	Displays information about Application response-time client groups.
show extended channel tn3270-server response-time global	Displays information about the Global response-time client group.
show extended channel tn3270-server response-time listen-point	Displays information about Listen-point response-time client groups.
show extended channel tn3270-server response-time subnet	Displays information about Subnet response-time client groups.

Syntax Description

slot	Slot number.
virtual channel	Virtual channel number.

Defaults

No default behavior or values.

Command Modes

Privileged EXEC

Command History

Release	Modification
11.2(18)BC	This command was first introduced.
12.0(5)T	This command was migrated to Cisco IOS Release 12.0 T.

Usage Guidelines

The show extended channel tn3270-server response-time listen-point command displays information about groups of clients summarized by listen point. A complete list of currently existing listen-point client groups is displayed along with their collection control parameters and aggregate response-time statistics.

Examples

Following is an example of the output for the show extended channel tn3270-server listen-point command:

Router# show extended channel 3/2 tn3270-server response-time listen-point
group LP 10.20.30.40:23
  aggregate YES excludeip NO dynamic definite response NO
  sample period multiplier 30
  bucket boundaries 10 20 50 100
  buckets 10 18 21 10 10
  average total response time 37 average IP response time 23
  number of transactions 69
group LP 50.60.70.80:23
  aggregate YES excludeip NO dynamic definite response NO
  sample period multiplier 30
  bucket boundaries 10 20 50 100
  buckets 310 418 521 510 210
  average total response time 27 average IP response time 20
  number of transactions 1969
 

Related Commands

Command	Description
response-time group	Configures a client subnet group for response-time measurements.
show extended channel tn3270-server response-time application	Displays information about Application response-time client groups.
show extended channel tn3270-server response-time global	Displays information about the Global response-time client group.
show extended channel tn3270-server response-time link	Displays information about Host Link response-time client groups.
show extended channel tn3270-server response-time subnet	Displays information about Subnet response-time client groups.

Syntax Description

slot	Slot number.
virtual channel	Virtual channel number.
ip-address	(Optional) Subnet IP address.
ip-mask	(Optional) Subnet mask.
detail	(Optional) Each client group entry is followed by a list of its client members and their respective response-time statistics.

Defaults

No default behavior or values.

Command Modes

Privileged EXEC

Command History

Release	Modification
11.2(18)BC	This command was first introduced.
12.0(5)T	This command was migrated to Cisco IOS Release 12.0 T.

Usage Guidelines

This command shows information about client subnet client groups. This includes all configured groups plus the CLIENT SUBNET OTHER group. If no optional parameters are specified, a complete list of client subnet client groups is displayed along with their collection control parameters. If you specify values for the ip-address and ip-mask arguments, only client groups containing that subnet are displayed. If you specify the detail keyword, each client group entry is followed by a list of its client members and their response-time statistics.

Examples

Following is an example of the output for all configured client groups using the show extended channel tn3270-server response-time subnet command:

Router# show extended channel 3/2 tn3270-server response-time subnet
group SUBNETGROUP1
  subnet 10.10.10.0 255.255.255.192
  aggregate NO excludeip NO dynamic definite response NO
  sample period multiplier 30
  bucket boundaries 10 20 50 100
group SUBNETGROUP2
  subnet 10.10.10.128 255.255.255.192
  subnet 10.10.10.192 255.255.255.192
  aggregate NO exclude ip NO dynamic definite response NO
  sample period multiplier 40
  bucket boundaries 20 30 60 120
group CLIENT SUBNET OTHER
  aggregate NO exclude ip NO dynamic definite response NO
  sample period multiplier 30
  bucket boundaries 10 20 50 100
 

Following is an example of the output for subnet 10.10.10.0 with IP mask 255.255.255.192, which shows a list of the client members and their response-time statistics:

Router# show extended channel 3/2 tn3270-server response-time subnet
10.10.10.0 255.255.255.192 detail
 
group SUBNETGROUP1
  subnet 10.10.10.0 255.255.255.192
  aggregate NO excludeip NO dynamic definite response NO
  sample period multiplier 30
  bucket boundaries 10 20 50 100
  client 10.10.10.129:23
    buckets 5 8 11 9 4
    average total response time 33 average IP response time 24
    number of transactions 37
  client 10.10.10.130:23
    buckets 6 9 10 10 2
    average total response time 32 average IP response time 25
    number of transactions 37
  client 10.10.10.131:23
    buckets 11 14 10 8 7
    average total response time 27 average IP response time 19
    number of transactions 50
 

Related Commands

Command	Description
response-time group	Configures a client subnet group for response-time measurements.
show extended channel tn3270-server response-time application	Displays information about Application response-time client groups.
show extended channel tn3270-server response-time global	Displays information about the Global response-time client group.
show extended channel tn3270-server response-time link	Displays information about Host Link response-time client groups.
show extended channel tn3270-server response-time listen-point	Displays information about Listen-point response-time client groups.

Syntax Description

This command has no arguments or keywords.

Defaults

The interface or entity is enabled.

Command Modes

TN3270 server configuration

PU configuration

DLUR configuration

DLUR PU configuration

DLUR SAP configuration

Listen-point configuration

Listen-point PU configuration

Command History

Release	Modification
10.2	This command was introduced.
11.2	Support for the following configuration modes was added: TN3270 PU DLUR DLUR SAP
11.2(18)BC	Support for the following configuration modes was added: Listen-point Listen-point PU
12.0(5)T	This command was migrated to Cisco IOS Release 12.0 T.

Usage Guidelines

In TN3270 server configuration mode, the command shuts down the entire TN3270 server function.

In PU configuration mode, the command shuts down an individual PU entity within the TN3270 server.

In DLUR configuration mode, the command shuts down the whole DLUR subsystem within the TN3270 server.

In DLUR PU configuration mode, the command shuts down an individual PU within the SNA session switch configuration in the TN3270 server.

In DLUR SAP configuration mode, the command shuts down the local SAP and its associated links within the SNA session switch configuration.

Examples

The following example issued in TN3270 server configuration mode shuts down the entire TN3270 server:

shutdown

Syntax Description

port-number

A valid TCP port number in the range of 0 to 65534. The default is 23, which is the IETF standard. The value 65535 is reserved by the TN3270 server.

Defaults

In TN3270 server configuration mode, the default is 23.

In PU configuration mode the default is the value currently configured in TN3270 server configuration mode.

Command Modes

TN3270 server configuration---The tcp-port command at this level applies to all PUs supported by the TN3270 server.

DLUR PU configuration---The tcp-port command at this level applies to all PUs defined under DLUR configuration mode.

PU configuration---The tcp-port command at this level applies only to the specified PU.

Command History

Release	Modification
11.2	This command was introduced.

Usage Guidelines

The tcp-port command is valid only on the virtual channel interface, and it can be entered in either TN3270 server configuration mode or PU configuration mode. A value entered in TN3270 mode applies to all PUs for that TN3270 server, except as overridden by values entered in PU configuration mode. The tcp-port command affects only future TN3270 sessions.

The no tcp-port command entered in PU configuration mode removes the override.

Examples

The following example entered in TN3270 server configuration mode returns the TCP port value to 23:

no tcp-port

Related Commands

Command	Description
pu (listen-point)	Creates a PU entity that has a direct link to a host, or enters listen-point PU configuration mode.
pu dlur (listen-point)	Creates a PU entity that has no direct link to a host, or enters listen-point PU configuration mode.

Syntax Description

This command has no arguments or keywords.

Defaults

No TN3270 server function is enabled.

Command Modes

Interface configuration

Command History

Release	Modification
11.2	This command was introduced.

Usage Guidelines

The tn3270-server command is valid only on the virtual channel interface. Only one TN3270 server can run on a CMCC adapter. It will always be configured on a virtual channel interface.

The no tn3270-server command shuts down TN3270 server immediately. All active sessions will be disconnected and all DLUR and PU definitions deleted from the router configuration. To restart a TN3270 server, you must reconfigure all parameters.

Examples

The following example starts the TN3270 server and enters TN3270 server configuration mode:

tn3270-server

Syntax Description

This command has no arguments or keywords.

Defaults

No WILL TIMING-MARKS are transmitted except by keepalive.

Command Modes

TN3270 server configuration

Command History

Release	Modification
11.2	This command was introduced.

Usage Guidelines

If the timing-mark command is configured the TN3270 server will send WILL TIMING-MARK as necessary to achieve an end-to-end response protocol. Specifically, TIMING-MARK will be sent if any of the following are true:

• The host application has requested a pacing response.

• The host application has requested a Definite Response, and either the client is not using TN3270E, or the request is not Begin Chain.

The use of the timing-mark command can degrade performance. Some clients do not support timing-mark used in this way. Therefore, timing-mark should only be configured where both of the following are true:

• All clients support this usage.

• The application benefits from end-to-end acknowledgment.

Examples

The following example enables TIMING-MARK transmission:

  timing-mark

Related Commands

Command	Description
idle-time	Specifies how many seconds of LU inactivity, from both host and client, before the TN3270 session is disconnected.
keepalive (TN3270)	Specifies how many seconds of inactivity elapse before transmission of a DO TIMING-MARK or Telnet no operation (nop) to the TN3270 client.

Syntax Description

keep	No automatic disconnect will be made by the server on receipt of an UNBIND.
disconnect	Session will be disconnected upon receipt of an UNBIND.

Defaults

In TN3270 server configuration mode, the default is disconnect.

In PU configuration mode the default is the value currently configured in TN3270 server configuration mode.

Command Modes

TN3270 server configuration---The unbind-action command at this level applies to all PUs supported by the TN3270 server.

Listen-point configuration---The unbind-action command at this level applies to all PUs defined at the listen point.

Listen-point PU configuration---The unbind-action command at this level applies only to the specified PU.

DLUR PU configuration---The unbind-action command at this level applies to all PUs defined under DLUR configuration mode.

PU configuration---The unbind-action command at this level applies only to the specified PU.

Command History

Release	Modification
11.2	This command was introduced.

Usage Guidelines

The unbind-action command is valid only on the virtual channel interface. This command can be entered in either TN3270 server configuration mode or PU configuration mode. A value entered in TN3270 mode applies to all PUs for that TN3270 server, except as overridden by values entered in PU configuration mode. The unbind-action command affects currently active and future TN3270 sessions.

The no unbind-action command entered in PU configuration mode removes the override.

The unbind-action command affects currently active and future TN3270 sessions.

Examples

The following example prevents automatic disconnect:

unbind-action keep

Syntax Description

vrn-name

Fully qualified name of the connection network.

Defaults

The adapter is not considered to be part of a connection network.

Command Modes

DLUR SAP configuration

Command History

Release	Modification
11.2	This command was introduced.

Usage Guidelines

The vrn command is valid only on the virtual channel interface. This command is used to discover routes without having to configure all possible links.

A connection network is also known as a shared-access transport facility (SATF). This means, at the MAC level, that all nodes in the network can reach each other using the same addressing scheme and without requiring the services of SNA session routing. A bridged LAN (whether source-route or transparent) is an example. Such a network is represented in the APPN topology as a kind of node, termed a virtual routing node (VRN).

To make use of this function, all APPN nodes must use the same VRN name for the SATF.

Refer to the VTAM operating system documentation for your host system for additional information regarding the VTAM VNGROUP and VNNAME parameters on the PORT statement of an XCA major node.

Several parameters in the DLUR configuration mode consist of fully qualified names, as defined by the APPN architecture. Fully qualified names consist of two case-insensitive alphanumeric strings, separated by a period. However, for compatibility with existing APPN products, including VTAM, the characters "#" (pound), "@" (at), and "$" (dollar) are allowed in the fully qualified name strings. Each string is from one to eight characters long; for example, RA12.NODM1PP. The portion of the name before the period is the NETID and is shared between entities in the same logical network.

Examples

The following example sets a VRN name:

vrn SYD.BLAN25

Related Commands

Command	Description
dlur	Enables the SNA session switch function on the CMCC adapter, or enters DLUR configuration mode.
adapter	Configures internal adapters.
lan	Configures an internal LAN on a CMCC adapter interface and enters the internal LAN configuration mode.
lsap	Creates a SAP in the SNA session switch, or enters DLUR SAP configuration mode.