Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Common Content for Data Engineering 10.5.2
  • All Products

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 autotune Command Reference
  10. Infacmd bg Command Reference
  11. infacmd ccps Command Reference
  12. infacmd cluster Command Reference
  13. infacmd cms Command Reference
  14. infacmd dis Command Reference
  15. Infacmd dis Queries
  16. infacmd dp Command Reference
  17. infacmd idp Command Reference
  18. infacmd edp Command Reference
  19. Infacmd es Command Reference
  20. infacmd ics Command Reference
  21. infacmd ipc Command Reference
  22. infacmd isp Command Reference
  23. infacmd ldm Command Reference
  24. infacmd mas Command Reference
  25. infacmd mi Command Reference
  26. infacmd mrs Command Reference
  27. infacmd ms Command Reference
  28. infacmd oie Command Reference
  29. infacmd ps Command Reference
  30. infacmd pwx Command Reference
  31. infacmd roh Command Reference
  32. infacmd rms Command Reference
  33. infacmd rtm Command Reference
  34. infacmd sch Command Reference
  35. infacmd search Command Reference
  36. infacmd sql Command Reference
  37. infacmd tdm Command Reference
  38. infacmd tools Command Reference
  39. infacmd wfs Command Reference
  40. infacmd ws Command Reference
  41. infacmd xrf Command Reference
  42. infacmd Control Files
  43. infasetup Command Reference
  44. pmcmd Command Reference
  45. pmrep Command Reference
  46. Working with filemanager
  47. Working with pmrep Files

Command Reference

Command Reference

Back Next

genReuseReportFromPC

genReuseReportFromPC

Generates a report that estimates how many PowerCenter mappings can be reused in the Model repository for a native or Hadoop environment. You can generate the report as a PDF or Excel file.
If you generate the report as an Excel file, click
Enable Content
 in the message bar to load all sheets.
Before you run the infacmd ipc genReuseReportFromPC command, verify that you complete the following tasks:
  • Configure the required environment variables for the pmrep command.
  • If you use a Linux environment, grant the read, write, and execute permissions on each release folder located in the following directory:
    <informatica server installation directory>/tools/pcutils
The infacmd ipc genReuseReportFromPC command uses the following syntax: 
genReuseReportFromPC
								
<-RepositoryName|-r> Pc_Repository_Name
        
<-HostName|-h> Pc_Domain_HostName
        
<-PortNumber|-o> Pc_Domain_PortNumber
        
[<-UserName|-n> Domain_UserName]
        
[<-Password|-x> Domain_Password]
       
[<-SecurityDomain|-s> Pc_Repository_Security_domain]
        
<-folderNames|-f> Pc_Folder_Names
        
<-SrcRelease|-srel> Pc_Release_version
        
[<-targetRelease|-trel> Target_Release_version]
        
[<-CodePage|-cp>  Pc_Repository_code_page]
        
<-targetDir|-td> Target_Directory

<-authenticationType|-at> authentication_Type
        
[<-LogFile|-lf> Log_file_Name]

[<-Font> Font_to_use_for_PDF]

[<-ExecutionEnvironment|-execMode> Execution_Environment]

[<-BlockSize> Block_Size]
The following table describes infacmd ipc genreusereportfrompc command options and arguments:
Option
Argument
Description
-RepositoryName
-r
Pc_Repository_Name
Required. The PowerCenter repository name.
-HostName
-h
Pc_Domain_HostName
Required. The host name of the PowerCenter repository.
-PortNumber
-o
Pc_Domain_PortNumber
Required. The port number of the gateway node.
-UserName
-n
Domain_UserName
Optional. User name of the PowerCenter domain. If you do not enter a user name, the command uses the value in the INFA_DEFAULT_DOMAIN_USER environment variable.
Password
-x
Domain_Password
Optional. Password of the PowerCenter domain. If you do not enter a user name, the command uses the value in the INFA_DEFAULT_DOMAIN_PASSWORD environment variable.
-SecurityDomain
-s
Pc_Repository_Security_domain
Required if you use LDAP authentication. Name of the security domain that the user belongs to. If you do not enter a security domain, the command uses the value in the INFA_DEFAULT_SECURITY_DOMAIN environment variable.
You can use Native, LDAP, or SSO as the value.
The default value is Native.
-folderNames
-f
Pc_Folder_Names
Required. PowerCenter folders that contain the objects to be reused. The folder names can contain expressions. The folder names can contain * as expressions.
If you use the Linux environment, you cannot use $ in the folder name.
-SrcRelease
-srel
Pc_Release_version
Required. The release associated with the PowerCenter repository.
Enter the version in the following format: 
10.x.x
For example, enter a version in the following format: 
10.2.0
-targetRelease
-trel
Target_Release_version
Optional. The release associated with the Model repository. If you do not enter a version, the command uses the product version. You can enter versions from 10.0.0 and above.
Enter the version in the following format: 
10.x.x
For example, enter a version in the following format: 
10.2.1
-CodePage
-cp
Pc_Repository_code_page
Optional. Code page of the PowerCenter repository. Default is UTF-8.
-targetDir
-td
Target_Directory
Required. Location of the target directory on the machine on which the infacmd client and server runs. You must have the read, write, and execute permissions on the target directory folder.
For example, enter the infacmd client location in the following format: 
installed_location_of_client\clients\DeveloperClient\infacmd
For example, enter the infacmd server location in the following format: 
installed_location_of_server\isp\bin
On a Linux machine, you cannot use $ in the target directory name.
authenticationType
-at
authentication_Type
Required. The type of user authentication for the domain. Enter one of the following values: LDAP, Native, or Kerberos Single Sign On.
-LogFile
-lf
Log_file_Name
Optional. Name of the generated log file. If you do not enter a name, the command prints the logs on the console. Uses the value of file_path/file_name.
If you enter a file name, the log file with the same name appears in the infacmd folder.
If you enter a directory path that is not valid, the log file with the path name appears in the infacmd folder. For example, if you enter x as the directory path, the log file named x appears in the infacmd folder.
-Font
Font_to_use_for_PDF
Optional. The location for the font file to have Unicode characters in the report.
-ExecutionEnvironment
-execMode
Execution_Environment
Optional. The run-time engine in the Hadoop environment. The report validates mappings based on the run-time engine that you choose. You can use Blaze or Spark as the value. If you do not enter a value, the report will run against all engines and include only the engine with the fewest errors.
-BlockSize
Block_Size
Optional. The number of mappings that you want to run the infacmd ipc genReuseReportFromPC command against. If you do not enter a value, the report runs and converts all the mappings within each folder at a time. When the memory required to run the command is unavailable, use the ‑BlockSize option to control the number of mappings instead of running the command on all the mappings in the repository.
0 COMMENTS
We’d like to hear from you!