Table of Contents

Search

  1. Preface
  2. Introduction to PowerExchange Bulk Data Movement
  3. PowerExchange Listener
  4. Adabas Bulk Data Movement
  5. Datacom Bulk Data Movement
  6. DB2 for i5/OS Bulk Data Movement
  7. DB2 for Linux, UNIX, and Windows Bulk Data Movement
  8. DB2 for z/OS Bulk Data Movement
  9. IDMS Bulk Data Movement
  10. IMS Bulk Data Movement
  11. Microsoft SQL Server Bulk Data Movement
  12. Oracle Bulk Data Movement
  13. Sequential File Bulk Data Movement
  14. VSAM Bulk Data Movement
  15. Writing Data with Fault Tolerance
  16. Monitoring and Tuning Options

Bulk Data Movement Guide

Bulk Data Movement Guide

Stopping the PowerExchange Listener

Stopping the PowerExchange Listener

To stop the PowerExchange Listener, use the CLOSE or CLOSE FORCE command on the system where the PowerExchange Listener runs.
You can issue the CLOSE and CLOSE FORCE commands from the command line. Alternatively, you can issue pwxcmd close or closeforce commands from a Linux, UNIX, or Windows system to a PowerExchange Listener running on any system.
The CLOSE or pwxcmd close command stops the PowerExchange Listener after the following subtasks complete:
  • Bulk data movement subtasks
  • CDC subtasks, which stop at the next commit of a unit of work (UOW)
  • PowerExchange Listener subtasks
The CLOSE FORCE or pwxcmd closeforce command forces the cancellation of all user subtasks and then stops the PowerExchange Listener. This option is useful if you have long-running jobs on the PowerExchange Listener. When you specify the FORCE parameter, PowerExchange performs the following processing:
  1. Checks if any PowerExchange Listener subtasks are active.
  2. If active subtasks exist, polls the number of active subtasks every second.
  3. During this wait period, ends any subtasks that are waiting for TCP/IP network input.
  4. Cancels any active subtasks that still remain after 30 seconds elapse.
  5. Stops the PowerExchange Listener.
Do not use the MVS CANCEL command. If you cancel a PowerExchange Listener, its port is not available for use until after TCP/IP completes clean up. If you submit another PowerExchange Listener job before TCP/IP completes this clean up, PowerExchange issues an error message. If you stop a PowerExchange Listener on z/OS while an active PowerExchange Navigator session is using it, PowerExchange issues the same error messages as for the MVS CANCEL command. In this case, exit the PowerExchange Navigator and restart the PowerExchange Listener on z/OS.
The syntax of the commands varies by operating system and method of issuing them.

0 COMMENTS

We’d like to hear from you!