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
  • Common Content for Data Engineering 10.5.3
  • All Products

Table of Contents

Search

  1. Preface
  2. Command Line Programs and Utilities
  3. Installing and Configuring Command Line Utilities
  4. Using the Command Line Programs
  5. Environment Variables for Command Line Programs
  6. Using infacmd
  7. infacmd as Command Reference
  8. infacmd aud Command Reference
  9. infacmd autotune Command Reference
  10. Infacmd bg Command Reference
  11. infacmd ccps Command Reference
  12. infacmd cluster Command Reference
  13. infacmd cms Command Reference
  14. infacmd dis Command Reference
  15. Infacmd dis Queries
  16. infacmd dp Command Reference
  17. infacmd idp Command Reference
  18. infacmd edp Command Reference
  19. Infacmd es Command Reference
  20. infacmd ics Command Reference
  21. infacmd ipc Command Reference
  22. infacmd isp Command Reference
  23. infacmd ldm Command Reference
  24. infacmd mas Command Reference
  25. infacmd mi Command Reference
  26. infacmd mrs Command Reference
  27. infacmd ms Command Reference
  28. infacmd oie Command Reference
  29. infacmd ps Command Reference
  30. infacmd pwx Command Reference
  31. infacmd roh Command Reference
  32. infacmd rms Command Reference
  33. infacmd rtm Command Reference
  34. infacmd sch Command Reference
  35. infacmd search Command Reference
  36. infacmd sql Command Reference
  37. infacmd tdm Command Reference
  38. infacmd tools Command Reference
  39. infacmd wfs Command Reference
  40. infacmd ws Command Reference
  41. infacmd xrf Command Reference
  42. infacmd Control Files
  43. infasetup Command Reference
  44. pmcmd Command Reference
  45. pmrep Command Reference
  46. Working with filemanager
  47. Working with pmrep Files

Command Reference

Command Reference

Back Next

displayStatsListener

displayStatsListener

Displays monitoring statistics for a PowerExchange Listener on Linux, UNIX, or Windows that the PowerExchange Listener Service manages. Also displays statistics for the client tasks and source or target connections that are associated with the Listener.
The command can print the following types of statistics, depending on the -type option that you specify:
  • PowerExchange Listener summary statistics on memory usage, CPU processing time, and activity on behalf of client requests. These statistics include counts of client tasks, connections, messages sent and received, and bytes of data sent and received.
  • Message and data volumes that client tasks sent and received for client requests, by task ID and access method. The message and data volumes are totals as of the time the statistics are generated.
  • Information about the active tasks that are running under the Listener to process client requests. These statistics include the task start time, CPU processing time, access method, read or write mode, and associated process and session IDs. Also includes the port number and IP address of the client that issued the request to the PowerExchange Listener.
For PowerExchange to collect PowerExchange Listener monitoring statistics, you must specify the MONITOR parameter in the STATS statement in the DBMOVER configuration file where the Listener runs.
The infacmd pwx displayStatsListener command uses the following syntax: 
displayStatsListener

[<-DomainName|-dn> domain_name]

[<-UserName|-un> user_name]

[<-Password|-pd> password]

<-ServiceName|-sn> service_name

[<-ResilienceTimeout|-re> timeout_period_in_seconds]

[<-SecurityDomain|-sdn> security_domain]

[<-Gateway|-hp> domain_host1:port domain_host2:port...]

[<-OSUser|-oun> OS_user_name]

[<-OSPassword|-oup> OS_password]

[<-OSEPassword|-ouep> OS_epassword]

