z/TPF Program Management - IBM

The default location is searched for the keypoints listed in the @KEYPOINT
control statement section. You can override the default location for a particular
keypoint by specifying a specific location for that keypoint.
specificloc
is the specific location for the keypoint to load, where specificloc is one of the
following:
v The name of a search path that was defined previously in an @DEFINE
control statement section (for example, &KEYPPATH)
v An absolute path (for example, /u/ztpf/keyppath)
v A relative path (for example, keyppath).
Note: All relative paths are appended to the current working directory, which
is defined using the CWD parameter in the @DEFINE control
statement section. Therefore, you must define the CWD parameter
before you can specify a relative path.
If you specify a specific location for a keypoint, this location overrides any
default location that may have been defined for the @KEYPOINT control
statement section; that is, only the specific location is searched for the keypoint.
If the keypoint is not found in the specific location, an error occurs.
CWD
is the value specified for the CWD parameter in the @DEFINE control
statement section. If you do not specify a default location or a specific location,
this is the only location that is searched.
keypoint
is the keypoint to write to load. Specify one of the following:
v CTK0
v CTK1
v CTK2
v CTK3
v CTK4
v CTK5
v CTK6
v CTK7
v CTK8
v CTK9
v CTKA
v CTKB
v CTKC
v CTKE
v CTKI
v CTKM
v CTKV.
See z/TPF and z/TPFDF System Generation for more information about these
keypoints.
version
is the 1- to 2-character alphanumeric version code for the keypoint.
.ext
specifies an extension of the full keypoint name as created by the linker, where
ext is the appropriate extension. For example, if the linker creates a keypoint
called ctk751.so, the .so portion of the name is optional.
z/TPF offline loader input file control statements 149