...
Description
Anchor
...
Usage
Method | Syntax | IBM i | HP NonStop | UNIX | Windows | z/OS |
---|---|---|---|---|---|---|
Configuration File Keyword | message_level level |
...
...
Values
...
level is the level of messages to write.
Anchor
- trace
Writes trace messages used for diagnostic purposes (see #Trace Files).
Note | ||
---|---|---|
| ||
Use trace only as directed by Stonebranch, Inc. Customer Support. |
- audit
Writes audit, informational, warning, and error messages. - info
Writes informational, warning, and error messages. - warn
Writes warning and error messages. - error
Writes error messages only.
Default is info.
...
Trace Files
Info | ||
---|---|---|
| ||
The trace file is created in the directory /var/opt/universal/trace. |
...
Info | ||
---|---|---|
| ||
The trace file is created in the installation directory of Universal Automation Center Agent, which defaults to: C:\Program Files\Universal\uag |
Info | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||
| 1256627 | 1256627 | There are two possible destinations of the trace data:|||||||||
Anchor | 1256628 | 1256628 | If ddname UNVTRMDL is defined in the UBROKER started task procedure, a sequential data set is created using the data set allocated to UNVTRMDL as a model.|||||||||
Anchor | 1256633 | 1256633 | The amount of space allocated for trace data sets modeled after UNVTRMDL is based upon the TRACE_FILE_LINES configuration option and the record format of the model data set. If the model data set is fixed record format, the total amount of space measured in bytes is TRACE_FILE_LINES *LRECL. If the model data set is variable record format, the total amount of space measured in bytes is TRACE_FILE_LINES * 50 (50 is considered the average length of a trace file record).|||||||||
Anchor | 1256646 |
Depending on the error condition being diagnosed, it is possible that the member name of the UNVTRACE PDS or PDS/E is not created. If this occurs, the UNVTRMDL ddname must be used to create a sequential data set name. Anchor
The records written to PDS and PDS/E members cannot be wrapped, so the TRACE_FILE_LINES limit has no effect on the maximum number of trace records written to the member.