- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- VMS Startup
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2006 05:18 AM
04-03-2006 05:18 AM
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2006 05:30 AM
04-03-2006 05:30 AM
Re: VMS Startup
regards Kalle
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2006 08:56 AM
04-03-2006 08:56 AM
Re: VMS Startup
Don
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2006 09:04 AM
04-03-2006 09:04 AM
SolutionI never tried, but you can create the logfile out of your startup procedure then I thik we will have to search all the COM procedure got executed from the startup procedure.
$ RUN SYS$SYSTEM:SYSMAN
SYSMAN> STARTUP SET OPTIONS/VERIFY=FULL/OUTPUT=anyfile.log
Archunan
Archie
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2006 10:11 AM
04-03-2006 10:11 AM
Re: VMS Startup
SYSMAN STARTUP SET OPTIONS
/VERIFY=FULL Displays every line of DCL executed by component startup procedures and by STARTUP.COM.
/VERIFY=PARTIAL Displays every line of DCL executed by component startup procedures, but does not display DCL executed by STARTUP.COM.
http://h71000.www7.hp.com/doc/73final/6017/6017pro_010.html#startlog
/OUTPUT=FILE
/OUTPUT=CONSOLE Creates SYS$SPECIFIC:[SYSEXE]STARTUP.LOG, which contains all of the output generated by startup procedures. Alternatively, you can display the output on the console.
/CHECKPOINTING Displays informational messages describing the time and status of each startup phase and component file.
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-04-2006 08:43 AM
04-04-2006 08:43 AM
Re: VMS Startup
Phil
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-04-2006 10:52 AM
04-04-2006 10:52 AM
Re: VMS Startup
Don't forget that you can get a full list of the first level of invoked files by using the SYSMAN utility to display the two startup databases (STARTUP$STARTUP_LAYERED and STARTUP$STARTUP_VMS).
Once you are in SYSMAN, the specific commands are:
STARTUP SET DATABASE STARTUP$STARTUP_LAYERED
STARTUP SHOW FILE
STARTUP SET DATABASE STARTUP$STARTUP_VMS
STARTUP SHOW FILE
For many purposes, this is less work than dealing with a trace of the startup process. It can also be done on live systems WITHOUT the need for a reboot.
- Bob Gezelter, http://www.rlgsc.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-04-2006 08:09 PM
04-04-2006 08:09 PM
Re: VMS Startup
I rather like Bob's solution, but there you have to realise, that one of the procedures you will find is SYS$MANAGER:SYSTRATUP_VMS.COM.
Depending on the specific system setup, some or most of the work is done from there (especially in systems that were initially set up way back when, because that WAS the original way to set thing up).
So, it would be wise to also inspect that file.
hth.
Proost.
Have one on me.
jpe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2006 12:04 AM
04-05-2006 12:04 AM
Re: VMS Startup
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2006 12:14 AM
04-05-2006 12:14 AM
Re: VMS Startup
SYS$MANAGER:SYSTARTUP_VMS.COM
SYLOGICALS.COM
SYCONFIG.COM
SYSECURITY.COM
SYPAGSWPFILES.COM
Many system managers like to create a SYS$MANAGER:DISK_MOUNTS.COM or something similar that contains all of the disk mounting commands and then insert a call to it from whichever procedure is appropriate for their site.
There are good reasons for each of these depending on the flavor of your system.
Have fun searching :-)
Robert
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-11-2006 02:29 PM
04-11-2006 02:29 PM
Re: VMS Startup
You may also want to try a verbose startup trace using console flags:
>>> b -fl
20000 enables verbose startup logging, and 10000 turns on verification of all DCL command lines executed. OR them together to get both. It will take a while! Output can be captured using SYSMAN STARTUP SET OPTIONS, and/or from a console manager or PC connected to the console port.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2006 03:28 AM
04-12-2006 03:28 AM
Re: VMS Startup
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2006 05:24 AM
04-12-2006 05:24 AM
Re: VMS Startup
once we created STARTUP.COM in )every) SYS$SPECIFIC:[SYSMGR],
containing only
@SYS$COMMON:[SYSMGR]STARTUP /OUTPUT=SYS$MANAGER:STARTUP.LOG_
That worked OK as well.
(only have to remove/rename it during upgrades!)
Proost.
Have one on me (peheaps in May in Nashua?)
jpe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2006 05:42 AM
04-12-2006 05:42 AM
Re: VMS Startup
I normally use STARTUP_P2="D". This write SYS$SYSTEM:STARTUP.LOG and also captures the early messages from SYLOGICALS.COM
See you in Nashua.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2007 03:08 PM
04-03-2007 03:08 PM
Re: VMS Startup
I realize this is an old question...
However, I didn't see anyone suggest the following. It doesn't limit itself to command files, but is instead a way to see all the files that were accessed during a startup.
Enable volume retention (ODS2 or ODS5) or file access dates (ODS5), then after booting but before other activity starts, find files that have been accessed since boottime, using the DFU program from the freeware.
This assumes you can stop all activity on the cluster for the duration of that startup, so it isn't a good solution for many cases. However, it does catch a lot of things that may not be obvious using the other techniques.