|
[EDI-L Mailing List Archive Home]
[Message List]
[Reply To This Message]
RE: Cleo 3780 & Sterling
I was told, in the early days of my adventures with bisync and Cleo, that by
choosing the proper settings for the parameters, this problem with 80 byte
blocks or one run-on line could be solved automatically. I was never able
to achieve this. The VANs and Cleo people had different terms for
parameters, to confuse things, and each change on the VAN side required a
phone call and putting up with their grousing. Time for Plan B.
One of my prouder accomplishments was my "unblocker" program that turned a
file divided into 80 byte records (with lf characters as a record separator,
I think) into a file of one segment per line, terminated by a cr/lf. This
was written in DCL. This program required a small change for Wal-Mart,
enough of a change that I kept the two versions separate. The only trick
involved was finding where in the process to put this program, because this
transformation had to be done after the file was received (obviously) but
before it was imported into the translator, and the translator controlled
the whole process. The translator called a DCL program to invoke the Cleo
software, I discovered after some poking around, so that solved my problem.
I edited that program to add an invocation of my own.
While I never experienced the problem with lf as a segment terminator that
Chris described, we did see a few wrinkles. In most circumstances, after
each IEA segment, the remainder of the record would be space filled, and the
next record would begin with the ISA. On occasion, however, there would be
10-20 spaces after the end of the IEA and the next ISA would begin. Also,
we saw enough variation in element separators and segment terminators to
redefine them after each ISA was encountered.
Howard Parks
1 Peter 4:10
|
 |
Subscribe in XML format
| RSS 2.0 |
|
| Atom 0.3 |
|
|
Cart
