Preface
Introduction to PowerExchange
- PowerExchange Overview
- PowerExchange Components
DBMOVER Configuration File
Netport Jobs
PowerExchange Message Logs and Destination Overrides
- PowerExchange Message Logs
  - PowerExchange Message Log File
  - PowerExchange Alternative Log Files
    - Determining the Size of the Alternative Log Data Sets on z/OS
    - Allocation Options for Alternative Log Data Sets on z/OS
- PowerExchange Message Destination Overrides
  - DTLMSGO File and Statements
SMF Statistics Logging and Reporting
PowerExchange Security
Secure Sockets Layer Support
PowerExchange Alternative Network Security
PowerExchange Nonrelational SQL
DTLDESCRIBE Metadata
- DTLDESCRIBE Metadata Overview
  - DTLDESCRIBE Metadata Syntax
  - DTLDESCRIBE Qualifiers
PowerExchange Globalization
Using the PowerExchange ODBC Drivers
PowerExchange Datatypes and Conversion Matrix
- PowerExchange Datatype Conversions
- ODBC and PowerExchange Datatype Equivalencies
Appendix A: DTL__CAPXTIMESTAMP Time Stamps
- Time Stamps That Are Reported in the DTL__CAPXTIMESTAMP Field by Data Source
Appendix B: PowerExchange Glossary
- Glossary of Terms

Reference Manual

10.5.4
- 10.5.6
- 10.5.5
- 10.5.3
- 10.5.2
- 10.5.1
- 10.5
- 10.4.1
- 10.4.0 HotFix 1
- 10.4.0

Back Next

TRACING_PARENT_CHECK_SECONDS Statement

The TRACING_PARENT_CHECK_SECONDS statement defines how frequently the existence of the parent is checked through the getppid() function.

IBM i, Windows, UNIX

TRACING_PARENT_CHECK_SECONDS={30|seconds}

Valid values are 0 to 86400. Default is 30 seconds.

This statement should be used only if PowerExchange alternative logging is enabled by the TRACING statement. Specify this statement only at the direction of Informatica Global Customer Support.

Rename Saved Search

Table of Contents

Reference Manual

Reference Manual

TRACING_PARENT_CHECK_SECONDS Statement

TRACING_PARENT_CHECK_SECONDS Statement