Browse Prior Art Database

IMSADF II DL/I Exit Packaging and Control

IP.com Disclosure Number: IPCOM000042864D
Original Publication Date: 1984-Jun-01
Included in the Prior Art Database: 2005-Feb-04
Document File: 2 page(s) / 24K

Publishing Venue

IBM

Related People

Filip, JA: AUTHOR

Abstract

In IMS (Information Management System) ADF (Application Development Facility), access to data base segments is only provided through key selection which is preview, validation, and selection of data, and transaction processing. These access points do not provide for such application needs as audit trails. Any enhancement of IMSADF, to accommodate these needs, requires isolation from the IMSADF common function package while maintaining access to certain of the common functions. This problem was overcome in IMSADF II by defining a new exit capability. The DL/I exit capability is called from the common segment handler, before and after actual IMS DL/I calls, under control of an input transaction rule.

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 86% of the total text.

Page 1 of 2

IMSADF II DL/I Exit Packaging and Control

In IMS (Information Management System) ADF (Application Development Facility), access to data base segments is only provided through key selection which is preview, validation, and selection of data, and transaction processing. These access points do not provide for such application needs as audit trails. Any enhancement of IMSADF, to accommodate these needs, requires isolation from the IMSADF common function package while maintaining access to certain of the common functions. This problem was overcome in IMSADF II by defining a new exit capability. The DL/I exit capability is called from the common segment handler, before and after actual IMS DL/I calls, under control of an input transaction rule. The actual user exit routine is link-edited with a mini transaction driver and is executed separate from the IMSADF II common function package. To allow the user exit routine to communicate with the required common functions, the mini driver contains a vector of the addresses of the routines. The rule generator interprets simple user specifications to link-edit the user exit routine with the minidriver and set the controls in the input transaction rule. At the start of execution, IMSADF II locates the common function routines and saves the addresses in the mini driver's vector. Then, when IMSADF II data base calls are made, the common segment handler calls the user exit routine. This technique required minimal modification to I...