Command Reference

10.5.3
- 10.5.5
- 10.5.4
- 10.0

Back Next

DISPLAYSTATS Command

Displays monitoring statistics for a PowerExchange Listener that runs on Linux, zLinux, UNIX, Windows, or z/OS. Also displays statistics for the client tasks and source or target connections that are associated with the Listener.

To display monitoring statistics on demand for a PowerExchange Listener that runs on i5/OS, you must issue the pwxcmd displaystats command from a remote Linux, UNIX, or Windows machine. You cannot issue a DISPLAYSTATS command with the SNDLSTCMD command from the command line, a CL program, or REXX procedure. For more information, see pwxcmd displaystats Command.

The command can print the following types of statistics:

PowerExchange Listener summary statistics on resource usage and client requests. These statistics include counts of client tasks, connections, access methods, messages sent and received, and bytes of data sent and received.

Message and data volumes 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. For CDC tasks that use the CAPX or CAPXRT access method, includes counts of SQL inserts, updates, and deletes processed.

Information about the active tasks that are running under the PowerExchange Listener to process client requests. These statistics include the task start time, CPU processing time, access method, read or write mode, and associated process name and session ID if available. Also includes the port number and IP address of the client that issued the request to the PowerExchange Listener.

Before you run the command, configure the following statements in the DBMOVER configuration file:

Specify the MONITOR parameter in the STATS statement to enable PowerExchange to collect these statistics. You can include an interval subparameter to publish the statistics at a regular interval as well as on demand.

For the proper display of monitoring output on z/OS, set the LOG_LINE_LIMIT statement to 132. Otherwise, the lines might wrap awkwardly, making the output hard to read.

On UNIX, PowerExchange uses memory-mapped files and shared memory as the inter-process communication (IPC) method for monitoring. The memory-mapped files are allocated in the directory that is specified by the LOGPATH statement in the dbmover.cfg file, or in the current directory if the LOGPATH statement is not specified. On Linux and zLinux, PowerExchange uses shared memory but not memory-mapped files. PowerExchange releases shared memory and cleans up the memory-mapped files when PowerExchange Listener subtasks end and when the PowerExchange Listener is closed. To check that the shared memory was freed, use the IPC command -ipcs - m. If you need to release shared memory, use the ipcrm -m command.

Syntax on Linux, zLinux, UNIX, and Windows

On Linux, zLinux, UNIX, and Windows, use the following command syntax:

displaystats [{listener|accessmethods|clients}]

ds [{l|a|c}]

You can use a mixture of the long and short forms of the command and its parameter, such as ds accessmethods and displaystats a.

Syntax on z/OS

On z/OS, use the MVS MODIFY (F) command to issue the DISPLAYSTATS command. Use the following command syntax:

F task_name,DISPLAYSTATS [{LISTENER|ACCESSMETHODS|CLIENTS}]

F task_name,DS [{L|A|C}]

The task_name variable is the name of the PowerExchange Listener started task or batch job. Usually, the PowerExchange Listener runs as a started task.

You can use a mixture of the long and short forms of the command and its parameter, such as DS CLIENTS and DISPLAYSTATS C.

Parameter Descriptions

In the DISPLAYSTATS command, you can specify one the following optional parameters to indicate the report type:

LISTENER or L: Reports PowerExchange Listener summary statistics on resource usage and client requests processed. These statistics include memory usage, CPU processing time, total number of tasks that were created for client requests, 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. For a PowerExchange Listener on z/OS, these statistics also include the total number of netport jobs that have run under the Listener.
ACCESSMETHODS or A: Reports statistics on PowerExchange Listener message and data transfer activity by client task and access method, as of the time the statistics are generated. For each active task and access method combination, these statistics include the number of rows read and written, bytes of data read and written, the source or target file name or data map file name, and the CPU processing time. For CDC requests that use the CAPX or CAPXRT access method, the report also includes the number of SQL inserts, updates, and deletes that the task processed.
CLIENTS or C: Reports information about the active tasks that are running under the PowerExchange Listener, including the associated client and session ID. A client is an application such as PowerCenter, the PowerExchange Navigator, or a PowerExchange utility. For each active client task, the statistics show some or all of the following information: the status, access method that the task is using, task read or write mode, process name and session ID if available, CPU processing time, and start date and time. The statistics also include the client port number and IP address. If the client is PowerCenter, the statistics include the PowerCenter session ID and the application name for CDC.

