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
  • PowerCenter 10.4.1
  • All Products

Table of Contents

Search

  1. Preface
  2. Understanding Pipeline Partitioning
  3. Partition Points
  4. Partition Types
  5. Pushdown Optimization
  6. Pushdown Optimization and Transformations
  7. Real-time Processing
  8. Commit Points
  9. Row Error Logging
  10. Workflow Recovery
  11. Stopping and Aborting
  12. Concurrent Workflows
  13. Grid Processing
  14. Load Balancer
  15. Workflow Variables
  16. Parameters and Variables in Sessions
  17. Parameter Files
  18. FastExport
  19. External Loading
  20. FTP
  21. Session Caches
  22. Incremental Aggregation
  23. Session Log Interface
  24. Understanding Buffer Memory
  25. High Precision Data

Advanced Workflow Guide

Advanced Workflow Guide

Back Next

Guidelines for Creating Parameter Files

Guidelines for Creating Parameter Files

Use the following rules and guidelines when you create parameter files:
  • List all session parameters.
     Session parameters do not have default values. If the Integration Service cannot find a value for a session parameter, it may fail the session, take an empty string as the default value, or fail to expand the parameter at run time. Session parameter names are not case sensitive.
  • List all necessary mapping parameters and variables.
    Mapping parameter and variable values become start values for parameters and variables in a mapping. Mapping parameter and variable names are not case sensitive.
  • Enter folder names for non-unique session names.
     When a session name exists more than once in a repository, enter the folder name to indicate the location of the session.
  • Precede parameters and variables in mapplets with the mapplet name.
     Use the following format:
    mapplet_name.parameter_name=value
mapplet2_name.variable_name=value
  • Use multiple parameter files.
     You assign parameter files to workflows, worklets, and sessions individually. You can specify the same parameter file for all of these tasks or create multiple parameter files.
  • When defining parameter values, do not use unnecessary line breaks or spaces.
     The Integration Service interprets additional spaces as part of a parameter name or value.
  • Use correct date formats for datetime values.
     Use the following date formats for datetime values:
    • MM/DD/RR
    • MM/DD/YYYY
    • MM/DD/RR HH24:MI
    • MM/DD/YYYY HH24:MI
    • MM/DD/RR HH24:MI:SS
    • MM/DD/YYYY HH24:MI:SS
    • MM/DD/RR HH24:MI:SS.MS
    • MM/DD/YYYY HH24:MI:SS.MS
    • MM/DD/RR HH24:MI:SS.US
    • MM/DD/YYYY HH24:MI:SS.US
    • MM/DD/RR HH24:MI:SS.NS
    • MM/DD/YYYY HH24:MI:SS.NS
      You can use the following separators: dash (-), slash (/), backslash (\), colon (:), period (.), and space. The Integration Service ignores extra spaces. You cannot use one- or three-digit values for year or the “HH12” format for hour.
  • Do not enclose parameter or variable values in quotes.
     The Integration Service interprets everything after the first equals sign as part of the value.
  • Use a parameter or variable value of the proper length for the error log table name prefix.
     If you use a parameter or variable for the error log table name prefix, do not specify a prefix that exceeds 19 characters when naming Oracle, Sybase, or Teradata error log tables. The error table names can have up to 11 characters, and Oracle, Sybase, and Teradata databases have a maximum length of 30 characters for table names. The parameter or variable name can exceed 19 characters.
0 COMMENTS
We’d like to hear from you!