AS/400 for foreign tables from another AS/400

Tom_Davidson

Tom_Davidson

VIP Member
We are trying to set up System i to System i communications to allow foreign tables in TC from one to the other.

We have added the RDB entry on the table with JDE on it. Created the datasource pointing to the 400 with the foreign tables. Have DDM working between the two boxes.

When we run the TC on the System i we get a message that we failed to get the columns:

JDE LOG:
491/5 MAIN_THREAD Mon Aug 20 20:23:50.437408 dbdrv_log.c196
OS400LI003 - initSQLCLIstructures:SQLConnect failed with Relation

The UBE finishes with:

491/5 MAIN_THREAD Mon Aug 20 20:23:51.504128 ipcmisc.c299
API ipcSawUnregisterProcV1 : process 491 unregistered in entry 20

491/5 MAIN_THREAD Mon Aug 20 20:23:51.506032 runbatch.c1287
PrintUBE failed, refer to joblog of job 008788/JDE /R570101Z for additional information.

491/5 MAIN_THREAD Mon Aug 20 20:23:51.506288 runbatch.c1303
Job of type UBE failed with rcode = 0

491/5 MAIN_THREAD Mon Aug 20 20:23:51.513000 runbatch.c1357
Batch job 144 ended in error

491/5 MAIN_THREAD Mon Aug 20 20:23:51.513984 zdrv.cpp389
Terminating Z driver

491/5 MAIN_THREAD Mon Aug 20 20:23:51.514152 zdrv.cpp406
Calling freeSession

491/5 MAIN_THREAD Mon Aug 20 20:23:51.651280 dbdrv_log.c196
OS400QL003 - DisconnectDB:Handle: '2' to DS 'Business Data - CV' in DB 'Business Data - CV' on Server DB 'TWINCO' via 'T' connection - unable to disconnect. QCPFMSG *LIBL - CPFB752 - Internal error in &2 API

We are on 8.12 Tools 8.96 OS/400: V5R4 for the JDE box and V5R3 for the foreign table box.

Any ideas would be much appreciated.

Tom Davidson
 
Hi Tom, I am see similar errors with my system, but I am doing something slightly different. We have to change the NETJOBD from ONEWORLD to a new user for the foundation subsystem for the JDE kernels and these are some of the errors I get after doing that:

Aug 24 03:12:27.492576 jdb_rq1.c1103 - 100597/515 MAIN_THREAD Exiting JDB_OpenTable(Table = F986180) with Success
Aug 24 03:12:27.492704 jdb_rq1.c2655 - 100597/515 MAIN_THREAD Entering JDB_TableExists (Table F986181)
Aug 24 03:12:27.521168 dbdrv_log.c196 - 100597/515 MAIN_THREAD OS400LI004 - initSQLCLIstructures:SQLAllocStmt failed with Connecti
Aug 24 03:12:27.521576 dbdrv_log.c220 - 100597/515 MAIN_THREAD OS400LI004 - initSQLCLIstructures:
Aug 24 03:12:27.521880 jdb_drvm.c1577 - 100597/515 MAIN_THREAD JDB9900189 - Failed to verify that table exists in SystemCH064-811
Aug 24 03:12:27.522240 dbdrv_cn.c973 - 100597/515 MAIN_THREAD >>>Decrementing ref count for AUTO commit connection dbc=SPP:0000 :0000 :0:7:11,RefCount=6
Aug 24 03:12:27.522344 jdb_rq1.c2664 - 100597/515 MAIN_THREAD Exiting JDB_TableExists with Failure(Table F986181)
Aug 24 03:12:27.522440 secnodemgr.c936 - 100597/515 MAIN_THREAD GethF986181Request: NID_F986181 does not exist
 
I found the problem with my issue, Tom.

For me the issue was the SQLServerMode setting in the JDE.INI was not present so it was on.

Once the INI setting was added and set to 0, I stopped having problems.
 
Tom and I have been working on this issue. The cause of the issue was with the setup of the foreign tables 400. It did not have the server name setup as *LOCAL in the RDB table, but rather still had the serial number as *LOCAL.

Since the foreign table 400 is still a Prod box, we added an entry in the JDE 400 RDB table for the serial number of the foreign table 400, added the serial number of the foreign table 400 in the host table of the JDE 400, added the serial number of the foreign table 400 as a database server in JDE and changed the server for the foreign table datasource to the serial number of the foreign table 400. All is working as it should now.

Even before this change JDE was able to read standard JDE defined tables on the foreign table 400 just fine, so JDE must send a different communication call to JDE tables vs. foreign tables.
 
Back
Top