Browse Prior Art Database

Determination of Db2/Sql Null Fields

IP.com Disclosure Number: IPCOM000060896D
Original Publication Date: 1986-May-01
Included in the Prior Art Database: 2005-Mar-09
Document File: 1 page(s) / 11K

Publishing Venue

IBM

Related People

Weber, O: AUTHOR

Abstract

IMSADF II (Information Management System Application Development Facility Version 2) uses an auditor to validate input data, perform application logic, and process application data. The auditor uses a symbol dictionary technique to decide which operations are to be performed on specified data. There exists a user requirement for the application program to be able to check fields to see whether they are null. These fields are stored in a DB2 user data base, and are always defined to IMSADF II via an offline Rules Generator program, the purpose of which is to build "rules" which describe the data and transactions to be executed online. During conversational processing, these rules and fields are stored in a specified format in the IMS Scratch Pad Area (SPA).

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

Page 1 of 1

Determination of Db2/Sql Null Fields

IMSADF II (Information Management System Application Development Facility Version 2) uses an auditor to validate input data, perform application logic, and process application data. The auditor uses a symbol dictionary technique to decide which operations are to be performed on specified data. There exists a user requirement for the application program to be able to check fields to see whether they are null. These fields are stored in a DB2 user data base, and are always defined to IMSADF II via an offline Rules Generator program, the purpose of which is to build "rules" which describe the data and transactions to be executed online. During conversational processing, these rules and fields are stored in a specified format in the IMS Scratch Pad Area (SPA). In previous versions of IMSADF, it was not possible for the user to request an audit operation which would return an indication of whether or not a field was null. In version 2, an audit operation was invented to perform such a check. Since the function of the auditor is to validate data, it was critical that this new function be added to the auditor, in order to allow the user to perform all application programming in the auditor. This function allows the user to be able to process data based on the null status. In many cases, the user will want to ignore the data, issue error messages, or make other logic decisions if a field is null. Without this new operation, such logic...