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.

Having said that, it's probably a good idea to keep it on LDEV 1, since if
you ever *did* have to boot into single-disk mode you might want to check
and or edit the SYSSTART file before booting into multi-disk mode.

So what do you do if you're unfortunate enough not to have a copy of MPEX to
do what 'd' does so elegantly?

> !if finfo("sysstart","ldev") <> 1
> !  main.pub.vesoft;info='altfile sysstart;dev=1'
> !endif

You could accomplish the same thing this way (lower case used for
compatibility with donna's jcl ;-)

...
!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.

Just proof that MPEX can do it in fewer lines, I guess... :-)

Patrick
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Patrick Santucci
HPe3000 Systems Administrator
Cornerstone Brands, Inc.

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