Pranoy
Active Member
Hi,
We are on application release 9.1 and tools 9.2.2.5 with windows 2012 servers.
JDE job is scheduled using a custom scheduling tool which has feature to override data selection of JDE jobs(UBE). This works fine for all the jobs except a job that is using JDE standard function B4309570- UBERetrieveDataSelection & B4302450- UBERetrieveDataSelectionCache which retrieves run time data selection. These functions do not retrieve the data selection that is overridden by scheduling tool at run time, instead gets the default static data selection of the version. Overridden data selection at run time by scheduling tool can also be seen in the execution detail of submitted job, however still the functions B4309570 & B4302450 fails to retrieve the same, instead retrieving default static data selection there by printing incorrect data on report.
we cleared runtime cache and UBEOverride folders also from PY server and it also didn't help.
The folder <pathcode>\spec\runtimeCache is used to store the persistent TAM cache files for UBE specs e.g. GBRLINK, GBRSPEC, RDASPEC and RDATEXT.
The folder <pathcode>\spec\UBEOverride is used to store version override specifications e.g. Data Selection, Data Sequencing overrides.
Any inputs or thoughts appreciated.
Thanks,
Pranoy.
We are on application release 9.1 and tools 9.2.2.5 with windows 2012 servers.
JDE job is scheduled using a custom scheduling tool which has feature to override data selection of JDE jobs(UBE). This works fine for all the jobs except a job that is using JDE standard function B4309570- UBERetrieveDataSelection & B4302450- UBERetrieveDataSelectionCache which retrieves run time data selection. These functions do not retrieve the data selection that is overridden by scheduling tool at run time, instead gets the default static data selection of the version. Overridden data selection at run time by scheduling tool can also be seen in the execution detail of submitted job, however still the functions B4309570 & B4302450 fails to retrieve the same, instead retrieving default static data selection there by printing incorrect data on report.
we cleared runtime cache and UBEOverride folders also from PY server and it also didn't help.
The folder <pathcode>\spec\runtimeCache is used to store the persistent TAM cache files for UBE specs e.g. GBRLINK, GBRSPEC, RDASPEC and RDATEXT.
The folder <pathcode>\spec\UBEOverride is used to store version override specifications e.g. Data Selection, Data Sequencing overrides.
Any inputs or thoughts appreciated.
Thanks,
Pranoy.