JDE Jobs abort using scripted solution for Applications Manager

Products

• CA Automic Applications Manager (AM)

Issue/Introduction

Error Message :
Cannot find jcjobnumber in response file - possible error

JDE jobs will abort with the following error message in the job's output file:

-rw-rw-r--   1 jdeb9      jdeb9          198 Sep 15 06:46 /pd/appworx8/am/run/145034762.00_out.xml
jcjobnbr
Cannot find jcjobnumber in response file - possible error
*****************************
* Finished on Fri Sep 15 06:46:14 EDT 2017 with status ABORTD (ABORTD)
 

Environment

OS Version: N/A

Cause

Cause type:
Configuration
Root Cause: This is an issue on the JDE side.

Resolution

The error message should reference a <JobID>_out.xml file.

Example:

-rw-rw-r--   1 jdeb9      jdeb9          198 Sep 15 06:46 /pd/appworx8/am/run/145034762.00_out.xml

Inside that file should be the error message that details why the job is aborting.

Example:

<?xml version='1.0' encoding='UTF-8' ?><jdeResponse pwd='' type='ube' user='' environment=''><ACTION TYPE='ERROR_MESSAGE'><ERROR VALUE='JDB_InsertTable failed for F986110.'/></ACTION></jdeResponse>
 

In the above example, the issue is with the JDE table F986110.  

Contact your JDE Administrator to investigate why the application cannot insert into that table.

Fix Status: No Fix

Fix Version(s):
N/A

Additional Information

Workaround :
Resetting the jobs initially may allow them to run.

BEWARE:  Eventually, the reset jobs will fail as well.