Default is LISTENER, which is used if a parameter is not specified.

Example Output - Listener Report

On z/OS, enter the following command to generate a Listener report for a PowerExchange Listener task on z/OS:

F task_name,DS

PowerExchange writes the following report output on the z/OS system:

PWX-00723 Command <displaystats Listener> succeeded
PWX-37101  Listener <PWXLST  > ASID=375 (x'177') UserID=AUSER
PWX-37102   Memory
PWX-37103    Region below 16-MB line:  In Use        108 KB  Limit Value       9192 KB  Free       9084 KB
PWX-37104    Region above 16-MB line:  In Use      53912 KB  Limit Value    1675264 KB  Free    1621352 KB
PWX-37117   CPU Time
PWX-37118    TCB Time   = 0 SRB Time     = 0  zIIP-NTime = zIPP_normalized_time
PWX-37119    Listener   = 0 hrs, 0 mins, 1 secs, 275762 mcrs
PWX-37106   Cumulative Requests
PWX-37107    Total Tasks=        11 Active Tasks =         3 HWM Tasks =         3 Maxtasks  =        50
PWX-37108    Connections=        11 Accepted     =        11 Active    =         0
PWX-37109    Msgs Sent  =         0 Msgs Received=        22
PWX-37110    Data Sent  =         0 Data Received=      7304
PWX-37111    NetportJobs=         0

On Windows, open the Command Prompt window, navigate to the PowerExchange installation directory, and enter the following command for the PowerExchange Listener on Windows:

ds l

PowerExchange displays the following report output in the Command Prompt window, provided that you are running the Listener in the foreground:

PWX-00723 Command <displaystats Listener> succeeded
PWX-37102   Memory
PWX-37105    Total Memory 50952 KB
PWX-37117   CPU Time
PWX-37119    Listener   = 0 hrs, 0 mins, 0 secs, 234001 mcrs
PWX-37106   Cumulative Requests
PWX-37107    Total Tasks=         2 Active Tasks =         2 HWM Tasks =         2 Maxtasks  =         5
PWX-37108    Connections=         2 Accepted     =         2 Active    =         2
PWX-37109    Msgs Sent  =         0 Msgs Received=         4
PWX-37110    Data Sent  =         0 Data Received=      1328

If you are running the PowerExchange Listener as a background process, you must use the pwxcmd program to issue the command.

The following fields occur in one or both these reports:

Listener: For the PowerExchange Listener on z/OS only. The Listener node name as specified in a LISTENER statement in the DBMOVER configuration file.
ASID: For the PowerExchange Listener on z/OS only, the identifier for the Listener address space.
UserID: For the PowerExchange Listener on z/OS only, the user ID under which the PowerExchange Listener task is running.
Memory > Region below 16-MB line: For the PowerExchange Listener on z/OS only, memory usage by the Listener and its client tasks below the 16-MB line of the Listener address space. The following memory statistics are reported:
In Use
. The amount of memory below the 16-MB line of the address space that is in use by the PowerExchange Listener and its client tasks.
Limit Value
. The maximum memory storage below the 16-MB line.
Free
. The amount of memory below the 16-MB line that is free.
Memory > Region above 16-MB line: For the PowerExchange Listener on z/OS only, memory usage by the Listener and its client tasks above the 16-MB line of the Listener address space. The following memory statistics are reported:
In Use
. The amount of memory above the 16-MB line of the address space that is in use by the PowerExchange Listener and its client tasks.
Limit Value
. The maximum memory storage above the 16-MB line.
Free
. The amount of memory above the 16-MB line that is free.
Total Memory: For the PowerExchange Listener on Windows only, the total amount of memory that is in use by the PowerExchange Listener on Windows.
CPU Time > TCB Time: For the PowerExchange Listener on z/OS only, the CPU processing time of the task control block (TCB) in the PowerExchange Listener address space on z/OS.
CPU Time > SRB Time: For the PowerExchange Listener on z/OS only, the CPU processing time of the service request block (SRB) in the PowerExchange Listener address space on z/OS.
CPU Time > zIIP-NTime: If you use a System z Integrated Information Processor (zIIP) and set the USESUP statement in the DBMOVER configuration file to Y, the zIIP Normalized time used by the PowerExchange Listener and its client tasks. zIIP Normalized time is CPU time adjusted to account for the difference in speed between CP and zIIP processors.
CPU Time > Listener: The CPU processing time of the PowerExchange Listener and its client tasks.
Total Tasks: The total number of client tasks that have run under the PowerExchange Listener since it started.
Active Tasks: The number of active client tasks that are running under the PowerExchange Listener, as of the time when these statistics were generated.
HWM Tasks: The greatest number of concurrent client tasks, also called high-watermark tasks
, that ran under the PowerExchange Listener at any one time. Compare the number of HWM tasks to the Maxtasks value to prevent exceeding the Maxtasks limit. If the Maxtasks limit is reached, PowerExchange Listener processing might be delayed, which can lead to reduced throughput and connection timeouts.
Maxtasks: The maximum number of concurrent tasks that can run under the PowerExchange Listener. This value is set in the MAXTASKS statement of the DBMOVER member.
Connections: The total number of connections to a source or target that were attempted for the client tasks that run under the PowerExchange Listener.
Accepted: The number of connections that were accepted.
The number of access methods can be greater than the number of connections if some connections are rejected or fail or if access methods share connections.
Active: The number of active connections, as of the time these statistics were generated.
Msgs Sent: The total number of messages that the PowerExchange Listener sent when processing requests from clients.
Msgs Received: The total number of messages that the PowerExchange Listener received when processing requests from clients.
Data Sent: The total bytes of data that the PowerExchange Listener sent in response to client requests. Includes the data for both bulk data movement and CDC tasks.
Data Received: The total bytes of data that the PowerExchange Listener received in response to client requests. Includes the data for both bulk data movement and CDC tasks.
NetportJobs: For the PowerExchange Listener on z/OS only. The total number of netport jobs that ran under the PowerExchange Listener.

