Explanation of fields of System Environment Settings

This section explains each field of the System Environment Settings.

Identification information definition

Local Host Name (MyHostName)

<<Alphanumeric characters within 44 bytes>>

Specify the local host name of the local HULFT-HUB Server instance. This field is used for output to the HULFT-HUB Manager screen or log.

In a clustering environment, specify the virtual host name.

Note

• If you change the local host name, the position information and host information retained in the HULFT-HUB Manager Management screen become unavailable. Therefore, the icon in the Structure Diagram at login will not be displayed in the previous position. Additionally, if you change the local host name while a connection is being established, reconnection will not be able to be performed. When you change the local host name, see the explanation of definitions related to the local host in the HULFT-HUB Manual or the HULFT-HUB Integration Management Manual.

• Specify the host name in alphanumeric characters only. Certain symbols can be used due to compatibility with lower versions, yet the operation under such settings is not guaranteed.

Service Name (ServiceName)

<<Alphanumeric characters within 100 bytes>>

Specify the service name of the local HULFT-HUB Server instance. This field is used for identification when HULFT-HUB Server or HULFT other than the local HULFT-HUB Server instance is running on the same host. You do not need to set this field when only the local HULFT-HUB Server instance is running on the same host.

Note

• If you change the service name, the position information and host information retained in the HULFT-HUB Manager Management screen become unavailable. Therefore, the icon in the Structure Diagram at login will not be displayed in the previous position. Additionally, if you change the local host name while a connection is being established, reconnection will not be able to be performed. When you change the service name, see the explanation of the definition related to the service name in the HULFT-HUB Manual or the HULFT-HUB Integration Management Manual.

• Note that only when Notification Host Name for Transfer via HUB is set to 'Format with Port No.', a HULFT or HULFT-HUB Server instance on the same host can be identified by service names. If 'Notification Host Name for Transfer via HUB' is set to 'Format with Port No. for Controlled Clients Only' or 'Format without Port No.', it is not allowed that multiple instances of HULFT or HULFT-HUB Server coexist on the same host.

Alias (DispName)

<<Full-width characters except external characters within 256 bytes>>

This set value is displayed in the HULFT-HUB Manager screen and others.

The value of Local Host Name (MyHostName) is set at a new installation. We recommend that you add a unique name in the controlled HULFT-HUB system to easily identify each instance of HULFT-HUB Server represented by local-host-name + service-name.

An external character is a double byte code other than JIS Level 1 and Level 2.

Note

If Kanji Code Type is not 'SJIS', the number of written characters might exceed 256 bytes and you might not be able to store them in a file.

Code-related definition

Kanji Code Type (KnjCode)

<<SJIS or EUC or UTF8>>

This field specifies the Kanji code of the system. Only 'SJIS' can be specified when the server OS is Windows.

SJIS:

Shift JIS code system

EUC:

EUC code system

UTF8:

UTF-8 code system

JIS Year (JISType)

<<78 or 83>>

If Kanji Code Type is 'SJIS', you need to specify JIS Year.

78:

78 year JIS

83:

83 year JIS

Communication-related definition

Port No. (HubPortNo)

<<1 to 65535>>

Specify the port number of HULFT-HUB Server.

Make sure the port number does not overlap with the port number reserved by the operating system or used by other application programs.

Connect Retry Count (SocketRetryMax)

<<0 to 9999 (times)>>

Specify the retry count of connection establishment. When '0' is set, reconnection is not carried out.

This field is only effective for HULFT-HUB Server for UNIX/Linux-ENT.

Note

If Communication of Transfer Conditions that is set for each ID in the Transfer Information screen is 'Defer to System Setting', the value of this field applies to the Connect Retry Count of Transfer Conditions.

If Communication is 'User Settings', changing the value of this field does not change the set value of Connect Retry Count of Transfer Conditions. Change the value if necessary. For details about how to edit Transfer Conditions, see the HULFT-HUB Manager Help.

Connect Retry Interval (SocketRetryInterval)

<<0 to 9999 (sec)>>

Specify the execution interval of retry processing for connection establishment.

This field is only effective for HULFT-HUB Server for UNIX/Linux-ENT.

Note

If Communication of Transfer Conditions that is set for each ID in the Transfer Information screen is 'Defer to System Setting', the value of this field applies to the Connect Retry Interval of Transfer Conditions.

