My client has been using telnet long before openssh was available... and still does.
The port is in /etc/services. My inetd.conf looks like this: #====================================================================== # service | socket | protocol | wait/ | user | server | server program # name | type | | nowait| | program | arguments #====================================================================== # otelnet stream tcp nowait OMVSKERN /usr/sbin/otelnetd otelnetd -l shell stream tcp nowait OMVSKERN /usr/sbin/orshd orshd -LV login stream tcp nowait OMVSKERN /usr/sbin/rlogind rlogind -m oexec stream tcp nowait OMVSKERN /usr/sbin/orexecd orexecd -LV ssh stream tcp nowait OMVSKERN /usr/sbin/sshd sshd -i /etc/services has a line like this added: otelnet nnn/tcp OMVS (nnn is the port - usually n23 or nn23) The PORT statement in TCPIP profile has it reserved as well: nnn TCP OMVS ; OE TELNET SERVER Regards, Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ On Thu, 5 Apr 2012 09:44:39 -0500, McKown, John <john.mck...@healthmarkets.com> wrote: >Using SSH is, IMO, superior. But if you are dead set on using Telnet (perhaps >due to lack of an SSH client - I suggest PuTTY), then you must be running the >INETD daemon. And you must have a dedicated port number on z/OS to use. We use >port 2023. In the /etc/inetd.conf file, you need a line like: > >2023 stream tcp nowait BPXROOT /usr/sbin/otelnetd otelnetd -l -t -D login > >Replace the "2023" with the port you want to use. Then, to get a UNIX shell >prompt, you telnet into that port number. This works for me. > >-- >John McKown >Systems Engineer IV >IT > >Administrative Services Group > >HealthMarkets(r) > >9151 Boulevard 26 * N. Richland Hills * TX 76010 >(817) 255-3225 phone * >john.mck...@healthmarkets.com * www.HealthMarkets.com > >Confidentiality Notice: This e-mail message may contain confidential or >proprietary information. If you are not the intended recipient, please contact >the sender by reply e-mail and destroy all copies of the original message. >HealthMarkets(r) is the brand name for products underwritten and issued by the >insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance >Company(r), Mid-West National Life Insurance Company of TennesseeSM and The >MEGA Life and Health Insurance Company.SM > > > >> -----Original Message----- >> From: IBM Mainframe Discussion List >> [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Chokalingam Thangavelu >> Sent: Thursday, April 05, 2012 8:52 AM >> To: IBM-MAIN@bama.ua.edu >> Subject: Accessing USS on Mainframe thru Telnet >> >> Hi, >> >> I am unable to access the Unix system services thru Telnet >> and could not find below configurations in USS files. >> >> >> 1. Could not find 'otelnet in file /etc/services' which >> points to the port of the USS telnet. >> >> 2. There is no otelnetd daemon or the configured inetd >> is running on the system >> >> 3. Could not fine INET in /etc/inet.conf >> >> Please let me know how to define above TELNET configurations >> and access USS thru TELNET. >> >> Regards, >> Chokalingam >> >> Please do not print this email unless it is absolutely necessary. >> >> The information contained in this electronic message and any >> attachments to this message are intended for the exclusive >> use of the addressee(s) and may contain proprietary, >> confidential or privileged information. If you are not the >> intended recipient, you should not disseminate, distribute or >> copy this e-mail. Please notify the sender immediately and >> destroy all copies of this message and any attachments. >> >> WARNING: Computer viruses can be transmitted via email. The >> recipient should check this email and any attachments for the >> presence of viruses. The company accepts no liability for any >> damage caused by any virus transmitted by this email. >> >> www.wipro.com >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN >> >> > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
