I'm still working with this customer to get their FTPS working.  It has
taken forever for the networking staff to work on the firewall.  I think
they have it fixed.

But when I connect and try to download with the sample JCL., now it says it
cannot find the file.  Also when I went to look at the sample JCL again
from the link on ShopZ. It says the PDF containing that JCL can not be
found.  I'm wondering if the sample/test file is not there anylonger.


GIM45201S ** 550 /GIMPAF.XML: No such file or
directory.
GIM46200I    GIMGTPKG PROCESSING HAS FAILED BECAUSE THERE WAS AN FTP
ERROR.
GIM20501I    GIMGTPKG PROCESSING IS COMPLETE. THE HIGHEST RETURN CODE WAS
12.
--------------------------------------------------------------------------------

DATE 11/17/16  TIME 10:03:04              SERVER Data              SMP/E
36.11


 <SERVER

  host="deliverycb-bld.dhe.ibm.com"


user="B0000000"


pw="*********">

 <PACKAGE


file="/GIMPAF.XML"


hash="A90291034CCA32D4BDCA7244B2BA899EE1FA9FB0"


id="test.content">

 </PACKAGE>

</SERVER>


On Thu, Sep 15, 2016 at 10:26 AM, Donald J. <[email protected]> wrote:

> What is the output of :
>
> RACDCERT ID(MP81136) LISTRING(bexarftp)
>
> --
>   Donald J.
>   [email protected]
>
> On Wed, Sep 14, 2016, at 08:05 AM, Mark Pace wrote:
> > I'm having them look at the firewall.  I tired HTTPS, but I believe at
> 1.13
> > it required a PTF to support https.  They must not have it applied as I
> get
> > a syntax error on the downloadmethod and the downloadkeyring parameters.
> >
> > On Wed, Sep 14, 2016 at 8:44 AM, Kurt Quackenbush <[email protected]>
> wrote:
> >
> > > On 9/12/2016 12:27 PM, Mark Pace wrote:
> > >
> > >> I'm setting up FTPS on a 1.13 system and am a little confused by this
> > >> sequence.  It logs on okay showing a secure connect.  But then it
> won't do
> > >> the actual download. So I'm confused if it's the certificate or not.
> > >>
> > >
> > > Not the certificate.
> > >
> > > 150 Opening BINARY mode SSL data connection for
> > >> /GIMPAF.XML.
> > >> EZA2870I TLS security mechanism negotiation failed - data connection
> > >> closed
> > >> 425 ftpd: (data conn) SSL_accept unspecified
> > >> error
> > >>
> > >
> > > I haven't seen this one before.  Your FTP.DATA seems proper.  Could be
> a
> > > firewall issue as someone suggested.  Sorry, but I think you'll need to
> > > open a problem with IBM Comm Server support and ask for their help to
> debug
> > > further.  Perhaps an IP trace is in order.
> > >
> > > As Skip suggested, HTTPS is usually way easier to use, especially with
> > > respect to firewalls.  Check it out:
> > > http://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.
> > > ibm.zos.v2r2.gim3000/dsetups.htm
> > >
> > > Kurt Quackenbush -- IBM, SMP/E Development
> > >
> > >
> > > ----------------------------------------------------------------------
> > > For IBM-MAIN subscribe / signoff / archive access instructions,
> > > send email to [email protected] with the message: INFO IBM-MAIN
> > >
> >
> >
> >
> > --
> > The postings on this site are my own and don’t necessarily represent
> > Mainline’s positions or opinions
> >
> > Mark D Pace
> > Senior Systems Engineer
> > Mainline Information Systems
> >
> > ----------------------------------------------------------------------
> > For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to [email protected] with the message: INFO IBM-MAIN
>
> --
> http://www.fastmail.com - Choose from over 50 domains or use your own
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>



-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to