If Communication is 'User Settings', changing the value of this field does not change the set value of Connect Retry Interval of Transfer Conditions. Change the value if necessary. For details about how to edit Transfer Conditions, see the HULFT-HUB Manager Help.

Socket Timeout (SocketTimer)

<<0 or 10 to 259200 (sec)>>

Specify the time-out value to be used for no-communication monitoring after connection has been established.

0:

Wait without limit until a response is returned.

10 to 259200:

Wait for a response for the specified time.

Note

If Communication of Transfer Conditions that is set for each ID in the Transfer Information screen is 'Defer to System Setting', the value of this field applies to the Socket Timeout of Transfer Conditions.

If Communication is 'User Settings', changing the value of this field does not change the set value of Socket Timeout of Transfer Conditions. Change the value if necessary. For details about how to edit Transfer Conditions, see the HULFT-HUB Manager Help.

Client Monitor Activities Response Timeout (AliveResponseTimer)

<<1 to 259200 (sec)>>

Specify the timeout value to be used when client activities are monitored from HULFT-HUB Manager in seconds.

Multiplex level definition

Transfer Processing Multiplex Level (TransRlyMax)

<<1 to 99999>>

Specify the maximum number of "transfer processing (total of relay, multicasting, and delivering)" that can be simultaneously executed.

This field is only effective for HULFT-HUB Server for UNIX/Linux-ENT.

Request Acknowledge Processing Multiplex Level (ReqRlyMax)

<<1 to 99999>>

Specify the maximum number of processing relaying requests to the Request Acknowledge system that can be simultaneously executed.

This field is only effective for HULFT-HUB Server for UNIX/Linux-ENT.

Manager Relay Multiplex Level (MgrRlyMax)

<<1 to 99999>>

Specify the maximum number of 'Managerrelays (processing that relays requests from HULFT-HUB Manager to other servers)' that can be simultaneously executed.

This field is only effective for HULFT-HUB Server for UNIX/Linux-ENT.

Simultaneous Manager Connection Count (MgrConnMax)

<<0 or 1 to 9999>>

Specify the number of HULFT-HUB Manager users that can be simultaneously connected to HULFT-HUB Server.

0:

No limit

1 to 9999:

Up to the specified number of users can log in

Simultaneous Manager Connection Request Count (MgrProcMax)

<<0 or 5 to 256>>

Specify the maximum number of 'Managerprocessing (processing that handles requests from HULFT-HUB Manager on the local server and makes a response)' that can be simultaneously executed. If 'Simultaneous Manager Connection Count' is equal to '0', specifying this field has no meaning (this field is '0').

0:

No limit

5 to 256:

Simultaneous execution is available within the specified number of processes.

Total Job Flow Multiplex Level (JFProcMax)

<<1 to 99>>

Specify the maximum number of 'job flow processing' processes that can be executed at a time.

This field is only effective for HULFT-HUB Server for UNIX/Linux-ENT.

Directory definition

Management Information Storage Directory (CurrentDBDir)

<<Within 128 bytes>>

Specify the storage directory for the server management information related to HULFT-HUB Server and the client management information related to clients in absolute path. If the specified directory does not exist, HULFT-HUB Server does not start.

System Status Storage Directory (MMapDir)

<<Within 128 bytes>>

Specify the storage directory for temporary files storing information such as the transfer status and operation status of HULFT-HUB Server in absolute path. If the specified directory does not exist, HULFT-HUB Server does not start.

Accumulated Data Storage Directory (AccumulateRootDir)

<<Within 128 bytes>>

Specify the storage root directory to be used when HULFT-HUB Server accumulates transfer data in absolute path. If the specified directory does not exist, HULFT-HUB Server does not start.

This field is only effective for HULFT-HUB Server for UNIX/Linux-ENT.

Management Information Backup Storage Directory (BackupDBDir)

<<Within 128 bytes>>

Specify the management information backup storage directory in absolute path. If the specified directory does not exist, HULFT-HUB Server does not start.

Transfer Log File CSV Save Directory (TrnlogCSVHoldDir)

<<Within 128 bytes>>

Specify the storage directory for storing the CSV-format Transfer Log in absolute path. If the specified directory does not exist, HULFT-HUB Server does not start.

Accumulated Data Extraction Work Directory (AccumulateWorkDir)

