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 HotFix 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 idp Command Reference
  16. infacmd edp 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

Entering Options and Arguments

Entering Options and Arguments

Each command line program requires a set of options and arguments. These include user name, password, domain name, and connection information.
Use the following rules when you enter command options and arguments:
  • To enter options, type a hyphen followed by one letter, two letters, or a word, depending on the program syntax for the command.
    For example, the pmrep Connect command uses a single letter option for the repository name: 
    Connect 
    -r
     <repository_name>
  • Enter options in any order.
  • If any option that you specify from the command line contains spaces, enclose the option in double quotes.
  • The first word after the option is the argument.
  • Most options require arguments.
    You must separate options from arguments with a single space when using pmcmd or infacmd. You do not have to separate options from arguments when using pmrep.
  • If any argument contains more than one word, enclose the argument in double quotes.
    For pmrep and pmcmd, you can also use single quotes.
    Unmatched quotes result in an error.
    For infacmd or pmcmd, the command line programs ignore quotes that do not enclose an argument.
  • If an argument is in the format
    option_name=value
    , and the value contains both a space and an equal sign (=), then you must precede the equal sign with a backslash.
    For example, an argument contains the option
    DatabaseUser
    , and the database user name is
    a#v%5^=! !
    . Use the following format when you enter the argument:
    DBUser=a#v%5^\=! !
  • To update connection options values with existing environment variables, use an escape character before any dollar sign ($) with any shell other than CSH.
  • For pmrep, you can use space characters in an argument. To specify an argument containing space characters, enclose the argument with either single or double quote characters. When you use either single or double quotation marks in the argument, you must precede the required quotation marks with a backslash.
0 COMMENTS
We’d like to hear from you!