[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference hydra::axp-developer

Title:	Alpha Developer Support
Notice:	[email protected], 800-332-4786
Moderator:	HYDRA::SYSTEM

Created:	Mon Jun 06 1994
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	3722
Total number of notes:	11359

3645.0. "Omnimark" by HYDRA::BRYANT () Tue May 20 1997 18:11

    Company Name :  Omnimark
    Contact Name :  Ean
    Phone        :  613/745-4242
    Fax          :  
    Email        :  
    Date/Time in :  20-MAY-1997 17:08:22
    Entered by   :  Pat Bryant
    SPE center   :  MRO

    Category     :  VMS
    OS Version   :  
    System H/W   :  


    Brief Description of Problem:
    -----------------------------
He is wondering if the startup file, SYSTARTUP_VMS.COM, which resides
under SYS$COMMON:[SYSMGR], gets installed there always.  He wants to 
have his users add two lines to it and therefore wants to get his
documentation correct.

T.R	Title	User	Personal Name	Date	Lines
3645.1	The joy of rooted logicals	HYDRA::NEWMAN	Chuck Newman, 508/467-5499 (DTN 297), MRO1-3/F26	`Tue May 20 1997 19:28`	7
	OpenVMS will look for the file in SYS$SYSROOT:[SYSMGR]. This first points to SYS$SPECIFIC:[SYSMGR] and then to SYS$COMMON:[SYSMGR] It is typical to keep only one copy and to keep it in SYS$COMMON:[SYSMGR]. -- Chuck Newman
3645.2	SYSTARTUP_VMS.COM is (almost) always...	AMCUCS::SWIERKOWSKI	Quot homines tot sententiae	`Tue May 20 1997 19:41`	28
	Greetings! Traditionally SYSTARTUP_VMS.COM (which was renamed from SYSTARTUP_V5.COM) some time ago always lives in SYS$COMMON:[SYSMGR]. You can move/rename it if you really want, but a lot of hackery is involved since by design the SWAPPER process which creates the SYSINIT process which in turn invokes the "site-independant" procedure STARTUP.COM in turn invokes SYSTARTUP_VMS.COM (plus the other SY*.COM procedures). If you're interested in the details, see the "OpenVMS System Manager's Manual" - Chapter 4. Personally I wouldn't move/rename SYSTARTUP_VMS.COM unless I was playing around and I wouldn't expect any production system to do it either so, yes, you can safely assume that SYSTARTUP_VMS.COM is called SYSTARTUP_VMS.COM and lives in SYS$COMMON:[SYSMGR]. If you had reason to believe another "site-independant" startup procedure had been selected (which doesn't invoke SYSTARTUP_VMS.COM), you could test for the definition of the symbol "STARTUP" (which can be set via SYSBOOT during a con- versational bootstrap) using SYSGEN (via "SYSGEN> SH/STARTUP"). This symbol can also be permanently wired into the system via MODPARAMS.DAT if you wish, but again this isn't normal, cheers... Tony Swierkowski Digital Equipment Corporation Software Partner Engineering Palo Alto, California (415) 617-3601 "[email protected]"
3645.3		HYDRA::SCHAFER	Mark Schafer, SPE MRO	`Wed May 21 1997 10:30`	5
	for documenters (writers), I often suggest that they read some of the DIGITAL products installation guides. System managers are so used to these conventions that it's seldom necessary to read them anymore. Mark
3645.4	Mail from partner	HYDRA::BRYANT		`Thu May 22 1997 09:55`	3
	This tells me that SYS$COMMON:[SYSMGR]SYSTARTUP_VMS.COM is the startup file if a user has the installation recommended by DEC. We can therefore tell most users where the file is.