Table of Contents

Search

  1. Preface
  2. Introduction to PowerExchange
  3. DBMOVER Configuration File
  4. Netport Jobs
  5. PowerExchange Message Logs and Destination Overrides
  6. SMF Statistics Logging and Reporting
  7. PowerExchange Security
  8. Secure Sockets Layer Support
  9. PowerExchange Alternative Network Security
  10. PowerExchange Nonrelational SQL
  11. PowerExchange Globalization
  12. Using the PowerExchange ODBC Drivers
  13. PowerExchange Datatypes and Conversion Matrix
  14. Appendix A: DTL__CAPXTIMESTAMP Time Stamps
  15. Appendix B: PowerExchange Glossary

DB2 for z/OS DBMOVER Statements

DB2 for z/OS DBMOVER Statements

PowerExchange provides DBMOVER statements specific to DB2 for z/OS data sources.
The following table briefly defines the DBMOVER statements specific to DB2 for z/OS data sources and provides cross-references to the complete description of the statements:
Statement
Description
Reference
DB2_ERRORFILE
Specifies the name of the user-customized SQL error file that PowerExchange uses for DB2 bulk data movement operations.
DB2CODEPAGE
Defines the single-byte, mixed, and graphics CCSID values that PowerExchange uses to process bulk data from the specified DB2 subsystem.
DB2DEF_ENCODING
Defines the default encoding scheme that PowerExchange assigns to any DB2 columns without an encoding scheme when you create a DB2 data map.
DB2ID
Defines the DB2 plan and the PowerExchange access method module that PowerExchange uses to process bulk data from the specified DB2 subsystem.
DB2PLAN
Defines the DB2 plan that PowerExchange uses for bulk data movement processing.
LOADCTLFILE
Specifies the PDS data set that contains the control card template member for DB2 for z/OS LOAD utility batch jobs.
LOADJOBFILE
Specifies the PDS data set that contains the JCL template member for DB2 for z/OS LOAD utility and CA IDMS/DB metadata retrieval batch jobs.
MVSDB2AF
Specifies which DB2 for z/OS attachment facility PowerExchange uses for DB2 bulk data movement operations.
SESSID
Specifies the value to use as the DB2 Correlation ID for DB2 requests.

0 COMMENTS

We’d like to hear from you!