× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



As you suggested, the problem is not with the ASCII translation, but with
the fixed record length of the database file. It's really strange that this
works beautifully with other FTP sites and other VANs.

What is the best command to use to copy a database file to true stream file
(with no fixed record length)? CPYTOSTMF, CPYTOIMPF, something else?

Bill

-----Original Message-----
From: Wilt, Charles [mailto:WiltC@xxxxxxxxxx]
Sent: Tuesday, July 10, 2007 4:54 PM
To: Midrange Systems Technical Discussion
Subject: RE: EDI and Inovis from Library Data


Bill,

EDI is stream data, not particularly compatible with a PF.

What's the data look like in the PF?


If I were going to try this, I'd send an IFS stream file.

HTH,
Charles


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Reger, Bill
Sent: Tuesday, July 10, 2007 4:15 PM
To: 'midrange-l@xxxxxxxxxxxx'
Subject: EDI and Inovis from Library Data

I am attempting to send an EDI 997 transaction to Inovis (a
VAN). I am doing an FTP PUT operation directly from a native
Database File using the format PUT library/file.member to a
folder/file on Inovis. I have tried to do all manner of
ASCII conversions - or have attempted to - using the QASCII
table, specifying the AScii operation within FTP, etc.

Nothing seems to work. Inovis keeps kicking out my data and
I'm getting terribly frustrated. Inovis has closed my
Support call since "we are not using Inovis' software" to
generate the 997 and send to them.

Someone must be doing outgoing EDI documents (without an EDI
Ttranslator) to Inovis. Help!

Bill
--
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 e-mail transmission contains information that is intended to be
confidential and privileged. If you receive this e-mail and you are not a
named addressee you are hereby notified that you are not authorized to read,
print, retain, copy or disseminate this communication without the consent of
the sender and that doing so is prohibited and may be unlawful. Please
reply to the message immediately by informing the sender that the message
was misdirected. After replying, please delete and otherwise erase it and
any attachments from your computer system. Your assistance in correcting
this error is appreciated.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.