Home > Error Code > Error Code 00017

Error Code 00017


If you have received it in error, please notify the sender immediately and delete the original and any copy or printout. Also, keyring names are case sensitive, so that could be it as well. With such a dump I could tell exactly what is going wrong. The KEYRING statement is also the place where you could specify *AUTH*/* if you wanted to try the virtual keyring I mentioned in option 1. http://megavoid.net/error-code/error-code-007-340.html

Don't forget you have to RACLIST the RDATALIB class for it to work. Please try again later. If so, mod_tls will refuse to write a log file there... FC0904 authServer: secure_socket_open () FC0971 authServer: secure_socket_init () FC0984 authServer: secure_socket_init failed with rc = 410 (SSL message format incorrect) FC1339 endSecureConn: entered EZA2897I Authentication negotiation failed FC1371 endSecureEnv: entered CZ0609

Error Code 00017

ArcGIS for Desktop Home Documentation Pricing Support ArcGIS Platform ArcGIS Online ArcGIS for Desktop ArcGIS for Server ArcGIS for Developers ArcGIS Solutions ArcGIS Marketplace About Esri About Us Careers Insiders Blog So I ran a RACDCERT CHECKCERT (MVS.DATASET.FOR.GTE,FROM,WEB) to verify it was a good xfer to the mainframe. Maybe others know about the specific fix to the FTP daemon. 2. I will tell you what the error is with the TLS handshake.

Follow-Ups: RE: FTP Secure (TLS/SSL) to BMC Support - TLS handshake failed From: Gray, Larry - Larry A References: RE: FTP Secure (TLS/SSL) to BMC Support - TLS handshake failed From: SC3799 loggedIn: entered CZ1054 ftpPass: entered with argc = 2 SC2588 sendCmd: entered EZA1701I >>> PASS FU0521 secureWrite: entered SC3026 getReply: entered SC3995 getNextReply: entered with waitForData = TRUE FU0421 secureRead: SC0473 initConnection: entered SC0549 initConnection: Calling getaddrinfo() with partner- ftpssl.farecast.com SC0588 initConnection: getaddrinfo() returned. Secure_socket_init Failed With Rc = 420 com [Download message RAW] Hi Steven, I think we're past the SSL handshake at this point and on to other issues with FTP configuration.

Logged Print Pages: [1] « previous next » forums.proftpd.org » OS Support » Other » TLS Authenication - Mainframe to Solaris SMF 2.0.11 | SMF © 2015, Simple Machines XHTML Std Return Code = 10220 CZ1152 SETCEC code = 11 >>>>>>>>>>>>>>LOOK SC3817 setLoggedIn: entered CU2842 write_smf_record: entered with type -1. I've asked it a couple of times and the reply has always been they got the file. http://marc.info/?l=racf-l&m=122962367324378 Now you can give a user READ access to a specific keyring using profiles in the RDATALIB class.

Sorry I don't have much experience with that. Secure_socket_init Failed With Rc = 435 You don't have to create this keyring (it's virtual). I'm thinking maybe that's the way it's still set. SC3360 smf_stat_session: entered GU4167 checkSpec: entered with 04 (0,3) CU1598 subtype_102: entered CU1701 build_security_section: entered SC3689 getLastReply: entered PC0907 setClientRC: entered SC3689 getLastReply: entered PC0977 setClientRC: std_rc=26530, rc_type=STD, rc=26530 >>>>>>>>>>LOOK EZA1735I

Std Return Code = 10220

The KEYRING statement is described here: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/F1A1B471/2.12.68?SHELF=EZ2Z \ O10K&DT=20080122114206 Regards, Mike Steven Wake Sent by: RACF Discussion List 12/16/2008 06:07 PM Please respond to RACF Discussion List To Go Here Find an XFINITY Store or service center near you. Error Code 00017 I know it works on the ldapsearch command but haven't tried it with FTP yet. Eza1735i Std Return Code = 10234, Error Code = 00010 COM> Date: 2010-03-19 22:02:21 Message-ID: 201003192202.o2JHQglm019880 () malibu !

Cancel icon-exclmation_orange_circle We’re Sorry - an error has occurred. check my blog On the client? Search the archives on IBMTCP-L or IBM-MAIN Dave Gibney Information Technology Services Washington State University > -----Original Message----- > From: Linux on 390 Port [mailto:[email protected]] On Behalf Of > Donald Russell Geodatabase annotation offers better drawing performance and a more efficient editing experience than map annotation. Eza2897i Authentication Negotiation Failed

EZA1736I ftp.gactr.uga.edu Um Google Groups Discussions nutzen zu können, aktivieren Sie JavaScript in Ihren Browsereinstellungen und aktualisieren Sie dann diese Seite. . What does a TLSLog show? this content Rate this article on a scale of 1 - 5 5 stars 4 stars 3 stars 2 stars 1 star Article Comment, maximum of 100 characters Submit Previous Article Next Article

Verifed with BING the start and end date and serial number ending with 1A5 with the one I found and that it match theirs. So if you created a keyring for USER1 named RING1, as I mentioned in option 4 of my note, you must specify KEYRING USER1/RING1 when you configure the FTP client. There's something new in z/OS 1.9 called a virtual keyring. *AUTH*/* is the name of the virtual keyring that includes all of the CERTAUTH certificates.

More info here: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/ICHZD180/2.26.4?SHELF=EZ2ZO \ 10K&DT=20070427233434 Regards, Mike [prev in list] [next in list] [prev in thread] [next in thread] Configure | About | News | Addalist | SponsoredbyKoreLogic [prev

cipherspecs = FC0326 ftpAuth: environment_open () FC0444 ftpAuth: environment_init () FC0453 ftpAuth: environment initialization complete EZA1701I >>> AUTH TLS 234 Proceed with negotiation. IBM ! hmmm > > Well, I'll keep digging. > > Cheers > > > On Wed, Dec 23, 2009 at 09:08, Stewart Thomas J > wrote: > > If I remember Although we have taken reasonable precautions to ensure no viruses are present in this e-mail, we accept no liability for any loss or damage arising from the use of this e-mail

Top Profile Reply with quote mgcicero Post subject: Re: z/OS Client using implicit TLS connection to FilezillaPostPosted: 2009-11-25 20:14 Offline 500 Command not understood Joined: 2009-11-25 15:40 Posts: 3 Logged surlypants New user Posts: 3 Re: TLS Authenication - Mainframe to Solaris « Reply #4 on: February 14, 2007, 03:05:02 pm » i'm having the same scenario on freebsd 5.5-STABLE So that's one approach. http://megavoid.net/error-code/error-code-005-3ds.html With z/OS 1.9 there's more granular support for allowing a user to have READ access to an individual keyring owned by someone else, rather than option 3 above.