SMPE internet retrieval gives connection failed

Products

• CIS
• COMMON SERVICES FOR Z/OS
• 90S SERVICES
• DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS
• COMMON PRODUCT SERVICES COMPONENT
• Common Services
• CA ECOMETER SERVER COMPONENT FOC
• Easytrieve Report Generator for Common Services
• INFOCAI MAINTENANCE
• IPC
• UNICENTER JCLCHECK COMMON COMPONENT
• LDAP SERVER FOR Z/OS
• Mainframe VM Product Manager
• CHORUS SOFTWARE MANAGER
• CA ON DEMAND PORTAL
• CA Service Desk Manager - Unified Self Service
• PAM CLIENT FOR LINUX ON MAINFRAME
• MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME
• GRAPHICAL MANAGEMENT INTERFACE
• WEB ADMINISTRATOR FOR TOP SECRET
• Xpertware
• MF - MISC OLD CODES
• SERVICE ASSURE
• GENERIC UNISERVICE FOR CICS
• GENERIC UNISERVICE II
• Output Management Web Viewer

Issue/Introduction

When getting a 'Connection failed' message at the SMPE Internet retrieval to get the latest maintenance downloaded and possibly received in your product CSI, it can have multiple causes and possible solutions...

Most of the time it is a connection issue with our servers because of firewall/proxy settings... 

How can you trace an debug the connection and what are the possible solutions.

Environment

Release : 15.0

Component : CCS390 - CA COMMON SERVICES FOR Z/OS

Resolution

The first thing to do is to check the Network configuration... 
See his special chapter in the manual :  

https://techdocs.broadcom.com/us/en/ca-mainframe-software/traditional-management/mainframe-common-maintenance-procedures/1-0/configure-ca-smp-e-internet-service-retrieval/troubleshoot-your-network-configuration.html

If this doesnt solve the issue, then add these 2 statements to the SMPE Receive order job :

-Djava.security.debug
-Djavax.net.debug

Like this :

<CLIENT                                                      
  downloadmethod="https"                                     
  javahome="/C/java/java64bt/v8r0m0/usr/lpp/java/J8.0_64"    
  classpath="/usr/lpp/smp/classes"                           
  javadebugoptions="-Dcom.ibm.smp.debug=severe -showversion  
                                  -Djava.security.debug                    
                                  -Djavax.net.debug">                      
</CLIENT>                                                    

If that doesnt show the error, it's possible there is still an issue with the firewall/proxy server settings and it's possible to add an additional HTTP Proxy statement.. 
Like this:

<CLIENT                                                    

  downloadmethod="https">                                   

  <HTTPPROXY host="<your proxy server host name>" port="8080">  

 </HTTPPROXY>                                                

</CLIENT>