Re: EDI and Inovis from Library Data

[Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>]

I'm finding myself REALLY interested in this thread.   My company has 
been using Inovis' software for years, but now we're in the process of 
upgrading our system from a 270 to a 520.

The TrustedLink EDI software was around $10k when we originally 
purchased it from Premenos, and we've faithfully paid for maintenance on 
the product.  However, just to transfer the license from the 270 to the 
520 they want $15k!!

This is an absolutely absurd price in my mind. This 520 is only 600 CPW, 
it's the smallest machine IBM makes.  (As was the 270 in it's day). 
They are the same software tier, but of course, Inovis doesn't care what 
the software tier is, they only care about the CPW. To me, the notion 
that it costs more to transfer a license for software that processes 
10-15 orders a day than it does to buy a new machine, or to buy the 
original software in the first place...  it just boggles the mind.

Anyway, my point is -- if I can simply write the EDI data to a stream 
file and FTP it, that would be AWESOME!  Not only would it save me 
money, but I could make the whole process much more efficient.

Can anyone give me more info about what's involved in this?  You just 
write the EDI formatted data to the IFS (I already know how to do that) 
and FTP it and your done?  (Could it be that simple?)  I assume the VAN 
requires some sort of contract?


Reger, Bill wrote:
> Yes, I know well how to call RPG IV Procedures.  However in my current
> working environment I have to contend with an older variety of procedures -
> S/36 procedures!  (Lucky me.)
>
> For those of you who may be interested, I ended up creating a Stream file
> from a Native file by doing the following in a small CLP:
>
> 1.  Create a flatfile in QTEMP, specifying the RCDLEN I need (i.e. no DDS).
> 2.  CPYF from my Native EDI file to the flatfile, specifying FMTOPT(*NOCHK)
> 3.  CPYTOSTMF from the flatfile to an IFS Path, specifying
> STMFCODPAG(*PCASCII) and ENDLINFMT(*FIXED)
>
> That did it.  Thanks to everyone for the ideas.  And I will look at Scott's
> tutorial at a later date.
>
> Bill