Joel,
BizTalk is using SQL Server, can't you just setup a linked server and
have it pull the data via SQL? The OLEDB driver will deliver it to SQL
Server and thus BizTalk in a format that it can use.
coy
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Stone, Joel
Sent: Wednesday, June 27, 2012 14:44
To: 'Midrange Systems Technical Discussion'
Subject: Iseries to Biztalk ETL
Biztalk folks tell me that they cant accept zoned or packed data, in
addition they want to see numerics as edited character strings; ie
"123.45"
I am trying to make the interface file fields refer back to our iseries
database files.
For a order detail file with field QTY defined as packed 10.2, can I
refer to the original field in my interface file, but add an edit code?
But I am pretty sure that there edit codes are ignored for physical &
logical files.
Is it possible to have DB2 utilize the edit codes for a PF?
Is there a better way than moving each numeric field to a work field for
the edit to add the decimal point, and then to the interface file?
I am using cobol so would like to do most fields with MOVE
CORRESPONDING, but that is secondary.
Primarily I would like DDS to handle the editing. Is this doable?
Thanks!
______________________________________________________________________
This outbound email has been scanned for all viruses by the MessageLabs
Skyscan service.
For more information please visit
http://www.symanteccloud.com
______________________________________________________________________
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
************************************************************************
This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or taking any action based on it, is strictly prohibited.
***********************************************************************
midrange.com
