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

getworkflowdetails

getworkflowdetails

Returns the following information about a workflow:
  • Folder and workflow names
  • Workflow run status
  • First error code and error message
  • Start and end times
  • Log file name
  • Workflow run type
  • Name of user that last ran the workflow
  • Name of associated Integration Service
The getworkflowdetails command uses the following syntax in the command line mode: 
pmcmd getworkflowdetails

<<-service|-sv> service [<-domain|-d> domain] [<-timeout|-t> timeout]>


<
<-user|-u> username
|
<-uservar|-uv> userEnvVar
>
<
<-password|-p> password
|
<-passwordvar|-pv> passwordEnvVar
>


[<<-usersecuritydomain|-usd> usersecuritydomain
|
<-usersecuritydomainvar|-usdv> userSecuritydomainEnvVar>]

[<-folder|-f> folder]

[<-runinsname|-rin> runInsName]

[-wfrunid workflowRunId] 

workflow
The getworkflowdetails command uses the following syntax in the interactive mode: 
getworkflowdetails

[<-folder|-f> folder]

[<-runinsname|-rin> runInsName]

[-wfrunid workflowRunId] 

workflow
The following table describes
pmcmd
 getworkflowdetails options and arguments:
Option
Argument
Description
-service
-sv
service
Required. Integration Service name.
-domain
-d
domain
Optional. Domain name.
-timeout
-t
timeout
Optional. Amount of time, in seconds,
pmcmd
 attempts to connect to the Integration Service.
If the -timeout option is omitted,
pmcmd
 uses the timeout value specified in the environment variable INFA_CLIENT_RESILIENCE_TIMEOUT. If the environment variable is not set,
pmcmd
 uses the default timeout value. Default is 180.
-user
-u
username
Required in command line mode if you do not specify the user name environment variable. User name. Not used in interactive mode.
-uservar
-uv
userEnvVar
Specifies the user name environment variable.
Required in command line mode if you do not specify the user name. Not used in interactive mode.
-password
-p
password
Required in command line mode if you do not specify the password environment variable. Password. Not used in interactive mode.
-passwordvar
-pv
passwordEnvVar
Required in command line mode if you do not specify the password. Password environment variable. Not used in interactive mode.
-usersecuritydomain
-usd
usersecuritydomain
Optional in command line mode. Required if you use LDAP authentication. Name of the security domain that the user belongs to. Not used in interactive mode. Default is Native.
-usersecuritydomainvar
-usdv
userSecuritydomainEnvVar
Optional in command line mode. Security domain environment variable. Not used in interactive mode.
-folder
-f
folder
Required if the workflow name is not unique in the repository. Name of the folder containing the workflow.
-runinsname
-rin
runInsName
Name of the workflow run instance. Use this option if you are running concurrent workflows.
-wfrunid
workflowRunId
Run identifier number (Run ID) of the workflow run instance. Use this option if you are running concurrent workflows.
Use this option if the workflow does not have a unique run instance name.
-
workflow
Name of the workflow.
The following table describes the different statuses for workflows:
Status Name
Description
Aborted
You choose to abort the workflow or task in the Workflow Monitor or through
pmcmd
. The Integration Service kills the DTM process and aborts the task. You can recover an aborted workflow if you enable the workflow for recovery.
Aborting
The Integration Service is in the process of aborting the workflow.
Disabled
You select the Disabled option in the workflow properties. The Integration Service does not run the disabled workflow until you clear the Disabled option.
Failed
The Integration Service fails the workflow because it encountered errors. You cannot recover a failed workflow.
Preparing to Run
The Integration Service is waiting for an execution lock for the workflow.
Running
The Integration Service is running the workflow.
Scheduled
You schedule the workflow to run at a future date. The Integration Service runs the workflow for the duration of the schedule.
Stopped
You choose to stop the workflow or task in the Workflow Monitor or through
pmcmd
. The Integration Service stops processing the task and all other tasks in its path. The Integration Service continues running concurrent tasks. You can recover a stopped workflow if you enable the workflow for recovery.
Stopping
The Integration Service is in the process of stopping the workflow.
Succeeded
The Integration Service successfully completes the workflow.
Suspended
The Integration Service suspends the workflow because a task failed and no other tasks are running in the workflow. This status is available when you select the Suspend on Error option. You can recover a suspended workflow.
Suspending
A task fails in the workflow when other tasks are still running. The Integration Service stops running the failed task and continues running tasks in other paths. This status is available when you select the Suspend on Error option.
Terminated
The Integration Service shuts down unexpectedly when running this workflow or task. You can recover a terminated workflow if you enable the workflow for recovery.
Terminating
The Integration Service is in the process of terminating the workflow or task.
Unknown Status
This status displays in the following situations:
  • The Integration Service cannot determine the status of the workflow or task.
  • The Integration Service does not respond to a ping from the Workflow Monitor.
  • The Workflow Monitor cannot connect to the Integration Service within the resilience timeout period.
Unscheduled
You remove a workflow from the schedule.
Waiting
The Integration Service is waiting for available resources so it can run the workflow or task. For example, you may set the maximum number of running Session and Command tasks allowed for each Integration Service process on the node to 10. If the Integration Service is already running 10 concurrent sessions, all other workflows and tasks have the Waiting status until the Integration Service is free to run more tasks.
The getworkflowdetails command displays the last workflow run type details. Workflow run types refers to the method used to start the workflow.
The following table describes the different workflow run types with the getworkflowdetails command:
Workflow Run Types
Description
User Request
Manually started a workflow.
Schedule
Workflow runs at the scheduled time.
0 COMMENTS
We’d like to hear from you!