Table of Contents

Search

  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

LOG_LINE_LIMIT Statement

LOG_LINE_LIMIT Statement

The LOG_LINE_LIMIT statement specifies the maximum line length for PowerExchange messages in the message log.
i5/OS, Linux, UNIX, Windows, and z/OS
Not applicable
No
LOG_LINE_LIMIT={
number_of_characters
|
79
}
For the
number_of_characters
variable, enter the number of characters that defines the maximum line length for messages in the message log. Messages that span multiple lines, such as messages that report diagnostic output or statistics messages in tabular format, might be improperly formatted if the log line limit is too short. In this case, try increasing this value to make the messages easier to read in the log.
Valid values:
  • On i5/OS, Linux, UNIX, or Windows, enter a number from 79 to 255.
  • On z/OS, enter a number from 79 to 132.
Default is 79 on all of these operating systems.
  • If you enter a value greater than 80 and do not specify the RECLEN parameter in the TRACING statement, PowerExchange uses the LOG_LINE_LIMIT value as the RECLEN value.
  • If you enter the MONITOR parameter in the STATS statement to produce summary statistics for a PowerExchange Listener on z/OS, set the LOG_LINE_LIMIT value to 132. Otherwise, the lines in the PowerExchange Listener displaystats report might wrap awkwardly on
    z/OS
    , making the report output hard to read.