<<Within 128 bytes>>

Specify the directory to be used when extracting the accumulated data in the job flow function in absolute path. If the specified directory does not exist, HULFT-HUB Server does not start.

This field is only effective for HULFT-HUB Server for UNIX/Linux-ENT.

DataMagic Installation Directory (DataMagicBinDir)

<<Within 128 bytes>>

Specify the directory to which DataMagic is installed as an absolute path. Specify this field when you want to call HULFT-DataMagic in the job flow.

This field is only effective for HULFT-HUB Server for UNIX/Linux-ENT.

DataMagic Environment Settings Directory (DataMagicEtcDir)

<<Within 128 bytes>>

Specify the directory to which the settings file for DataMagic is stored as an absolute path. Specify this field when you want to call HULFT-DataMagic in the job flow.

This field is only effective for HULFT-HUB Server for UNIX/Linux-ENT.

Transfer conditions definition

When Multicasting is Unsuccessful (MulticastError)

<<C or S>>

Specify the treatment of Send processing to the other transfer-destination hosts when an error occurs in transfer to some transfer-destination hosts during multicasting.

This field is only effective for HULFT-HUB Server for UNIX/Linux-ENT.

C:

Continue

S:

Stop Immediately

Criterion for Unsuccessful Multicasting (MulticastErrorCondition)

<<0 or 1>>

Specify the error condition when the sending client is notified of the result of multicasting. If you specify 'S' for the field When Multicasting is Unsuccessful (MulticastError), this field is not used.

This field is only effective for HULFT-HUB Server for UNIX/Linux-ENT.

0:

Error when all transfers ended unsuccessfully

1:

Error when some transfers ended unsuccessfully

Compression Type Selection (CompSelect)

<<C or N>>

Specify the compression type to be used if the receiving host does not support the compression type specified on the sending host.

C:

Common

The compression type of the highest compression efficiency that is compatible with both the sending side and receiving side is used

The supported types in order of compression efficiency are as follows:

Zstandard > DEFLATE > None

Example: If the compression type specified on the sending side is 'Zstandard' and the compression type with the highest compression efficiency that can be specified on the receiving side is 'DEFLATE', 'DEFLATE' is used for transfers.

N:

None

If the receiving side does not support the compression type specified on the sending side, no compression is used

Log information definition

Transfer Log Storage Threshold (TrnlogThreshold)

<<0 or 1 to 999999 (records)>>

If the number of the Transfer Log records exceeds the value of this field, the Transfer Log records for Number of Transfer Log Records Kept Undeleted (TrnlogHoldCount) remain and older log records are automatically deleted.

0:

Automatic deletion is not performed (Accumulated without limit).

1 to 999999:

Automatic deletion is performed according to the specified value.

Number of Transfer Log Records Kept Undeleted (TrnlogHoldCount)

<<Less than TrnlogThreshold>>

If the number of the Transfer Log records exceeds the Transfer Log Storage Threshold (TrnlogThreshold), the Transfer Log records for the value of this field remain and older log records are automatically deleted. If the value for the field Transfer Log Storage Threshold (TrnlogThreshold) is '0', this field is not used even if it is specified (0 records).

Note

If it is detected that the number of the Transfer Log records exceeds the threshold value, older log records beyond the value specified in Number of Transfer Log Records Kept Undeleted are deleted and then new log records are added.

Number of Months to Save Transfer Log as CSV Files (TrnlogCSVHoldCount)

<<0 or 1 to 99 (months)>>

Specify the number of months to retain the files when you save the Transfer Log in CSV format.

0:

Do Not Save

1 to 99:

Save according to the specified value.

Job Flow Log Storage Threshold (JFlogHold)

<<0 or 1 to 999999 (records)>>

If the number of job flow log records exceeds the specified value, the results for Number of Job Flow Log Records Kept Undeleted (JFlogHoldCount) remain and older results are automatically deleted.

This field is only effective for HULFT-HUB Server for UNIX/Linux-ENT.

0:

Automatic deletion is not performed (Accumulated without limit).

1 to 999999:

Automatic deletion is performed according to the specified value.

Number of Job Flow Log Records Kept Undeleted (JFlogHoldCount)

<<JFlogHold-1 (records) or less>>

