Patrick Santucci wrote:

> I just checked and found our SYSSTART file on LDEV 3 on our 989. That's not
> something I've *ever* checked before, and we haven't had a problem with it
> running. Seems to me your SYSSTART file would only have to be on LDEV 1 if
> you were coming up in SINGLE-DISK mode, and when was the last time you did
> that? And in that case most of the jobs in our SYSSTART file wouldn't stream
> anyway, so I'd probably say NOSYSSTART.

that's all quite true....although (like you said) if i was bringing the system
up single-disc i *really* think i'd be saying nossystart too :-)  i'm trying to
remember the exact subtly about *why* you want the sysstart file on ldev
1....but my brain's not being helpful at the moment :-)  it probably has
something to do with reloading the system....  btw -- is editor on ldev 1 too??
think about it....you've had an 'uh oh' and the only thing you've got is ldev
1.  what are you going to edit a file with?  hmmmm.....

> !if finfo("sysstart","ldev") <> 1
> !  if finfo("sscopy","exists")
> !    purge sscopy
> !  endif
> !  copy sysstart,sscopy
> !  purge sysstart
> !  build sysstart;rec=-72,,f,ascii;dev=1;disc=![finfo("sscopy","eof")],1,1
> !  fcopy from=sscopy;to=sysstart
> !endif
> ...
>
> The above builds a new SYSSTART file the same size as your old one (and
> reserves the space for it) on LDEV 1, then FCOPYs the contents from your
> original SYSSTART file (now in SSCOPY) into it. Oh, and you should still do
> the ALTSEC stuff, that's a great idea.

we're not seeing all the changes you might have made, i hope...  what if
sysstart has changed?  does it get copied into sscopy in a different
step?         - d

--
Donna Garverick     Sr. System Programmer
925-210-6631        [log in to unmask]

>>>MY opinions, not Longs Drug Stores'<<<

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *