|
Scott, Right you are. I think I saw the -93 error at one point before I configured DCM. Now I see -24 (certificate expire) on our system. So I think you are right about the FTP server initializing for SSL even if it is not used. I've usually been able to see diagnostic information in the FTP server job log when something like this happens. But IFS file system operations do not generate nearly the amount of diagnostic information into the joblog that you might like. I would be inclined at this point to look at the authority matrix on the IFS directory. If the directory owner does not match the user ID of the FTP session there could be problems creating the file. Patrick ----- Original Message ----- From: "Scott Klement" <klemscot@xxxxxxxxxxxx> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> Sent: Saturday, March 01, 2003 1:30 AM Subject: Re: Cannot FTP one IFS file > > Patrick, > > As Rob already pointed out, error -93 is "SSL Not Available". See > file QSYSINC/H member SSL. This is part of the original SSL API, > not the GSKit. (The telltale sign of that is that the number is > negative) > > I think what Rob is probably seeing here is that his FTP server is > trying to run both as an SSL server and as a regular server. When the > SSL portion of it does not work (because SSL is not configured on his > machine) it reports this error and then just works as a non-SSL server. > > That's just a guess -- but I know that all of the iSeries TCP servers > do try to run as SSL if they can. > > I don't think that error message is actually a symptom of the problem he's > experiencing. But, without actually seeing what's going on, it's hard to > say. > > > On Fri, 28 Feb 2003, Patrick Townsend wrote: > > > Rob, > > > > I agree, it is odd. I looked for the 93 error in the gskssl.h file but > > didn't find anything. This C header file has the return codes and error > > codes for SSL APIs based on the GSKit SSL interface. Looks like time to > > spend some $$ on IBM support.... > > > > Patrick > > > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.