If the number of job flow log records exceeds the threshold value defined by JFlogHold, the job flow log records for the value of this field remain and older log records are automatically deleted. If the value for the field Job Flow Log Storage Threshold (JFlogHold) is '0', this field is not used even if it is specified (0 records).

This field is only effective for HULFT-HUB Server for UNIX/Linux-ENT.

Note

If it is detected that the number of the job flow log records exceeds the threshold value, older log records beyond the value specified in Number of Job Flow Log Records Kept Undeleted are deleted and then new log records are added.

Transfer Error Resolution Determination Condition (TrnErrorRecoveryCheckType)

<<0 or 1>>

Select the transfer error resolution (the server is automatically changed to normal display in the Structure Diagram) mode.

0:

No Transfer Error

1:

No Delivery Error

Security definition

Min. Number of Characters for User ID (UserIDMinLength)

<<3 to 32 (bytes)>>

Specify the minimum number of characters for user ID. When you register a user from HULFT-HUB Manager, a user ID less than the value of this field cannot be registered.

Min. Number of Characters for Password (PasswordMinLength)

<<8 to 32 (bytes)>>

Specify the minimum number of characters for the password. When you register a user from HULFT-HUB Manager, a password with fewer characters than the value of this field cannot be registered.

Inter-HUB Server Encryption Type (CipherTypeNeighbor)

<<0 or 1 or 2 or 3>>

Specify whether to encrypt messages sent to neighboring servers.

This field is only effective for HULFT-HUB Server for UNIX/Linux-ENT.

0:

No Encryption

1:

HULFT Encryption Scheme

2:

C4S Priority

3:

AES Priority

Accumulation-Related File Deletion Mode (AccumulateFileDelete)

<<0 or 1>>

Specify whether to make the accumulated files unrecoverable once deleted.

0:

Normal mode

The accumulated files are deleted using the conventional method

1:

Unrecoverable mode

The accumulated files are made unrecoverable once deleted

Regular startup definition

Client Activity Monitoring Interval (HealthCheckInterval)

<<0 or 10 to 86400 (sec)>>

Specify the interval at which the activity of Registered Clients is monitored.

0:

Regular activity monitoring is not performed.

10 to 86400:

The activity of Registered Clients is monitored at the specified interval.

Management Information Backup Interval (BackupInterval)

<<0 or 1 to 99 (days)>>

Specify the interval at which the management information is regularly backed up.

0:

Regular backup is not performed.

1 to 99:

Backup is performed at the specified interval.

Management Information Backup Start Time (BackupTime)

<<0000 to 2359 (hour and minute)>>

Specify the time to regularly back up the management information. For example, if you want to specify 20:15 for the startup time, specify 2015.

Management Information Backup Target (BackupTarget)

<<0 or 1 or 2 or 3>>

Specify the management information to be backed up and the backup conditions.

0:

Back up All Only When Updated

The updated data of all the management information(*) is backed up.

1:

Always Back up All

All of the management information(*) is backed up regardless of whether it is updated.

2:

Back up Partially Only When Updated
Only the updated part of the management information(*) is backed up.

3:

Always Back up Partially

Only part of the management information(*) is backed up regardless of whether it is updated.

*:

For details about the range indicated by 'all the management information' or 'part of the management information', see Table 3.37 Management information to be backed up in Management Information Backup utility. 'Specifying -a' corresponds to 'all the management information' and 'omitting -a' corresponds to 'part of the management information'.

Management Information Backup Generation File Count (BackupCount)

<<0 or 1 to 99 (generations)>>

This field indicates the generation file count to retain for the backed up management information. If the number of the backed up management information files exceeds the specified value, the oldest retained backup file is deleted.

0:

Automatic deletion is not performed (accumulated without limit).

1 to 99:

Backup files with the specified generation file count are retained.

Transfer Log CSV File Output Execution Time (TrnlogCSVExecuteTime)

<<0000 to 2359 (hour and minute)>>

Specify the time to perform the save if you save the Transfer Log in CSV format. For example, if you want to specify 20:15 for the startup time, specify 2015.

Direct Transfer Log Batch Processing Interval (HubhistoryInterval)

<<0 or 5 to 1440 (min)>>

Specify the interval at which the batch processing for collecting log records of Direct Transfer processes starts.

0:

Batch processing is not regularly started.

5 to 1440:

Batch processing for collecting log records of Direct Transfer processes starts at the specified interval.

