Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • PowerExchange for CDC and Mainframe 10.5.9
  • All Products

Table of Contents

Search

  1. Preface
  2. Introduction to PowerExchange Utilities
  3. createdatamaps - Data Map Creation Utility
  4. DTLCCADW - Adabas PCAT Utility
  5. DTLCUIML - IMS Log Marker Utility
  6. DTLINFO - Release Information Utility
  7. DTLINFOX - Enhanced Release Information Utility
  8. DTLREXE - Remote Execution Utility
  9. DTLUAPPL - Restart Token Utility
  10. DTLUCBRG - Batch Registration Utility
  11. DTLUCDEP - CDEP Maintenance Utility
  12. DTLUCSR2 - IDMS SR2 and SR3 Records Utility
  13. DTLUCUDB - Db2 for Linux, UNIX, and Windows CDC Utility
  14. DTLULCAT and DTLULOGC - IDMS Log Catalog Utilities
  15. DTLURDMO - Data Map Utility
  16. DTLUTSK - Task Control Utility
  17. EDMLUCTR - Log Scan and Print Utility
  18. EDMUOPTS - Service Aid Utility
  19. EDMXLUTL - Event Marker Utility
  20. HOSTENT - TCP/IP Address Reporter Utility
  21. PWXCATMY - MySQL Catalog Utility
  22. PWXUCCLPRT - Print Log Summary Utility
  23. PWXUCDCT - Logger for Linux, UNIX, and Windows Utility
  24. PWXUCREG - Capture Registration Utility
  25. PWXUMAP - Map List Utility
  26. PWXUCRGP - Capture Registrations Print Utility
  27. PWXUDMX - Data Maps Update Time ECSA Memory Utility
  28. PWXUGSK - SSL Reporting Utility
  29. PWXUMSGS - PowerExchange Listener Messages Utility
  30. PWXUSSL - PowerExchange SSL Reporting Utility
  31. WRKJRNLCKE- Journal Lock Table Utility for IBM i
  32. ZOSTOUCH - Set Last Referenced Date Utility for z/OS

Utilities Guide

Utilities Guide

Back Next

Control Statement Parameters for the PWXUMSGS Utility

Control Statement Parameters for the PWXUMSGS Utility

The PWXUMSGS utility uses the following parameters as shown in the syntax:
REPORTTYPE={FILEINFO|FILEINFO_MSGS|MSGS_ONLY}
The type of report you want to generate. Valid options are:
FILEINFO
Retrieve the following information:
  • File name
  • Timestamp of the first write operation to the file
  • Number of records
FILEINFO_MSGS
Retrieve messages that include the following information from alternate log files:
  • Date
  • Time
  • Process ID
  • Message text
The start date and time for message filtering is obtained from STARTDATE and STARTTIME, if specified. Otherwise, The start date and time is obtained from the restart.txt file in the current directory, if it is present.
MSGS_ONLY
Retrieve messages only.
SOURCE={SINGLE|LISTENER|OTHER}
The source of the messages. Valid options are:
SINGLE
detail.log file
LISTENER
PowerExchange Listener
OTHER
Retrieve messages without running in the address space of the process that writes the messages.
This option can be useful when you want to retrieve messages from a long-running PowerExchange Logger for Linux, UNIX, and Windows process, or if you want to access another user's PowerExchange Listener.
OUTDIR=
output_directory
The directory to contain the output report.
LOCATION=
node
[UID=
user
 EPWD=
password
]
The location of the messages. Valid options are:
node
The node specified by the NODE statement in your DBMOVER configuration file for the remote machine where the PowerExchange Listener runs.
UID=
user
The user ID for the PowerExchange Listener on the remote machine.
EPWD=
password
An encrypted password for the user ID specified by UID. PowerExchange uses this encrypted password to connect to the PowerExchange Listener on the remote machine.
SUMMARYFREQ={HOURLY|DAILY|WEEKLY|MONTHLY|ENDOFRUN|NONE}
The frequency at which the summary report is issued. Valid options are:
HOURLY
Hourly summary
DAILY
Daily summary
WEEKLY
Weekly summary
MONTHLY
Monthly summary
ENDOFRUN
Daily report to get the messages issued since the last report
NONE
The report is generated once when you run the utility.
MIN_MSG_SEVERITY={0-4}
Minimum message severity level to include in the report. Valid options are:
  • 0. Messages with no severity. For example, trace messages.
  • 1. Informational messages.
  • 2. Warning messages.
  • 3. Error messages.
  • 4. Severe error messages that might require action.
