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

ApplyLabel

ApplyLabel

Applies a label to an object or a set of objects in a folder. If you enter a folder name, all the objects in the folder receive the label. You can apply the label to dependent objects. If you use the
dependency_object_types
 option,
pmrep
 labels all dependent objects. To apply a label to selected dependent objects, separate each object type name by a comma with no spaces between them on the command line.
Use ApplyLabel to label reusable input objects. If you want to label non-reusable input objects, you must use a persistent input file that contains encoded object IDs.
If ApplyLabel succeeds,
pmrep
 displays either no status information or a list of objects that already have the label. If the command fails,
pmrep
 displays the reason for the failure.
The ApplyLabel command uses the following syntax: 
applylabel 

-a <label_name> 

{{-n <object_name> 

  -o <object_type> 

  [-t <object_subtype>]

  [-v <version_number>] 

  [-f <folder_name>] } |

  -i <persistent_input_file>} 

[-d <dependency_object_types>] 

[-p <dependency_direction (children, parents, or both)>] 

[-s (include pk-fk dependency)] 

[-g (across repositories)] 

[-m (move label)] 

[-c <comments>]

[-e dbd_separator]
The following table describes
pmrep
 ApplyLabel options and arguments:
Option
Argument
Description
-a
label_name
Required. Label name to apply to the object.
-n
object_name
Required if you are updating a specific object. Name of the object to receive the label. You cannot enter object names if you use the -i option.
-o
object_type
Type of object to apply the label to. You can specify source, target, transformation, mapping, session, worklet, workflow, scheduler, session config, task, cube, or dimension. Required when applying a label to a specific object.
-t
object_subtype
Required. Type of task or transformation you are labeling.
pmrep
 ignores other object types. For more information about valid subtypes, see Listing Object Types.
-v
version_number
Optional. Version of the object to apply the label to. The command fails if the version is checked out. Applies the label to the latest version of the object by default.
-f
folder_name
Optional. Folder that contains the objects. If you enter a folder name but no object name,
pmrep
 applies the label to all objects in the folder. If you enter a folder name with an object name,
pmrep
 searches the folder for the object. You cannot use the -f option if you use the -i option.
-i
persistent_input_file
Optional. Name of a text file generated from ExecuteQuery, ListObjectDependency, or Validate. Contains a list of objects to receive the label. If you use this option, do not use the object name, object type, or folder name to specify objects.
-d
dependency_object_types
Optional. Dependent object types to label. Valid dependent object types include shortcuts, mappings, mapplets, sessions, workflows, worklets, target definitions, source definitions, and foreign key dependencies.
Use this option with option -p. If you enter an object type, the label applies to dependent objects of that object type.
-p
dependency_direction
Optional. Dependent parents or children to apply the label to. You can specify parents, children, or both. If you do not enter option -d, all dependent objects receive the label.
If you do not enter this option, the label applies to the specified object.
-s
-
Optional. Include the primary key-foreign key dependency objects regardless of the direction of the dependency.
-g
-
Optional. Find object dependencies across repositories.
-m
-
Optional. Move a label from the current version to the latest version of an object. Use this argument when the label type is one_per_object.
-c
comments
Optional. Comments about the label.
-e
dbd_separator
Optional. If an ODBC source has a period (.) in the name, define a different separator character when you define the source object. For example, instead of database_name.source_name, define the source object as database_name\source_name, and define the dbd_separator as backslash (\).
0 COMMENTS
We’d like to hear from you!