Browse Prior Art Database

Multiple Destination Secondary Transactions

IP.com Disclosure Number: IPCOM000042872D
Original Publication Date: 1984-Jun-01
Included in the Prior Art Database: 2005-Feb-04

Publishing Venue

IBM

Related People

Authors:
Bailey, CG Filip, JA [+details]

Abstract

In IMS (Information Management System) ADF (Application Development Facility), execution of one user transaction can require another transaction to be executed. This is called a secondary transaction. Early versions required that such transactions be processed through IMS message queues. With IMSADF II, secondary transactions can be sent not only to an IMS logical terminal (LTERM) and another IMS transaction; they can also be sent to a sequential operating system (OS) file. This is done in such a way that the application developer does not have to change the definition of the transaction process. Rather, the destination of the secondary transaction is controlled in the message data base (MSGDB) and does not involve either the transaction definition or the secondary transaction.