Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

PI Interface for Universal File and Stream Loading UFL

[SETTING] section

  • Last UpdatedNov 16, 2022
  • 2 minute read

Operational settings

This section specifies various operational and debugging settings.

Operational and debug settings

Setting

Description

DEB

Debug level. The interface maintains its own log file, where it redirects all errors, debug, and informational messages. See the description of the OUTPUT keyword below.

The higher the debug level (0-6) the more detailed is the printout. For more information about debug levels see the Debugging levels section below.

Example: DEB = 4

LOCALE

Specifies how the interface transforms the string representation of numbers to the native numeric form; that is, which locale it uses. The default Locale is English – United States. Different decimal separators can be handled. The list of all locale codes can be found at the Microsoft Developer Network site.

You can specify locale using the long form, short form, or numeric identifier (LCID).

Examples:

  • LOCALE = "German – Germany"

  • LOCALE = "de-de"

  • LOCALE = 1031

MAXLOG

The circular buffer grows from 1 to the specified value and the interface starts overwriting the oldest log files when the value for MAXLOG has been reached.

Default value is 10. If a negative value or zero is specified, MAXLOG is set to default value.

Example: MAXLOG = 15

MAXLOGSIZE

Maximum size of a log file in MB. When a log file reaches the specified size, the interface creates a new log file. Default is 20 MB.

Example: MAXLOGSIZE = 5

MSGINERROR

Specify the path and filename for the log file containing lines that were not successfully processed.

Example: MSGINERROR = c:\ufl_logs\errors.txt

OUTPUT

Specify the path and filename for the interface log file, which contains debugging output. Each time the interface starts, it appends a version number to any existing log and creates a new one. If you omit this option, errors are logged in the message log.

Example: OUTPUT = c:\ufl_logs\PI_UFL.log

Debugging levels

Higher levels include the information from lower levels.

Debug levels

Debug Level

Logged Output

0

No debug output. Default debug level.

1

Tasks that are normally performed once, such as startup messages, shutdown messages, and points added to the interface cache.

2

More detail than level 1.

3

Include raw data.

4

Include data about to be sent to Data Archive.

5

Include read scan cycles start and end time, interface internal cache refresh cycles starts and ends times, etc.

6

Log lines read from input before processing.

Note: For typical operation, choose level 0 or 1, because higher levels can increase log file size significantly.

In This Topic
TitleResults for “How to create a CRG?”Also Available in