Yeah, I read that using the IBM Personal Communications package was a big win, using Win32::OLE ( i think from one of your old posts ;). Problem is, i'd like to stay in the open source world if at all possible, since that package is kinda costly.
Here's what i did with IPC::Run (aand some example code found
here
#!/usr/bin/perl
my @s3270 = s3270;
use IPC::Run qw( start pump finish timeout );
$IPCRUNDEBUG=details;
# Incrementally read from / write to scalars.
# $in is drained as it is fed to cat's stdin,
# $out accumulates cat's stdout
# $err accumulates cat's stderr
# $h is for "harness".
my $h = start \@s3270, \$in, \$out, \$err, timeout( 10 );
$in .= "connect(L:ssl3270.myhost.org:2023)\n";
$in .= "ascii\n";
$in .= "quit";
finish $h or die "s3270 returned $?";
warn $err if $err;
print $out; ## All of s3270's output
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.