Error trying to run JDE file conversions (AS400 ES)

Hi all,

I have an issue that is driving me crazy (even more that usual!!)..
Please help if you can.

I am trying to run a JDE submitted file conversion (it can't be run
locally). I get the same error no matter where it's run from (Fat or
Citrix).

The error is: OS40002001 - Error Type: OTHER enum: 9 - Could not bind
to the QZDMMDTA SRVPGM or could not find one of its exports!
I do know that this error has to do with Opti-Connect but the
Opti-Connect software doesn't exist and isn't going to be used. We had a
lot of other errors that I've made changes on but now I have this one and
it's a real bugger...

I saw this error at the last place I worked and it happened for
everything that was trying to run on the LPAR--security server was on the
main AS400. We had to change the data bse DataSources there from DBDR to
JDBNET on all of the ones that had to communicate between the two
AS400s. Here everything else seems to work just fine and we have 2 LPARs
we are using off of two AS400s. We are using DBDR for all data base
DataSources and everything that didn't work where I was before does work
fine here using DBDR. So.. I'm not sure if we need to change to JDBNET
here to get conversions to work or if there is another resolution.

Is there anyone that has any experience or knows about this? I'd sure
appreciate any help I can get. This is a hot issue and has been going on for
awhile here...

Is there anyone that has any experience or knows about this? I'd sure
appreciate any help I can get. This is a hot issue and has been going on
for awhile here...

Thanks in Advance!!

Lori [emsmilep.gif]

OW Xe SP20_I1 Update 4

Two AS400s V5R1 (with LPARs on each)

NT Citrix

Lori,
The OS40002001 error message is not a problem in and of itself. This
message will appear in all UBE and Kernel jde.log files that require a
connection (DB lookup) to the remote server. The way it was explained to me
by JDE is that the OneWorld services attempt to connect to REMOTE
datasources in the following order via JDBNET, Opti-Connect or TCP/IP. If
JDBNET is not configured in the server map data sources, OneWorld tries to
use Opti-Connect if that fails it reverts to TCP/IP. Therfore you will get
messages pointing to the non-existent Opti-Connect program, QZDMMDTA.

If you have subsequent error messages after the OS40002001 message, like
'Failed to connect to System - B7333', then you probably have an issue with
the AS/400 EDRSQL service.

I would avoid using JDBNET AS/400 to AS/400 communication at all costs.

Brent Marxhausen
DBT, Inc.
email: [email protected]

Brent,


How would you configure AS/400 to AS/400 communications? DBDR only works
on the LOCAL AS/400 the only other choice I know of is JDBNET.

Tom Davidson
Xe U1 700+ ESU's; AS/400; CO on SQL 7; W2K TSE w/Metaframe XP




OW 7333 SP 19.1, AS/400, WIN2K, TSE 2000, Metaframe XP FR 1, CO SQL 7.0

You can get away from JDBNET by starting the EDRSQL TCP Host service on the
target AS/400, and adding a RDBDIRE containing the target AS/400's name/IP
address on the 'initiating' AS/400. Then just change the data source
definitions in the initiating AS/400's server map to use DBDR vs. JDBNET.

Not a very 'advertised' approach, but, IMHO, it works well. Removes a layer
from the server-server communication process.

Brent Marxhausen
DBT, Inc.
email: [email protected]

Brent,

the
target AS/400

Is this STRHOSTSVR SERVER(*DATABASE)?

I had the RDBDIRE set up as follows:

Relational database: servername
Remote Location: servername
Type: *IP
Port number or service name: *DRDA

I don't remember what error I received, but only JDBNET seemed to work. If
the config above is correct, I will try this weekend and see what happens.

Tom Davidson
Xe U1 700+ ESU's; AS/400; CO on SQL 7; W2K TSE w/Metaframe XP; 2 instances
English/Western European & Japanese




OW 7333 SP 19.1, AS/400, WIN2K, TSE 2000, Metaframe XP FR 1, CO SQL 7.0

It set it up a bit different.

STRHOSTSVR SERVER(*EDRSQL)

Relational database: servername
Remote Location: IP Address (although servername should be valid here)
Type: *IP
Port number or service name: <blank>

I definitely did not use *DRDA and did not modify the enterprise server
jde.ini as mentioned in the July 2000 IBM RedBook for JDE.

Brent Marxhausen
DBT, Inc.
email: [email protected]