Oracle EBS plugin: Passing variables to program arguments

Products

• Autosys Workload Automation
• Workload Automation Agent

Issue/Introduction

When passing an environment variable as an argument to an Oracle EBS jobs, if the environment variable is not defined, the job remains in a RUNNING state.

Example: The following is set in a user profile that is sourced by the job.

AUTO_SYSDATE="`date '+%Y/%m/%d %H:%M:%S'`"
export AUTO_SYSDATE

• When variable is undefined, the actual variable name; in this case $AUTO_SYSDATE is passed as the argument. Thus causing job to remain in RUNNING state.
  STANDARD,$$(G_CFG2_XXXXX_STARTTIME_FORACE),$AUTO_SYSDATE,$$(G_CFG2_XXXXX_ORG_NAME),$$(G_CFG2_XXXXX_ORG_NAME),$$(G_XXXXX_WRKLD_ID),$$(G_XXXXX_WRKLD_ID)
• When variable IS defined, it looks more like the following, and job runs to completion.
  STANDARD,$$(G_DVL7_XXXXX_STARTTIME_FORACE),2025/01/29 14:46:52,$$(G_DVL7_XXXXX_ORG_NAME),$$(G_DVL7_XXXXX_ORG_NAME),$$(G_XXXXX_WRKLD_ID),$$(G_XXXXX_WRKLD_ID)

 

Environment

Any

Resolution

Use AutoSys Global Variable instead.

Example:

AUTO_SYSDATE="`date '+%Y/%m/%d %H:%M:%S'`"
export AUTO_SYSDATE

sendevent -E SET_GLOBAL -G G_AUTO_SYSDATE=$AUTO_SYSDATE

Use $$G_AUTO_SYSDATE as the variable to be passed as argument to Oracle EBS program.