JD Edwards jobs error with message: pool-4-thread-12: JDEdwardsAgentImpl: Exit getMaxRunid error
search cancel

JD Edwards jobs error with message: pool-4-thread-12: JDEdwardsAgentImpl: Exit getMaxRunid error

book

Article ID: 282410

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

JD Edwards jobs are erroring out when the JDE run numbers are 8 digits or more in length AND JD Edwards runs on MS SQL Server.

The JDEUBE job completes with exit code 2 and the plog shows the error:

java.lang.RuntimeException: Unable to find the JDE run id for the submitted job

and the report shows:

JDEdwardsAgentImpl: Exit getMaxRunid:1.71384e+007

Unable to find the JDE run id for the submitted job

Environment

Automation Engine 21.0.9
JDE agent version 2.2.4
JD Edwards installed using Microsoft SQL Server

Cause

This was due to the way the select was run. 
When a SELECT with CAST is used, the returned run number is truncated:

select *, CAST(jcjobnbr AS VARCHAR(25)) as runID from F986112

This issue does not happen with JD Edwards is run in Oracle.

Resolution

This has been resolved in JDE agent version 2.2.5 published Apr 22, 2024.

Additional Information

This is how the correcting query against the table F986111 should be added to the JDE agent settings