HNGROUP statement

Use the optional HNGROUP Client Identifier statement to define a group of host names. The group name can be used on several mapping statements.

Tip: To cause the host name to be present in the control vector (CV64) information, or to make the host name that is used to inform the mechanism be associated with the CHECKCLIENTCONN statement, add a dummy HNGROUP-ENDHNGROUP statement block.

Syntax

Read syntax diagramSkip visual syntax diagram
                          .---------.               
                          V         |               
>>-HNGROUP--hngroup_name----hn_name-+--ENDHNGROUP--------------><

Parameters

hngroup_name
The group name (up to 16 characters) that contains the host names.
hn_name
An exact, completely qualified host name or a wildcard host name.
Wildcards can be specified in two ways:
  • Use a single asterisk (*) to indicate that any value is acceptable for a particular qualifier in a particular position within the host name. For example, *.*.IBM.COM matches USER1.RALEIGH.IBM.COM, but does not match USER1.TCP.RALEIGH.IBM.COM because this name includes an extra qualifier.

    Restriction: Use of a single asterisk cannot follow any non wildcarded name. For example, RALEIGH.*.COM is not allowed.

  • Use a double asterisk (**) to indicate that any number of qualifiers are acceptable to the left of the asterisks. For example, **.IBM.COM matches USER1.IBM.COM, USER1.RALEIGH.IBM.COM, and USER1.TCP.RALEIGH.IBM.COM.
Both wildcard techniques require that the entire qualifier be wildcarded. For example, *USER.IBM.COM is not a valid use of a wildcard. In this case, use *.IBM.COM instead.

Usage notes

  • Any given host name or wildcard host name can only appear one time within all HNGROUPs.
  • Results in DNS hostname resolution for every new connection processed by the TN3270 server.
  • See Rules for host name specification for host name resolution and display information.