Hi HP3000-L,

My Patchman patch installation tool has just been updated to v2.1.

- Mark B.

# PATCHMAN v2.1 MPE Patch analysis tool.
# --------------------------------------
# Patchman is a patch management tool that analyzes the patches previously
# installed on your system, looking for:
#
#       patches that have been marked bad
#       patches that have been superseded by downloadable patches
#       patches that have been superseded by non-downloadable patches
#       patches that are unrecognized (generally alpha or beta patches)
#
# Patchman then suggests which new patches you might want to download and
# install:
#
#       new patches superseding any of your previously installed patches
#       new patches for FOS or HPSWINFO-patched subsystems
#       new patches for other subsystems
#
# Patchman is willing to optionally download and unpack any recommended
# patches.
#
# See patchman -h for full usage information.  If run with no parameters, the
# default behavior is just to report on installed patches and recommend new
# patches.

# Download patchman from:
#
# ftp://ftp.bixby.org/pub/mpe/patchman-2.1
# or
# http://www.bixby.org/ftp/pub/mpe/patchman-2.1

# This piece of personal freeware is unsupported by HP, but I'm willing to
# answer comments and questions as time permits:
#
# Hewlett-Packard Company
# ATTN: Mark Bixby
# 19447 Pruneridge Avenue, MS 47UX
# Cupertino, CA  95014
#
# email: [log in to unmask]
# phone: +1 408 447-5653
# web  : http://www.bixby.org/mark/

# README README README README README README README README README README README
#
# This tool is not a substitute for exercising your own good judgement or
# talking to the HP Response Center!!!!!
#
# A very small number of people have reported unabortable hung terminal
# sessions when running Patchman.  This may be due to SR 4701279174.  If you
# experience this problem, please Please PLEASE open an HPRC call!  The more
# people who report this, the more likely it is to be fixed.  It is an MPE bug,
# not a Patchman bug.
#
# I make some critical assumptions in this script:
#
# 1) Patch names must match the regexp [A-Z]{2}[0-9A-Z][A-Z]{2}[0-9A-Z]{2}[A-Z]
#
# 2) A superseding patch will have a name alphanumerically greater than the
#    superseded patch.
#
# 3) HPSWINFO is NOT examined chronologically.  Thus if you installed a patch,
#    then supersede it, then at some later date re-install the old version,
#    this script won't know it and will think you're still using the
#    superseding patch.
#
# 4) "Interesting" new non-superseding patches for FOS are identified by a
#    fixed list of prefixes.  I don't know if the prefixes are 100% accurate.
#    Take a look and let me know.  Thanks.
#
# 5) "Interesting" new non-superseding patches for HPSWINFO are identified by
#    existing HPSWINFO prefixes.  Thus if a new non-FOS subsys patch appears
#    in the catalog, and you don't already have any patches in HPSWINFO for
#    this subsys, the new patch won't be listed in the HPSWINFO section (but
#    it WILL be listed in the other section).
#
# 6) No attempt is made to analyze dependency information.  That's a job for
#    Patch/iX anyway.  (You ARE using Patch/iX, aren't you?)
#
# README README README README README README README README README README README

# CHANGE HISTORY
# --------------
#
# v2.1  November 18, 1999
#
#       Uncommented the :ALTSEC @.PATCHXL.SYS;DELACD that had been commented
#       out in Patchman v2.0.  Stage/iX automatically deletes these bogus ACDs,
#       but if you use Patch/iX to create a tape, the ACDs will be retained and
#       mess up your system after you update.  So Patchman now once again
#       deletes these ACDs for you.

...remainder snipped...