Hi Mike,
    Thanks for the warning and the info :)

     Are any of the Lund Performance Tool box products are effected?

Art Bahrs
+-------------------------------------------+------------------------------+
| Oregon Health Sciences Foundation         |The views here are no one's,  |
| Art Bahrs, Manager of Information Services|  least of all, mine!         |
| President, HP Oregon Regional Users Group (ORERUG)                       |
+-------------------------------------------+------------------------------+
| And the men who hold high places must be the ones to start.              |
+--------------------------------------------------------------------------+
| [log in to unmask] 'The Professor' Work: (503) 220-8333 Fax: (503) 228-9588 |
+--------------------------------------------------------------------------+

>>> "Michael D. Hensley" <[log in to unmask]> 01/22/97 07:14am >>>
We interrupt this mailing list to bring you an important
announcement:

We've found a pretty nasty bug in MPE/iX 5.5, and want to get the
info out as quickly as possible.

Q. What is the bug?
A. Option 2019 of the AIFPROCPUT INTRINSIC, which is used to change
the numerical priority of a process while leaving it in the same
queue, changes the priority to 255 no matter what parameter is passed
to it.  As soon as the process completes a transaction, the
dispatcher changes it back to the base of the queue it was in.
However, if your system is busy enough the process may never get
enough CPU to complete a transaction.

Q. What is affected?

1. Our Q-Xcellerator product is seriously affected by this bug.
Since there is no patch or workaround from HP yet, the only solution
is to stay on (or revert to) MPE/iX 5.0 (or earlier), or don't use
Q-Xcellerator.

2. Any other package that uses AIFPROCPUT to change process
priorities will also be affected, but we haven't tested any other
vendor's software.

3. The "queue jump" function  in SOS/3000 (and the similar function in
GLANCE/XL) are also affected.  Don't use this function.  Nothing else
in SOS/3000 is affected, so there's no reason not to use SOS/3000 on
MPE/iX 5.5.

4. The :ALTPROC command is NOT affected.  If you use ALTPROC to change
the numerical priority of a process, the process is placed in the
linear queue at the new priority and stays there.  If you use ALTPROC
to change the alphabetic queue of a process, the process is moved to
the base of the new queue and then behaves normally.

Q. What's being done to fix this?
A. We have submitted SR 5003353003, and HP is investigating a
possible patch.  We'll post a notice as more info becomes available.

We now return you to your regularly scheduled mailing list.
---
Michael D. Hensley             | [log in to unmask] (personal)
Software Development Manager   | [log in to unmask]    (business)
Lund Performance Solutions     | http://www.lund.com