umask value
to use when creating output files, such as the output files from jobs.
The umask value must be numeric. If
not set, the shell's umask value
is used. Example: default_umask = 002.
DefaultAuth value
is used.
true,
the set of credentials associated with the current domain is searched
to find a set that is usable by the given authenticated user. If multiple
credentials are found, the first complete set is used.
iom://<host>:<port>,
where <host> is the name of the computer executing the authentication
server and <port> is the port to contact the authentication
server. If the authenticating server is a DataFlux Authentication
Server, then the port should be specified as 21030 unless the default
server has been changed.
BASE/AUTH_SERVER_LOC=c:\SAS\Config\Lev1\metadataConfig.xml The
example includes the default name and location of the metadata cluster
profile.
YES to
enable single-sign-on connections to the SAS Metadata Server from
DataFlux Data Management Studio. Add this option to a user's
app.cfg file or the default app.cfg file for DataFlux Data Management
Studio. Do not set this option in the configuration files for DataFlux
Data Management Servers.
true (value
of 1), it indicates that the application
is using the dmstudio process (not processes started by the application,
like batch.cfg, for example). The user should not adjust or override
this value.
iso8601 and iso8601_no_milli.
The later does not include the millisecond portion of the ISO8601
standard.
etc directory.
off.
This must be set before starting the application of interest, because
this setting is read only at start-up.
1 or a combination of letters
where: M = do not show module info, V = turn verbose on, U = install
the Unhandled Exception Filter, C = install the continue Exception
Filter, and f = do not install the first chance exception filter.
Setting it to 1 shows all the information.
etc subfolder of the
installation folder.
0 (or
not specified) for normal messages or 1,
which includes source file and line number in messages.
-1),
then node statistics are logged only when the job has finished executing.
-1 disables
events from client.
true, the temporary data
file honors the variable-width record indicator at temporary data
file creation time. When the value is set to false (default),
the temporary data file sort support converts a variable-width file
to a fixed-width file, if the record does not contain any string fields,
or if the lengths of the string fields in a record are within the
overhead threshold necessary to sort variable-width records. Set to true to
mimic behavior prior to the 2.4 release.
DFEXEC_HOME/share/liti.
GMT and LOCAL,
which is the default. If this is set to GMT, the current date returns
in GMT instead of the localized time. This affects anything that uses
the current date timestamp.
True to
indicate that the SAS sort is to be used. If not specified or set
to False, then the DataFlux Data Management
sort is used.
yes, 1,
or true, this setting disables the
listing of the SYSCAT type DSNs into DSNs that are on that server.
off.
Any value turns it on.
core/sasext directory
off of the executable directory.
DFEXEC_HOME/etc/dftkdsn.
DFEXEC_HOME/etc/dsn.
directory/DataFlux/dac/9.0.
1000.
This affects row-logging events, as well as historic custom and standard
metrics. This value can be changed to enhance the performance of jobs
that monitor business rules when those jobs include row-logging events.
0 (not debug
mode) or 1 (debug mode). The default
is 0.
-1 retries
until a connection is established.
-1 (frequency
distribution engine default).
128kb.
NO.
The default behavior is for these definitions to fail to load. Results
obtained when this option is turned on are undefined.
dfpower82, unity21, unity22,
or dmp21 through dmp26.
If not specified, it defaults to the latest version. You can use this
option if you want to use the latest version of DataFlux Data Management
Studio, but want the outputs of your QKB-related Data Job nodes (for
example, matchcodes) to be exactly the same as the outputs for earlier
versions.
YES.
The application start-up creates a QKB pool that sets the option for
all consumers (Profile, Explorer, and Nodes) with the exception of
the Expression Engine, which has its own initialization. Set this
option to No to find errors within
definitions and to see error messages specific to Pattern Logic nodes.
NO.
0 (target), 1 (Source
and Target), and 2 (All). This determines
whether data flow nodes should automatically fill their pass-through
list from their parent nodes.
ALL.
300000.
Larger values allow for more referenced data to be cached, which
can improve performance. However, this also increases the amount of
memory your process attempts to consume. If you encounter out-of-memory
errors, try lowering this value.
0. It resides
in macros/ncoa.cfg.
ALL or
an empty string. Using ALL requires
a large amount of memory. It resides in macros/ncoa.cfg.
Name (Address Update), and
it resides in macros/ncoa.cfg.
0 (Guess), 1 (ODBC),
or 2 (DFTK). If the value is 0,
the node attempts to determine the type from the connection string.
This is typically set by the Address Update Administration utility
and resides in the app.cfg.
CASS/DPV/etc data.
It resides in macros/ncoa.cfg.
C:\Program Files\DataFlux\dfIntelliServer\etc\dfclient.cfg.
Modify the dfclient.cfg file to point to the server and port.
zero or not is
specified, no limit exists for concurrent child launches.
no time-out.
0.
This is a puddle option.
0 (never
terminate it).
0,
the number of concurrent pooled processes is unlimited. Default is
unlimited after 2.2 (previously was 10).
If POOLING/GET_PROCESS_TIMEOUT is set, it waits for that amount of
time to get a new process if it needs one.
0 (unlimited).
installationdir/etc/udf.
foundations/master_data to be overwritten
by the user when putting the contents of [INSTALL_ROOT]/share/mdm into
a repository.