HP 3000 MPE V: notes on Y2K Safe release

From: Stan Sieler <ss_at_allegro.com>
Date: Tue Feb 8 18:33:19 2000

Hi,

If you have a Classic HP 3000 (any two-digit model #),
and if you received the "Y2K Safe" release of MPE recently,
and if you haven't installed it yet,
I have some notes that you should find interesting.

(If you didn't get your Y2K Safe MPE V (which was free!),
email Allan Hertling at allan_hertling_at_hp.com)


0. 3P Patches?
--------------

If your goal is to get Release 40 installed, you don't need to bother
with the 3P patches you may have received.

I simply installed 3P, and then did the Turbo Update to Release 40,
and then installed the Release 40 patches.


1. TUINSTAL Y2K bug
-------------------

The Turbo Update mechanism has a Y2K bug in it. TUINSTAL builds
the file TUSYSDMP, which builds a new SL and tries to create a SYSDUMP tape
with a partial backup. If run today (8 Feb 2000), the partial backup
would be specified incorrectly as 2/8/0 ... and STORE (which is used by
SYSDUMP) doesn't accept a single digit year.

Workarounds:

   1) change system date to 1999-12-31 before running TUINSTAL
      (note: you may have to purge TUSYSDMP if it's already been built)

or

   2) edit TUSLINFO prior to running TUINSTAL and change the line
      towards the end with "$$/$$/$$" to "02/04/00" (or some such)
      ...note: I haven't tested to see if TUNINSTALL will complain
      if it can't find the $$/$$/$$ line.


2. Release 40 Patches
---------------------

There are 7 patches on the Release 40 patch tape. Accompanying the tape
is a list of the patches ... these are also the names of the files to stream
to install each patch!

Notes:

   1) Be sure to restore the patches into PATCH.TELESUP!
      (They're on the tape as _at_.PATCH40.TELESUP)

   2) Don't rely on setting LIMIT to 1! Each job has a ";HIPRI",
      and each builds a new file called "PATCH1JJ" (or some such),
      and streams it with HIPRI! I.e., it you attempt to minimize
      your time at the console by streaming all the jobs at once,
      you'll regret it! (Been there, done that :)

   3) INFDVA7B and TRVDVA8B both replace RAPID000.PUB.SYS ...
      the latter with a bigger file than the former. My *guess* is
      that TRVDVA8B should be installed second.

   4) BBRDVA1B, RPRDVB0A, and SIMANY5B each build a new SYSDUMP tape and
      require a coldload. I streamed the other 5 jobs first (one at a time),
      then did:

         stream BBRDVA1B
         COLDLOAD from the tape

         stream RPRDVB0A
         COLDLOAD from the tape

         stream SIMANY5B
         COLDLOAD from the tape

         did a manual SYSDUMP with date 0 and "_at_.@.@"

      If you're ambitious, you could combine the three patches into
      one job (with one sysdump/coldload)


3. Disk Space
-------------

I didn't want to risk my existing disks/system, so I bought a
used Coyote (HP 6000 670H ... 670 MB?), and setup a single disk system.
After installing just the 3P FOS tape, FREE5 reported 2,348,785
available sectors (573 MB) ... before installing the SUBSYS tape!

After going to Release 40, installing the subsystems, and installing the
Release 40 patches, I have about 1,600,000 sectors free (383 MB).


Stan

Stan Sieler sieler_at_allegro.com
www.allegro.com/sieler/wanted/index.html www.allegro.com/sieler
Received on Tue Feb 08 2000 - 18:33:19 GMT