Neighboring HUB Server Activity Monitoring Interval (ServerAliveInterval)

<<0 or 180 to 86400 (sec)>>

Specify the interval at which the activity of neighboring server is monitored.

0:

Regular activity monitoring is not performed.

180 to 86400:

The activity of neighboring server is monitored at the specified interval.

Note

• If regular activity monitoring is not performed, a file might not be transferred via a neighboring server or a request might not be issued properly.

• Even if you set a value other than '0' in Neighboring HUB Server Activity Monitoring Interval (ServerAliveInterval), servers for which you specify 'No' for Operation Monitoring in Neighboring Server Information are not monitored.

Operation status output

Trace File Name (TraceFile)

<<Within 255 bytes>>

Specify the trace file name by using a full path. If you specify '0000000000000000' for the field Trace Acquisition Mode (TraceMode), this field is not used.

Trace File Max. Size (TraceMaxSize)

<<0 or 1 to 1024 (MB)>>

Specify the maximum size of the trace file. If the size of the trace file exceeds the value of this field, the existing trace file is backed up and a new one is created. The backup file name is created by adding '.bk' to Trace File Name (TraceFile).

0:

Automatic backup and re-creation are not performed (accumulated without limit).

1 to 1024:

Automatic backup and re-creation are performed according to the specified value.

Trace Acquisition Mode (TraceMode)

<<0 or 1 or 2 or 3 or 4>>

Specify the level of messages that are output to the trace file for each daemon or program. Specify the message level according to the specification method.

[Message Level]

There are five types of levels as follows:

0:

Do not acquire

1:

Acquire only fatal errors

2:

Acquire traces for the error level and higher

3:

Acquire traces for the warning level and higher

4:

Acquire traces for the information level and higher

[Specification Method]

Using 16 bytes, specify the message level by specifying 1 byte for each daemon or program.

1st byte:

Set the mode of the HUB daemon.

2nd byte:

Set the mode of the PROXY daemon.

3rd byte:

Set the mode of the relay daemon (*).

4th byte:

Set the mode of the multicasting daemon (*).

5th byte:

Set the mode of the Manager daemon.

6th byte:

Set the mode of the monitor activities program.

8th byte:

Set the mode of the utility program, centralized management program of direct transfer log, and log backup program.

9th byte:

Set the mode of the delivery daemon/delivery process (*).

10th byte:

Job flow daemon (*).

11th byte:

Job flow execution program (*)

12th byte:

Job flow utility (*)

13th byte and subsequent bytes:

Reserved area

* : This only applies to HULFT-HUB Server for UNIX/Linux-ENT.

(Example) TraceMode=3333334033330000

If you specify the field in the System environment settings file as above, the utility program does not output a message. Daemons and programs output messages whose level is warning or higher to the trace file.

Dump File Acquisition Mode (DumpFlag)

<<0 or 1>>

Specify whether to acquire dump information when a failure occurs for each program according to [Specification Method] of Trace Acquisition Mode.

0:

Do not acquire

1:

Acquire

(Example) DumpFlag=1111111011110000

If you specify the field in the System environment settings file as above, the utility program does not output dump information when a failure occurs. The other daemons and programs output dump information when a failure occurs.

Event Log Error Level Output Mode (EventlogMode)

<<0 or 1 or 2 or 3 or 4>>

Specify the message level to be output to the event log when the server OS is Windows for each program according to [Specification Method] of Trace Acquisition Mode. Messages in the specified level or higher are output.

(Example) EventlogMode=1100111000000000

If you specify the field as above, the utility program outputs no event log when a failure occurs. The other daemons and programs output the event log when a failure occurs.

Operation log definition

Operation Log Output Mode (OplSelectMode)

<<0 or 1 or 2 or 3>>

Specify whether to output the operation log.

0:

Do not output the operation log

1:

Output only the File Access Log

2:

Output only the Command Execution Log

3:

Output both File Access Log and Command Execution Log

Operation Log Auto Switch Size (OplChangeSize)

<<0 or 1 to 9999 (MB)>>

Specify the maximum size of the operation log file in units of MB.

If the file size exceeds this value, the file output to that point is renamed to be backed up and a new operating log file is created automatically. The backup file is created in the same output directory as the operation log file.

If you specify '0' for this field, HULFT does not switch the operation log automatically.

