If A Program Is Too Large; Allocating Data Sets For Object Programs; When Programs Are Segmented; Allocating Data Sets For Program Files - IBM 5280 Programmer's Manual

If A Program Is Too Large
If a program is too large for a partition, you should first determine whether or
not a larger partition exists in your system. This can be done with the system
status utility (SYSST A T) described in the Utilities Reference/Operations
Manual.
If a program is too large for any of the partitions available on your system,
you can do one of the following:
• Divide the program into segments as described under "Segmentation" in
the 5280 COBOL Language Reference, or
• Increase the partition size using the system configuration program as
described in the System Control Programming Reference/Operation
Manual.
Allocating Data Sets for Object Programs
The data set to hold the object module must be in either the I-exchange or
basic exchange format. The size of the I-exchange data set can be either 80 or
128 bytes, depending on the size of the object module as determined by the
DECK option at compile time. The size of the basic exchange data set must
always be 128 bytes.
Follow the procedures described in the Utility Reference/Operations Manual
and the Systems Concepts manual. Special rules apply when allocating data
sets to hold segmented programs, as described below.
When Programs Are Segmented
When programs are segmented, the data set name you specify at allocation is
determined by the PROGRAM-ID name of the segmented program. Specify
the data set name as follows:
1. If the PROGRAM-ID name is less than or equal to six characters, place
the letter
0
after the PROGRAM-ID name. For example, if the
PROGRAM-ID is SEND, the data set name for the overlay segments
would be SENDO.
2. If the PROGRAM-ID is more than six characters, truncate all
characters above six and add an O. For example, CONCATENATE
would become CONCA TO.
U'Note: If the 5280 RJE was used to receive the object data set from the host,
you will have to change the name of the data set to conform with the above
naming conventions using the diskette label maintenance (SYSLABEL)
utility.
Allocating Data Sets for Program Files
Initializing Diskettes
Before running the program, the opemtor must ensure the diskette data sets
used by your program, if any, are allocated and available. If not, the diskettes
must be initialized and the data sets allocated as explained in the Utilities
Reference/Operations Manual.
(When initializing and allocating diskettes, consider the factors discussed
under "Improving Performance" later in this chapter.)
To ini tialize the diskette( s) that is to hold the data sets, use the diskette
initialization utility (SYSINIT). You will be prompted for information by
the utility.
8- 4 IBM 5280 COBOL Programmer's Guide