Shawn Gordon wrote:
>
> I'm bringing all my systems up to 5.5 and PP 2 this weekend from 5.0,
> and I want to start using Telnet.  Can anyone point me in the right
> direction to get started?  I'm sure there is something in the pile of
> papers I got from HP, but I'd rather not wade.
>
> Thanks,
> Shawn

Shawn, I have included my cheat sheet on setting up at least in-bound
telnet below:

Configuring In-Bound Telnet On the HP3000

I had success configuring the in-bound Telnet capability of MPE/iX
version 5.5 using Powerpatch 1 so I thought that I would share what I
did to accomplish the task.  Unfortunately, the customer did not have a
printer connected to the 3000 yet, so my "sharing" is only as good as my
notes and memory.  The Response Center can help with this too if you run
into difficulty.

After Powerpatch #1 or 2 is installed and the system is again
operational, a few final steps need to be performed for in-bound telnet
to function properly:

o       Logon to MANAGER.SYS,NET

o       Do a :LISTF SERVICES,2
            o   If a file exists, use :EDITOR to text in and insure that
                TELNET is not commented out.
            o   If a file does not exist, copy the file SERVSAMP.NET
and                  call it SERVICES.NET. Review the SERVICES.NET file
to
                 see if TELNET is commented out or not.
o       Type in the following command and press enter:
            NEWLINK /etc/services, services.net.sys

o       Do a :LISTF PROTOCOL.NET.SYS,2
            o  If the file does not exist, copy the file PROTSAMP.NET
               and call it PROTOCOL.NET
o       Type the following command in at an MPE/iX colon prompt:
            NEWLINK /etc/protocols, protocol.net.sys

o       Do a :LISTF INETDCNF.NET.SYS,2
            o  If the file does not exist, copy the file
INCNFSMP.NET                 and call it INETDCNF.NET.  Edit the file
and uncomment
              the TELNET line.
            o  If the file already existed, edit the file and uncomment
                the TELNET line.
o       Type the following command at the MPE/iX colon prompt:
            NEWLINK /etc/inetdcnf, inetdcnf.net.sys

If the network had been properly configured and these 3 files properly
copied and the NEWLINK commands executed, In-bound TELNET should
function properly after the job JINETD.NET.SYS has been launched
(add/change passwords in job stream first) and is running.  This job
MUST BE running at anytime someone wishes to use the in-bound TELNET
capabilities.  Best to leave running all of the time.

The customer tested the In-bound TELNET capability from 3 different
computer systems and it functioned as expected.

Let me know if you see any corrections to this.

Hope this helps....

Mike Tilford
ASE - Falls Church
Hewlett-Packard Company
email: [log in to unmask]
(703) 234-2495