HP-UX SNAplus2 R7 Administration Guide

Managing SNAplus2 Client/Server Systems
Managing Win32 clients
MSG_tracing
file1 = msg_trace_filename_1
file2 = msg_trace_filename_2
flip_size = filesize
truncation_length = length
fmi = YES | NO
CS_tracing
file1 = cs_trace_filename_1
file2 = cs_trace_filename_2
flip_size = filesize
admin_msg = YES | NO
datagram = YES | NO
data = YES | NO
send = YES | NO
receive = YES | NO
Internal_tracing
file1 = internal_trace_filename_1
file2 = internal_trace_filename_2
flip_size = filesize
trace_level = nn
trace_flushing = YES | NO
Appl_Name
APPCTPN = tp_name
APPCLLU = lu_name
CSV_data
CSVTBLG = table_G_filename
Note
The domain = domain_name value is the only required value in the Registry.
The following sections explain the conguration parameters. Where a parameter takes the values YES or NO,any
string beginning with Y or y is interpreted as YES, and any string beginning with N or n is interpreted as NO.
Conguration
The Configuration subkey contains conguration information for the client, as follows:
domain
The Registry data type of this value is REG_SZ.
The domain_name value indicates the domain name of the SNAplus2 LAN, as specied during the client
installation. This line is required.
snagroup
The Registry data type of this value is REG_SZ.
The group_name value indicates the group name of the SNAplus2 user on this client. This name must match
the SNAplus2 conguration on servers, as follows:
If the client will be running 3270 or 5250 emulation, and you have set up the SNAplus2 conguration
to include emulator records for groups of users rather than an individual record for each user, this name
must match the name of an emulator user record that is dened for use by a group of users. Emulator user
records are dened using the define_emulator_user command; for more information, see Section
8.1.1, Conguring 3270 Emulator Users or Section 8.2.1, Conguring 5250 Emulator Users.
148