Example Output - Accessmethods Report

On z/OS, enter the following command to generate an accessmethods report for a PowerExchange Listener on z/OS:

F listener_task,DS A

PowerExchange writes the following report output to the screen or message log on the Windows system:

PWX-00723 Command <displaystats AccessMethods> succeeded
PWX-37201   Active Access Methods                                                                  
PWX-37202    Task ID    = 42412 AM           =     CAPXRT
PWX-37203                       Rows read    =       1029  Rows written  =          0
PWX-37204                       Bytes read   =     116277  Bytes written =          0
PWX-37205                       File         = d2ivd0.d002root_ROOT
PWX-37206                       Table        = <Capture Extract Realtime>
PWX-37208                       Inserts      =        564  Updates       =          0  Deletes     =        465
PWX-37121                       CPU time     = 0 hrs, 0 mins, 0 secs, 299809 mcrs
PWX-37202    Task ID    = 42414 AM           =       NRDB
PWX-37203                       Rows read    =         10  Rows written  =          0
PWX-37204                       Bytes read   =        570  Bytes written =          0
PWX-37205                       File         = ABCD.VSAM.MASTER_REC
PWX-37206                       Table        = <Non-relational source>
PWX-37202    Task ID    = 42414 AM           =       KSDS
PWX-37203                       Rows read    =         10  Rows written  =          0
PWX-37204                       Bytes read   =        800  Bytes written =          0
PWX-37205                       File         = XYZ.TEST.KSDS
PWX-37206                       Table        = XYZ.TEST.KSDS
PWX-37121                       CPU time     = 0 hrs, 0 mins, 0 secs, 76151 mcrs

On Linux, UNIX, Windows, or zLinux, the

displaystats accessmethods

ds a

command provides the same type of report output for a PowerExchange Listener that runs on Linux, UNIX, Windows, or zLinux.

The following fields occur in this report:

Task ID: The identifier for an active task that the PowerExchange Listener created to service a request from a client. The client task can be for accessing data, reading source metadata, or other functions.
AM: The access method, or source type, that the task uses.
A client task can use multiple access methods, for example, one for reading source data and one for mapping nonrelational source data to a relational format. In the sample output, task 42412 uses the NRDB access method with the data map file specified in the
File
field to map nonrelational data to a relational format. The same task uses the KSDS access method to retrieve data from the KSDS data set identified in the
File
field.
Rows read: The number of rows that the active client task has read from the source by using the specified access method. This value is 0 if the task is performing another function such as mapping a nonrelational source to relational format.
Rows written: The number of rows that the active client task has written to the target by using the specified access method. This value is 0 if the task is performing another function such as mapping a nonrelational source to relational format.
Bytes read: The bytes of data that the active client task has read from the source by using the specified access method. This value is 0 if the task is performing another function such as mapping a nonrelational source to relational format.
Bytes written: The bytes of data that the active client task has written to the target. This value is 0 if the task is performing another function such as mapping a nonrelational source to relational format.
File: The name of the source or target file or the name of a data map file, depending on the access method that is used to process the data.
Table: The source or target table name, if applicable.
Inserts: The number of SQL inserts that the client task processed from the source with the CAPX or CAPXRT access method for a CDC request.
Updates: The number of SQL updates that the client task processed from the source with the CAPX or CAPXRT access method for a CDC request.
Deletes: The number of SQL deletes that the client task processed from the source with the CAPX or CAPXRT access method for a CDC request.
CPU time: The CPU processing time of the active client task. A CPU time is not reported for PowerExchange internal tasks such as reading data maps.

