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

ListObjectDependencies

ListObjectDependencies

Lists dependency objects for reusable and non-reusable objects. If you want to list dependencies for non-reusable objects, you must use a persistent input file containing object IDs. You can create this file by running a query and choosing to create a text file.
ListObjectDependencies accepts a persistent input file and it can create a persistent output file. These files are the same format. If you create an output file, use it as input to the ApplyLabel, AddToDeployment Group, or Validate
pmrep
 commands.
ListObjectDependencies returns the number of records if the command runs successfully.
The ListObjectDependencies command uses the following syntax: 
listobjectdependencies 

{{-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)]

[-u <persistent_output_file_name>

  [-a (append)]]

[-c <column_separator>]

[-r <end-of-record_separator>]

[-l <end-of-listing_indicator>]

[-b (verbose)]

[-y (print database type)]

[-e <dbd_separator>]
The following table describes
pmrep
 ListObjectDependencies options and arguments:
Option
Argument
Description
-n
object_name
Required. Name of a specific object to list dependencies for.
-o
object_type
Required. Object type to list dependencies for. You can specify source, target, transformation, mapping, session, worklet, workflow, scheduler, session, session config, task, cube, dimension, query and deploymentgroup.
-t
object_subtype
Type of transformation, task, or query. Ignored for other object types. For more information about valid subtypes, see Listing Object Types.
-v
version_number
Optional. List dependent objects for an object version other than the latest version. You must use this option only for versioned repositories. It does not apply to non-versioned repositories.
-f
folder_name
Folder containing object name. Folder is required if you do not use the -i option.
-i
persistent_input_file
Optional. Text file of objects generated from ExecuteQuery or Validate commands. You must use this file if you want to list dependencies for non-reusable objects.
If you use this option, then you cannot use the -n, -o, -f options to specify objects.
-d
dependency_object_types
Optional. Type of dependent objects to list. You can enter ALL or one or more object types. Default is ALL.
If ALL, then
pmrep
lists all supported dependent objects. If you choose one or more objects, then
pmrep
lists dependent objects for these types. To enter multiple object types, separate them by commas without spaces.
-p
dependency_direction
Required if you do not use the -s option. Parents or children dependent objects to list. You can specify parents, children, or both. If you do not use the -p option,
pmrep
 does not list parent or child dependencies.
-s
-
Required if you do not use the -p option. Include the primary key-foreign key dependency object regardless of the direction of the dependency. If you do not use the -s option,
pmrep
 does not list primary-key/foreign-key dependencies.
-g
-
Optional. Find object dependencies across repositories.
-u
persistent_output_file_name
Send the dependency result to a text file. Use the text file as input to the ApplyLabel, AddToDeployment Group, or Validate
pmrep
 commands. The default sends the query result to stdout. You cannot use the -b and -c options with this option.
-a
-
Append the result to the persistent output file instead of overwriting it.
-c
column_separator
Character or set of characters used to separate object metadata columns. Use a character or set of characters that is not used in repository object names. If any repository object name contains spaces, you might want to avoid using a space as a column separator. You cannot use this option with the -u option.
If you omit this option,
pmrep
 uses a single space.
-r
end-of-record_
separator
Character or set of characters used to specify the end of the object metadata. Use a character or set of characters that is not used in repository object names.
Default is newline /n.
-l
end-of-listing_indicator
Character or set of characters used to specify the end of the object list. Enter a character or set of characters that is not used in repository object names.
If you omit this option,
pmrep
 uses a period.
-b
-
Verbose. Displays more than the minimum information about the objects. If you omit this option,
pmrep
 displays a shorter format including the object type, the word reusable or non-reusable, the object name and path. Verbose format includes the version number and folder name.
The short format for global objects, such as label, query, deployment group, and connection, includes the object type and object name. Verbose format includes the creator name and creation time. You cannot use this option with the -u option.
-y
-
Optional. Displays the database type of sources and targets.
-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!