|
|
|
|
The configuration text file contains the following types of configuration records:
Specifies the following information about a host that can be accessed using TN3270:
Either the host's symbolic domain name or Internet Protocol (IP) 32-bit dotted-decimal address
TCP/IP port used to access the host
3270 screen model that the host supports
The configuration file contains at least one host record for each host that you can access. If a host can support more than one screen model, the configuration file has multiple host records for that host (one record for each screen model supported).
The host record may correspond either to a host computer that supports direct TN3270 access over TCP/IP or to another computer's communications product that provides the TN Server function. The standard SNAP-IX product provides TN Server function, which provides an intermediary function that connects to terminals over TCP/IP and to the host over SNA communications links.
Specifies the following information about a TN3270 user:
User's Solaris login name
User's default TN3270 style file
Hosts (identified by the name field of host records) that the user can use
The configuration file contains one user record for each Solaris user who has permission to use TN3270 emulation. Instead of configuring each user explicitly, you can set up a default user record to be used by any Solaris user.
Specifies the following information about diagnostics:
Files used to hold SNAP-IX TN3270 audit and error log information
Types of information logged
Boundaries used to classify Response Time Monitor (RTM) information
The configuration file must contain one and only one diagnostics record, which may contain only the record header [diagnostics] or the record header and values. If only the [diagnostics] record header is present, default values for the fields are used.
The specific formats for host, user, and diagnostics records are described in the following sections. Each record has the following general format:
[record_name]
field_name = value
.
.
.
field_name = value
Each record_name or field_name entry must be on a separate line. The record_name must be in square brackets and must have a value of host, user, or diagnostics. Each record (host, user, or diagnostics) includes one or more field names, some of which have a value assigned to them. Valid field names for each record type are described in the section that describes that record. The allowed values for each field name depend on which of the following field types are described by the field name:
A name that identifies the individual record. The value assigned must not match the name of any other record of the same type. The following characters are valid: A-Z, 0-9, @, #, and $. (The characters a-z are also accepted but are converted to uppercase.)
The value chosen is for the System Administrator's use only; it has no relevance outside of the SNAP-IX TN3270 system. Choose a name that identifies the resource.
Text string of any printable characters. The string is case sensitive and is not converted to uppercase.
Solaris file name, which can be the file name only or can include a full path (do not use a relative path). Ensure that the file name and path are valid; SNAP-IX TN3270 does not check for validity of path and file name.
A numeric value interpreted as one of the following:
Decimal by default
Hexadecimal if the value begins with 0x
Octal if the value contains a leading 0 (zero) character
No value is assigned to a flag field. Including a flag field in a record implies that the option represented by the flag is enabled. If the flag field is not included in a record, the corresponding option is disabled.
A choice from a group of values. The valid values are specified in the notes for the field.
The sections that follow describe the specific record formats for host, user, and diagnostics records. A table shows the following field attributes for each record type:
Which field type is associated with the field name.
Range of allowed values. The value shown in the table depends on the field type:
For record, text, and file fields, range indicates the minimum and maximum number of characters allowed in a string.
For number fields, range indicates the minimum and maximum numeric values for the field.
For flag and choice fields, range is not used.
Whether the field is required or optional.
The default value used for any optional fields (not including
flag fields) that do not have a value specified. (No default is required for
flag fields; the appropriate option is always not allowed
if
the flag is not specified.)
Note also the following conditions about the configuration text file:
In general, the host, user, and diagnostics records within a configuration file can appear in any order. Similarly, the individual fields within a record can be in any order. However, the following restrictions apply:
A host record must be defined before any user record that refers to it.
A TN3270 user's sessions are assigned to the host fields in a user record in the order in which host records appear in the configuration file. For example, if you configure two host fields, the user's first session is assigned to the host described by the first host field, and the user's second session is assigned to the host described by the second host field.
Field values cannot contain blank spaces; each value is a single continuous text string. All other blank spaces in the text file are ignored. Thus, any combination of spaces and tabs or completely blank lines is ignored.
The semi-colon (;) character indicates a comment string. If you include this character at any point on a line, any text following it (to the end of the line) is treated as a comment and ignored.
The host record provides information about a session with a TCP/IP host.
If users may use this host session for file transfer, the host LU configuration must specify DFT mode (3279 configuration), and not CUT mode (screen mode). Although there will be no difference when using the host LU for 3270 emulation, SNAP-IX does not support CUT mode file transfer. If an LU is configured at the host as CUT mode, any attempts to transfer files on a session using this LU will fail.
Check the host logmode table entry for the LU with your host administrator. The query bit in the PSERVIC operand of the MODEENT macro must be set to indicate a DFT mode LU; this means that the third hexadecimal digit (upper digit of the second byte) of the PSERVIC operand must be 8.
Summary of host Parameters, summarizes the parameters in a host record.
Specify values for name, domain, and any desired optional fields as described in the following list:
Specify the name of the TN3270 host record. Use 1-8 characters from the following set: A-Z, a-z, 0-9, @, # and $ (characters a-z are converted to uppercase).
The value chosen is for the System Administrator's use only; it has no relevance outside of the SNAP-IX TN3270 system. Choose a name that identifies the resource.
Specify either the symbolic domain name or the 32-bit dotted-decimal Internet Protocol (IP) address of the TN3270 host. Use 1-100 of any printable, case-sensitive characters. For examples, see Example of a host Record Using a Symbolic Domain Name and Example of a host Record Using a 32-Bit Dotted-Decimal IP Address.
The host record may correspond to either of the following:
A host computer that supports direct TN3270 access over TCP/IP.
Another computer's communications product that provides the TN Server function. The standard SNAP-IX product provides TN Server function. The TN Server function provides an intermediary function that connects to terminals over TCP/IP and to the host over SNA communications links.
Specify one of the following values:
This session with a TN3270 host uses a 3270 screen model 2.
This session with a TN3270 host uses a 3270 screen model 3.
This session with a TN3270 host uses a 3270 screen model 4.
This session with a TN3270 host uses a 3270 screen model 5.
This session with a TN3270E host uses a printer.
Include this flag field to allow a TN3270 user to override the screen model (change the TN3270 session customization to use a different model).
Specify the TCP/IP port number that the host uses for TN3270 data.
Specify the level of TN3270 support desired. Possible values are:
Only basic TN3270 protocols are supported. Even if the host supports TN3270E protocols, only TN3270 protocols will be used on the session.
Both basic TN3270 protocols and enhanced TN3270E protocols are supported. However, if the host does not support TN3270E, only TN3270 protocols will be used on the session.
Specify the name of a specific display or printer LU. If this field is blank, a generic display or printer LU is used.
Specify the name of a printer session associated with a display session.
This field is ignored if the value of the tn3270_support
field is
Do not include a separate host record in the file for the associated printer session. The only configuration information you need for the printer session is the session name you specify in the host record for the associated display session.
Following are two examples of host records:
[host] name = hostrec1 domain = remote.host.addr model = 4 ; model 4: 43 x 80 override ; user can override screen model lu_name = TNLU1 ; use LU specified tn3270_support = TN3270E ; use enhanced TN3270E protocols
[host] name = hostrec2 domain = 123.123.123.123 model = 4 ; model 4: 43 x 80 override ; user can override screen model port = 3270 tn3270_support = TN3270E ; use enhanced TN3270E protocols
The user record specifies the details of a TN3270 user. Summary of user Parameters, summarizes the parameters in a user record.
Specify values for name and any desired optional fields as described in the following list:
Specify the name of the TN3270 user. Use 1-20 of any printable, case-sensitive characters. This value must match the Solaris login ID of a user on the SNAP-IX TN3270 computer.
You can also set up a default TN3270 user record, using the name <DEFAULT> (in uppercase letters and surrounded by angle brackets, as shown). The <DEFAULT> record allows any Solaris user to use TN3270 emulation. If the user's Solaris login ID does not match the name field in any user record, SNAP-IX TN3270 uses the <DEFAULT> configuration record when the user starts TN3270 emulation.
Specify the name of the host record that describes the session to be used. Use 1-8 characters from the following set: A-Z, a-z, 0-9, @, # and $ (characters a-z are converted to uppercase). This name must match the name of a host record in this configuration file.
Specify a separate host entry for each session that the user can access (maximum of 10 sessions). If you specify multiple entries with the same host value, this provides multiple sessions to the same host.
If you do not configure at least one host field, the user will not be able to use the TN3270 emulation program.
If you have defined a host record for a display session with an associated printer session, you must include the name of the associated printer session in this list as well as the name of the host record for the display session.
Specify the name of the default TN3270 style file for this user. Use 1-8 of any printable, case-sensitive characters. This style file is used if the TN3270 user does not specify a style file when starting the TN3270 emulation program.
If no file name is specified, the TN3270 emulation program uses its own default settings.
Do not include an extension for the file name specified for this field because SNAP-IX TN3270 adds the extension automatically. For example, if you enter the name newsty, SNAP-IX TN3270 uses the file newsty.stu.
SNAP-IX TN3270 searches for this file in the directory /etc/opt/tn3270. However, if you give the user permission to modify the default style by including the modify_style field, SNAP-IX TN3270 first searches for a file of the same name in the user's home directory. If you are setting up a standard style for all your users, store the file in /etc/opt/tn3270 and do not give users write access to this file. If you give a user permission to modify the default style, the user should save the modified version in the user's home directory with the same file name as the file in /etc/opt/tn3270. This ensures that the correct file is found when the TN3270 emulation program is started.
Include this flag field to give the TN3270 user permission to change the TN3270 customization (either by using the TN3270 emulation program's menu interface or by loading a different style file).
Include this flag field to give the TN3270 user permission to view Response Time Monitor (RTM) data of host response times on each TN3270 session. To configure the boundaries by which response times are classified, see Format of diagnostics Record.
Include this flag field to give the TN3270 user permission to specify an alternative domain and port for a particular session. For more information about host domains and ports, refer to the SNAP-IX TN3270 User's Guide.
In the following example, the user has three sessions: two sessions that use hostrec1 and one session that uses hostrec2 :
[user]
name = <DEFAULT>
host = hostrec1
host = hostrec1
host = hostrec2
style_file = stdsty ; this is /etc/opt/tn3270/stdsty.stu
; modify_style not set - users can't use own style file
view_rtm ; users can view RTM data
change_domain ; users can override domain and port field in host records
The diagnostics record specifies the files used for audit and error logging and specifies the default logging level. The configuration text file must contain only one diagnostics record. Summary of diagnostics Parameters , summarizes the parameters in a diagnostics record.
Specify values for any desired optional fields as described in the following list:
Use 5-49 characters to indicate the full path and file name of the error log file, which is used to record exception and problem messages. The file extension must be either .log or .err.
If you want to send both error and audit messages to the same file, use the file extension .log and specify the same value for this field and for the audit_file field.
Use 5-49 characters to indicate the full path and file name of the audit log file, which is used to record audit messages. The file extension must be either .log or .aud.
If you want to send both error and audit messages to the same file, use the file extension .log and specify the same value for this field and for the error_file field.
Include this flag field to enable audit messages, or do not include this field to disable audit messages. Audit messages record normal system events. Because audit logging generates large amounts of text and may degrade performance, you may prefer to disable it unless you need it to diagnose a problem.
Include this flag field to enable exception messages, or do not include this field to disable exception messages. Exception messages record abnormal events that do not necessarily indicate problems.
Problem messages are always enabled. For more information about the three types of log messages, see Using SNAP-IX TN3270 Log Messages.
The four rtm_bdy values specify the boundaries, in tenths of seconds, by which host response times on TN3270 sessions are classified. If you give TN3270 users permission to view RTM data, they can view (for each session) a chart of the percentage of host response times in each of the time intervals specified by these boundaries. For example, if you specify rtm_bdy_1 through rtm_bdy_4 , users can view the percentage of responses below boundary 1, between boundaries 1 and 2, between boundaries 2 and 3, between boundaries 3 and 4, and above boundary 4.
Specify the boundaries as decimal numbers, from 5-1000, representing tenths of seconds. A value of 10 represents 1 second. The boundaries must not overlap. Boundary 4 must be greater than boundary 3, boundary 3 must be greater than boundary 2, and boundary 2 must be greater than boundary 1.
Following is an example of a diagnostics record:
[diagnostics]
error_file = /var/opt/tn3270/current.err
audit_file = /var/opt/tn3270/current.aud
exception ; problem and exception messages are logged,
; but not audit messages
rtm_bdy_1 = 10 ; 1 second
rtm_bdy_2 = 20 ; 2 seconds
rtm_bdy_3 = 50 ; 5 seconds
rtm_bdy_4 = 100 ; 10 seconds
|
|
|
 |
|