Table of Contents

Search

  1. Preface
  2. Command Line Programs and Utilities
  3. Installing and Configuring Command Line Utilities
  4. Using the Command Line Programs
  5. Environment Variables for Command Line Programs
  6. Using infacmd
  7. infacmd as Command Reference
  8. infacmd aud Command Reference
  9. Infacmd bg Command Reference
  10. infacmd cluster Command Reference
  11. infacmd cms Command Reference
  12. infacmd dis Command Reference
  13. Infacmd es Command Reference
  14. infacmd ihs Command Reference
  15. infacmd ipc Command Reference
  16. infacmd isp Command Reference
  17. infacmd ldm Command Reference
  18. infacmd mrs Command Reference
  19. infacmd ms Command Reference
  20. infacmd oie Command Reference
  21. infacmd ps Command Reference
  22. infacmd pwx Command Reference
  23. infacmd rms Command Reference
  24. infacmd rtm Command Reference
  25. infacmd sch Command Reference
  26. infacmd search Command Reference
  27. infacmd sql Command Reference
  28. infacmd tdm Command Reference
  29. infacmd wfs Command Reference
  30. infacmd ws Command Reference
  31. infacmd xrf Command Reference
  32. infacmd Control Files
  33. infasetup Command Reference
  34. pmcmd Command Reference
  35. pmrep Command Reference
  36. Working with pmrep Files

Command Reference

Command Reference

createdatamaps

createdatamaps

Creates data maps for bulk data movement operations.
Use the createdatamaps command to generate data maps for IMS, SEQ, and VSAM data sources from the command line. This command provides an alternative to using the PowerExchange Navigator in certain cases and allows you to generate or regenerate data maps noninteractively.
If the command fails with a Java memory error, increase the system memory available for infacmd. To increase the system memory, set the -Xmx value in the ICMD_JAVA_OPTS environment variable. For more information, see ICMD_JAVA_OPTS.
The infacmd pwx createdatamaps command uses the following syntax:
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.
For more information about the createdatamaps command, see the PowerExchange Utilities Guide.


Updated April 22, 2019