Michael_Lowry

RA job attributes

Discussion created by Michael_Lowry on Oct 26, 2017
Rapid Automation (RA) jobs have attributes that are specific to each particular RA solution. To list all of the job attributes for a given RA solution, run the following query. Replace JobName with the name of a job that uses the solution you’re interested in.
select OCV_VName as Attribute,OCV_Value as Value
from OH join OCV on OH_Idnr=OCV_OH_Idnr
where OH_Name='JobName'
For example, RA Informatica (PowerCenter) jobs have the following attributes:

Attribute Description Value
repository Connection object   
folderName Folder Name   
workFlowName WorkFlow Name   
startFromTask Start from Task   
parameterFileName Parameter File Name   
runInstanceName Run instance name  
abort Abort on kill true/false
componentName Solution type   
overrideAgentOption Session log file transfer option – override agent option true/false
sessionOption   When to transfer session logs
Always
For failed sessions or workflows
Only for failed sessions
Never
Value
1
2
3
4
variable_0_0 First parameter name  
variable_0_1 First parameter value  
variable_1_0 Second parameter name  
variable_1_1 Second parameter value  
variable_2_0 Third parameter name  
variable_2_1 Third parameter value  
etc. and so on...  

Just as with other AE object attributes, RA job attributes can be read using GET_ATT and set using :PUT_ATT.

To use the Automation Engine DB change program (ucybchng) to change RA job attributes, just insert the prefix CVALUE: or JPCVALUE: before the name of the attribute:
  • CVALUE:attributechanges attributes ofstand-alone RA job definitions. E.g.,CVALUE:repository
  • JPCVALUE:atttributechanges attributes ofRA job tasks within workflows. E.g.,JPCVALUE:repository
If you want to change both a stand-alone RA job and the instances of that job inside workflows, you must define two rules:
  1. A rule that changes the attribute of the stand-alone jobs (JOBS objects) using theCVALUE:prefix:
  2. Another rule that changes the attribute of the workflow tasks (instances of the jobs inside JOBP objects) using theJPCVALUE:prefix.
For example:
REPLACE JOBS, UC0.MAL.*, CVALUE:repository, UC0.PCE.CONN_DEV, UC0.PCE.CONN_TESTREPLACE JOBP, UC0.MAL.*, JPCVALUE:repository, UC0.PCE.CONN_DEV, UC0.PCE.CONN_TEST REPLACE_PART JOBS, UC0.MAL.*, CVALUE:workFlowName, DEV, TEST REPLACE_PART JOBP, UC0.MAL.*, JPCVALUE:workFlowName, DEV, TEST
If you execute RA jobs from an external application using the AE Java Application Interface, you can also override RA job attributes using the setInstanceParameter() method of the ExecuteObject class. E.g., if you run
exeObj.setInstanceParameter("runInstanceName", "test_run_01");
when submitting an RA Informatica (PowerCenter) job, then this will set the run instance name of the job when it is submitted to PowerCenter.

Attribute values set in this way take precedence over values set in any other way. The order of precedence is:
  1. Value set usingExecuteObject.setInstanceParameter()
  2. Value set using:PUT_ATT
  3. Value set in workflow task
  4. Value set in RA job definition

Outcomes