Shared Content for Data Engineering 10.1.1
- All Products
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
getworkflowdetails [<-folder|-f> folder] [<-runinsname|-rin> runInsName] [-wfrunid workflowRunId] workflow
Required. Integration Service name.
Optional. Domain name.
Optional. Amount of time, in seconds,
pmcmdattempts to connect to the Integration Service.
If the -timeout option is omitted,
pmcmduses the timeout value specified in the environment variable INFA_CLIENT_RESILIENCE_TIMEOUT. If the environment variable is not set,
pmcmduses the default timeout value. Default is 180.
Required in command line mode if you do not specify the user name environment variable. User name. Not used in interactive mode.
Specifies the user name environment variable.
Required in command line mode if you do not specify the user name. Not used in interactive mode.
Required in command line mode if you do not specify the password environment variable. Password. Not used in interactive mode.
Required in command line mode if you do not specify the password. Password environment variable. Not used in interactive mode.
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.
Optional in command line mode. Security domain environment variable. Not used in interactive mode.
Required if the workflow name is not unique in the repository. Name of the folder containing the workflow.
Name of the workflow run instance. Use this option if you are running concurrent workflows.
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.
Name of the workflow.
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.
The Integration Service is in the process of aborting the workflow.
You select the Disabled option in the workflow properties. The Integration Service does not run the disabled workflow until you clear the Disabled option.
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.
The Integration Service is running the workflow.
You schedule the workflow to run at a future date. The Integration Service runs the workflow for the duration of the schedule.
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.
The Integration Service is in the process of stopping the workflow.
The Integration Service successfully completes the workflow.
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.
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.
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.
The Integration Service is in the process of terminating the workflow or task.
This status displays in the following situations:
You remove a workflow from the schedule.
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.
Workflow Run Types
Manually started a workflow.
Workflow runs at the scheduled time.