CORBA 2.6 Programmer's Guide for Java

defaults for these values by using the Console, or by editing the default@ORB entity using the cfgmgt
tool.
log_file {EMS-process-name | STDCOLL | STDOUT | STDERR |
oss-file-name}
Default is STDCOLL.
trace_file {file-name | STDOUT | STDERR}
Default is STDOUT.
max_threads number
The maximum number of servant threads available in a process. Default is 4097. The effective
maximum number of threads in a server depends on the size of each thread's stack and the number
of NSK threads available in a CPU.
nsdom_ir file-name
Default is $NSD_ROOT/etc/nsdom.ir.
giop_version version
Allows you to select the ORB giop version for both the client and server directions. The key
values are 1.0, 1.1, and 1.2. The default is version 1.2. The key sets the ORBs GIOP version.
IORs generated by this ORB will have this version and GIOP requests will have a version that is
the minimum of this version and the remote IOR's version.
allow_wchar_wstring_in_1_0 {true | false}
Controls whether wchar and wstring are enabled over GIOP 1.0. The key is
allow_wchar_wstring_in_1_0, and the key value is true or false. The default is false.
Since the default is false, you must set this configuration value if you want NonStop CORBA 2.6
to allow wchar and wstring to be transmitted over GIOP 1.0. Many vendors, including NonStop
CORBA 2.3 B13, allow wchar and wstring to be transmitted over GIOP 1.0. NonStop CORBA 2.6
also allows wchar and wstring to be transmitted over GIOP 1.0. If the
allow_wchar_wstring_in_1_0 key value is set to false, marshalling exceptions are thrown
if GIOP 1.0 is in effect. If the allow_wchar_wstring_in_1_0 key value is set to true,
marshalling exceptions are not thrown if GIOP 1.0 is in effect.
wchar_native_code_set code set
Controls whether the C10 C++ ORB publishes UCS-2 or UTF-16 as its wide character native code
set. The key is wchar_native_code_set, and the key value is UCS-2 or UTF-16. The
default is UCS-2. Interoperation with IONA E2A ASP 5.1 (or any other ORB that implements
UCS-2 incorrectly) is the only reason to use UTF-16. IONA has fixed their handling of wstring
endian-ness in ASP 6.0, so UTF-16 is only required for ASP 5.x.
Chapter 1. Introduction to NonStop
CORBA Programming
Chapter 3. Compiling and Building an
Application