Troubleshoot Your Network Configuration

To process a RECEIVE ORDER request, SMP/E assumes that you have network connectivity from your z/OS system to the following CA Technologies servers:
cmcm
To process a RECEIVE ORDER request, SMP/E assumes that you have network connectivity from your z/OS system to the following CA Technologies servers:
  • eapi.broadcom.com
  • rdownloads.broadcom.com
For information about how to set up your z/OS system network configuration, consult your network administrator and the 
z/OS Communications Server: IP Configuration Guide
.
If a RECEIVE ORDER request fails with the following message, follow the suggested tasks in this topic to check for the necessary connectivity to CA’s servers:
GIM69207S ** RECEIVE PROCESSING HAS FAILED BECAUSE THE CONNECTION WITH THE SERVER FAILED. java.net.UnknownHostException: eapi.broadcom.com
SMP/E HTTPS operations require a host name to IP address resolution. This requirement is met using a Domain Name System (DNS) Name server. A Name server is defined using the NSINTERADDR or NAMESERVER statement within a resolver configuration file (TCPIP.DATA information). When using an application such as SMP/E, you can find a resolver configuration file in several locations. Because SMP/E uses a UNIX process for its HTTPS operations, the z/OS UNIX search order is used to find the resolver configuration file. For details about specifying the resolver configuration file location, see “Resolver configuration files” and "Search orders that are used in the z/OS UNIX environment" in the 
IBM z/OS Communications Server: IP Configuration Guide
.
However, because of the asynchronous UNIX process that SMP/E uses for its HTTPS operations, two exceptions exist for the documented search order: you cannot use the SYSTCPD DD statement or the RESOLVER_CONFIG environment variable to define the location of the resolver configuration file.
RECEIVE ORDER processing requires access to eapi.broadcom.com and rdownloads.broadcom.com.
  • The eapi.broadcom.com server is used to communicate before SMP/E and the CA Order Server.
  • The rdownloads.broadcom.com server is used to download packages using HTTPS protocol.
You can verify your Name server (eapi.broadcom.com and rdownloads.broadcom.com) setup by using the following sample job to invoke the DIG command:
//jobname JOB ... //NSLOOKUP EXEC PGM=BPXBATCH, // PARM='PGM /bin/dig eapi.broadcom.com' //STDOUT DD PATH='/tmp/&SYSUID..bpxbatch.stdout', // PATHOPTS=(OWRONLY,OCREAT,OTRUNC), // PATHMODE=SIRWXU //OUTSTEP EXEC PGM=IKJEFT01 //SYSTSPRT DD SYSOUT=* //INPUT DD PATH='/tmp/&SYSUID..bpxbatch.stdout', // PATHOPTS=(ORDONLY), // PATHDISP=DELETE //OUTPUT DD SYSOUT=*, // DCB=(RECFM=V,LRECL=256) //SYSTSIN DD * OCOPY INDD(INPUT) OUTDD(OUTPUT) /*
Although the DIG command can be run from the OMVS shell, this sample job runs the command in an environment similar to the environment in which SMP/E runs.
If your Name server is set up properly, the DIG command returns the IP address for the server. Command output is similar to the following sample:
Allocated socket 5, type udp ; <<>> DiG 9.2.0 <<>> eapi.broadcom.com ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49597 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;eapi.broadcom.com....IN.A ;; ANSWER SECTION: eapi.broadcom.com...300.IN.CNAME.internal-l7eapi-int-1216108561.us-east-1.elb.amazonaws.com. internal-l7eapi-int-1216108561.us-east-1.elb.amazonaws.com. 60 IN A 10.144.193.11 internal-l7eapi-int-1216108561.us-east-1.elb.amazonaws.com. 60 IN A 10.144.67.184 ;; Query time: 5 msec ;; SERVER: 141.202.1.108#53(141.202.1.108) ;; WHEN: Mon Jun 12 14:15:36 2017 ;; MSG SIZE rcvd: 130
If an IP address for the eapi.broadcom.com or rdownloads.broadcom.com server is not returned, verify that your Name server setup and resolver configuration file are proper. For Trace Resolver debug facility details, see "Diagnosing resolver problems" in the 
z/OS Communications Server: IP Diagnosis Guide
.