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
  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. DTL__CAPXTIMESTAMP Time Stamps
  15. PowerExchange Glossary

Notational Conventions for DBMOVER Statements

Notational Conventions for DBMOVER Statements

The syntax descriptions of the DBMOVER statements use notational conventions.
The following table describes the notational conventions used in the DBMOVER statement syntax and provides examples:
Notation
Description
italic
Italic indicates variables that you must replace with a name or value.
For example:
ADABAS_DEFAULT_DBID=
dbid
{ }
Single braces enclose alternative entries. Use only one of the entries. Do not type the braces when you enter the option.
For example:
ABEND_SW={
N
|Y}
[ ]
Brackets surround optional parameters for a statement. Do not type the brackets when you enter the parameter.
For example:
DB2ID=(
db2_subsystem
[,
plan
][,
module_name
])
|
A vertical bar indicates a mutually exclusive choice. When used with brackets, enter one or none of the items. When used with braces, you must enter one of the items.
For example:
CREDENTIALS_CASE={A|
D
|S}
_
Underline indicates the default used if you do not specify any of the alternatives.
For example:
ABEND_SW={
N
|Y}
,
A comma separates the parameters on a statement.
For example:
DB2ID=(
db2_subsystem
[,
plan
][,
module_name
])
...
An ellipsis indicates additional parameters that do not appear in the syntax.
For example:
TYPE=(AS4J, ... )