Binder Manual (G06.24+, H06.03+)

BIND Commands
Binder Manual—528613-003
3-18
CHANGE Command
the file remains the current file and repeated attempts to CHANGE result in the
same error.
•
Each successive CHANGE command specifying one of these parameters
overrides the previous specification. Use the SHOW command with the SET
attribute option to determine the current values of the file attributes.
•
CHANGE can be used on files without a Binder region.
•
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.
See Running Processes at a High PIN on page 3-65 for more information.
•
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. See Running Processes at a High PIN on page 3-65 for more information.
Examples
The following examples illustrate the syntax of the CHANGE command.
•
The following command specifies that a save file for MYFILE is to be created if the
process terminates abnormally during execution:
@CHANGE SAVEABEND ON IN myfile
•
The following command specifies that the user library LIBFILE is to be associated
with MYFILE at run-time:
@CHANGE LIBRARY libfile IN myfile
•
The following command shows the sequence of actions you need to perform in
order to find out the current value of an attribute, change the value of the attribute,
and verify that the attribute has been changed:
@file cref.cobext
CURRENT FILE IS $DATA.CREF.COBEXT
@show set subtype
SUBTYPE 0
@clear
@change subtype 1 in cref.cobext
@file cref.cobext
CURRENT FILE IS $DATA.CREF.COBEXT
@show set subtype
SUBTYPE 1