Automic Workload Automation

Expand all | Collapse all

RA job attributes

  • 1.  RA job attributes

    Posted 10-26-2017 05:24 AM

    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:



    repositoryConnection object 
    folderNameFolder Name 
    workFlowNameWorkFlow Name 
    startFromTaskStart from Task 
    parameterFileNameParameter File Name 
    runInstanceNameRun instance name 
    abortAbort on killtrue/false
    componentNameSolution type 
    overrideAgentOptionSession log file transfer option – override agent optiontrue/false
    sessionOptionWhen to transfer session logs
    For failed sessions or workflows
    Only for failed sessions
    variable_0_0First parameter name 
    variable_0_1First parameter value 
    variable_1_0Second parameter name 
    variable_1_1Second parameter value 
    variable_2_0Third parameter name 
    variable_2_1Third 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:attribute changes attributes of stand-alone RA job definitions. E.g., CVALUE:repository
    • JPCVALUE:atttribute0 changes attributes of RA 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 the CVALUE: prefix:
    2. Another rule that changes the attribute of the workflow tasks (instances of the jobs inside JOBP objects) using the JPCVALUE: prefix.

    For example:


    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 using ExecuteObject.setInstanceParameter()
    2. Value set using :PUT_ATT
    3. Value set in workflow task
    4. Value set in RA job definition

  • 2.  Re: RA job attributes

    Posted 04-05-2019 09:09 AM

    If you want to get a list of all RA job attributes currently defined in an AE system, this query will do the trick:

    select distinct JBA_JobType,OCV_VName
    from JBA left join OCV on OCV_OH_Idnr=JBA_OH_Idnr
    order by JBA_JobType,OCV_VName


    This shows only RA attributes for RA solutions for which at least one job exists.

  • 3.  Re: RA job attributes

    Posted 04-29-2019 03:31 AM

    We are in the process of switching from the transport case to XML for moving batches of scheduling objects from one AE system to another. As a part of this, we are developing our own XML change program to replace the role of the AE DB Change program (ucybchng).


    Here’s an Xpath that can be used to find (& change) RA job attributes in an AE XML file:

    /uc-export//CIT/citcont/cit/component[@xmlName='attribute_name' and @value='old_attribute_value']/@value


    See also:

    Transport case unload/load vs. XML export/import 

    AE XML schema 

    XML schema description for AE export file format 

  • 4.  RE: RA job attributes

    Posted 06-11-2019 10:55 AM
    Edited by Michael A. Lowry 06-11-2019 11:07 AM
    Here's a different SQL query that will list RA job attributes by RA solution.
    RA_Job_Attributes as
    (select distinct JBA_JobType as RA_Solution, OCV_VName as RA_Attribute
    from OH
    join OCV on OH_Idnr=OCV_OH_Idnr
    join JBA on OH_Idnr=JBA_OH_Idnr
    where OH_OType='JOBS'
    and JBA_JobType is not null
    order by JBA_JobType, OCV_VName
    select * from RA_Job_Attributes

    This still doesn't describe what each attribute corresponds to in the JUI/AWI. This really ought to be documented.