SP23 problems with external object calls (Unicode?)

[jimmymac]

A while back we upgraded our OneWorld XE to SP23 on the A400 and had major problems. We quickly had to roll back to SP22. We have custom C programs which serve as an interface between a legacy RPG/JAVA system to One World XE. These C programs call the OneWorld Work Order and Purchase Order MBFs to update and create Work orders and Purchase Orders.

Beginning after we installed SP23, the C program that calls the PO BeginDoc returned with an error code. We only get that the function failed, not why unfortunately. But in the jdedebuglog we see very strange things. For example, the function Verify Approval Route Code was being called and failing. However we do not use Approval Route Codes and the version of P4310 that we reference in the calls has a blank for the option which means to not edit route codes. It seems to be doing it anyway and other similar things are occuring that indicate the the values we are passing to the MBFs and the data that the MBFs are receiving are somehow different or corrupted. Note that when we run the same test in a SP22 environment, everything passes and the logs show among other things that the Approval Route Code is not called, which is correct. It has been suggested that in SP23 JDE introduced unicode and our C programs may need to be converted to be unicode capable to work. However, it was my understanding that unicode wasn't introduced until 8.9 and shouldn't have any effect on XE.

Oracle/JDE has been zero help and we seem to be on our own.

Any thoughts about the unicode recommendation or any other ideas would be appreciated.

Thanks.

 

[gotjde]

Check this:

Case ID 4113676 - Error starting [DEF6] XMLCALLOBJ
Solution details
Summary : LOAD LIBRARY FAILED AFTER SP22.1
Details: PROBLEM:
After customer installed SP 22.1 they are having problems with interoperabi lity with XML calls and mq series adaptor.
1200 Fri Sep 3 11:31:18 2004 netflow.c478
Load library failed - 'XMLCALLOBJ'
1200 Fri Sep 3 11:31:57 2004 jdekdisp.c963
INITIALIZING CALL OBJECT KERNEL

SOLUTION:
The problem is that their system library is B7333SYS but the 'System Direct ory' on line 700 states 'B7334SYS', it should read:
700 'System Directory: B7333SYS '
To correct this the client should use the following steps:
1) WRKOBJ OBJ(B7333SYS/BUILD_VER)
Then, put option 3 to copy to another library (ex. BACKUP). This needs to b e done for a backup - a must do in case we need to go back to the old data area.
2) Bring down your OneWorld Services.
3) On the AS/400, issue the command:
CHGDTAARA DTAARA(B7333SYS/BUILD_VER (725 1)) VALUE('3')
4)To verify that the data area has been corrected run the following command "
DSPDTAARA DTAARA(B7333SYS/BUILD_VER)
Page down and verify the following:
700 'System Directory: B7333SYS '
SEARCH TEXT: Load Library failed, XPI, XML, Call Object,

System Code: OWH90I
Program ID: OWH90I
Release: Xe
Service Pack: SP22
Platform: AS400

We had a similiar issue and this resolved it. The data area must match your current system library name.

 

[Sebastian Sajaroff]

Hi,

Have you built and deployed a full server package after
your SP23 install?