Binder Manual (G06.27+, H06.04+, J06.03+)

BIND Commands
Binder Manual—528613-004
3-65
SET Command
•
Extended data block sizes for all languages are set at compile time, and Binder
collects all of these blocks into one extended segment that is automatically
allocated at run time. SET DATA does not affect the size of this extended segment.
•
Once set with the SET PFS command, the default process file segment size is 128
pages. At this point, entering a RESET command causes Binder to set the PFS
size to 128 pages.
•
If you do not set the size of the PFS, Binder uses the largest size encountered in
the input object files when building the target file. Binder treats files created with a
previous version of Binder as if they have a PFS size of 128 pages.
The PFS value can be from 64 to 512 pages. If you specify a value outside of this
range, Binder returns the following error message:
Illegal PFS size. Legal range is 64 to 512 pages.
•
The HIGHREQUESTERS ON attribute specifies that an object file is allowed to
support requests from processes running at high PINs. It does not specify that an
object file meets the conditions to support requests from processes running at high
PINs.
Examples
The following examples illustrate the syntax of the SET command.
•
The following command specifies that a save file is to be created if a process
terminates abnormally when the target file is executed:
@SET SAVEABEND ON
•
The following example shows that two or more set parameters can be set in a
single command. In this case the Inspect symbol tables from the object files are
not to be retained in the target file, and the user library LIBFILE is to be associated
with the target file at run time.
@SET SYMBOLS OFF, LIBRARY libfile
Running Processes at a High PIN
The HIGHPIN ON attribute specifies that an object file is allowed to run at a high PIN. It
does not specify that an object file meets the conditions to run at a high PIN.
When the operating system creates a process, it assigns a process identification
number (PIN) to the process. D-series systems support the following ranges of PINs:
To run an object file at high PIN from the TACL prompt, the following conditions must
be met:
Low-PIN range 0 through 254
High-PIN range 256 through the maximum number
supported for the processor