HULINFO message
August 3, 2001
From: Charles Husbands
Subject: Progress report on 806H Abend Problems

On 10 January 2000 storage problems in HULPR that had arisen as a result of changes to application programs necessitated introducing a "temporary" fix; namely terminating any task that currently had more than a certain number of storage areas associated with it. This task termination shows itself to the unfortunate user as an abend coded 806H.

The 806H abend can be raised in a number of innocent situations. A message I sent at the time of its inception apologized for the rudeness of this method of dealing with a system problem by penalizing individual users. The utilitarian principal of the greatest good for the greatest number was invoked as justification.

806H has been very effective in eliminating the "short on storage" condition it was introduced to prevent. On a typical day 10 to 30 tasks are canceled in this way, and the small number of calls OIS has received about them over the last year or so indicates that most users have adjusted to 806H as an unpleasant fact of life. However, something has changed this month. We have received a number of enquiries about 806H and the number of occurrences has jumped to nearly 70 per day. This suggests that users are undertaking some new operations or have just forgotten what 806H means, and what to do about it. It is time for a reminder, with some tips on recovery.

If your task abends with code 806H, what should you do? That depends on context. Here is a list of cases and workarounds. It is guaranteed not to be complete.

1. You are paging through a long index, or you are looking at many successive bib records, with next and/or prev (or doing a combination of these) when the abend interrupts. You can recover your position in the index by clearing the screen and re-entering the command LTHU INDex. (or LTRV if that's where you were.) This will redisplay the index page you were working on at the time of the abend. Then you can select a record and continue work. With the limit we have established, it is usually possible to browse through more than 70 bibliographic records before raising the abend. You can prevent the abend from occurring if you clear once in a while, back to the point where LTHU appears alone on the screen, then entering the INDex command (PF5) and resuming work.

(If you are about to update a record that you have found after a long search, you can protect against the abend by clearing once from the bibliographic display, then pressing enter to redisplay the record before starting work on it. Your place in the index is still known to the system.)

2. You are doing a similar browse operation with invoices using the invoice ID index. This case is similar to #1 and can be handled in a similar way.

3. You are paging through an invoice when the abend occurs. Take note of the invoice number and the numbers of last statement that was displayed when the abend occurred. Then clear the screen. Redisplay the invoice by entering LTHU INV {invoice number}. Next enter STmt n, where n is the number of the last statement displayed before the abend. Resume paging through the invoice. Repeat this sequence if the 806H recurs before you have reached the end of the invoice.

4. Using next and/or prev, you are looking at items linked to a LOC that has a sizable number of linked items. Clear the screen, call up the bib again and ask for the item summary again (ITem n, where n is the LOC repeat number.) Identify the item you last saw and request it by the number assigned to it on the summary screen.

5. You are paging through a long item summary when 806H occurs. If you get an 806H while paging through an item summary, you can continue by noting the sequence number of the last item displayed before the abend, clearing the screen, recalling the item summary via the bib, and entering LINE n, where n is the item sequence number you previously noted. This will display the part of the item summary that begins with the specified number. From there you can page forward with MOre, jump with LINE, or view individual items. Repeat as needed, because 806H recurrence is likely.