Browse Prior Art Database

Correlate IMSADF Secondary Transaction MFS Generation With the Generation of the Output Format Rule

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

Publishing Venue

IBM

Related People

Weber, OW: AUTHOR

Abstract

In IMS (Information Management System) ADF (Application Development Facility), secondary transactions are defined by means of an output format rule (OFR) and built under IMS by a Message Format Service (MFS). Previously, the MFS controls had to be hand coded by the application developer following exactly the code sequence defined by the OFR. If any changes were required, the rule generator input had to be changed, the OFR regenerated, and the MFS coding upgraded to reflect the contents of the new OFR. In rule generator Manual coding of MFS (Image Omitted) GENERATE OPTIONS=SEGL,SEGID=xx This problem was overcome in IMSADF II by defining a new rule generator interface and combining it with existing IMSADF capabilities.

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

Page 1 of 1

Correlate IMSADF Secondary Transaction MFS Generation With the Generation of the Output Format Rule

In IMS (Information Management System) ADF (Application Development Facility), secondary transactions are defined by means of an output format rule (OFR) and built under IMS by a Message Format Service (MFS). Previously, the MFS controls had to be hand coded by the application developer following exactly the code sequence defined by the OFR. If any changes were required, the rule generator input had to be changed, the OFR regenerated, and the MFS coding upgraded to reflect the contents of the new OFR. In rule generator Manual coding of MFS

(Image Omitted)

GENERATE OPTIONS=SEGL,SEGID=xx This problem was overcome in IMSADF II by defining a new rule generator interface and combining it with existing IMSADF capabilities. This interface defines a simple specification, TYPE=OMFS, to request the secondary transaction definition (an OFR). The familiar IMSADF screen image input technique is used to build both the OFR and the required MFS codes. Then the rule generator builds both the OFR and the MFS codes for the secondary transaction. Because the rule generator builds these items, the previously required manual effort has been eliminated. The corresponding error potential is also removed and the application developer can more easily and quickly implement applications that are correct. In rule generator GENERATE OPTIONS=OMFS, SIMAGE=YES " " " screen image specifications " "...