Browse Prior Art Database

Methodology for Generating Template Programs in COBOL/2 Which Access the Open, Close, Read and Write Architecture

IP.com Disclosure Number: IPCOM000107196D
Original Publication Date: 1992-Jan-01
Included in the Prior Art Database: 2005-Mar-21
Document File: 2 page(s) / 110K

Publishing Venue

IBM

Related People

Catino, RJ: AUTHOR [+5]

Abstract

This article describes the methodology for generating template COBOL/2* programs which access the Open, Close, Read and Write architecture of a Graphical User Interface (GUI). This methodology increases programmer productivity by providing easy access to the GUI code by generating a bug-free, pre-tested COBOL/2 program template, which may then be enhanced and customized by the programmer. For each control available in the GUI, one working storage file was created. The working storage files all end with the suffix of ".WS". Each working storage file prefix corresponds with the control name. Each file contains fields necessary when extracting information about the control during the Read and Write operations. For example, if a window consists of one list box and three push buttons, the working storage files LIST.WS and PUSH.

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

Methodology for Generating Template Programs in COBOL/2 Which Access the Open, Close, Read and Write Architecture

       This article describes the methodology for generating
template COBOL/2* programs which access the Open, Close, Read and
Write architecture of a Graphical User Interface (GUI).  This
methodology increases programmer productivity by providing easy
access to the GUI code by generating a bug-free, pre-tested COBOL/2
program template, which may then be enhanced and customized by the
programmer.  For each control available in the GUI, one working
storage file was created.  The working storage files all end with the
suffix of ".WS".  Each working storage file prefix corresponds with
the control name.  Each file contains fields necessary when
extracting information about the control during the Read and Write
operations.  For example, if a window consists of one list box and
three push buttons, the working storage files LIST.WS and PUSH.WS
would be accessed and included in the template program.

      There is also a procedure division file for each control.  The
procedure division files all end with the suffix of ".PD".  Each
procedure division file prefix corresponds with the control name.
Each file for each control contains a similar structure:  Process All
Messages, Messages Resulting From User Actions, Messages To PM
Controls From Application Logic, and Messages To GUI As Result of A
Query.

      One procedure division section is created for each symbolic
name chosen in the GUI.  Using the same example of a window with one
list box and three push buttons, there would be a group of code for
the window and groups of code based on the symbolic names for each of
the push buttons. This is achieved by storing a unique string in all
procedure division files which is replaced by the generator...