SYSSTART.PUB.SYS must be created by Manager.sys.  It also should be on
LDEV1.

The "STARTUP" line must be the first line in the file... and I have seen
SYSSTART files not work because of a blank line at the start.

It is also possible to boot the machine at the ISL prompt and specify
that the SYSSTART file is not used... with NOSYSSTART.  Not the likely
cause in this case... but handy when doing patches.

There can exist multiple sections in the SYSSTART file for options such
as WARMSTART, COOLSTART, COLDSTART.  The sysstart option that is
executed depends on the boot method for the machine.

The ISL start option maps to the following SYSSTART sections...

"startup"       I believe is always executed.
"warmstart"     Only on START RECOVERY
"coolstart"     On START NORECOVERY
"update"        On UPDATE
"reload"        On INSTALL, this assumes that the SLT has the SYSSTART
                written on the tape...

So your SYSSTART should have looked like:

STARTUP
some commands
WARMSTART
some more commands
COOLSTART
even more commands
UPDATE
just imagine the commands
RELOAD
these commands only if the SYSSART is included on the SLT.


Rexor wrote:
>
> We have an HP3000 939KS020 with MPE 5.5
>
> We have modified our SYSSTART file, there's several weeks.
> Yesterday we have to stop the machine. When we restart our HP300, all the
> commands from this hasn't been executed.
> So, we erase the last modifications from the SYSSTART file, then we restart
> again the machine.
>
> The same thing happen, the SYSSTART file hasn't been executed.
> Our SYSSTART file is Numbered, is it right or does it have to be Unnumbered.
>
> We are sure that all the commands are right in this file, it works like this
> for several months.
>
> So why our SYSSTART file hasn't been executed?
>
> Best Regards,
>                                 Fabien Visini
>                                 REXOR