Preserving the essence of a system...
JF Mezei
"identity", and have those recorded for posterity in text form.
Anyone I have forgotten ?
Core:
SYS$STARTUP_VMS.COM (and custom file it calls)
SYLOGICALS.COM
SYLOGIN.COM
SYS$ANNOUNCE, SYS$WELCOME
Anything "SYSTARTUP"
The SYSGEN file (VAXVMSSYS.PAR on VAX for instance)
MODPARAMS.DAT
Can one get NCP to generate a "command file" that could recreate itself
for the DECnet config ? (does NETCONFIG.COM parse the NCP stuff or
does it start from scratch ?)
How would one do the same for TCPIP services ?
I know that I need to catch some of the /etc (oops, already in unix
mode... I meant TCPIP$ETC ) files (sysconfigtab if I recall).
What else should one preserve ?
H Vlems
MODPARAMS.DAT
SYS$ANNOUNCE and SYS$WELCOME are logical names.
You might want to save what's in LTLOAD.COM (or is it LAT$STARTUP.COM
now?)
The contents of SYSUAF.DAT and ALTSYSUAF.
And perhaps ACCOUNTG.DAT may be useful as well.
I guess JF that it is quite a lot of work to make this happen !
Hans
Lee K. Gleason
"H Vlems" <hvl...@freenet.de> wrote in message news:2b56361c-4f60-4933-9b62-
>MODPARAMS.DAT
>SYS$ANNOUNCE and SYS$WELCOME are logical names.
>You might want to save what's in LTLOAD.COM (or is it LAT$STARTUP.COM
>now?)
>he contents of SYSUAF.DAT and ALTSYSUAF.
>And perhaps ACCOUNTG.DAT may be useful as well.
>I guess JF that it is quite a lot of work to make this happen !
>Hans
RIGHTSLIST.DAT would be good to have.
--
Lee K. Gleason N5ZMR
Control-G Consultants
lee.g...@comcast.net
Bob Gezelter
JF,
With regards to SYSTARTUP_VMS.COM and other command files used in the
STARTUP process, the explicit list is not correct.
The list of first level command files is stored as "phases" in files
VMS$VMS.DAT and VMS$LAYERED.DAT in directory SYS$STARTUP:[STS
$STARTUP]. SYS$STARTUP:SYSTARTUJP_VMS.COM is actually invoked one
level below that. The STARTUP databases actually may contain
additional processing required by layered products used by the files.
The only definitive way to find all files involved is to track down
the list of files contained in the STARTUP databases, and the list of
files they reference, either as data or command files, and continue
iterating until there are no new files referenced.
Therefore, any otherwise specific list will not be definitive.
- Bob Gezelter, http://www.rlgsc.com
Phillip Helbig---undress to reply
<jfmezei...@vaxination.ca> writes:
> I am trying to compile a list of files that give the system its
> "identity", and have those recorded for posterity in text form.
>
> Anyone I have forgotten ?
>
> Core:
>
> SYS$STARTUP_VMS.COM (and custom file it calls)
> SYLOGICALS.COM
> SYLOGIN.COM
> SYS$ANNOUNCE, SYS$WELCOME
>
> Anything "SYSTARTUP"
>
> The SYSGEN file (VAXVMSSYS.PAR on VAX for instance)
> MODPARAMS.DAT
All the files mentioned in SYLOGICALS.TEMPLATE which can have logical
names pointing to them.
The TCPIP configuration.
Arne Vajhøj
> On 24 dec, 20:04, JF Mezei<jfmezei.spam...@vaxination.ca> wrote:
>> I am trying to compile a list of files that give the system its
>> "identity", and have those recorded for posterity in text form.
>>
>> Anyone I have forgotten ?
>>
>> Core:
>>
>> SYS$STARTUP_VMS.COM (and custom file it calls)
>> SYLOGICALS.COM
>> SYLOGIN.COM
>> SYS$ANNOUNCE, SYS$WELCOME
>>
>> Anything "SYSTARTUP"
>>
>> The SYSGEN file (VAXVMSSYS.PAR on VAX for instance)
>> MODPARAMS.DAT
>> What else should one preserve ?
>
> MODPARAMS.DAT
Very important since it usualy will contain node name and DECnet number.
> SYS$ANNOUNCE and SYS$WELCOME are logical names.
He probably mean the files the logicals are pointing to.
> The contents of SYSUAF.DAT and ALTSYSUAF.
If it is a hobbyist system with a very limited number
of users, then I would prefer to have COM files that
adds the necessary accounts over the binary files.
Arne
Rob Brown
On Thu, 24 Dec 2009 at 22:16 -0600, Lee K. Gleason wrote:
> "H Vlems" <hvl...@freenet.de> wrote in message news:2b56361c-4f60-4933-9b62-
>
>> MODPARAMS.DAT
>> SYS$ANNOUNCE and SYS$WELCOME are logical names.
>> You might want to save what's in LTLOAD.COM (or is it LAT$STARTUP.COM
>> now?)
>> he contents of SYSUAF.DAT and ALTSYSUAF.
>> And perhaps ACCOUNTG.DAT may be useful as well.
>> I guess JF that it is quite a lot of work to make this happen !
>> Hans
>
>
> RIGHTSLIST.DAT would be good to have.
CLUSTER_AUTHORIZE.DAT
--
Rob Brown b r o w n a t g m c l d o t c o m
G. Michaels Consulting Ltd. (780)438-9343 (voice)
Edmonton (780)437-3367 (FAX)
http://gmcl.com/
Paul Sture
Rob Brown <mylas...@gmcl.com> wrote:
> On Thu, 24 Dec 2009 at 22:16 -0600, Lee K. Gleason wrote:
>
> > "H Vlems" <hvl...@freenet.de> wrote in message news:2b56361c-4f60-4933-9b62-
> >
> >> MODPARAMS.DAT
> >> SYS$ANNOUNCE and SYS$WELCOME are logical names.
> >> You might want to save what's in LTLOAD.COM (or is it LAT$STARTUP.COM
> >> now?)
> >> he contents of SYSUAF.DAT and ALTSYSUAF.
> >> And perhaps ACCOUNTG.DAT may be useful as well.
> >> I guess JF that it is quite a lot of work to make this happen !
> >> Hans
> >
> >
> > RIGHTSLIST.DAT would be good to have.
>
> CLUSTER_AUTHORIZE.DAT
To summarize:
SYSUAF.DAT
RIGHTSLIST.DAT
VMSMAIL_PROFILE.DATA
NET$PROXY.DAT
NETPROXY.DAT
CLUSTER_AUTHORIZE.DAT
MODPARAMS.DAT
SYS$ANNOUNCE
SYS$WELCOME
Custom startup files
TCP/IP Services stuff - TCPIP$*.DAT
DECnet Phase IV - NET*.DAT (? it's been a long time since I looked)
DECnet Phase V:
SYS$SPECIFIC:[SYSMGR]NET$*.NCL
SYS$SYSTEM:NET$*.DAT
Something to rebuild the print and batch queues:
<http://labs.hoffmanlabs.com/node/589>
Last but not least, don't forget your license database(s).
--
Paul Sture