Automic Automation: Logical Date Activation Omits U00007026 Message.
search cancel

Automic Automation: Logical Date Activation Omits U00007026 Message.

book

Article ID: 452299

calendar_today

Updated On:

Products

Automic Automation

Issue/Introduction

The Automation Engine activation report fails to display the U00007026 message when a task is started with a logical date set for the next day, particularly within specific UTC+ timezones and timeframes.

Symptoms

  • Activation report omits the expected message: U00007026 'JOBS.####.####' activation is processed with the logical date 'YYYYMMDD'.
  • Issue occurs when the logical date is set for the next day and execution occurs between 00:00 and 02:00 AM (or similar early morning hours, depending on the timezone offset).
  • Observed in UTC+1, UTC+2, and UTC+5 timezones.
  • The behavior is not observed in UTC- timezones (e.g., EST).

Environment

  • Automic Automation Engine version 24.4.3, 24.4.4, and 24.4.5.

Cause

A logic issue within the Automation Engine activation report processing causes the U00007026 message to be omitted under specific timezone and logical date configurations. This issue is tracked under defect DE210549.

Resolution

Targeted to be fixed in release Automation Engine 24.4.6 - TBA and 26.1.0 - TBA.

  1. Workaround Explicitly print the logical date in the job script to ensure visibility in the report:

    1. Open the object script.
    2. Add the following lines:
      :SET &LDATE# = SYS_LDATE("YYYY-MM-DD")
:PRINT "Logical Date: &LDATE#"

Support If the issue persists or requires further assistance, contact support. For steps to create a support case, see Creating and Managing Broadcom Support Cases. To speak with a customer representative or a Support Engineer, see Contact Support. Scroll to the bottom of the page and click on the respective region.

Additional Information

Powered by Wolken Software