If you want to see more verbose error output, try the following:

cpan[1]> look MVS::JESFTP perl Makefile.PL make make test

Looking at the source code of the failing test, it dies because it can't connect to an (old, old) machine:

my($host, $logonid, $password, $job, $jobname) = ('nmgsdisd.state.nm.us', 'DPMIKE', 'JTREE', './TEST.SEQ', 'DPMIKE1 +'); $jes = MVS::JESFTP->open($host, $logonid, $password) or die "not ok 2\ +n";

So, maybe the module works ,but it's just the tests that are bad... If you edit that test and supply better credentials, maybe it passes its test suite.

Looking at its source, it's just a thin wrapper around Net::FTP, so if you feel uncomfortable with using a module that fails its tests, reimplementing the functionality from reading its source should get you just as far.


In reply to Re: cpan install MVS::JESFTP failed by Corion
in thread cpan install MVS::JESFTP failed by deanb2

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.