Table of Contents

Search

  1. Preface
  2. Introduction to PowerExchange Utilities
  3. createdatamaps - Data Map Creation Utility
  4. DTLCCADW - Adabas PCAT Utility
  5. DTLCUIML - IMS Log Marker Utility
  6. DTLINFO - Release Information Utility
  7. DTLREXE - Remote Execution Utility
  8. DTLUAPPL - Restart Token Utility
  9. DTLUCBRG - Batch Registration Utility
  10. DTLUCDEP - CDEP Maintenance Utility
  11. DTLUCSR2 - IDMS SR2 and SR3 Records Utility
  12. DTLUCUDB - DB2 for Linux, UNIX, and Windows CDC Utility
  13. DTLULCAT and DTLULOGC - IDMS Log Catalog Utilities
  14. DTLURDMO - Data Map Utility
  15. DTLUTSK - Task Control Utility
  16. EDMLUCTR - Log Scan and Print Utility
  17. EDMXLUTL - Event Marker Utility
  18. HOSTENT - TCP/IP Address Reporter Utility
  19. PWXCATMY - MySQL Catalog Utility
  20. PWXUCCLPRT - Print Log Summary Utility
  21. PWXUCDCT - Logger for Linux, UNIX, and Windows Utility
  22. PWXUCREG - Capture Registration Suspend Utility
  23. PWXUCRGP - Capture Registrations Print Utility
  24. PWXUDMX - Data Maps Update Time ECSA Memory Utility
  25. PWXUGSK - SSL Reporting Utility for z/OS
  26. PWXUMAP - Map List Utility
  27. PWXUSSL - PowerExchange SSL Reporting Utility

createdatamaps Command Syntax

createdatamaps Command Syntax

The infacmd pwx createdatamaps command uses the following syntax:
infacmd pwx createdatamaps [<-pwxLocation|-loc> pwx_location] [<-pwxUserName|-pun> pwx_user_name] [<-pwxPassword|-ppd> pwx_password] [<-pwxEncryptedPassword|-epwd> pwx_encrypted_password] [<-datamapOutputDir|-dod> datamap_output_directory] [<-replace|-r> replace_existing_datamaps <-controlFile|-cf> file_path_for_control_file [<-logFile|-lf> file_path_for_log_file] [<-verbosity|-v> logging_verbosity]
The following table describes infacmd pwx createdatamaps options and arguments:
Option
Argument
Description
-pwxLocation
-loc
pwx_location
Optional. The location of the data source as specified in a NODE statement in the PowerExchange dbmover configuration file. If pwxLocation is not specified, the createdatamaps utility accesses the copybook and DBD metadata on the local file system.
If you configure the control file to find record IDs, pwxLocation is required.
-pwxUserName
-pun
pwx_user_name
Optional. The user ID for connecting to the PowerExchange Listener, if pwxLocation is specified.
-pwxPassword
-ppd
pwx_password
Optional. Password for connecting to the PowerExchange Listener, if pwxLocation is specified.
Instead of a password, you can enter a valid PowerExchange passphrase. Passphrases for accessing a PowerExchange Listener on z/OS can be from 9 to 128 characters in length and can contain the following characters:
  • Uppercase and lowercase letters
  • The numbers 0 to 9
  • Spaces
  • The following special characters:
    ’ - ; # \ , . / ! % & * ( ) _ + { } : @ | < > ?
    The first character is an apostrophe.
Passphrases cannot include single quotation marks (‘), double quotation marks (“), or currency symbols.
If a passphrase contains spaces, you must enclose it with double-quotation marks ("), for example,
"This is an example passphrase"
. If a passphrase contains special characters, you must enclose it with triple double-quotation characters ("""), for example,
"""This passphrase contains special characters ! % & *."""
. If a passphrase contains only alphanumeric characters without spaces, you can enter it without delimiters.
On z/OS, a valid RACF passphrase can be up to 100 characters in length. PowerExchange truncates passphrases longer than 100 characters when passing them to RACF for validation.
To use passphrases, ensure that the PowerExchange Listener runs with a security setting of SECURITY=(1,N) or higher in the DBMOVER member. For more information, see "SECURITY Statement" in the
PowerExchange Reference Manual
.
-pwxEncryptedPassword
-epwd
pwx_encrypted_password
Optional. Encrypted password for connecting to the PowerExchange Listener, if pwxLocation is specified.
If the PowerExchange Listener runs on a z/OS or i5/OS system, you can enter an encrypted PowerExchange passphrase instead of an encrypted password. Do not encrypt a passphrase that contains characters that are not valid, such as double-quotation marks, single quotation marks, or currency symbols.
-datamapOutputDir
-dod
datamap_output_directory
Optional. The local file directory to which to write the output data maps. Default is the current working directory.
-replace
-r
replace_existing_datamaps
Optional. Specifies whether to replace existing data maps.
If replace=Y, replaces any data maps in datamap_output_directory that have the same name as the data map that you are creating.
If replace=N, skips the creation of a data map if a data map with the same name already exists in datamap_output_directory.
Default is N.
-controlFile
-cf
file_path_for_control_file
Required. Path and file name of the control file that controls data map generation.
-logFile
-lf
file_path_for_log_file
Optional. Path and file name of the output log file. Default is STDOUT.
-verbosity
-v
logging_verbosity
Optional. Verbosity for log files. Default is INFO. Valid values:
  • DEBUG. Most detailed logging. Might show stack traces.
  • INFO. Informational messages.
  • WARN. Indicates a potential problem.
  • ERROR. Indicates a failure. Processing continues.
  • FATAL. Indicates a fatal condition. Process terminates.
The PowerExchange node name and credentials are optional. If you do not include the pwxLocation option, the command accesses the local file system directly to read metadata. In this case, PowerExchange does not need to be installed on the machine on which you run createdatamaps.

0 COMMENTS

We’d like to hear from you!