I am worn out from all of these "learning" opportunities and want to get back to "doing" the job I am paid to do.
There should be no need for me to start writing code or installing curl or any of the other fine suggestions here. As I see it. IBM changed a reliable working encrypted exchange by adding an intermediate certificate to the chain of signers for their certs. This forces the world to add information to their local keystores to be able to 'confirm' details required to complete the exchange we have been performing since the last forced change upon their customer base. My complaint at this point is that I have added the new cert and yet the new failures remain. This is needlessly obscured by the fact that the now broken Receive Order job fails with a useless Java I/O error message that gives no clue referring to the cert errors involved. RACF is of no help when it tells me that the new TLS RSA SHA256 G2 Digicert certificate is "incomplete" without telling me WHY. Or telling me what to go acquire to "complete" it. Additional personal frustration arises when I do not understand or agree to the arguments about why the exchange of ptfs is even required to be encrypted during transfer. Placing arbitrary barriers in the path to the acquisition of improvements and corrections is counter productive to me. Enough ranting. Fair or not, this is the world I am forced to endure. Time to get back to my next guess at a resolution. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
