Browse Prior Art Database

PL/I Optimization After Execution

IP.com Disclosure Number: IPCOM000081238D
Original Publication Date: 1974-Apr-01
Included in the Prior Art Database: 2005-Feb-27
Document File: 2 page(s) / 58K

Publishing Venue

IBM

Related People

Healey, MJ: AUTHOR

Abstract

In order to obtain an optimum storage allocation for a PL/I program, the program is first loaded with a typical data input and a REPORT option request. An optimizing program then executes the loaded PL/I program with the REPORT option. The REPORT output is stored and, after execution of the PL/I program, is scanned for the string "Total PL/I Storage Used". This value is saved. The optimizing program then scans the load module for the constant ISASIZE (000001). The ISASIZE is then replaced with the saved REPORT value rounded up to a 2K multiple (to suit GETMAIN requirements).

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 100% of the total text.

Page 1 of 2

PL/I Optimization After Execution

In order to obtain an optimum storage allocation for a PL/I program, the program is first loaded with a typical data input and a REPORT option request. An optimizing program then executes the loaded PL/I program with the REPORT option. The REPORT output is stored and, after execution of the PL/I program, is scanned for the string "Total PL/I Storage Used". This value is saved. The optimizing program then scans the load module for the constant ISASIZE
(000001). The ISASIZE is then replaced with the saved REPORT value rounded up to a 2K multiple (to suit GETMAIN requirements).

The drawing is a flow chart showing the main operations in the automatic optimizing of the ISASIZE of a PL#I program module.

(Image Omitted)

1

Page 2 of 2

2

[This page contains 2 pictures or other non-text objects]