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

Important CR Information

MPE documents

Complete PDF
Table of Contents

Please take note of the updated CR information.

: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.

TermDSM C.05.01.002 port reset doesn't work when auto-restart = 'Y'

CR# JAGaf26937 / 860636633

One of the new features added to Host-based DTC Management is the ability to enable automatic restart of the X.25 and PAD protocols on the SNP cards installed in the DTCs. This feature is enabled by setting the field "AutoRestart = 'Y'" on the DTC configuration screen in NMMGR. A problem has been found when this feature is enabled.

If TermDSM is used to initiate a DTC DUMP on a DTC where the Auto-Restart feature is enabled, then TermDSM displays the following error after the dump is completed, but before TermDSM returns to the user prompt: 

  ***** TERMDSM C.05.01.002 UNEXPECTED CONDITION *****
  Severity=non-fatal Location=9 Reporting module is Special.
  Parm1= hex 000000C9= decimal 201
  Parm2= hex 0000003C= decimal 60
  Parm3= hex FFFFFE48= decimal -440
  Parm4= hex 00000001= decimal 1
  Parm5= hex FFFEFFFF= decimal -65537
  Parm6= hex 000001CC= decimal 460
After this message is displayed, the following problems will occur:

  • The DTC will not be able to establish any X.25 or PAD connections.

  • TermDSM will not be able to communicate with the DTC Manager and messages similar to the one shown above will be displayed. The error display will include the following line: 

    Severity=non-fatal Location=9 Reporting module is Special.

  • DTCCONTL will not be able to communicate with the DTC Manager and will hang for about 8 minutes and then return the following error: 

    CTL ERROR: System error: bad Extend_receive status received,
info = 1010, subsys = 122. (CTLERR 106)

These problems will persist until the DTC is reset by cycling the power OFF then ON. Once the DTC is power cycled, the DTC will be automatically re-downloaded. The DTC download is complete when you see the following messages on the system console: 
19:13/40/DTCM C0501001 download started for DTC address 080009xxxxxx
19:14/40/DTCM C0501001 code download completed for DTC address
  080009xxxxxx
The DTC will be be able to re-establish X.25 and PAD connections about three minutes after these messages are displayed.



Chapter 1 Information You Need Before Installing MPE/iX 7.5 PowerPatch 2

Predictive Changes SYSSTART during UPDATE