STARTDATE=
date_YYMMDD
 [STARTTIME=
time_HHMMSS
]
Filter the report by the start date and start time.
ENDDATE =
date_YYMMDD
 [ENDTIME =
time_HHMMSS
]
Filter the report by the end date and end time.
TRANS_FROM_LANG={BRAZILIAN;ENGLISH;JAPANESE;KOREAN;CHINESE;*}
Translate messages from the specified language to the localized language for the Windows machine where the PWXUMSGS utility runs. For example, if you browse an alternate log file and see the z/OS messages are in English but want to view the messages in Japanese, which is your localized language, specify TRANS_FROM_LANG=ENGLISH.
Valid options are:
BRAZILIAN
Translate the messages from Brazilian.
ENGLISH
Translate the messages from English.
JAPANESE
Translate the messages from Japanese.
KOREAN
Translate the messages from Korean.
CHINESE
Translate the messages from Chinese.
*
Allow PWXUMSGS to determine the language from which to translate the messages.
You can also translate alternate log file messages localized from a language, such as Japanese, into English. The requirements are:
  • The PWXUMSGS utility must run on a Windows machine that is localized for English, which is the default configuration.
  • You must set the TRANS_FROM_LANG parameter to match the language used in alternate log file messages, for example, Japanese.
  • You must set the TRANS_FROM_DTLMSG_CODEPAGE parameter to the option for the DTLMSG.TXT file, for example, shiftJIS.
TRANS_FROM_DTLMSG_CODEPAGE={UTF8_PORTUGUESE-BZ|shiftJIS|KO_UTF8|SC_UTF8}
Specify this parameter when translating Linux, UNIX, and Windows messages to English from a localized language only. Use this parameter in the following ways:
  • To locate the DTLMSG.TXT file that was used when the messages were written. This file corresponds to the DTLMSG_LANGUAGE statement that the PowerExchange Listener uses.
  • To specify the code page in which the DTLMSG text is encoded. PWXUMSGS uses UTF-8, but translates external shiftJIS text, as needed.
The following DTLMSG files are supported:
UTF8_PORTUGUESE-BZ
dtlmsg_UTF8_PORTUGUESE-BZ.txt
shiftJIS
dtlmsg_shiftJIS.txt
KO_UTF8
dtlmsg_KO_UTF8.txt
SC_UTF8
dtlmsg_SC_UTF8.txt
The utility does not support the dtlmsg_GB2312.txt and dtlmsg_MS949.txt files.
SINGLEFILENAME=
file
Specify the name of the single detail.log file to process.
OTHERFILEPREFIX=
text
Specify the file prefix to use for selecting the alternate log files to read. Both OTHERFILEPREFIX and OTHERNBRFILES are used to locate the alternate log files to be read.
OTHERNBRFILES={0-20}
Specify the number of alternate log files to read. Both OTHERFILEPREFIX and OTHERNBRFILES are used to locate the alternate log files to be read.
When you specify OTHERFILEPREFIX and OTHERNBRFILES, the utility does not access the file names from PowerExchange Listener shared memory. In this mode, it is possible to access alternate log files that have been written by non-Listener jobs that are long running, such as Condense jobs on IBM i or z/OS or PowerExchange Logger for LUW jobs on Linux, UNIX, or Windows. Running the utility in this mode is not recommended because the process that writes the alternate log files might have trouble opening a fresh log file while the utility is reading the log. Also, determinining the values for OTHERFILEPREFIX and OTHERNBRFILES can be challenging.
0 COMMENTS
We’d like to hear from you!