Example Output - Clients Report

Use this report to learn about the client requests for which the PowerExchange Listener created tasks.

On z/OS, enter the following command to generate a clients report for a PowerExchange Listener task on z/OS:

F listener_task,DS C

PowerExchange writes the following report output on the z/OS system:

PWX-00723 Command <displaystats Clients> succeeded
PWX-37112   Active Tasks
PWX-37113    Task ID    = 42407 Status       = Active
PWX-37114                       Port         = 6580  Partner = ::ffff:127.0.0.1
PWX-37115                       PwrCntrSess  = N/A
PWX-37207                       Application  = N/A
PWX-37116                       AM           = CPR  Mode    = Read  Process =  SessionId =
PWX-37113    Task ID    = 42412 Status       = Active
PWX-37114                       Port         = 6580  Partner = ::ffff:10.33.8.137
PWX-37115                       PwrCntrSess  = N/A
PWX-37207                       Application  = myappl
PWX-37116                       AM           = CAPXRT  Mode    = Read  Process =  SessionId =
PWX-37121                       CPU time     = 0 hrs, 0 mins, 0 secs, 299809 mcrs
PWX-37122                       Start time   = 2014-05-01 14:32:28

On Linux, UNIX, Windows, or zLinux, the

displaystats clients

ds c

command provides the same type of output for a PowerExchange Listener that runs on Linux, UNIX, Windows, or zLinux.

The following fields occur in this report:

Task ID: The identifier for an active task that the PowerExchange Listener created to service a request from a client. The client task can be for accessing data, reading source metadata, or other functions.
Status: The status of the active client task, which can be one of the following values:
Active
STOPTASK acknowledged, if a STOPTASK command has been issued for the active task
STOPTASK set, if a STOPTASK command has been issued for the active task
Port: The port number of the client for which the task was created.
Partner: The TCP/IP address of the client. A value that begins with :ffff indicates an IPv6 address.
The full IPv6 address is not reported because the PowerExchange Listener uses addresses in IPv4 format.
PwrCntrSess: If the client is PowerCenter, the PowerCenter session ID for a bulk data movement or CDC workflow in the format integration_service/workflow_name/session_name. Otherwise, this field displays N/A for not applicable.
Application: For PowerCenter CDC sessions, the value of the
Application Name
attribute on the PWXPC application connection. Otherwise, the value is N/A for not applicable.
AM: The access method, or source type, that the task uses.
Mode: The data request mode that the task uses, which can be one of the following values:
Read
Write
Process: The name of the process that the PowerExchange Listener starts to service the client request, if available.
SessionId: A session ID that is optionally defined for client requests. This value primarily pertains to client requests for DB2 access. If you use PowerCenter with the PowerExchange Client for PowerCenter (PWXPC), this value can be the correlation ID that is specified in the SESSID statement of the DBMOVER configuration file or in the
Correlation Id
override attribute on the PWXPC DB2 Batch connection. For ODBC connections, it can be the value of the DTLSESSID SQL escape sequence, if defined.
CPU time: The CPU processing time of the client task. This value is expressed in hours, minutes, seconds, and microseconds, as appropriate. This value is not reported for PowerExchange internal tasks such as those that read data maps.
Start time: The start date and time of the client task in the format YYYY-MM-DD HH:MM:SS. This value is not reported for PowerExchange internal tasks such as those that read data maps.

Rename Saved Search

Table of Contents

Command Reference

Command Reference

DISPLAYSTATS Command

DISPLAYSTATS Command

Syntax on Linux, zLinux, UNIX, and Windows

Syntax on z/OS

Parameter Descriptions

Example Output - Listener Report

Example Output - Accessmethods Report

Example Output - Clients Report