[<-Type|-tp> report_type]
The following table describes infacmd pwx displayStatsListener options and arguments:
Option
Argument
Description
-DomainName
-dn
domain_name
Name of the Informatica domain. You can set the domain name with the -dn option or the environment variable INFA_DEFAULT_DOMAIN. If you set a domain name with both methods, the -dn option takes precedence.
-UserName
-un
user_name
Required if the domain uses Native or LDAP authentication. User name to connect to the domain. You can set the user name with the -un option or the environment variable INFA_DEFAULT_DOMAIN_USER. If you set a user name with both methods, the -un option takes precedence.
Optional if the domain uses Kerberos authentication. To run the command with single sign-on, do not set the user name. If you set the user name, the command runs without single sign-on.
-Password
-pd
password
Required if you specify the user name. Password for the user name. The password is case sensitive. You can set a password with the -pd option or the environment variable INFA_DEFAULT_DOMAIN_PASSWORD. If you set a password with both methods, the password set with the -pd option takes precedence.
-ServiceName
-sn
service_name
Required. Name of the Listener Service.
-ResilienceTimeout
-re
timeout_period_in_seconds
Optional. Amount of time in seconds that infacmd attempts to establish or re-establish a connection to the domain. You can set the resilience timeout period with the -re option or the environment variable INFA_CLIENT_RESILIENCE_TIMEOUT. If you set a the resilience timeout period with both methods, the -re option takes precedence.
-SecurityDomain
-sdn
security_domain
Required if the domain uses LDAP authentication. Optional if the domain uses native authentication or Kerberos authentication. Name of the security domain to which the domain user belongs. You can set a security domain with the -sdn option or the environment variable INFA_DEFAULT_SECURITY_DOMAIN. If you set a security domain name with both methods, the -sdn option takes precedence. The security domain name is case sensitive.
If the domain uses native or LDAP authentication, the default is Native. If the domain uses Kerberos authentication, the default is the LDAP security domain created during installation. The name of the security domain is the same as the user realm specified during installation.
-Gateway
-hp
gateway_host1:port gateway_host2:port ...
Required if the gateway connectivity information in the domains.infa file is out of date. The host names and port numbers for the gateway nodes in the domain.
-OSUser
-oun
OS_user_name
Required if you enable operating system security. User name for the operating system.
Enable operating system security as follows:
  • To require users to enter a valid operating system user ID and password on the command, specify 1 or 2 for the first parameter of the SECURITY statement in the DBMOVER configuration file on each Linux, UNIX, or Windows system that is the target of the command. PowerExchange uses operating system facilities on the target system to authenticate the user ID and password for use of the infacmd pwx program.
  • To authorize users to run specific infacmd pwx commands, specify 2 for the first parameter of the SECURITY statement and define AUTHGROUP and USER statements in the PowerExchange sign-on file on each Linux, UNIX, or Windows system that is the target of the command. PowerExchange checks the sign-on file to determine whether to allow the user ID supplied on the infacmd pwx program to run commands.
-OSPassword
-oup
OS_password
Required if you specify a user name and do not specify an encrypted password. Password for the operating system.
You can set a plain text password with the -p option or the environment variable INFA_DEFAULT_PWX_OSPASSWORD. If you set a password with both methods, the password set with the -p option takes precedence.
-OSEPassword
-ouep
OS_epassword
Required if you specify a user name and do not specify a plain text password. Encrypted password for the operating system.
You can set an encrypted password with the -e option or the environment variable INFA_DEFAULT_PWX_OSEPASSWORD. If you set a password with both methods, the password set with the -e option takes precedence.
-type
-tp
report_type
Optional. The type of monitoring statistics to report for the PowerExchange Listener and its client tasks and connections. The report_type must be one of the following values:
  • listener. For a specific PowerExchange Listener, reports memory usage, CPU processing time, total number of client tasks, active tasks, high-watermark tasks, maximum allowed tasks, total number of connections attempted, connections accepted, active connections, number of messages sent and received, and bytes of data sent and received.
  • accessmethods. For each access method of each active task, reports the number of rows read and written, bytes of data read and written, the source or target file name or data map file name depending on the access method, and the CPU processing time.
  • clients. For each active task, reports the task ID, status, access method, read or write mode, process and session IDs if available, CPU processing time, and start date and time. Also reports the port number and IP address of the client that issued the request for which the task was created. If the client is PowerCenter, reports the PowerCenter session ID and the application name for CDC.
Default is listener.
In these reports, an access method can be a source type such as NRDB. A client task might be associated with multiple access methods: one for reading the source data, and one for mapping nonrelational data to a relational format.
0 COMMENTS
We’d like to hear from you!