Browse Prior Art Database

Repeated Invocation Management

IP.com Disclosure Number: IPCOM000047987D
Original Publication Date: 1983-Dec-01
Included in the Prior Art Database: 2005-Feb-08
Document File: 1 page(s) / 11K

Publishing Venue

IBM

Related People

Filip, JA: AUTHOR [+2]

Abstract

Overhead is reduced in module-module repeated invocation by embedding an interface with each set of routines. Consider, for example, assembler modules repeatedly invoking incidental routines written by a user in the programming language PL/I. Normally, an incidental routine environment will be established and terminated on each invocation. This affects performance resulting in excessive overhead burden. In order to reduce the requirements for establishing an environment for multiple invocations, each incidental routine is linked with an interface which uses a common function module to manage environments.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 100% of the total text.

Page 1 of 1

Repeated Invocation Management

Overhead is reduced in module-module repeated invocation by embedding an interface with each set of routines. Consider, for example, assembler modules repeatedly invoking incidental routines written by a user in the programming language PL/I. Normally, an incidental routine environment will be established and terminated on each invocation. This affects performance resulting in excessive overhead burden. In order to reduce the requirements for establishing an environment for multiple invocations, each incidental routine is linked with an interface which uses a common function module to manage environments.

1