....  at least I think it's another problem;  so far the HP RC
disagrees....  Let's see what y'all think:

Reference my previous "rant" about the System Software
Maintenance Manual telling you to load the CSLT twice
(instead of the Factory SUBSYS Tape and then the CSLT
(or could it be the CSLT and *then* the Factory SUBSYS;
at this point I'm kind of "manualed out") ).   anyway:  also:

Look at Step 8 on page 5-42 in the "Applying the Modification"
section.   Note that it says to enter   "UPDATE",  *not*
UPDATE CONFIG.  Following this instruction to the letter
during my SUBSYS + PP5 + Reactive Patches saga last
weekend caused me to come to serious grief during the middle
of the day *today*);  four days later;  i.e.:  our system was down
for about two hours until we finally got everything pieced back
together (user discontent was rising fast).

Now whether or not an   UPDATE CONFIG  is  *theoretically*
required at this point for this or any  SUBSYS-PP-reactive
sequence  may be open to debate.  But after my second not-
fun experience in a week using this manual, I would argue that
UPDATE CONFIG should be the default here;  perhaps with a
note that says ~~"if you do NOT want to activate the
CONFIG.SYS files STOREd on the CSLT you just created,
enter UPDATE NOCONFIG instead" (or something like that).

Why ??.... well:  While users were all at lunch at 11:30 today,
we rebooted the system to clear a couple hung network printing
processes (another story in itself:  orphan CHILD process had a
death grip on a spoolfile;  PARENT process printing program not
running or even being accessed anymore (SHOT said CHILD was
not alive;  and that PARENT *appeared* not to be alive) ).  anyway:

No problem, says I (fool):  A simple 10-minute reboot while users
are at lunch will fix this hung printing process... NOT SO FAST..:
Without thinking about it at the time, I shut down all sessions/jobs
and user logging;  CTRL-B RS;  and then START NORECOVERY
(experienced users are probably already starting to fast-forward to
what happened).  System comes up;  initially seems to be O.K...
but... YIKES !!!!  *All* NMMGR LDEV's are toast;  absolutely gone...

< Omit frantic interlude, trying to figure this out (which in
hindsight should not have taken me nearly as long as it did). >

Well, of course with the  START NORECOVERY we came up on
the nine files in the CONFIG.SYS  group, *not* BOOTUP.  When I
CREATEd my CSLT during my last infamous Patch/iX run, the new
CONFIG.SYS  group got put on the CSLT O.K...  but because the
aforementioned Step 8 on page 5-42 said  UPDATE  instead of
UPDATE CONFIG, the CONFIG.SYS group was *NOT* updated on
disc.....  since if you follow the current manual to the  "YOU ARE
DONE!"  finish on page 6-25, there is NO other step that allows you
or even asks if you want to bring in the new CONFIG.SYS that was
written to the CSLT.

Maybe the HP RC is right, and a "pure" PP5 update does not
require an UPDATE CONFIG....  but remember I was doing a
PP + SUBSYS...  or maybe somehow I screwed up weeks ago,
when I did that last STAGEMAN COMMIT to BASE of a staging
group;  and somehow CONFIG.SYS files never got updated....
who knows;  right now I'm tired of thinking about it.

Whatever the case may be, I'm pushing for  UPDATE CONFIG
as the default manual instruction on page 5-42 (of course *I*
won't need reminding ever again....).  Summary of reasons:

(1)  Avoids MANAGER.SYS agony during the middle of the day,
      if CONFIG.SYS on disc is "old" for *whatever* reason and
      somebody does a START NORECOVERY.

(2)  Verifies that CONFIG.SYS on the CSLT is good along with
      rest of the tape (yes, can also do CHECKSLT, but still....).

(3)  Avoids variations of the following even uglier scenario:

     [a]  Your CONFIG.SYS is "old", but you run a long time
           without doing a  START NORECOVERY.  Memory of
           details of last UPDATE starts to fade;  and you are a
           little sloppy or busy and never happen to check or notice
           that BOOTUP.SYS and CONFIG.SYS are not the same.

     [b]  Eventually you do another reactive / PP update, and
           create another CSLT.  Your *old* CONFIG.SYS on disc
           gets written to the "newer" CSLT.  You then UPDATE
           and  START NORECOVERY  from this newer CSLT.

      [c]  *** NOW ***.:  The $64K ?:  How long will it take you
           to figure out that you've got to go back to the *older*
           CSLT to get your "newer" CONFIG.SYS...  which may
           or may not be compatible with the rest of the "newer"
           second CSLT and later online changes....  good luck...

If I am guilty of some grievous oversight;  something that should
always be done by any semi-competent MANAGER.SYS;  that
will preclude getting into some version of the above fix;  I invite
correction and education...  But regardless of any prior screw-up
I may or may not have been guilty of, I close with one question:
What percentage of the time would you want to keep an *old*
CONFIG.SYS on disc (as CONFIG.SYS, I mean;  not as some
renamed backup group that you KEEP through SYSGEN (always
a good idea) ) ??....   I say percentage is real low;  and therefore
UPDATE CONFIG  is a much more fail-safe thing to do sometime
before you reach the "YOU ARE DONE!" at the end of the SSMM
maze....

arrggghhhh.....  *more* than enough fun for this week.... so I'm
going to do the only rational thing:  I'm going to head for the
mountains for four days....

Ken Sletten