Hi, I'm Bolo!
What would you like to know?
ASK BOLOPreview
Please to access Bolo.
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.3
  • All Products

Table of Contents

Search

  1. Preface
  2. Introduction to PowerExchange Commands
  3. Adabas Log-Based ECCR Commands
  4. Batch VSAM ECCR Commands
  5. CICS/VSAM ECCR Commands
  6. Datacom Table-Based ECCR Commands
  7. DB2 for z/OS ECCR Commands
  8. IDMS Log-Based ECCR Commands
  9. IMS Synchronous ECCR Commands
  10. IMS Log-Based ECCR Commands
  11. PowerExchange Agent Commands
  12. PowerExchange Condense Commands
  13. PowerExchange Listener Commands
  14. PowerExchange Logger for z/OS Commands
  15. PowerExchange Logger for Linux, UNIX, and Windows Commands
  16. pwxcmd Commands

Command Reference

Command Reference

Back Next

SHUTCOND Command

SHUTCOND Command

Stops the PowerExchange Logger for Linux, UNIX, and Windows in a controlled manner after initiating and completing a final processing cycle. The final processing cycle enables the PowerExchange Logger to capture all of the changes made up to point when the command is issued.
After the processing cycle completes, the PowerExchange Logger performs the following actions:
  • Closes open log files.
  • Writes information to the CDCT file, including restart and sequence tokens.
  • Closes the CAPI.
  • Stops the Writer and Command Handler subtasks.
  • Ends the pwxccl program.
  • Reports CPU usage.
  • Reports summary Logger monitoring statistics if the STATS=(MONITOR) parameter is specified in the PowerExchange Logger configuration file, pwxccl.cfg, either with or without the optional
    interval
     subparameter.
The message output from this command is displayed on screen and written to the PowerExchange message log.

Syntax

Use the following syntax to issue the command from the command line against a PowerExchange Logger process that is running in foreground mode: 
SHUTCOND
Alternatively, use the pwxcmd program to issue the shutcond command. You must use pwxcmd if you run the PowerExchange Logger in background mode.

Usage Notes

Use this command to stop the PowerExchange Logger if a processing cycle has not run recently.

Example Output

The following example SHUTCOND output indicates the order in which PowerExchange Logger subtasks and processing stop: 
PWX-26011 Command handler received command "SHUTCOND"
PWX-06467 Command Handler: Setting Condense to shut down on running out of data.
PWX-33289 Condense: Condense completed. Total Records=3036, Inserts=1404, Updates=0,Deletes=1404, 
UOWs=228

PWX-06416 Condense: Shutting down because Single Condense run completed
PWX-36940 Closed file c:\pwx\capture/condenseO.CND.CP160819.T1036001.
PWX-36941 Records 2808. Commits 168. End sequence 00000833A3460000000000000833A34600000000.
PWX-33256 CCLWTR File switch complete. Current restart tokens: Sequence 00000833A3460000000000000833A34600000000 Restart D4C9C7D34040000008166DE000000000.
PWX-33278 Total Records 3036. Inserts 1404. Updates 0. Deletes 1404. UOWs 228. Bytes 652056
PWX-33279 CPU total 670804. This file total 670804. CAPI Reads 156002. Writing file 62400. Other 452402
 
PWX-33274 CPU Total 670804. CAPI Read 156002. Writing 62400. File switching 0. Other 452402

PWX-06414 Condense: Closing down CAPI 
PWX-10780 CAPI: INFO: Extraction return counts: no data 3, commits 229, inserts 1404, updates 0, deletes 1404.
PWX-10781 CAPI: INFO: Extraction subordinate read counts: no data 0, commits 232, inserts 1548, updates 0, deletes 1404, backouts 0.                                                                                     
PWX-10782 CAPI: INFO: Extraction resource maximums: memory cache 32 KB, spill files 0.    
PWX-10746 CAPI: INFO: Last data returned: timestamp 2015/06/15 10:34:19, 
sequence 00000833A3460000000000000833A34600000000.
PWX-10743 CAPI: INFO: No noteworthy transactions.
PWX-10749 CAPI: INFO: + Current subordinate sequence number 00000833A61A00000000.
PWX-33304 Connection: 10.43.203.106:62818, Type: TASK_CNTL, Task ID: 0, Operation timeout: (-) secs, Heartbeat interval: 30 secs, Session: (-) 
PWX-06453 Command Handler: shutting down. 
PWX-33255 CCLWTR Restart tokens at run termination: Sequence 00000833A3460000000000000833A34600000000 Restart D4C9C7D34040000008166DE000000000.
PWX-33221 CCLWTR closing after a SHUTDOWN request.
PWX-06110 Unloaded module 2 (CCL WRITER).
PWX-06454 Command Handler: has stopped.
PWX-06110 Unloaded module 1 (COMMAND_HANDLER).
PWX-06060 Controller: subtask Condense ended.
PWX-06060 Controller: subtask Command Handler ended.
PWX-06107 Controller: All subtasks shut down.
PWX-25803 Process pwxccl pid 9064 unlocked file c:\pwx\capture/condenseO_loggerfiles_lockfile.lck
PWX-25803 Process pwxccl pid 9064 unlocked file c:\pwx\capture\CDCT_instance_IME0_lockfile.lck
 
PWX-33254 pwxccl ended. return code 0
PWX-33274 CPU Total 686404. CAPI Read 156002. Writing 62400. File switching 0. Other 468002

PWX-00723 Command <Shutdown stats> succeeded
PWX-37130   PWXCCL pid = 9064       Writer status = Shutting down
PWX-37134   CPU Time =    0:00:00.686404
PWX-37131   Memory  (Current/Total/Maximum)
PWX-37132    Controller: (476/477/1853) KB    Command Handler: (476/477/1853) KB    Writer: (0/0/0) KB
PWX-37105    Total Memory 16468 KB
PWX-37135   Status  9064                  Totals  I=000000001404 U=000000000000 D=000000001404 C=000000000228 Total=000000003036
PWX-37136    CurrFileOpened : 2016-08-19 10:37:47 I=000000000000 U=000000000000 D=000000000000 C=000000000000 Total=000000000000
PWX-37137     Active Cycle  : 2016-08-19 10:37:47 I=000000001404 U=000000000000 D=000000001404 C=000000000228 Total=000000003036
For this example, the pwxccl.cfg file specifies VERBOSE=Y and STATS=(MONITOR). In the output, the monitoring messages are highlighted in bold.
If the PowerExchange Logger runs on a SUSE Linux version 11 machine, the PWX-37105 message incorrectly reports 0 KB as the total amount of memory that the Logger used. This problem does not occur if the Logger runs on a later SUSE Linux version.
0 COMMENTS
We’d like to hear from you!