search cancel

The GSO Solution for submitting jobs to JD Edwards uses the 2 methods JD Edwards allows for ‘batch’ scheduling.


Article ID: 88434


Updated On:


CA Automic Applications Manager (AM)


The GSO Solution for submitting jobs to JD Edwards uses the 2 methods JD Edwards allows for ‘batch’ scheduling.


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


When submitting jobs using ‘runubexml’ from Automic, a JD Edwards jobid is returned by the process, so Automic can track and manage the submitted job. When customers are submitting jobs using the JD Edwards ‘runube’ command, a jobid is not returned from JD Edwards and the solution has to query the F986110 table. The solution selects the max JD Edwards jobid from the F986110 table and look for jobs greater than that JD Edwards jobid returned and then the solution uses the jobs and prompts to locate the submitted jobs and it’s corresponding JD Edwards jobid. This has always been a limitation when using JD Edwards tool set version 9.1.4 and lower.

JD Edwards tool set 9.1.5 has a change to the jcfndfuf2 column in the F986110 table.

This is what was stored in the column prior to version JD Edwards tool set version 9.1.5.
This has the problem of truncating the version when the JD Edwards jobid number gets too big.
R0006P_XJDE000_1000000001_PDF <-the version> is truncated and match is not found to extract the JD Edwards jobid
So when a search is performed for the combination of ‘report’ and ‘version’, no rows are returned because the field (version) is truncated.

Tool set 9.1.5 fixes the truncation of the version in the jcfndfuf2 column.
Now it just stores the report and the version in this new column and does not truncate any values

This makes looking up the JD Edwards number in the F986110 table easier/better because they do not need to truncate the version now.

*** Customers must send us the exec/jde* scripts for Automic to review
*** Customers must send the data/awserver_sqlusr.dat for Automic to review