Freeing HP's Diagnostics Inside the 3000
July 8, 2015
When HP officially closed its formal HP 3000 support, the vendor left its diagnostics software open for use by anybody who ran a 3000. Throughout the years when HP sold 3000 support, CSTM needed a password that only HP's engineers could supply. But the CSTM diagnostics tools started to run in 2011 without any HP support-supplied password.
However, managers need a binary patch to free up the diagnostics. Support providers who've taken over for HP know how to enable CSTM. The community has a former Hewlett-Packard engineer to thank, Gary Robillard, for keeping the door to the diagnostics open. Robillard says he is the engineer who last worked on CSTM for MPE/iX when he was a contractor at HP.
A 3000 site must request a patch to get these expert tools working. HP arranged for 3000 sites to get such patches for free at the end of 2010. We tracked the procedure in a NewsWire story, since the HP link on how to get these patches, once on the old division's webpages, has gone dead.
One such patched version of CSTM needs a binary patch. Robillard created this binary patch fix.
Versions of CSTM [patched] with ODINX19A or ODINX25A allow the expert tools with no licensing, but you still have to issue the HLIC command.
If you install ODINX25A/B/C (6.5, 7.0, 7.5) you won't need to do anything except issue the HLIC command with any password. The HLIC command might say it was not accepted, but the license is activated anyway
When HP halted all its support of the 3000, Robillard said his patch corrects the problem with ODINX19A -- and gives 3000 managers access to these system diagnostics -- for servers running the 6.5, 7.0, or 7.5 versions of CSTM.
If you have installed ODINX19A, you need to do the following:
Logon as MANAGER.SYS. It's safest to create an input file to sompatch.
1. Run editor.pub.sys
2. Add the following three lines EXACTLY. The sompatch will only work if the instruction at offset 268 matches 86a020c2. The message "Error: Old value does not match" is displayed and no changes are made)
Here are the contents of BINPCHIN file (You will want to copy and paste these):
~~~~~The 3 lines are below~~~~~~~
; Fix problem in DIAGMOND after 12/19/2010
modify ms_init_manage_sys + 268,1 86a020c2|08000240
exit
~~~~The 3 lines are above~~~~~~~~
//
K binpchin,unn• Make sure DIAGMOND is not running (run STMSHUT.DIAG.SYS)
• copy /usr/sbin/stm/uut/bin/sys/diagmond,DIAGMOND
• run sompatch.pub.sys;stdin=BINPCHIN;INFO='DIAGMOND'
• copy DIAGMOND,/usr/sbin/stm/uut/bin/sys/diagmond;YES
• Restart DIAGMOND (run STMSTART.DIAG.SYS)After a few minutes, a "SHOWPROC 1;TREE;SYSTEM" should show the DIAGMOND process, and either the mapping processes, or memlogd, diaglogd and maybe cclogd (on A/N Class 3000s only).