HPlogo Read Before Installing MPE/iX Release 7.5 PP5 > 1 Information You Need

Important CR Information

MPE documents

Complete PDF
Table of Contents

Please take note of the updated CR information.

Shut4 20 Min Hang on Shutdown due to tcpsip not Terminating

CR# JAGad62997 / 8606193787

If the Support Tools Manager (STM) is not shutdown prior to doing a =SHUTDOWN, then the =SHUTDOWN will pause for 5 minutes or longer between the Shut4 and Shut6 messages, for example: 

  Shutdown of system processes begins (Shut 4)
  /*5 minute or longer pause */
  Shutdown of operating system complete. (Shut 6)
To avoid this delay, shutdown STM before the network is stopped by entering the stmshut command in cstm. 

  cstm
  cstm>stmshut
  cstm>exit
  :nscontrol stop
  :netcontrol stop
  =SHUTDOWN

:STMSHUT sometimes unable to completely close daemon

CR# JAGae78289 / 8606315566

During certain installations of the PowerPatch, an installation job has been found to fail due to the inability of the diagnostic monitor to completely shutdown. The symptom of the problem is that the job I0231900 will abort, which will trigger the installing tool (usually HPINSTAL) to systematically abort. Within the spoolfile of this jobstream, the following failure text is seen: 

  :purge /usr/lib/libmcats.sl
  EXCLUSIVE VIOLATION: FILE ACCESSED EXCLUSIVELY (FSERR 91)
  Unable to purge file "/usr/lib/libmcats.sl". (CIERR 384)
  REMAINDER OF JOB FLUSHED.
This condition can be resolved, and the installation can be resumed, by following these steps (user entries are in bold below):

  1. Kill the diagmond daemon.

    From MANAGER.SYS, 

    
  :run sh.hpbin.sys
  $ ps -ef | grep diagmond
    The above command should return a line similar to this: 
    
  0 65584 1 0 Jan 01 1:10 /usr/sbin/stm/uut/bin/sys/diagmond
    ^^^^^
    Note this number. It is the pid number of the process that needs to be killed. Issue the kill command for this pid: 
    $kill 65584 (for pid# 65584)
    Now, verify that the process has been aborted, by repeating the 'ps' command: 
    $ ps -ef | grep diagmond
    There should not be any entries returned. Merely a line-feed. If the entry is still showing, use this kill command: 
    $kill –9 65584 (for pid# 65584)

  2. Resume the installation. Simply run the installer program again. Make sure you are in the INSTALL group, and issue the run command. 

    :run hpinstal
    The installation process will detect where it left off, and will resume from that point.

HAFO Errors while Booting

CR# JAGaf58821 / 8606398856

As a result of the inclusion of MPE/iX Patches MPEMXG9 and MPEMXL5 in C.75.03, the FOS High Availability FailOver product components are automatically installed on all systems. This may, temporarily, result in non-harmful error messages being printed on the system console during system boot activities.

Specifically, after ISL>START, the MPE/iX OS will attempt to open configuration files, if a HAFOCONF file is not part of the configuration group then the system will report this via the following error messages: 

  ISL> start norecovery nosysstart logon=manager.sys

  MPE/iX launch facility

  Initialize_genesis - Ver bld1: <<pci 2.1601>>
  THU, MAR 31, 2005, 12:44:30 PM (y/n)? y
  . . . ( Various messages ) . . .
  Create port process has been completed.
  ERROR - Opening the file: %hafoconf.CONFIG.SYS% failed!
  status - subsys: #150 info: #-169
  ERROR - Unable to save necessary configuration files!
These errors can be ignored if you are not using the HAFO product. They may also be easily eliminated by creating a dummy HAFOCONF file in the current system configuration group with the SYSGEN utility. The following is an example of the SYSGEN commands that will create a HAFOCONF file in the current configuration group, user input in bold type: 

  CSYLE18<PUB.SYS>:sysgen
  sysgen> io
      io> hold
      io> exit
  sysgen> keep
         keeping to group CONFIG.SYS
         Purge old configuration (yes/no)? y
         ** configuration files successfully saved **
  sysgen> exit
For more information on HAFO please refer to the High Availability FailOver/iX Manual for MPE/iX 7.5, which is located at:

http://docs.hp.com/en/mpeix-all.html#MPE/iX%20High%20Availability.



"Relocation Failed" Possible during System Boot

2 Patch Information for MPE/iX 7.5 PowerPatch 5