Telnet character limit?

[rfolden]

I have a perl telnet script which sends commands to a remote VAX host. The
commands get wrapped around at 80 characters, which cause them to get
truncated with errors.

%RMS-F-RER, file read error
-SYSTEM-W-DATAOVERUN, data overrun

Anyone have any ideas?

[James Willmore]

On Mon, 14 Jun 2004 19:32:38 +0000, rfolden wrote:

> I have a perl telnet script which sends commands to a remote VAX host. The
> commands get wrapped around at 80 characters, which cause them to get
> truncated with errors.
>
> %RMS-F-RER, file read error
> -SYSTEM-W-DATAOVERUN, data overrun
>
> Anyone have any ideas?

If memory serves correctly, there's an example in the Net::Telnet
documentation on how to read a character at a time versus a line at a
time. It's a little more work, but insures that the buffer is flushed,
you have control over the way the lines are broken up (think your own line
wrapping) and each character is read.

No guarantee this will work, but it's worth a try. Unless, of course,
this *is* the way you're doing it now (you don't show any code or state
how you're doing it now :-) ).

HTH

--
Jim

Copyright notice: all code written by the author in this post is
released under the GPL. [url]http://www.gnu.org/licenses/gpl.txt[/url]
for more information.

a fortune quote ...
Any two philosophers can tell each other all they know in two
hours. -- Oliver Wendell Holmes, Jr.

[rfolden]

I didn't see the character at a time example. However, good point about the
code. Here is the code I am using:

sub Send_OneVaxCmd {
my ($mycmd, $print) = @_;
my $prematch;
my $match;
while (1) {
$t->print($mycmd);
($prematch, $match) = $t->waitfor(Match => '/press
return.*$/i',
Match => '/.*\? $/i',
Match => '/.*\: $/i',
Match => "/$prompt/");
if ($print) { print $prematch; };
last if ($match =~ /$prompt/);
print $match;
$mycmd = <$infile>;
chomp ($mycmd);
}
}


"James Willmore" <jwillmore@remove.adelphia.net> wrote in message
news:pan.2004.06.15.14.49.29.712066@remove.adelphi a.net...

> On Mon, 14 Jun 2004 19:32:38 +0000, rfolden wrote:
>

> > I have a perl telnet script which sends commands to a remote VAX host.

The

> > commands get wrapped around at 80 characters, which cause them to get
> > truncated with errors.
> >
> > %RMS-F-RER, file read error
> > -SYSTEM-W-DATAOVERUN, data overrun
> >
> > Anyone have any ideas?

>
> If memory serves correctly, there's an example in the Net::Telnet
> documentation on how to read a character at a time versus a line at a
> time. It's a little more work, but insures that the buffer is flushed,
> you have control over the way the lines are broken up (think your own line
> wrapping) and each character is read.
>
> No guarantee this will work, but it's worth a try. Unless, of course,
> this *is* the way you're doing it now (you don't show any code or state
> how you're doing it now :-) ).
>
> HTH
>
> --
> Jim
>
> Copyright notice: all code written by the author in this post is
> released under the GPL. [url]http://www.gnu.org/licenses/gpl.txt[/url]
> for more information.
>
> a fortune quote ...
> Any two philosophers can tell each other all they know in two
> hours. -- Oliver Wendell Holmes, Jr.
>

[Unregistered]

I have a perl telnet script which sends commands to a remote VAX host. The
commands get wrapped around at 80 characters, which cause them to get
truncated with errors.

%RMS-F-RER, file read error
-SYSTEM-W-DATAOVERUN, data overrun

Anyone have any ideas?

I ran into the same problem, and could not find a ready answer anywhere, so dug through the CPAN documentation.
One way around this could be to change the output record seperator to null (i.e. Ors => "") while creating a new telnet object, and then break the commands larger than 80 characters into smaller parts and send them. Send a newline character after the whole command is sent.