ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

After resetting the next job number in JDE, some JDE jobs go to a DIED status.

book

Article ID: 88379

calendar_today

Updated On:

Products

CA Automic Applications Manager (AM)

Issue/Introduction

After resetting the next job number in JDE, some JDE jobs go to a DIED status.

Environment

Release: AAMOS499000-8.0-Automic Applications Manager-OS400 Agent
Component:

Resolution

Symptoms

After resetting the next job number in JDE, some JDE jobs go to a DIED status in the backlog when run in Applications Manager.

 



 

Resolution

1.    Delete the DIED jobs from the backlog.
2.    Check to ensure that you do not have more instances of the jde2.sh script running on the server as you have displayed in the Applications Manager backlog.  If you do, you will need to kill these processes from the command line, and kill the JDE_SERVER job in the backlog and resubmit it.