 |
» |
|
|
|
For WindowsSNAplus2 enables machines running Microsoft Windows 95 and
Windows NT to act as clients in the SNAplus2 domain. The SNAplus2
client software includes API libraries that are fully compatible
with Microsoft SNA Server and the Windows Open Systems Architecture
(WOSA), enabling applications written
for SNA Server to run unchanged on the SNAplus2 Win32 client. SNAplus2 supports the following WOSA APIs: 3270 Emulator Interface Specification
For more information about Windows SNA APIs, see the documentation
provided with Microsoft SNA Server. SNA network information, and other information required by
Win32 clients, is held in the Windows Program Registry. On a Win32 client, the component that handles access to SNAplus2
servers is called the Win32 client. The client must be enabled before
you can use SNAplus2 applications or emulation programs on the client.
For more information, see “Enabling a Win32 Client”. When the client is enabled, it contacts a server running SNAplus2
over the TCP/IP network in order to access SNAplus2 features. You
can optionally set up SNAplus2 servers to enforce password checking
for Win32 clients when running on Windows 95, so that the client
user must enter the correct password when enabling the client in
order to gain access to the server. For more information, see “Win32 Client Security”. The operation of the client is also controlled by the information
in the Windows Program Registry. The Windows Program Registry contains
information about the following: Configuration information specific
to Win32 clients Servers that the client can access Logging and tracing options for applications running
on the client Additional options for CPI-C and CSV applications
running on the client Invokable TPs (APPC or CPI-C) that can run on the
client
For more information, see “Win32 Client Configuration”. Enabling a Win32 Client | |
To enable the SNAplus2 software on a Windows 95 computer,
either double-click on the Win32
Client icon, or use the normal Windows “File Run”
mechanisms to run sxclappl.exe.
On a Windows NT computer, start the Win32 client service from the
control panel. On both Windows 95 and Windows NT systems, the installation
program sets up the system to start the Win32 client when the computer
is started. The client then uses the information in the Windows Program
Registry, described in “Win32 Client Configuration”, to locate a server running
SNAplus2. On a Windows 95 system, if the server is set up to validate
user names for Win32 clients (as described in “Win32 Client Security”), SNAplus2
displays a pop-up message requesting a password. You must type in
a password. SNAplus2 uses this password and the user name configured
for the Win32 client to validate that you are authorized to access
the server. If the server is not set up to validate user names,
the pop-up message does not appear. Disabling SNAplus2 for a Win32
Client | |
Before disabling the client, ensure that all SNAplus2 applications
(3270 and 5250 emulation programs, or applications using the SNAplus2
APIs) on the Win32 client have been stopped. To disable the client on a Windows 95 system, click on the
Win32 Client
icon and choose Close.
On a Windows NT system, stop the Win32 client service from the Control
Panel. Win32 Client Security | |
SNAplus2 provides a facility for validating the user name
and password of any Win32 client running on Windows 95 and attempting
to contact a server running SNAplus2. This enables you to ensure
that only authorized Windows users are able to access the SNAplus2
system. On Windows NT no validation is performed (the fact that
the user had to enter a password to access the desktop is considered
to provide sufficient security). By default, Win32 client security is not active, so that any
computer with the Win32 client software installed can access SNAplus2
servers. To enable Win32 client security, use the following procedure: Agree on a user
name and password with each Win32 client user who is authorized
to access the SNAplus2 system. On all servers that this client
can access, define this user name and password to the HP-UX system
as a system user name. After enabling the SNAplus2
software on a server, use the following command: snapwinsec domain This command enables Win32 client security on all servers
in the SNAplus2 domain. You do not need to repeat the command when
enabling the SNAplus2 software on other servers.
When a Win32 client starts up and tries to access a server
on which Win32 client security is enabled, the client software displays
a pop-up message requesting a password. This password from the Registry
is checked against the user names defined to the HP-UX system on
the server. If the Win32 client user does not specify a password,
or if the user name and password cannot be matched with a user name
and password on the server, the server rejects the client's access
attempt. To stop using Win32 client security, so that any Win32 client
user can access SNAplus2 servers without having to specify a password,
use the following command: snapwinsec off This command removes Win32 client security on all servers
in the SNAplus2 domain. You do not need to repeat the command on
other servers. Win32 Client Configuration | |
On both Windows NT and Windows 95, configuration information
is managed through the Windows Program Registry. The Windows Program Registry contains SNA network information
(similar to the information held in the client network data file
on HP-UX clients). It also contains some additional configuration
information that is specific to Win32 clients. The information is contained in values configured under subkeys
of the following key: The possible values for each Registry subkey are as follows: |
Configuration
domain = domain_name
snagroup = group_name
invoked_tps = YES | NO
lan_access_timeout = nn
broadcast_attempt_count = nn
server_lost_timeout = nn
client_start_timeout = nn
Servers
Server1 = * | servername1
Server2 = servername2
.
.
.
Server10 = servername10
Logging
exception_logging_enabled = YES | NO
audit_logging_enabled = YES | NO
log_directory = directory
error_file = error_filename
backup_error_file = backup_error_filename
error_file_wrap_size = error_file_size
audit_file = audit_filename
backup_audit_file = backup_audit_filename
audit_file_wrap_size = audit_file_size
succinct_errors = YES | NO
succinct_audits = YES | NO
API_tracing
file1 = trace_filename_1
file2 = trace_filename_2
flip_size = filesize
truncation_length = length
all_api = YES | NO
appc = YES | NO
cpic = YES | NO
csv = YES | NO
rui = YES | NO
nof = YES | NO
ms = YES | NO
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
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 contents of the file. Where
a parameter in the file 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. The Configuration subkey
contains configuration 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 specified 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 configuration on servers, as follows: If the client will be running 3270
or 5250 emulation, and you have set up the SNAplus2 configuration
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 defined for use by a group of users. Emulator
user records are defined using the define_emulator_user
command; for more information, see “Configuring 3270 Emulator
Users” or “Configuring 5250 Emulator
Users”. If you have not set up emulator user records for
groups of users, this line of the file is optional. If neither the
user name nor the group name is specified, 3270 or 5250 users on
the client can use the <DEFAULT>
user record, if any, in the domain configuration file. If the client will not be running 3270 or 5250 emulation,
this line of the file is not required.
- invoked_tps
The Registry data type of this value is REG_SZ. Specify one of the following values: This line is optional. If it is not specified, the default
is NO. - lan_access_timeout
The Registry data type of this value is REG_SZ. Specify the time in seconds for which the TCP/IP connection
from the client to a server should be kept active while no applications
on the client are using SNAplus2 resources. For more information,
see “LAN Access Timeout”. The valid range is 0-65535. The minimum timeout is 60
seconds (lower values are rounded up to 60 seconds). To deactivate
the TCP/IP connection more quickly, disable the client. This parameter is optional. If it is not specified, the default
is no timeout, and the TCP/IP connection is kept active as long
as the client is running. - broadcast_attempt_count
The Registry data type of this value is REG_SZ. If the client uses the broadcast method to contact a server
(specified by the * entry described
in “Servers”),
this parameter specifies the maximum number of broadcasts to be
made in one attempt to contact a server. The valid range is 1-65535. The minimum value is 1; if a higher value is specified,
the client retries every 10 seconds until it contacts a server or
until this count is reached. If the count is reached without contacting
a server, the client then attempts to contact a named server (as
described in “Servers”). This parameter is optional. If it is not specified, the default
is 5. - server_lost_timeout
The Registry data type of this value is REG_SZ. If the client loses contact with a server and needs to reconnect,
or if it has failed to contact a server using either broadcasts
or named servers (as described in “Servers”), this parameter specifies
the time in seconds for which the client waits before attempting
to contact a server. If the client has lost contact with the server,
SNAplus2 does not wait for the full timeout period, but retries
after a random period between 5 seconds and the specified timeout;
this is to avoid bursts of network traffic caused by large numbers
of clients attempting to contact a server at the same time. This parameter is optional. The valid range is 5-65535.
If it is not specified, the default is 200
(seconds). - client_start_timeout
The Registry data type of this value is REG_DWORD. Specify the time in seconds that an application waits while
the Win32 client starts and tries to contact a server. Values between
0 and 300 are valid; values outside this range are forced into the
range. The default value is 10 seconds. This parameter can be used to control events when both the
application and the Win32 client are configured to be started on
system startup (either by being in the Startup Folder or by being
an automatically started service). The application waits for the
number of seconds specified in this field, to enable the Win32 client
to get in first. In this way, the Win32 client can connect to a
server to provide the resources required by the application, before
the application fails due to the lack of those resources.
The Servers subkey contains
information about SNAplus2 servers that the client can access, as
follows: - Server1
The Registry data type of this value is REG_SZ. Enter an asterisk (*)
or a server name: To indicate that the client should
attempt to find a server running SNAplus2 by using a UDP broadcast
message to all computers on its TCP/IP subnet (or on all subnets
that it can access, if the client computer contains more than one
LAN adapter card), specify *. The client retries the broadcast every 10 seconds, up to the
number of attempts specified by the broadcast_attempt_count
parameter, until it contacts a server. If the limit specified by
broadcast_attempt_count
is reached before a server has been contacted, the client then tries
using directed messages to one or more named servers (specified
by the following lines of the file). In situations where the client cannot reach any
servers using UDP broadcasts, and must use directed messages, specify
the name of the first server it should try to contact. This applies
in the following cases: When the SNAplus2
LAN spans multiple TCP/IP subnets, and there are no SNAplus2 servers
in any TCP/IP subnet that the client can access using UDP When UDP support is not installed on the client.
In
other cases, the use of UDP broadcasts is optional; to specify that
broadcasts should not be attempted, specify the name of the first
server instead of *.
- Server2-Server10
The Registry data type of this value is REG_SZ. Specify the names of additional SNAplus2 servers that the
client should contact, in order of preference. If the client has
tried to contact a server using a UDP broadcast (or has tried to
contact the server specified in Server1),
but has received no response, it then attempts to contact the server
specified in Server2 using
a directed message. If this fails, it tries the server specified
in Server3, and so on. These server names are optional, but provide a backup mechanism
if the broadcast method of locating a server fails or if the server
specified by Server1 is
unavailable. If the client tries all the servers listed without success,
it waits for the number of seconds specified by the server_lost_timeout
parameter, then restarts the process of trying to contact a server
(either with UDP broadcasts or with the first server listed). The parameters Server2-Server10
cannot be set to * to indicate
the use of UDP broadcasts. Only the Server1
parameter can be used to indicate this, because the * value must precede any server
names in the file.
The Logging subkey specifies
logging options for the client. These options can be used to specify
client logging settings that override the logging options specified
for the domain as a whole. For more information about specifying
domain logging options, see “Configuring Logging”. If central logging is enabled, all log messages are written
to a central file on a server. In this case, only the exception_logging_enabled
and audit_logging_enabled
parameters specified here are used; the remaining parameters are
ignored. The logging options are specified as follows: - exception_logging_enabled
The Registry data type of this value is REG_SZ. Set this parameter to one of the following values: - YES
Record exception messages. - NO
Do not record exception messages.
This parameter is optional. If it is not specified, the Win32
client uses the global domain settings to determine whether exception
messages are recorded. (The initial default is that exception messages
are recorded.) - audit_logging_enabled
The Registry data type of this value is REG_SZ. Set this parameter to one of the following values: - YES
Record audit messages. - NO
Do not record audit messages.
This parameter is optional. If it is not specified, the Win32
client uses the global domain settings to determine whether audit
messages are recorded. (The initial default is that audit messages
are recorded.) - log_directory
The Registry data type of this value is REG_SZ. The full path of the directory where log files are stored
on this client. All the log files and backup log files (specified
in the following parameters) are stored in this directory. This parameter is optional. If it is not specified, the files
are stored in the Windows installation directory. - error_file
The Registry data type of this value is REG_SZ. Name of the file to which error messages are written. This
parameter is optional. If it is not specified, the default is sna.err. To log error and audit messages to a single file, specify
the same file name for both this parameter and the audit_file
parameter. - backup_error_file
The Registry data type of this value is REG_SZ. Name of the backup error log file. When the error log file
reaches the size specified in error_file_wrap_size,
SNAplus2 copies its contents to the backup file (overwriting any
existing file), then clears the error log file. This parameter is optional. If it is not specified, the default
is bak.err. To log error and audit messages to a single file, specify
the same file name for both this parameter and the backup_audit_file
parameter. - error_file_wrap_size
The Registry data type of this value is REG_DWORD. The maximum size of the log file specified by error_file.
When a message written to the file causes the file size to exceed
this limit, SNAplus2 copies the current contents of the log file
to the backup log file, then clears the log file. This means that
the maximum amount of disk space taken up by error log files is
approximately twice the value of the error_file_wrap_size
parameter. This parameter is optional. If it is not specified, the default
is 1000000 (bytes). If you
are logging error and audit messages to the same file, this parameter
must be set to the same value as the audit_file_wrap_size
parameter. - audit_file
The Registry data type of this value is REG_SZ. Name of the file to which audit messages are written. This
parameter is optional. If it is not specified, the default is sna.aud. To log error and audit messages to a single file, specify
the same file name for both this parameter and the error_file
parameter. - backup_audit_file
The Registry data type of this value is REG_SZ. Name of the backup audit log file. When the audit log file
reaches the size specified in audit_file_wrap_size,
SNAplus2 copies its contents to the backup file (overwriting any
existing file), then clears the audit log file. This parameter is optional. If it is not specified, the default
is bak.aud. To log error and audit messages to a single file, specify
the same file name for both this parameter and the backup_error_file
parameter. - audit_file_wrap_size
The Registry data type of this value is REG_DWORD. The maximum size of the log file specified by audit_file.
When a message written to the file causes the file size to exceed
this limit, SNAplus2 copies the current contents of the log file
to the backup log file and clears the log file. This means that
the maximum amount of disk space taken up by audit log files is
approximately twice the value of the audit_file_wrap_size
parameter. This parameter is optional. If it is not specified, the default
is 1000000 (bytes). If you
are logging error and audit messages to the same file, this parameter
must be set to the same value as the error_file_wrap_size
parameter. - succinct_errors
The Registry data type of this value is REG_SZ. Specifies whether to use succinct logging or verbose logging
in the error log file. This setting applies to both exception logs
and problem logs. You can specify either of the following values: - YES
Use succinct logging: each message in the log file
contains a summary of the message header information (such as the
message number and log type) and the message text string and parameters.
To obtain more details of the cause of the log and any action required,
you can use the snaphelp utility
on a computer running HP-UX. - NO
Use verbose logging: each message in the log file
includes a full listing of the message header information, the message
text string and parameters, and additional information on the cause
of the log and any action required.
This parameter is optional. If it is not specified, the default
is taken from the previous set_global_log_type
command issued to the master server (or set using the Motif administration
program). The initial default, before any set_global_log_type
command has been issued, is to use succinct logging. If you are using central logging, the choice of succinct or
verbose logging for messages from all computers is determined by
the setting of this parameter on the server acting as the central
logger; this setting may either be from the set_global_log_type
command, or from a set_log_type
command issued to that server to override the default. - succinct_audits
The Registry data type of this value is REG_SZ. Specifies whether to use succinct logging or verbose logging
in the audit log file. The permitted values and their meanings are
the same as for the succinct_errors
parameter.
The API_tracing subkey
specifies API tracing options for applications running on the client.
For more information about tracing, refer to HP-UX SNAplus2
Diagnostics Guide. The tracing options are specified
as follows: - file1
The Registry data type of this value is REG_SZ. The full path name of the trace file, or of the first trace
file if tracing is to two files (see the description of the file2
parameter). This parameter is required if you want to enable API tracing. - file2
The Registry data type of this value is REG_SZ. The full path name of the second trace file. This parameter
is optional; to indicate that tracing is to one file instead of
two files, do not include this line. If both file1 and
file2 are specified, tracing
is to two files. When the first file reaches the size specified
by the flip_size parameter,
the second file is cleared, and tracing continues to the second
file. When this file then reaches the size specified by flip_size,
the first file is cleared, and tracing continues to the first file.
This ensures that tracing can continue for long periods without
using excessive disk space; the maximum space required is approximately
twice the value of the flip_size
parameter. - flip_size
The Registry data type of this value is REG_DWORD. The maximum size of the trace file. If two file names are
specified, tracing switches between the two files when the current
file reaches this size. If only one file name is specified, this
parameter is ignored; the file size is not limited. This parameter is optional. If it is not specified, the default
is 1000000 (bytes). - truncation_length
The Registry data type of this value is REG_DWORD. The maximum length, in bytes, of the information written to
the trace file for each message. If a message is longer than this,
SNAplus2 writes only the start of the message to the trace file,
and discards the data beyond truncation_length.
This enables you to record the most important information for each
message but avoid filling up the file with long messages. This parameter is optional. If it is not specified, SNAplus2
does not truncate messages (all the data from each message is written
to the file). - all_api
The Registry data type of this value is REG_SZ. To trace messages for all APIs, set this parameter to YES. In this case, SNAplus2 ignores
the parameters from appc
through nof. To disable tracing for all APIs, set all_api
and all of the parameters from appc
through nof to NO. To trace only messages for specific APIs, set all_api
to NO, and use the parameters
from appc through nof
to indicate which APIs to trace. This parameter is optional. If it is not specified, the default
is NO. - appc
The Registry data type of this value is REG_SZ. To trace APPC API messages, set this parameter to YES; otherwise, set it to NO. This parameter is optional. If it is not specified, the default
is NO. If the all_api
parameter is set to YES, this
parameter is ignored, and APPC messages are traced. - cpic
The Registry data type of this value is REG_SZ. To trace CPI-C API messages, set this parameter to YES; otherwise, set it to NO. This parameter is optional. If it is not specified, the default
is NO. If the all_api
parameter is set to YES, this
parameter is ignored, and CPI-C messages are traced. - csv
The Registry data type of this value is REG_SZ. To trace CSV API messages, set this parameter to YES; otherwise, set it to NO. This parameter is optional. If it is not specified, the default
is NO. If the all_api
parameter is set to YES, this
parameter is ignored, and CSV messages are traced. - rui
The Registry data type of this value is REG_SZ. To trace LUA RUI messages, set this parameter to YES; otherwise, set it to NO. This parameter is optional. If it is not specified, the default
is NO. If the all_api
parameter is set to YES, this
parameter is ignored, and LUA RUI messages are traced. - nof
The Registry data type of this value is REG_SZ. To trace NOF API messages, set this parameter to YES; otherwise, set it to NO. NOF messages are not used directly
by applications on Win32 clients, but are used internally by SNAplus2
components in obtaining configuration information. This parameter is optional. If it is not specified, the default
is NO. If the all_api
parameter is set to YES, this
parameter is ignored, and NOF messages are traced. - ms
The Registry data type of this value is REG_SZ. To trace MS API messages, set this parameter to YES; otherwise, set it to NO. This parameter is optional. If it is not specified, the default
is NO. If the all_api
parameter is set to YES, this
parameter is ignored, and MS messages are traced.
The MSG_tracing subkey
specifies options for tracing on Win32 client 3270 emulation programs.
For more information about tracing, refer to HP-UX SNAplus2
Diagnostics Guide. The tracing options are specified
as follows: - file1
The Registry data type of this value is REG_SZ. The full path name of the trace file, or of the first trace
file if tracing is to two files (see the description of the file2
parameter). This parameter is required if you want to enable message tracing;
you also need to set the fmi
parameter. - file2
The Registry data type of this value is REG_SZ. The full path name of the second trace file. This parameter
is optional. To indicate that tracing is to one file instead of
two files, do not include this line. If both file1 and
file2 are specified, tracing
is to two files. When the first file reaches the size specified
by flip_size, the second
file is cleared, and tracing continues to the second file. When
this file then reaches the size specified by flip_size,
the first file is cleared, and tracing continues to the first file.
This ensures that tracing can continue for long periods without
using excessive disk space; the maximum space required is approximately
twice the value of the flip_size
parameter. - flip_size
The Registry data type of this value is REG_DWORD. The maximum size of the trace file. If two file names are
specified, tracing switches between the two files when the current
file reaches this size. If only one file name is specified, this
parameter is ignored; the file size is not limited. This parameter is optional. If it is not specified, the default
is 1000000 (bytes). - truncation_length
The Registry data type of this value is REG_DWORD. The maximum length, in bytes, of the information written to
the trace file for each message. If a message is longer than this,
SNAplus2 writes only the start of the message to the trace file,
and discards the data beyond truncation_length.
This enables you to record the most important information for each
message but avoid filling up the file with long messages. This parameter is optional. If it is not specified, SNAplus2
does not truncate messages (all the data from each message is written
to the file). - fmi
The Registry data type of this value is REG_SZ. To trace 3270 messages, set this parameter to YES; otherwise, set it to NO. This parameter is optional.
If it is not specified, the default is NO.
The CS_tracing subkey
specifies options for client/server tracing (tracing on messages
between the client and SNAplus2 servers). For more information about
tracing, refer to HP-UX SNAplus2 Diagnostics Guide.
The tracing options are specified as follows: - file1
The Registry data type of this value is REG_SZ. The full path name of the trace file, or of the first trace
file if tracing is to two files (see the description of the file2
parameter). This parameter is required if you want to enable client/server
tracing; you also need to set the trace_flags
parameter. - file2
The Registry data type of this value is REG_SZ. The full path name of the second trace file. This parameter
is optional; to indicate that tracing is to one file instead of
two files, do not include this line. If both file1 and
file2 are specified, tracing
is to two files. When the first file reaches the size specified
by the flip_size parameter,
the second file is cleared, and tracing continues to the second
file. When this file then reaches the size specified by flip_size,
the first file is cleared, and tracing continues to the first file.
This ensures that tracing can continue for long periods without
using excessive disk space; the maximum space required is approximately
twice the value of the flip_size
parameter. - flip_size
The Registry data type of this value is REG_DWORD. The maximum size of the trace file. If two file names are
specified, tracing switches between the two files when the current
file reaches this size. If only one file name is specified, this
parameter is ignored; the file size is not limited. This parameter is optional. If it is not specified, the default
is 1000000 (bytes). - admin_msg
The Registry data type of this value is REG_SZ. To trace internal messages relating to client/server topology,
set this parameter to YES;
otherwise, set it to NO. This parameter is optional. If it is not specified, the default
is NO. - datagram
The Registry data type of this value is REG_SZ. To trace datagram messages, set this parameter to YES; otherwise, set it to NO. This parameter is optional. If it is not specified, the default
is NO. - data
The Registry data type of this value is REG_SZ. To trace data messages, set this parameter to YES; otherwise, set it to NO. This parameter is optional. If it is not specified, the default
is NO. - send
The Registry data type of this value is REG_SZ. To trace all data messages sent from the client to the server,
set this parameter to YES;
otherwise, set it to NO. This parameter is optional. If it is not specified, the default
is NO. - receive
The Registry data type of this value is REG_SZ. To trace all data messages received by the client from the
server, set this parameter to YES;
otherwise, set it to NO. This parameter is optional. If it is not specified, the default
is NO.
The Appl_Name
subkey specifies options for a CPI-C application. To set these options
for one or more applications, include a section in this format for
each application, and replace the Appl_Name
variable with the application program's executable name (not including
the .exe file name extension). For more information about CPI-C, refer to HP-UX
SNAplus2 CPI-C Programmers Guide. The options are specified as follows: - APPCLLU
The Registry data type of this value is REG_SZ. The name of the local LU that this application uses. This parameter is optional. If it is not specified, the application
attempts to use the default LU (the LU associated with a local node's
control point). - APPCTPN
The Registry data type of this value is REG_SZ. The TP name of the application. This name is used in log and
trace files to identify the application. For an invoked application
(one that issues Accept_Conversation), it is also used to match
the TP name on an incoming Allocate request with the correct application;
the invoked application can also use the Specify_Local_TP_Name call
to specify additional names to be matched with incoming Allocate
requests. This parameter is optional. If it is not specified, the default
is CPIC_DEFAULT_TPNAME.
The CSV_data subkey specifies
options for applications that use the CSV interface. It applies
only to applications that use the CONVERT verb to perform character
conversion with a user-defined conversion table (Table G). For more
information about the CONVERT
verb, refer to HP-UX SNAplus2 CSV Programmers Guide. If no applications on the client use this function, you do
not need to include this section. The only option in this section is as follows: - CSVTBLG
The Registry data type of this value is REG_SZ. The full path name of the file containing the user-defined
Table G conversion table. This parameter is required if CSV applications
need to perform Table G character conversion (there is no default);
otherwise it is optional.
|
Printable version
