Browse Prior Art Database

METHOD for Creating an Encoded Customer Diskette for Debug Purposes

IP.com Disclosure Number: IPCOM000047786D
Original Publication Date: 1983-Dec-01
Included in the Prior Art Database: 2005-Feb-08
Document File: 1 page(s) / 12K

Publishing Venue

IBM

Related People

Gentry, AV: AUTHOR [+2]

Abstract

A copy of a customer's data diskette is often necessary in order to properly diagnose and debug failures in word processing software. The customer's data diskette may contain confidential data which is sensitive to the customer's business. Therefore, the customer is reluctant and often unwilling to release a copy of the data diskette for diagnostic purposes. Many times the failure of word processing software is due to the inability of the software to handle a specific sequence of controls (e.g., begin underscore, tab, word underscore, etc.) and graphics (alphanumerics, symbols, etc.). In the case of data stored in logical records on a diskette, the failure may be due to how the data is stored in a record or how the records are arranged on a diskette.

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

Page 1 of 1

METHOD for Creating an Encoded Customer Diskette for Debug Purposes

A copy of a customer's data diskette is often necessary in order to properly diagnose and debug failures in word processing software. The customer's data diskette may contain confidential data which is sensitive to the customer's business. Therefore, the customer is reluctant and often unwilling to release a copy of the data diskette for diagnostic purposes. Many times the failure of word processing software is due to the inability of the software to handle a specific sequence of controls (e.g., begin underscore, tab, word underscore, etc.) and graphics (alphanumerics, symbols, etc.). In the case of data stored in logical records on a diskette, the failure may be due to how the data is stored in a record or how the records are arranged on a diskette. Determining the cause of such failures is frequently very difficult without the data with which the errors occur. Actually, the specific text is not required. Only a document with the same arrangement of controls and graphics is needed. For example, consider the following sentence: This is a test. The above sentence may be replaced with the following pattern and the debug operation will be unaffected: XXXX XX X XXXX. In the above pattern, each "X" represents a character having the same character width as the one it replaces. In other words, if a data stream failure occurs with the first sentence, it should also occur with the substituted character pa...