HP3000-L Archives

November 1998, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Stigers, Greg [And]" <[log in to unmask]>
Reply To:
Stigers, Greg [And]
Date:
Fri, 6 Nov 1998 14:43:42 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (28 lines)
I remember being told that most of our third party software (we have Adager,
SuprTool and VeSoft's packages, among others) had to be on the system volume
set, which made little sense to me, but I did not care to argue the point at
that time, as we were testing DR as well as creating private volume sets.
Can anyone clarify if this is generally the case?

> -----Original Message-----
> From: Gavin Scott [SMTP:[log in to unmask]]
> Sent: Friday, November 06, 1998 1:22 PM
> To:   [log in to unmask]
> Subject:      Re: sysstart
>
        <snip>
> There certainly are files in PUB.SYS (NMCONFIG, XL, etc.) that need to be
> on LDEV 1, but I don't know of a case where SYSSTART would be one of them,
> other than if you wanted to start the system in SINGLE-DISK mode and still
> have SYSSTART execute.  Personally, if I ever have to start a system with
> only LDEV 1 available, I probably don't *want* SYSSTART trying to execute.
>
> SYSSTART doesn't go onto SLT tapes, so it doesn't have to be on LDEV 1
> for that reason either.
>
> Unless I'm missing something, I think the documentation is probably just
> being unnecessarily conservative because the author didn't know for sure
> whether the file had to be on $SYSTEM_MASTER or not.
>
> G.

ATOM RSS1 RSS2