GeekInterview.com
   Home |  Tech FAQ  |   Interview Questions |  Placement Papers |  Tech Articles |  Learn |  Freelance Projects |  Online Testing |  Geeks Talk |  Job Postings |  Knowledge Base | Site Search |  Add/Ask Question

  GeekInterview.com  >  Tech FAQs  >  Informatica

 Print  |  
Question:  In a sequential batch how can i stop/start the particular session?



June 06, 2007 13:37:31 #6
 rsannu2k Database Expert  Member Since: June 2007    Total Comments: 4 

RE: In a sequential batch how can i stop/start the par...
 
Madhu, Here is the statement to start/stop a session....


$PM_HOME/pmcmd starttask -s $PM_PMSERVER_PORT -uv USERNAME -pv PASSWORD -wait -f $Folder -w $Workflow $Task

#                  1. PowerMart Folder - Can pass the $PMFolder from
#                                        cdw_application_variables.
#                  2. Workflow - Name of Workflow being executed from $PMFolder
#                  3. Task Name - name of the session or task to be started.  If
#                                 the session or task is in a worklet then the name
#                                 is worklet.task.
#                  4. Log File - Name of the log file. Use $LogFile(path/file name)
#                                from cdw_app.. variables or your own log file
#                                with path variable... $Logs/xyz.log.

----------------------------------------------------------
$PM_HOME/pmcmd $EndMethod -s $PM_PMSERVER_PORT -uv USERNAME -pv PASSWORD -wait -f $Folder $Workflow

#                  1. PowerMart Folder - Can pass the $PMFolder from
#                                        cdw_application_variables.
#                  2. Workflow - Name of Workflow being executed from $PMFolder
#                  3. End Method - stopworkflow or abortworkflow.  Use abortworkflow
#                                  only if stopworkflow doesn't work.
#                  4. Log File - Name of the log file. Use $LogFile(path/file name)
#                                from cdw_app.. variables or your own log file
#                                with path variable... $Logs/xyz.log.
     

 

Back To Question