[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Calling webservices from ISeries v5r3 Cobol Program
You ping from the System i command line (call qcmd)
ping www.webservicex.net
These are the messages that are returned...
Verifying connection to host system WWW.WEBSERVICEX.NET at address
209.162.186.60.
PING reply 1 from 209.162.186.60 took 103 ms. 256 bytes. TTL 105.
PING reply 2 from 209.162.186.60 took 106 ms. 256 bytes. TTL 105.
PING reply 3 from 209.162.186.60 took 98 ms. 256 bytes. TTL 105.
PING reply 4 from 209.162.186.60 took 106 ms. 256 bytes. TTL 105.
PING reply 5 from 209.162.186.60 took 104 ms. 256 bytes. TTL 105.
Round-trip (in milliseconds) min/avg/max = 98/103/106.
Connection verification statistics: 5 of 5 successful (100 %).
>From the QCMD screen, use F10 to see detailed messages. The name to number
resolution is what we are checking (first line of returned messages). It is
common that ping may be blocked, but the name resolution needs to work.
On your system i, you can check the DNS setup by prompting a CHGTCPDMN
command. In the domain server section, you should have a list of valid DNS
servers. We list two internal servers and one DMZ server on our system. If
the servers listed on your system are external, then you need to check if
port 53 is open (so that your system i can reach those servers). If you know
how to use NSLOOKUP; you can use it to verify some information about DNS. It
is on our system I (V5R4).
Mike
-----Original Message-----
From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of kakou kesse
Sent: Monday, September 10, 2007 10:54 AM
To: HTTPAPI and FTPAPI Projects
Subject: Re: Calling webservices from ISeries v5r3 Cobol Program
Hello Mike,
Pingging on url or IP doesn't return response (I have to cancel request). Do
you test it from your home, perhaps this server rejects ping request ? It's
just to be sure..cause when I'm pingging www.google.com i've got the same
"no return".
I'll see tomorrow my net administrator for verify... That's stange, in fact,
for me, all HTTP streams are open in our firewall..
Regards
2007/9/10, Mike Krebs <mkrebs@xxxxxxxxxxxxxxxxxx>:
>
> Sorry, finger check on the ping command.
> PING www.webserviceX.NET
>
>
> -----Original Message-----
> From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Mike Krebs
> Sent: Monday, September 10, 2007 9:33 AM
> To: 'HTTPAPI and FTPAPI Projects'
> Subject: RE: Calling webservices from ISeries v5r3 Cobol Program
>
> >"host not found" perhaps a firewall problem,
>
> Check to make sure you can resolve DNS.
> PING www.weverviceX.net
>
> Even if the ping can't reach anything, you should see something like this.
> Verifying connection to host system WWW.WEBSERVICEX.NET at address
> 209.162.186.60.
> The 209.162.186.60 is the important part.
>
>
> > what is the port used for webservice communications ?
>
> Port 80 is standard (the traffic is HTTP protocol). I think all the
> examples use port 80 (there might be some using https so 443 for
> those), but you can use other ports. In addition, Scott has been
> working on proxy support. So, it might be possible to use your proxy.
>
> Mike Krebs
>
> ----------------------------------------------------------------------
> - This is the FTPAPI mailing list. To unsubscribe, please go to:
> http://www.scottklement.com/mailman/listinfo/ftpapi
> ----------------------------------------------------------------------
> -
>
> ----------------------------------------------------------------------
> - This is the FTPAPI mailing list. To unsubscribe, please go to:
> http://www.scottklement.com/mailman/listinfo/ftpapi
> ----------------------------------------------------------------------
> -
>
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------