AS400 Agent 24.4.5 Job Execution Delay Due to Job Log Retry Settings

Products

• Automic Automation

Issue/Introduction

Users may experience significant delays in job execution after upgrading to AS400 Agent version 24.4.5. This issue manifests as jobs taking significantly longer to complete compared to previous versions (e.g., 24.4.0 HF1). This article describes the cause and provides a configuration workaround to restore expected performance.

Environment

• AS400 Agent 24.4.5
• Previous version: 24.4.0 HF1
• Impact: Jobs configured with LOG(...*NOLIST) in their Job Description (JOBD).

Cause

Internal Case ID: DE210510

The issue is caused by the AS400 Agent's job log retry cycle. When a job is configured with LOG(...*NOLIST), the agent performs an unnecessary 15-retry cycle (default) to retrieve a job log that will never be produced. This retry loop, combined with the agent's single-threaded spool-checking architecture, causes serial delays for each affected job, leading to substantial cumulative execution time.

Resolution

Possible Workaround If Applicable

IMPORTANT: Please check with the OS400 team  if all of the jobs do not require any log output. If not, please modify the parameters below within the ini file of the AS400 agent to reduce the retry attempts.

1. Locate the AS400 agent INI file (typically UCXJO41.ini).

2. Modify the [MISC] section parameters:

From:

[MISC]
GETJOBLOGRETRY=15
GETJOBLOGDELAY=700

 

To:
[MISC]
GETJOBLOGRETRY=1
GETJOBLOGDELAY=100

3. Restart the AS400 agent for the changes to take effect.

Additional Information

Internal Defect:  DE210510