File to Kermit truncates end of line spaces

[fran...@my-dejanews.com]

A file sent to a Kermit system should have a record length of 150, but the
Kermit system sees them as being variable length. I don't see a NOTRIM option
in ASPECT and CLRF is being used.

-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own

[John Schultz]

In article <7fi8gg$t46$1...@nnrp1.dejanews.com>,

fran...@my-dejanews.com wrote:
> A file sent to a Kermit system should have a record length of 150, but the
> Kermit system sees them as being variable length. I don't see a NOTRIM option
> in ASPECT and CLRF is being used.

It's been a while since I've had to mess with Kermit, but here's my guesses.
Do the values of the default characters in the Kermit Setup tab (open Setup,
click on the Data tab, then the Transfer Protocol button), such as the pad
character and end of line character, match what the receiving system is
expecting? I believe you should be able to use the SHOW command once you have
started Kermit on the remote system to see what values it is anticipating.

I'm not familiar with Kermit's NOTRIM option, and by CRLF I'm assuming you
mean that carriage returns and linefeeds should be translated? If so, you'll
want to make sure that the Text radiobutton in Kermit Setup is enabled, so
that carriage returns and linefeeds are translated. The default is to enable
the Binary radiobutton, which means no translation is performed. The
corresponding ASPECT command is SET KERMIT FILETYPE TEXT.