Re: Using telnet with USS

 I hope you got telnet working.
As for INETD, there is only a single instance running in MVS Unix. What you see in MVS is the MVS address space (dubbed) where it is running. Cancel this address space would terminate the INETD process.
As for the services file, stop thinking singular like in Unix and think combined. Unix admins have a different skillset than z/OS sysprogs. They want to use vi instead of ISPF edit. Additionally, remember that z/OS does not require a file system, so /etc may not exist but TCP still requires the /etc/services definitions.
As I said before, debug this as if it were a Unix system. Use netstat and verify the port is listen by the INETD process. Look at unix logs for error messages. Instead of specifying the service name in inetd conf, specify the port number.  Look as MVS syslog to see if there are messages there.. 

Jon

    On Monday, September 9, 2019, 07:42:28 AM PDT, John Murray [email protected] [H390-MVS] <[email protected]> wrote:  
 
     
There are two instances of inetd, one in USS and one in z/OS. The USS one uses the /etc/services file to determine which ports are associated with which applications and the z/OS uses some ETC.SERVICES dataset to do the same. So my question is: how does z/OS determine which ETC.SERVICES dataset to use?


The reason I ask the question is because I cannot get telnet to contact USS.. I know it’s because I have to use different ports for telnet on USS and z/OS which I believe I’ve done, but it doesn’t work. My theory is that I’ve update the wrong ETC.SERVICES dataset.

John Murray

Ottawa

On 8 Sep 2019, at 16:38, [email protected] [H390-MVS] <[email protected]> wrote:

Do you mean /etc/services from Unix file system? It's not a dataset. And it does not define what is started and what not.