Foreign tables and OCM's

[amwalshjde]

Foreign tables and OCM\'s

I want to write outbound EDI data directly to the as/400 tables that are
read by the translator. I am debating with myself on how to do this. These
are the options I have:

Option 1: Define all the fields in the one world data dictionary then define
the table in oneworld. Then add a OCM record to tell OW that that
particulat table is not in the standard business data lib but instead in the
library when the translator is set up to read.

Option 2: Same as above but have the file in both places (therefore I dont
need the record for the OCM) and once I populate my tables (which are copies
of the legacy) do a AS/400 copy file to move the data over there.

Option 3: I would like to not define the tables in OW, but instead treat it
as a foreign table. I could set up a new datasource pointing to the
translator library, then set up a OCM that uses the "defualt" object, and
uses that datasource. However I have been told that there can be only one
default ocm mapping per environment. If that is true I dont think that the
rest of the IT group would want me to change the mapping for all "default"
objects. Is there a way around this?

Option 4: Any ideas you might have.

Thanks again,
AW

B7332 sp 13.1 AS/400 v4r4


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

 

[jastips]

Re: Foreign tables and OCM\'s

Hi

Third option might going to work. First 2 may not work. But you are talking about translator what translator you are talking about. But by using client access also you can get this work to be done. Create a datasource and create a ODBC DSN in client access after that create a OCM record specially for this table. Then with this process it should work. I worked on Access not on AS/400. But here ODBC is playing big role in both sides so this method should work.

Best of luck


Jastips
JDE CNC Consultant
DTI
USA

 

[Zoltan_Gyimesi]

Re: Foreign tables and OCM\'s

Hi Aaron,
Why do you want to map your table into your new datasource as DEFAULT?
You can map your table using its name simply instead of DEFAULT. Why does not it work for you?
Zoltán

B7332 SP11, ESU 4116422, Intel NT4, SQL 7 SP1
(working with B7321, B7331, XE too)