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.4
  • 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

FILESWITCH Command

FILESWITCH Command

Closes the current condense files if they contain data and switches to a new set of condense files for PowerExchange Condense. If the current condense files do not contain any data, the file switch does not occur.
You can issue a pwxcmd fileswitch command from a Linux, UNIX, or Windows system to a PowerExchange Condense process running on a remote i5/OS or z/OS system.

Syntax

The syntax varies by system.
  • On an i5/OS system, use the following syntax: 
    SNDPWXCMD CMDHDLRLIB(
    condlib
    ) DTLCMD(FILESWITCH)
    The
    condlib
     variable is the name of the library that contains the condense files, which you specified in the COND_DIR parameter of the CAPTPARM configuration member.
  • On an z/OS system, use the following syntax: 
    F 
    task_name
    ,FILESWITCH
    The
    task_name
     variable is the name of the PowerExchange Condense started task or batch job for which you want to switch to a new set of condense files. Usually, PowerExchange Condense runs as a started task.

Usage Notes

You can use this command to make change data in the current condense files available for extraction before the next file switch is due to occur. For example, you want to extract change data hourly from condense files on z/OS. Set the FILE_SWITCH_CRIT and FILE_SWITCH_VAL parameters in the CAPTPARM configuration file such that a file switch occurs after every one million record updates. Then include the FILESWITCH command as part of a batch job to perform an automated file switch hourly, before extraction processing runs.
If you perform both partial and full condense processing in a single Condense job, PowerExchange uses separate sets of condense files for the partial and full condense operations. If you issue the FILESWITCH command, a file switch occurs for both sets of condense files.

Example Output

The FILESWITCH command produced the following example output on z/OS: 
PWX-26011 Command handler received command "FILESWITCH"
PWX-06460 Command Handler: New File Switch requested.
PWX-06415 Condense: Condense completed. Total Records=34, Data=16, UOWs =12
PWX-06422 Condense: Received FILESWITCH request.
PWX-06419 Condense: Doing file switch. Records=34 Reason=FILESWITCH request Cdcts=2 CPU: TotMs=20558768 Diff=20558768
PWX-06418 Condense: Closed file ABCD.D1010QB.CND.CF160524.T1716003
PWX-06136 Checkpoint taken to file=ABCD.D1010QB.CHKPTV0 time=16/05/24 17:17:04
PWX-06420 Condense: Checkpoint done. Sequence=000027B4415F00000000000027B4415F00000000 
          PowerExchange Logger=D8C1C8D3404000001C6E83F400000000
PWX-06421 Condense: 16/05/24 17:17:04 Starting wait on commands for 268 seconds
0 COMMENTS
We’d like to hear from you!