/
MESSAGE_LEVEL - UBROKER configuration option

MESSAGE_LEVEL - UBROKER configuration option

Feb 04, 2025

 Description

The MESSAGE_LEVEL option specifies the level of messages to write.

Usage

Method

Syntax

IBM i

UNIX

Windows

z/OS

Configuration File Keyword

message_level level

Values

level is the level of messages to write.

Valid values for level are:

  • trace
    Writes trace messages used for diagnostic purposes (see Trace Files, below).

    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.

  • time
    Prefixes messages with the date/time. The yyyy.mm.dd hh.mm.ss.uuu format is always used.

  • notime
    Omits the date/time prefix from messages.

    The time and notime values can be specified by themselves or along with one of the other message levels. For example, message_level time and message_level info,notime are both valid values. The default is time.

Default is info.

 Trace Files

IBM i

The trace file name is UNVTMP510/UNVTRCUBR).

UNIX

The trace file name depends on how it is started:

  • If running as a console application, the file name is ubroker.trc.

  • If running as a daemon, the file name is ubrokerd.trc.
    The trace file is created in the directory /var/opt/universal/trace.

Windows

  • The trace file name depends on how it was started:

    • If running as a console application, the file name is ubroker.trc.

    • If running as a service, the file name is ubrsvc.trc.
       
      The trace file is created in the installation directory of Universal Broker, which defaults to:
      C:\Program Files\Universal\Ubroker

z/OS

There are two possible destinations of the trace data:

  1. 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.
     
    The dynamically allocated trace data set name is #HLQ.UBR.Dyymmdd.Thhmmss, where:

    • #HLQ is the data set name allocated on the UNVTRMDL ddname.

    • yymmdd is the year, month, and day.

    • hhmmss is the hour, minute, second the data set was allocated.
       

      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).
       
       The number of cylinders is calculated from the total amount of space in bytes. The total number of cylinders is calculated base on a total of 16 extents being allocated.
       
       The formula is cylCount = (totalSize / 16) / 750000.
       
       The allocation unit is set to cylinders and the primary and secondary space allocation is set to cylCount (that is, SPACE=(CYL,(cylCount,cylCount),RLSE)).
       

  2. If ddname UNVTRMDL is not defined in the UBROKER started task procedure, member name UBROKER is created in the PDS or PDS/E allocated to the UNVTRACE ddname.


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.

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.