The handshake error means that you need to load the CAs from the
certificate. Don't try to import the whole thing. You need to import one
or all (there could be more than one) CA from the cert into your *SYSTEM
You'll need to do it one at a time, starting at the top most level and
working your way down.
First go here to see how to export the CA(s) from the .cer file:
Then here to import them into the *SYSTEM store:
Forget about the other things with the client certificate and creating an
application. That doesn't apply.
On Tue, Sep 10, 2013 at 2:05 PM, Versfelt, Charles <CVERSFELT@xxxxxxxxx>wrote:
Thank you for the explanation! I definitely needed that background for
Now... I found out some more information that may shed light on my
I tried sending my CSV send again and again failed with the handshake
error. I wanted to try creating an application through the DCM and do it
that way. Bruce (he's the Operations VP) sent me a "Goto meeting" and we
went through the screens together.
During the process, I asked about the final certificate, a .p12 file. He
told me that, while he was unable to load the .p12, he was able to "launch"
the .p12 and turn it into a .cer!
This doesn't sound right to me. I suspect my problem is because we never
loaded the .p12 in its correct form.
Am I right, and if so, is there anything different he needs to do to load
a .p12 certificate on the AS/400?
PS. No, using the named application didn't work either. Handshake error.
This email message has been delivered safely and archived online by
Mimecast. For more information please visit http://www.mimecast.com
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
This mailing list archive is Copyright 1997-2013 by MIDRANGE dot 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 here. If you have questions about this, please contact