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
Subject: OpenVMS VAX boot question
Original Message
Name: Dmedia
Date: April 13, 2008 at 14:11:49 Pacific
Subject: OpenVMS VAX boot questionOS: OpenVMS VAXCPU/Ram: KA670 V3.7 VMB 2.12Model/Manufacturer: vax4000-300
Comment: This box (vax4000-300)was given to me to wiht with [OpenVMS VAX (ver6.1)]. No problem with startup before today.I can startup_p1 "MIN" to get inside. An OPA0 startup has two major issues; licenses and images. I was able to load licenses during the "MIN" session so they are okay.
But during a "regular" startup (meaning as the box was given to me) neither images nor licenses will load. They just stopped loading and the box hangs.
I'm not familiar with the O/S, but am learning. It seems to me this is a pretty basic startup problem, but could use some help.
Thanks.
DM
Report Offensive Message For Removal
Response Number 1
Name: HakZan
Date: April 14, 2008 at 05:07:35 Pacific
Subject: OpenVMS VAX boot question
Reply: (edit )What do you mean by "the box hangs" ?You can log the boot by setting the parameter STARTUP_P2 = "VDC"
This will create the file SYS$SYSTEM:STARTUP.LOG
or
If you set STARTUP_P2 = "V" you vill get the output on the console.
Try this and report your findings.
regards,
Hakan Zanderau HA-solutions
Report Offensive Follow Up For Removal
Response Number 2
Name: Dmedia
Date: April 14, 2008 at 13:05:18 Pacific
Subject: OpenVMS VAX boot question
Reply: (edit )Thanks for the reply.>You can log the boot by setting the >parameter STARTUP_P2 = "VDC"
>This will create the file >SYS$SYSTEM:STARTUP.LOG
The log was created. The boot process is evidently quite complicated. The log file is 1805 lines (ugh!).
>What do you mean by "the box hangs" ?
Sorry. The system does not try to start. It drops to >>> prompt. I set the boot device, b/1 to sysboot, SET "parameters" and CONTINUE.
Regards,
Dennis
DM
Report Offensive Follow Up For Removal
Response Number 3
Name: HakZan
Date: April 15, 2008 at 01:14:27 Pacific
Subject: OpenVMS VAX boot question
Reply: (edit )It drops to ">>>".....from what ?Does not try to start ?......you got 1800 lines in the logfile. The logfile contains all VMScommands executed during the boot.
$ TYPE/TAIL=20 SYS$SYSTEM:STARTUP.LOG will give you the last 20 lines executed.
If a VMS node "drops" to ">>>", it has probably crashed.
$ ANAL/CRASH SYS$SYSTEM:SYSDUMP.DMP SDA> SHOW CRASH
regards,
Hakan Zanderau HA-solutions
Report Offensive Follow Up For Removal
Response Number 4
Name: Dmedia
Date: April 16, 2008 at 18:32:01 Pacific
Subject: OpenVMS VAX boot question
Reply: (edit )>$ ANAL/CRASH SYS$SYSTEM:SYSDUMP.DMP >SDA> SHOW CRASHyielded: VAX/VMS System dump analyzer %SDA-E-DUMPEMPTY, dump file contains no vaild dump
So I guess it did not crash as I presumed.
>$ TYPE/TAIL=20 SYS$SYSTEM:STARTUP.LOG
Yields the 20 lines. If you don't mind I took a picture to avoid writing it out: disk-media.com/v420_1.jpg
Line 7 is slightly cut off: "...then goto done_subprocess_wait"
I can see this is not helping much. Should I look for something specific to help explain images not being loaded?
Regards,
Dennis
DM
Report Offensive Follow Up For Removal
Response Number 5
Name: Dmedia
Date: April 19, 2008 at 14:06:11 Pacific
Subject: OpenVMS VAX boot question
Reply: (edit )What I meant to say was is there something in the STARTRUP.LOG that I need to look for that will explain why images are not being loaded? And if so what should I post? Thanks again.
DM
Report Offensive Follow Up For Removal
Response Number 6
Name: HakZan
Date: April 20, 2008 at 00:37:04 Pacific
Subject: OpenVMS VAX boot question
Reply: (edit )Mail me STARTUP.LOG and I will take a look at it.regards,
Hakan Zanderau HA-solutions hakan.zanderau@ha-solutions.se
Report Offensive Follow Up For Removal
Response Number 7
Name: Dmedia
Date: April 21, 2008 at 08:27:25 Pacific
Subject: OpenVMS VAX boot question
Reply: (edit )There isn't a way to output files at the moment. It is not on a network and no printer attached.I'll see what I can do.
Thanks.
DM
Report Offensive Follow Up For Removal
Response Number 8
Name: HakZan
Date: April 22, 2008 at 01:11:42 Pacific
Subject: OpenVMS VAX boot question
Reply: (edit )Connect the consoleport to a PC and use Hyperterm to catch the output.regards,
Hakan Zanderau HA-solutions
Report Offensive Follow Up For Removal
Response Number 9
Name: Dmedia
Date: April 23, 2008 at 14:20:19 Pacific
Subject: OpenVMS VAX boot question
Reply: (edit )Still working on that. Here is something in the mean time. Hope it helps and thanks again. www.disk-media.com/0211.jpg
www.disk-media.com/0208.jpg
www.disk-media.com/0211.jpg
Regards,
DM
Report Offensive Follow Up For Removal
Response Number 10
Name: HakZan
Date: April 23, 2008 at 21:54:00 Pacific
Subject: OpenVMS VAX boot question
Reply: (edit )It really doesn't say anything.....The file SYS$SYSTEM:VMS$INITIAL-050_CONFIGURE.COM is one of the first files executed during boot.
no errormessages......just commands....
Are they really the last pages in STARTUP.LOG ?
I need to see the whole file.
regards,
Hakan Zanderau HA-solutions
Report Offensive Follow Up For Removal
Use following form to reply to current message: