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.1
  • 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 rms Command Reference
  30. infacmd rtm Command Reference
  31. infacmd sch Command Reference
  32. infacmd search Command Reference
  33. infacmd sql Command Reference
  34. infacmd tdm Command Reference
  35. infacmd wfs Command Reference
  36. infacmd ws Command Reference
  37. infacmd xrf Command Reference
  38. infacmd Control Files
  39. infasetup Command Reference
  40. pmcmd Command Reference
  41. pmrep Command Reference
  42. Working with pmrep Files

Command Reference

Command Reference

Back Next

Run

Run

Opens a script file containing multiple
pmrep
 commands, reads each command, and runs them. If the script file is UTF-8 encoded, you must use the -u option and the repository code page must be UTF-8. If you run a UTF-8 encoded script file that includes the Connect command against a repository that does not have a UTF-8 code page, the Run command will fail.
If the script file is not UTF-8 encoded, omit the -u option. If you use the -o option and the -u option,
pmrep
 generates the output file in UTF-8. If you use the -o option and omit the -u option,
pmrep
 generates the output file based on the system locale of the machine where you run
pmrep
.
The command returns “run successfully completed” or returns “run failed” message. The run might fail if the Repository Service cannot open the script file or output file.
The Run command uses the following syntax: 
run 

-f <script_file_name>

[-o <output_file_name>]

[-e (echo commands)]

[-s (stop at first error)]

[-u (UTF-8 encoded script file and output file)]
The following table describes
pmrep
 Run options and arguments:
Option
Argument
Description
-f
script file name
Required. Name of the script file.
-o
output file name
Optional. Name of the output file. This option writes all messages generated by the commands in the script file into the output file. If you use the -u option and the -o option,
pmrep
 generates a UTF-8 encoded output file. If you use the -o option without the -u option,
pmrep
 encodes the output file based on the system locale of the machine running
pmrep
.
-e
-
Optional. Commands are echoed back to the script.
-s
-
Optional. Stops running the script after the first error.
-u
-
Optional. Encodes the output file in UTF-8 format. If you use the -u option and the -o option,
pmrep
 also encodes the output file in UTF-8 format. Use this option only if the repository code page is UTF-8.
0 COMMENTS
We’d like to hear from you!