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

ImportFromPC

ImportFromPC

Converts a PowerCenter repository object XML file to a Model repository object XML file. Export PowerCenter repository objects to an XML file. Run the importFromPC command to create a target XML file with objects that you can import into a Model repository.
You can import the target XML file to a Model respository with the infacmd oie ImportObjects command or from the Developer tool. If you use the command line to import the target XML file, ImportFromPC does not assign connections to the Model repository objects in the target XML file. You can assign connections with the infacmd oie ImportObjects command or from the Developer tool.
The infacmd ipc importFromPC command uses the following syntax:
importFromPC <-Release|-rel> release_number [<-SourceFile|-sf> source_file] [<-TargetFile|-tf> target_location] [<-Check|-c>] [<-Db2Type|-dt> default_db2_type] [<-Db2TypesFile|-df> db2_types_file] [<-DefaultLookUpConType|-dl> default_lookup_con_type] [<-LookUpConTypesFile|-lcf> lookup_connection_types_file] [<-ConvertOverriddenProps|-orprops> recreate_transformation_with_overridden_properties_ in_mappings] [<-LogFile|-lf> log_file]
The following table describes infacmd ipc ImportFromPC command options and arguments:
Option
Argument
Description
-Release
-rel
release_number
Required. The version of the Model repository.
-SourceFile
-sf
source_file
Required. The full path to a PowerCenter XML file containing the source objects.
-TargetFile
-tf
target_location
Required. The full path to a target XML file.
-Check
-c
-
Optional. Tests the conversion without creating a target file.
When you test object conversion, you do not require target location.
-Db2Type
-dt
default_db2_type
Optional. The DB2 subsystem type used for conversion.
You can specify either Db2Type or Db2TypesFile, or both. If you specify both Db2Type and Db2TypesFile for IBM DB2 objects, the DB2 source and target that are not listed in the Db2TypesFile gets converted to the Db2Type.
If you do not specify a DB2 subsystem type, the default DB2 subsystem type is used. Default is LUW.
-Db2TypesFile
-df
db2_types_file
Optional. A property file that contains the PowerCenter DB2 source and Db2 subsystem type. You can use a Db2 types file if the Db2 source and target are from different subsystems such as LUW, z/OS, or i/OS.
You can specify either Db2Type or Db2TypesFile, or both. If you specify both Db2Type and Db2TypesFile for IBM DB2 objects, the DB2 source and target that are not listed in the Db2TypesFile gets converted to the Db2Type.
If you do not specify the DB2 subsystem type, the default DB2 subsystem type is used. Default is LUW.
-DefaultLookUpConType
-dl
default_lookup_con_type
Optional. The lookup connection type used for conversion.
You can specify either DefaultLookUpConType or LookUpConTypesFile, or both. If you specify both DefaultLookUpConType and LookUpConTypesFile for the lookup objects, the Lookup transformations that are not listed in the LookUpConTypesFile are converted to the DefaultLookUpConType.
If you do not specify the DefaultLookUpConType for a lookup object during conversion, the default connection type is used. Default is ODBC.
-LookUpConTypesFile
-lcf
lookup_connection_type_file
Optional. A property file that contains the lookup source and the lookup connection type. You can use a lookup connection type file if the lookup objects are from different databases, such as Oracle or IBM DB2.
You can specify either DefaultLookUpConType or LookUpConTypesFile, or both. If you specify both DefaultLookUpConType and LookUpConTypesFile for the lookup objects, the Lookup transformations that are not listed in the LookUpConTypesFile are converted to the DefaultLookUpConType.
If you do not specify the DefaultLookUpConType for a lookup object during conversion, the default connection type is used. Default is ODBC.
-ConvertOverridenprops
-orprops
True|False
Optional. Preserves override properties for reusable PowerCenter source, target, and transformations during conversion.
The command creates nonreusable transformations for PowerCenter transformations with override properties. It also creates reusable data objects for PowerCenter sources and targets with override properties.
Valid values are True or False. Default is True.
-LogFile
-lf
log_file
Optional. Path and file name of the output log file. Default is STDOUT.


Updated April 22, 2019