For details, see the explanation of the operation log in the HULFT-HUB Manual or the HULFT-HUB Integration Management Manual.

0:

The operation log is not automatically switched.

1 to 9999 (MB):

The operation log is switched when the specified size is exceeded.

Operation Log Generation File Count (OplCycleCount)

<<2 to 9999>>

Specify how many generations of backup files of the operation log file should be kept when the operation log file is switched. When the number of backup files exceeds this value through automatic or manual switching, the operation log file is overwritten sequentially from the oldest file.

Setting a value other than '0' in the field Operation Log Auto Switch Size (OplChangeSize) enables this field.

Operation Log User ID Output Format (OplUseridType)

<<0 or 1>>

Specify the output format of the Operation Log User ID (OS) when the server OS is Windows.

0:

Down-level logon name

1:

User Principal Name (UPN)

Database-related definition

Write to DB Sync Mode (DBSyncMode)

<<0 or 1 or 2>>

Specify the timing of database update and deletion processing completion, and whether to synchronize completion of write to the physical disk.

If the disk cache is enabled, changing this tag might improve the access processing to the database.

Operation is as follows depending on the set value:

Table 1.19 Operation of Write to DB Sync Mode

Setting	Data part written in the file system
	Real data part	Meta-data part
0 (OS mode)	No Sync	No Sync
1 (OS/HW mixed mode)	Sync	No Sync
2 (HW mode)	Sync	Sync

No Sync	:	Write to the physical disk is not waited for. The time when write to the disk cache has been completed is considered as the completion of the database update or deletion processing.
Sync	:	Write to the physical disk is waited for. The time when write to the physical disk has been completed is considered as the completion of the database update or deletion processing.

Note

If a power failure or OS failure occurs before the contents of the disk cache are written to the hard disk, the information might be lost.

DB Mutex Lock Timeout (DBMutexTimeout)

<<0 or 60 to 600 (sec)>>

Specify the time-out period to wait for a lock in database access in seconds.

The response time to access a database depends on the amount of information or concentrated access for the server capability. When access to the database is concentrated and an attempt to acquire the database access lock is made, a timeout might occur.

Adjusting the value of this field might prevent a timeout error due to such temporary processing delay from occurring.

0:

Wait without limit until the lock is acquired.

60 to 600 (sec):

Wait until the lock is acquired for the specified time (after the time has passed, a timeout occurs).

DB Lock Mode (DBLockMode)

<<0 or 1>>

Specify the database lock mode.

The specified lock mode changes the method of accessing the database.

0:

Wait mode (compatible)

The sequence of entering a reading and writing lock is not specified and is in accordance with the re-entrant possibility restrictions. Normally, the processing capability is higher than '1 (queuing mode)'. Note that because a lock competes continuously under high load, multiple references or updates might be postponed without limit and might result in a timeout.

1:

Queuing mode

In queuing mode, the reading and writing lock is fairly entered in arrival sequence. If a lock has been acquired, processes are sequentially delayed. If not, a lock is assigned in arrival sequence. Even under high load, it is guaranteed that processing is performed within the range of 'number of tasks waiting processing x resource access time + queuing processing time'. Normally, the processing capability is lower than '0 (wait mode)'.

Other definition

Notification Host Name for Transfer via HUB (HostNameNotice)

<<0 or 1 or 2>>

Specify the name of the remote host to be registered in the client when transfer via HUB is defined and the format to be used in the host name reported from the remote host when transfer is via HUB.

0:

Format with Port No.

Uses the host name in the 'Host Name_Receive Port No.' format for all the hosts.

1:

Format with Port No. for Controlled Clients Only

Uses the host name in the 'Host Name_Receive Port No.' format for the controlled hosts.

Uses the host name as-is for hosts that are outside of control.

2:

Format without Port No.

Uses the host name as-is for all the hosts.

For details about the set value and operation of Notification Host Name for Transfer via HUB, see the HULFT-HUB Manual.

HUB Operation Language (HubLang)

<ja or en>

Specify the language in which HULFT-HUB Server displays messages.

ja:

Japanese

en:

English

The value is case-insensitive.

The language specified here applies to the following:

• Trace logs

• Outputs from some utilities

For details about the output of utilities, see HULFT-HUB Server Utilities.

For details about the trace log, see List of Messages.