JDE Job in J-Done status while Job is still running in JDE

Products

• CA Automic Applications Manager (AM)

Issue/Introduction

When running JDE Jobs in Applications Manager (scripted solution), they go immediately to J-Done status while those jobs are actually still running in JDE.

This may cause subsequent component Jobs to Abort or not run correctly if they depend on the previous Job to complete successfully. 

Note that this is a JDE specific issue. If needed, please refer to your JDE admin.

Environment

Applications Manager 9.x

Cause

The JDE Job number may have a duplicate record. In JDE, the job number has a max value and a "next number" value.

There are times when the next number value is manually reset to a lower value.

This issue can occur if the next number value used for the JDE Job Number has been used previously AND that previous used job number's record has not been purged or archived.

Applications Manager determines the status of a JDE Job through a custom awexe command that queries the JDE database. When multiple records for a job number is found, the older Job record is which is listed as completed is taken, hence the Job in AM goes to J-done status.

Resolution

There are two solutions for this.

1. In JDE, change the next number value for the Job number a value higher then the current max value

2. In JDE, run its "clean up" job to purge or archive old records whose job numbers that are and will be used by the next number values.