Table of Contents


  1. Preface
  2. Introduction to PowerExchange
  3. DBMOVER Configuration File
  4. Netport Jobs
  5. PowerExchange Message Logs and Destination Overrides
  6. SMF Statistics Logging
  7. PowerExchange Security
  8. Secure Sockets Layer Support
  9. PowerExchange Alternative Network Security
  10. PowerExchange Nonrelational SQL
  11. PowerExchange Globalization
  12. Using the PowerExchange ODBC Drivers
  13. PowerExchange Datatypes and Conversion Matrix
  14. DTL__CAPXTIMESTAMP Time Stamps
  15. PowerExchange Glossary

DTLMSGO File and Statements

DTLMSGO File and Statements

The DTLMSGO file contains statements that indicate destinations for specific message numbers. Define a DTLMSGO file if you want to redirect certain messages to destinations other than the default location.
Override destinations include the PowerExchange message log file or alternative log files, stdout, or system operator console.
In the DTLMSGO file, you can also suppress a message so that it is not displayed in any of these locations

DTLMSGO Statements - Syntax and Parameters

Use the correct syntax and valid parameter values when defining message destination override statements in the DTLMSGO file.
Use the following syntax:
/*Message sent to multiple destinations
}, ... /*Message destination is not overriden
/*Suppress message
The following syntax rules apply:
  • Comment lines must begin with “/*” in column 1.
  • If the same message appears more than once in the DTLMSGO file, only the last occurrence is used.
Required. Specify a message number. The message number must exist in the DTLMSG file on i5/OS or z/OS or in the dtlmsg.txt file on Linux, UNIX, or Windows. Message numbers are 5-digit numbers with no prefix.
Specify the message number with or without the leading zeroes. You cannot specify a mask with wildcards for a
Optional. Select one or more options to indicate the override destinations for the specified message number. Options are:
  • null
    . If no destination is specified for the message number, the message is not redirected to a different destination. The message is treated as if it is not included in the DTLMSGO file.
  • LOG
    . The message is routed to the primary PowerExchange message log or to an alternative log file. If alternative logging is enabled but the alternative logging subtask has not initialized, the message is routed to the PowerExchange message log file.
  • NONE
    . The message is suppressed. The message is not displayed in any location. Do not specify this value with any other option.
    . The message is routed to the standard output location, which varies by system.
    On z/OS, STDOUT is sent to the SYSPRINT DD data set if specified or to a dynamically allocated temporary JES SPOOL data set.
    On i5/OS, STDOUT is sent to QPRINT if PowerExchange is running as a background job or to the terminal if PowerExchange is running interactively.
    On Linux, UNIX, and Windows, STDOUT is sent to the terminal by default unless you redirect it elsewhere.
    . On i5/OS and z/OS, the message is displayed in the system operator interface.
    On z/OS, the message is processed by the Write-To-Operator (WTO) macro and displayed in the system operator console. No routing code is associated with the WTO so the ROUTCODE value that is specified in the DEFAULT statement of CONSOLxx is used for routing.
    On i5/OS, the message is sent to the operator message queue.
    On Linux, UNIX, and Windows, SYSCONS is ignored.
and NONE options are mutually exclusive. The other options can be specified together.

DTLMSGO File Example

The following example DTLMSGO file includes six message destination override statements:
/* /* Sample file to change message destinations /* /* region size msg to console 594,SYSCONS /* use pwx defaults 00595 /* multiple destinations 00650,SYSCONS,LOG 00651,SYSCONS,LOG,STDOUT /* suppress stats msg 00408,NONE /* 607,STDOUT,LOG /*
The message numbers 594 and 607 are entered without leading zeroes. The message number 00595 has no override destination. The message numbers 00650, 00651, and 607 have multiple override destinations.