|
|
|
The application program performs all I/O. The first call to SHRINK or EXPAND which refers to a particular file number or SCB causes 1K to 8K bytes of dynamic storage to be acquired, the FDT to be loaded, and code to perform the function to be custom compiled. Subsequent calls execute only the custom-compiled code. This provides the fastest possible execution time.
SHRINKZ and EXPANDZ do not require this initial processing.
SHRINKS and EXPANDS build a small dynamic area, and depending on how they are called, they may need to load the appropriate Standard Table.
SHRKHCS and SHRKHCX also build a small dynamic area, and they need to load the appropriate hardware compression dictionary load module. The following illustration shows the general flow of subroutines.
The language dependent conventions for parameter passing and subroutine linkage are described in the following sections.
| Copyright © 2012 CA. All rights reserved. |
|