Specialty Forums
Security and Virus
General Hardware
CPUs/Overclocking
Networking
Digital Photo/Video
Office Software
PC Gaming
Console Gaming
Programming
Database
Web Development
Digital Home

General Forums
Windows XP
Windows Vista
Windows 95/98
Windows Me
Windows NT
Windows 2000
Win Server 2008
Win Server 2003
Windows 3.1
Linux
PDAs
BeOS
Novell Netware
OpenVMS
Solaris
Disk Op. System
Unix
Mac
OS/2

Drivers
Driver Scan
Driver Forum

Software
Automatic Updates

BIOS Updates

My Computing.Net

Solution Center

Free IT eBook

Howtos

Site Search

Message Find

RSS Feeds

Install Guides

Data Recovery

About

Home
Reply to Message Icon Go to Main Page Icon

Subject: Hostname Problems

Original Message
Name: DrWorm
Date: May 18, 2004 at 15:02:32 Pacific
Subject: Hostname Problems
OS: OpenVMS
CPU/Ram: Alpha/64MB
Comment:
I came across a DEC 3000 recently. It was running OpenVMS. It has an odd host name (WPCQ), i think. I asked a friend who knows VMS to change it for me. I gave him telnet access. He was trying to change it to 'below'. However, he somehow messed up and now it won't boot. Actually, it will, but it gives me a 'User Authorization Error' when I try to log on. Can anybody help me? What are the steps to change a hostname?


Report Offensive Message For Removal

Response Number 1
Name: Hakan Andersson (by HakAnd)
Date: May 18, 2004 at 23:31:54 Pacific
Subject: Hostname Problems
Reply: (edit)
Well,.....
It's easy to change just the nodename, but
a lot of applications needs to be
reconfigured, like DECnet, TCPIP,........

OK,.......to get you going.....

>>> boot -flag 0,1 'device'

SYSBOOT> SHOW SCSNODE
SYSBOOT> SET SCSNODE "new_name"

SYSBOOT> SET /STARTUP OPA0:
SYSBOOT> CONTINUE

this will finally get you a "$"

$ SPAWN
$ SET DEF [VMS$COMMON.SYS$STARTUP]
$ @VMS$INITIAL-050_VMS
$ SET DEF SYS$SYSTEM
$ MC AUTHORIZE
UAF> now change your account
UAF> EXIT
$ MCR SYSGEN
SYSGEN> SET /STARTUP SYS$SYSTEM:STARTUP.COM
SYSGEN> WRITE CURRENT
SYSGEN> EXIT

Now it's time for a reboot....
If the node ends up with SYSBOOT>
just type in CONTINUE.

Hopefully you now has a node with a correct
name and that you can login.

You need to change the nodename in the file
SYS$SYSTEM:MODPARAMS.DAT, otherwise you get
the old name back next time you run AUTOGEN.


Report Offensive Follow Up For Removal

Response Number 2
Name: Hakan Andersson (by HakAnd)
Date: May 18, 2004 at 23:36:14 Pacific
Subject: Hostname Problems
Reply: (edit)
Let's talk about the different steps when the the node is up and running.
You can mail me if you need faster support.

Report Offensive Follow Up For Removal

Response Number 3
Name: DrWorm
Date: May 21, 2004 at 12:26:17 Pacific
Subject: Hostname Problems
Reply: (edit)
I got the computer to boot! And the node name is correct. Thank you!

Report Offensive Follow Up For Removal

Response Number 4
Name: DrWorm
Date: May 22, 2004 at 10:22:17 Pacific
Subject: Hostname Problems
Reply: (edit)
Oops. I just found out that the Batch queue sitll thinks that the node name is WKRQ. What can I do to fix this?

Report Offensive Follow Up For Removal

Response Number 5
Name: Hakan Andersson (by HakAnd)
Date: May 22, 2004 at 11:29:36 Pacific
Subject: Hostname Problems
Reply: (edit)
Do you mean the queue has on=WKRQ ?

Do a
STOP/QUE/RESET 'queue'
START/QUE/ON='newname::' 'queue'

or a

STOP/QUE/RESET 'queue'
DELETE/QUE 'queue'
INIT/QUE/BATCH 'queue'


Report Offensive Follow Up For Removal



Use following form to reply to current message:

   Name: From My Computing.Net Settings
 E-Mail: From My Computing.Net Settings

Subject: Hostname Problems

Comments:

 
  Homepage URL (*): 
Homepage Title (*): 
         Image URL: 
 


Data Recovery Software



Version Tracker Pro
Keep your software current and secure, effortlessly

Click Here for a Free Scan

Driver Agent
Automatically find the latest drivers for your computer.
Click Here for a Free Scan



The information on Computing.Net is the opinions of its users. Such opinions may not be accurate and they are to be used at your own risk. Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE

All content ©1996-2007 Computing.Net, LLC