Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Menu Driver Invocation Minimization

IP.com Disclosure Number: IPCOM000036886D
Original Publication Date: 1989-Nov-01
Included in the Prior Art Database: 2005-Jan-29
Document File: 4 page(s) / 83K

Publishing Venue

IBM

Related People

Dykstal, DW: AUTHOR [+3]

Abstract

Described is a method that allows for a reduction of a program invocation stack when displaying menus implemented in a user interface manager menu driver function. By reducing the invocation stack, the menu driver is able to save a large amount of storage and increase system performance.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 55% of the total text.

Page 1 of 4

Menu Driver Invocation Minimization

Described is a method that allows for a reduction of a program invocation stack when displaying menus implemented in a user interface manager menu driver function. By reducing the invocation stack, the menu driver is able to save a large amount of storage and increase system performance.

A user interface manager menu driver function allows a user to traverse through a menu hierarchy. Displaying a series of menus in a menu hierarchy presents a problem with the way an AS/400* System typically goes about getting a function executed. On the AS/400, as a user requests a system function, the program responsible for executing that function is placed on the user's program invocation stack. After being placed on the invocation stack, the program is executed. After the program finishes execution, it is then removed from the program

(Image Omitted)

invocation stack. If, while the program was still in the invocation stack, the user requested the same function again, the program would simply be added to the invocation stack again, and the new invocation of the program would be executed. Since a user typically displays many more then one menu at a time, multiple copies of the 'menu driver' program would be placed on the invocation stack using this standard method of executing a program. The described method solves this problem.

On AS/400, a user requests the display of a menu by invoking a GO CPP command. The job of the command processing program is to display the menu for the user. Typically, it places the menu on the menu stack and then invokes the menu driver program to display the menu. In order to minimize the program invocation stack, instead of just simply re-invoking the menu driver program to display the menu, the command checks to see if a "reachable" menu driver is found in the program invocation stack. If so, then the command stacks the menu to display on the menu stack and returns to that reachable invocation of the menu driver program. If a reachable menu driver does not exist in the program invocation stack, then the command processing program invokes a new copy of the menu driver.

(Image Omitted)

If a reachable menu driver is found in the pr...