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.2.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 dps Command Reference
  16. infacmd edl Command Reference
  17. Infacmd es Command Reference
  18. infacmd ihs Command Reference
  19. infacmd ipc Command Reference
  20. infacmd isp Command Reference
  21. infacmd ldm Command Reference
  22. infacmd mas Command Reference
  23. infacmd mi Command Reference
  24. infacmd mrs Command Reference
  25. infacmd ms Command Reference
  26. infacmd oie Command Reference
  27. infacmd ps Command Reference
  28. infacmd pwx Command Reference
  29. infacmd roh Command Reference
  30. infacmd rms Command Reference
  31. infacmd rtm Command Reference
  32. infacmd sch Command Reference
  33. infacmd search Command Reference
  34. infacmd sql Command Reference
  35. infacmd tdm Command Reference
  36. infacmd tools Command Reference
  37. infacmd wfs Command Reference
  38. infacmd ws Command Reference
  39. infacmd xrf Command Reference
  40. infacmd Control Files
  41. infasetup Command Reference
  42. pmcmd Command Reference
  43. pmrep Command Reference
  44. Working with pmrep Files

Command Reference

Command Reference

Back Next

Creating a Persistent Input File Manually

Creating a Persistent Input File Manually

If you want to run
pmrep
 commands against a set of objects that you cannot identify through commands such as ExecuteQuery, you can manually create an input file.
Use the following rules and guidelines when you create a persistent input file:
  • Enter “none” for the encoded ID. The
    pmrep
     commands get the object information from the other arguments in the records.
  • For source objects, enter the object name as <DBD_name>.<source_name>.
  • For objects, such as mappings, that do not have a sub_type, enter “none” as object_subtype, or leave it blank. For more information about valid transformations and task types, see Listing Object Types.
  • For versioned repositories, enter the version number of the object you want, or enter “LATEST” to use the latest version of the object.
  • For non-versioned repositories, leave the version_number argument blank.
  • For object types, such as targets, that are not reusable or non-reusable, drop the argument.
  • You cannot include non-reusable objects. You can specify the reusable parent of the non-reusable object.
    For example, you want to list the object dependencies for a non-reusable Filter transformation. You can specify the mapping that is the parent object of the transformation: 
    none,CAPO,m_seqgen_map,mapping,none,1,reusable
    The mapping m_seqgen_map is the reusable parent of the Filter transformation. The command runs successfully when you specify the reusable parent.
When you use a manually created persistent input file, the Repository Service returns a message indicating that the ID is not valid. This is an informational message. The Repository Service recognizes that this is a manually created input file and can process the command with “none” as the ID.
0 COMMENTS
We’d like to hear from you!