Browse Prior Art Database

Record Size Control during Customizing

IP.com Disclosure Number: IPCOM000082358D
Original Publication Date: 1974-Nov-01
Included in the Prior Art Database: 2005-Feb-28
Document File: 2 page(s) / 14K

Publishing Venue

IBM

Related People

Gordon, RD: AUTHOR

Abstract

During the customizing of programming code for a user, a record size conflict occurs when the total size of all fields in a record exceeds the allowable maximum for the record. A methodology is described for dynamically sensing that a record exceeds a given maximum length, and then for automatically adjusting the fields to fit within that maximum length. The sensing is accomplished by loading a "conflict table" with the maximum size for each record, and deducting therefrom the length of each field to show the available space in each record.

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

Page 1 of 2

Record Size Control during Customizing

During the customizing of programming code for a user, a record size conflict occurs when the total size of all fields in a record exceeds the allowable maximum for the record. A methodology is described for dynamically sensing that a record exceeds a given maximum length, and then for automatically adjusting the fields to fit within that maximum length. The sensing is accomplished by loading a "conflict table" with the maximum size for each record, and deducting therefrom the length of each field to show the available space in each record.

Many fields include in their definition a truncation number, which is the number of characters that can be dropped from the field, if necessary. When the field selection is complete, the driver notes any negative available space entries and deletes any less-necessary fields, as established in a predetermined list, truncates the remaining fields if needed, and then deletes the other fields only if the truncation fails.

The processing during the customizing run and the information present in the model are as follows: 1. The model contains a record code list giving the maximum allowable length for each record being selected. This data is passed to a driver program prior to term selection, and the driver uses it to initialize a "conflict table" for records in the data base. 2. As the model selects each term and passes it to the driver, the driver deducts the terms size from the conflictable entries for each record containing the term. The entries in the conflict table show the available space left in each record, and negative available space represents a conflict to be resolved. 3. As the driver receives each term, it creates a listing of each record and the terms it contains. 4. Some terms selected by the model are eligible for shortening. These fields are so identified and have a truncation number as well as a size. The truncation number is the number of characters that can be dropped from the field's size, if necessary. The driver uses such fields to set up a "long field table", which includes the field's name. size, truncation number, and codes of the records it appears in. 5. When the model's term selection is finished, the driver looks at the conflict table for negative entries, indicating conflicts to be resolved first by function-delete and then by a combination of field shortening and function-delete. 6. The model contains a "function-d...