Skip Ribbon Commands
Skip to main content
Navigate Up
Sign In

Quick Launch

Average Rating:

facebook Twitter
Email
Print Bookmark Alert me when this article is updated

Feedback

FAQ: Is it possible to run workflows with and without “OS Profile” enabled when the operating system profile is configured at the folder level?
Answer

If the requirement is to enable OS Profile for certain workflows in the folder, then you should not assign any operating system profiles at the folder level. Instead, you should use the Start Workflow Advanced option to assign the operating system profile for the workflow. You can also use the pmcmd startworkflow command to assign operating system profile to a workflow.

Example

 pmcmd startworkflow
<<-service|-vs.> service [<-domain|-do> domain] [<-timeout|-to> timeout]>
<<-user|-up> username|<-server|-up> userEnvVar>
<<-password|-up> password|<-passwordvar|-pv> passwordEnvVar>
[<<-usersecuritydomain|-used> usersecuritydomain|<-usersecuritydomainvar|-used> userSecuritydomainEnvVar>]
[<-folder|-if> folder]
[<-start from> taskInstancePath
[<-recovery|-no recovery>]]
[<-profile> profile]
[<-localparamfile|-lap> localparamfile]
[<-osprofile|-of> Souse]
[-wait|-no wait]
[<-runinsname|-rim> runInsName]
workflow

The following table describes pmcmd startworkflow options and arguments:

 Option

 

 Argument

 

Description

 

 -osprofile
-o

osProfile

Optional. Specifies the operating system profile assigned to the workflow.


More Information

Applies To
Product: PowerCenter
Problem Type:
User Type:
Project Phase:
Product Version: PowerCenter 8.5; PowerCenter 8.5.1; PowerCenter 8.6; PowerCenter 8.6.1
Database:
Operating System:
Other Software:

Reference
For more information see, PowerCenter Command Reference guide.

Attachments

Last Modified Date:1/9/2019 6:03 PMID:113255
People who viewed this also viewed

Feedback

Did this KB document help you?



What can we do to improve this information (2000 or fewer characters)