Browse Prior Art Database

RPG II Source Mapping Technique

IP.com Disclosure Number: IPCOM000089587D
Original Publication Date: 1977-Nov-01
Included in the Prior Art Database: 2005-Mar-05
Document File: 2 page(s) / 36K

Publishing Venue

IBM

Related People

Bartz, MR: AUTHOR

Abstract

This technique maps IBM System/3 and IBM System/32 RPG II at source code level. The ability to map IBM System/3 and System/32 RPG II source code is beneficial for the application programmer, inasmuch as areas of untested and unnecessary code can thereby be readily identified.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 59% of the total text.

Page 1 of 2

RPG II Source Mapping Technique

This technique maps IBM System/3 and IBM System/32 RPG II at source code level. The ability to map IBM System/3 and System/32 RPG II source code is beneficial for the application programmer, inasmuch as areas of untested and unnecessary code can thereby be readily identified.

DEBUG, a previously obtainable feature in the IBM System/3 and IBM System/32 RPG II, is used to provide mapping information. DEBUG is normally used to aid the RPG II programmer in locating errors in programs. The feature consists of the DEBUG operation code which, when placed at key points in the calculation specifications, records all active indicators unique to the program and the values of prespecified fields.

Since the status of these unique indicators controls the execution of the RPG II program, DEBUG could then provide input to a mapping program. The mapping program would relate the status of the indicators to the RPG II source code to determine instruction execution. Therefore, the gap between the RPG II compiler-generated object code and the RPG 11 source code would be bridged.

A precompile step is necessary for DEBUG operation insertion into the source code. Any calculation specification which alters the logic flow or status of the active indicators should be followed by a DEBUG operation. In order to determine logic flow, each DEBUG operation would be assigned an identifying number. This number would be used by the mapping program to establish the s...