/
MESSAGE_LEVEL - UDM Server configuration option

MESSAGE_LEVEL - UDM Server configuration option

Jul 03, 2023

 Description

The MESSAGE_LEVEL option specifies the level of messages to write.

It also specifies, optionally, whether or not to write a date and time stamp with each message.

Usage

Method

Syntax

IBM i

UNIX

Windows

z/OS

Configuration File Keyword

message_level level[,time]

Values

level indicates either of the following level of messages:

  • trace
    Activates tracing and generates a trace file to which UDM writes trace messages used for debugging.
     

  • 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.



time specifies either of the following:

  • time
    Include a time and date stamp on each message.

  • notime
    Do not include a time and date stamp on each message.

Default is time.

 Trace Files

 

IBM i

Trace file name is *CURLIB/UNVTRCUDMS(Txxxyyyyyy) where:

  • xxx = first three digits of the process ID, in hexadecimal, assigned to this instance of the Server by IBM i.

  • yyyyyy = last six digits of the component ID, in hexadecimal, assigned to this instance of the Server by the Broker.
     
    These values are used to generate a unique identifier for each invocation of the UDMSRV program.
     
    The default library for TRACE is the current library (*CURLIB) of the UBROKER process, not the user process. The UBROKER current library is the temporary library designated during the Universal Agent installation process; by default, the UBROKER current library is UNVTMP510.

UNIX

Trace file name is udmsrv-N-S.trc where:

  • N = Component ID assigned to this instance of the Server.

  • S = Sequence number.
     
    The trace file is created in the trace directory, as specified by the TRACE_DIRECTORY option (default is /var/opt/universal/trace).

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.UDM.Dyymmdd.Thhmmss.Cnnnnnnn where:

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

    • yymmdd is the year, month, day

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

    • nnnnnnn is the last seven digits of the Server's component ID in hexadecimal format

  2. If ddname UNVTRMDL is not defined in the UBROKER started task procedure, member name Dnnnnnns is created in the PDS or PDS/E allocated to the UNVTRACE ddname, where, nnnnnn is the last six digits of the Server's component ID in hexadecimal format, and s is the component ID's sequence number (from 0 - F). Each time a server is restarted, its sequence number is incremented. If a server is restarted more than 15 times, tracing is disabled.
     
    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.