Error only occurs in PD

[Lynnol]

Dear JDE List,

We have a customized UBE that has been encountering a problem in PD but cannot be resolved or replicated during testing. We have even tried testing using the exact same data backed up from production, but the error still does not occur. Tried monitoring the processing through Debugger, but everything looks ok.

There are different versions of this UBE that is scheduled to run nightly. And the error only occur maybe once a month, with one version only. We don't think this is a version problem, because it occurred to different versions.

We have re-deployed the UBE on the server to make sure
that the specs are OK, but this does not solve the problem either.

I have extracted the following from the log file:
256250 Mon Jul 14 22:23:19.857680 runbatch.c310 INITIALIZING RUNBATCH job: 541237

256250/106 MAIN_THREAD Mon Jul 14 22:23:19.998160 ipcmisc.c299 process 256250 <E810SYS/PRINTUBE> registered in entry 16

256250/106 MAIN_THREAD Mon Jul 14 22:23:20.072160 runbatch.c438 Generating Joblog for UBE, refer to joblog of job 051612/PSFT /R58XXXXXX for additional information.
...

256250/106 MAIN_THREAD Mon Jul 14 22:23:30.375968 zdrv.cpp328 Initializing the Z Driver 256250/106 MAIN_THREAD Mon Jul 14 22:23:30.376224 zdrv.cpp342 Gettting user data from hEnv

256250/106 MAIN_THREAD Mon Jul 14 22:23:30.376384 zdrv.cpp364 User data is XXXXX, PH810

256250/106 MAIN_THREAD Mon Jul 14 22:23:30.376600 zdrv.cpp373 Creating XML Session

256250/106 MAIN_THREAD Mon Jul 14 22:23:30.700360 runbatch.c1099 RUNBATCH: Remote CP=1252, Remote OS=1, Local CP=37, ConvertToASCII=0

256250/106 MAIN_THREAD Mon Jul 14 22:23:48.783224 ipcmisc.c299 API ipcSawUnregisterProcV1 : process 256250 unregistered in entry 16

256250/106 MAIN_THREAD Mon Jul 14 22:23:48.789176 zdrv.cpp389 Terminating Z driver

256250/106 MAIN_THREAD Mon Jul 14 22:23:48.789456 zdrv.cpp406 Calling freeSession

The " ipcSawUnregisterProcV1 : process 256250 unregistered in entry 16" message seems to be the only unusual thing from the log.

Does any one know what ipcSawUnregisterProcV1 means?
Or does anyone have any idea whereelse to look for the bug?

We are running on E810, AS400.

Please shed some light. Thank you in advance.

Lynnol

 

[Chan Rana]

Are you creating any data file or temp file on AS/400 thru this UBE?.

Also write details about your E1 version etc. so it can help to understand better.

Chan

 

[Zoltan_Gyimesi]

Hi Lynnol,

At first blick, it seems to me, that ProcOpt template had been modified/extended after the versions were created. In this case sometimes the UBE can receive junk data in the PO values, mainly in those parameters, which were added newly to PO template.

This is just an assumption from me.

If it is feasible, then create new versions, deploy and schedule these versions.

IMPORTANT: create the new versions with ADD instead of COPY an already existing.

I do not know, is it a bit help or is not.

Regards,

Zoltán

 

[Bill Dotson]

Since you're on an AS/400, you may need to delete the SQLPKG associated with this UBE.

 

[Lynnol]

Hi Chan,

The UBE does not create any temp file but updates a couple of standard JDE tables and a customized table. It is more like an integrity report. So after the UBE has been run, there should be no differences between the JDE table and customized table.

For the versions, I don't spot any significant differences. The only differences between versions are data selections, for example, to select different companies, etc.

Thanks & Regards,

Lynnol

 

[Lynnol]

Hi Zoltan,

Good to see you reply. Just like to mention, many if your posts have been very helpful. Thanks

Back to the UBE, the existing UBE does not have any processing options. We've been monitoring the UBE and data over the past couple of months, the weird thing is that this error only occurs maybe once a month. But we will try and create a new version to see if the error occurs again over next month. Please let me know if you have other suggestions in the meanwhile.

Thanks & Regards,

Lynnol

 

[VickiHedrick]

If the problem occurs in a scheduled version, make sure that version has not been submitted manually with data selection changes.