Ravi Maybe you should tune your Google skills!
I tried "inet_addr failed, cannot convert address" and - after a few hits where the partially sighted were leading the less ocularly fortunate a merry pointless dance - I found the following: http://support.sas.com/kb/3/540.html <quote> The following messages may be displayed when using the TCP communications access method: ERROR: Unable to initialize the TCP/IP Subsystem. ERROR: inet_addr failed, cannot convert address ''; These errors are likely to occur when the TCP/IP HOSTS file does not contain an entry for "localhost". For example, on Windows and Unix systems the HOSTS file would contain an entry similar to the following: 127.0.0.1 localhost On MVS and OS/390 systems, these messages may occur if SAS is unable to locate the TCPIP.ETC.SERVICES file. A possible solution is to allocate the TCPDATA file with a DDname of SYSTCPD. For example, ALLOC F(SYSTCPD) DA(prefix.SYS1.PARMS(TCPDATA)) </quote> Doesn't that solution bear an uncanny resemblance to what I managed to deduce? Unfortunately, the folk responsible for this information, while they may know Windows and UNIX well enough, are a bit "at sea" when it comes to the IP component of z/OS Communications Server. The problem is not related to the xxx.ETC.SERVICES file or not being able to access that file is just one of the ways you could get similar problems and far less likely than the missing "localhost" entry and the proposed solution is quite unrelated to the supposed problem. - If you are confused over how to solve your problem, please post the following: 1. If you believe you use a name server, mention the response of your colleagues responsible for your name server when you ask whether or not they resolve "localhost" to 127.0.0.1 2. Post the contents of your resolver procedure - if you have one 3. If you have a resolver procedure, post the contents of the resolver setup file 4. Post the contents of the generically named TCPIP.DATA file which applies to this SASMSTR procedure As you did before, you can "blank out" any identifying information with X's. If you are not familiar with the above points, get help from whomever in your organisation is responsible for the IP component of z/OS Communications Server. Based on the answers, I/we can advise how to deal with the problem of the missing "localhost" to "127.0.0.1" mapping. Incidentally, you might like to have a look into your "hosts" file on your PC. On this PC the file is found as C:\WINDOWS\system32\drivers\etc\hosts You will very probably see - fanfare! - that, apart from comments, the only entry is the following: 127.0.0.1 localhost Another incidentally: while searching I noticed you have had this problem since at least the end of August! Chris Mason On Thu, 18 Nov 2010 03:21:52 -0600, Ravi Kumar <[email protected]> wrote: >Before I talk to SAS thought to cross post here.. > >I am exploiting mailing service using SAS however on particular lpar only >it seems to be not working ..below is my JCL. > >//SENDMAIL EXEC SASMSTR, >// OPTIONS='EMAILSYS=SMTP EMAILHOST=xxx.xxx.xxx.xxx' >//SYSIN DD * > Filename emp email > From='[email protected]' > To='[email protected]' > Subject='TEST' > Attach ='xxxxx.TEMPFTP.TEXT'; > Data _Null_ ; > File emp; > put ; > run; > >I have checked the SMTP Mailer address in SMTP Config >EZA5348I IP Mailer Address : xxx.xxx.xxx.xxx ==same as used >in job. > >I get below error :- > >ERROR: Unable to connect to SMTP server. >ERROR: Unable to connect to SMTP server. >ERROR: Unable to connect to SMTP server. >ERROR: inet_addr failed, cannot convert address 'LOCALHOST'. >ERROR: inet_addr failed, cannot convert address 'LOCALHOST'. >ERROR: inet_addr failed, cannot convert address 'LOCALHOST'. > > >Now not able to crack it down to find why it's not able to resolve the SMTP >mailing server address... > >One of the diagnostic step I took was to start the packet trace on address >= xxx.xxx.xxx.xxx and port 25(smtp) however seems my job when ran could not >even hit this hence nothing was captured in the Packet tracing... > >Does anyone has any kind of thought or ideas to crack it down ...Thanks > > > > > > > >-------------------------------------------------------------------------- - >Note ** I have searched in archive and also cross post to tcp forum ** also >did google however when listed doesn't match with solution for me ** >-------------------------------------------------------------------------- ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
