>FROM: "James T. McDermott" <[log in to unmask]>
 
>I had a strange situation occur on Monday on our HP3000 Series 37.  I
>wanted to change a UDC at the user level and was logged on as Manager of
>the account.  Since multiple users logon with username Manager, I saved
>the active UDC under another name in order to edit the file.  When I
>issued the SETCATALOG command, the system hung.  We had to bring the
>system down and called HP to do the dump and run the analysis software.
>This is what they found:  it was my session that caused the failure BUT
>the process was in the BS queue in a loop.  I have never intentionally
>accessed the BS queue as a programmer in all the 17 years I have worked
>on the HP3000.  I know that the operator command, ALTPRI, can do this for
>whatever reason you would want to, but a SETCATALOG?  In December we
>upgraded to the latest release of MPE/ix version 5.0.  Also, for what
>it's worth, almost all of our applications are still running in
>compatibility mode (don't ask).  Anyone ever have a similar experience?
 
We also experienced a system hang after issuing as SETCATALOG ;SYSTEM on
MPEi/X
5.0.  The HP response center said it was a known bug (SR# 1653-139568) and
at
that time there was a binary patch they could apply by dialing in (they used
 
debug to change some bits).  HP RC indicated all problems reported had
always
involved setting the system level UDC's.
 
A user installable patch was not yet available when PowerPatch 3 was
available.
 I don't know if it is included in PowerPatch 4 yet.  HP Supportline has not
 
yet been updated.