SIZE: Space specification option

The SIZE option allows you to specify the amount of space available for processing load modules. You can specify the amount of virtual storage the binder can use and the size of the load module buffers. If you specify SIZE when you bind program objects, the value2 subparameter is ignored. Also, if you specify WKSPACE, the first subparameter of WKSPACE overrides the first subparameter of SIZE.
Note: Start of change We recommend that you do not use the SIZE option. Block size for load modules should be specified with the MAXBLK option (see MAXBLK: Maximum block size option), and workspace can be allocated with the WKSPACE option (see WKSPACE: Working space specification option).End of change
The syntax of the SIZE option is:

SIZE={value1[K] | ([value1[K],value2[K])}

value1
Specifies the maximum number of bytes of available virtual storage. For the binder, the minimum value is 16 KB (16384) and the maximum value is 16000 KB (16 MB).
value2
Specifies the number of bytes of storage to be allocated for the load module buffer. For the binder, the minimum value is 512 and the maximum value is 65520 (approximately 64KB).

The binder only uses this value to determine the block size of the load module. If MAXBLK is not specified, the block size is set to half of value2.

When coded in the PARM field, value1 and value2 parameters are enclosed in parentheses. For example:
//LKED       EXEC   PGM=IEWBLINK,PARM='SIZE=(2048K,32K),...'

Both value1 and value2 can be expressed as integers specifying the number of bytes of virtual storage or as nK, where "n" represents the number of 1KB (1024) of virtual storage.

The binder provides default values for the SIZE option. The default values are used if you do not specify any values, or if you specify one or more of the values incorrectly. These defaults should be adequate for most binds, relieving you from needing to specify the SIZE option.