z/TPF Program Management - IBM

@KEYPOINT
Note: The length of the data that you are validating can have fewer bytes or
more bytes than the new data. If the validation is completed successfully,
only the number of bytes in your new data will be replaced.
Use the @KEYPOINT control statement to load keypoints.
The following figure shows the syntax for the @KEYPOINT control statement
section of the loader input file. In this figure, the double arrowhead (►►) indicates
that the information must begin on a new line.
►►
148 z/TPF Program Management
@KEYpoint
CWD
defaultloc
Note: This must be the first line of the @KEYPOINT control statement section.
►► ▼
,
defaultloc/
keypoint
specificloc/ version .ext %cpuid (progcmt)
Note: If you have more than one keypoint to load, use this line as many times
as you need. Each time you use it, separate occurrences with a comma
or start each occurrence on a new line.
►► ▼ @@keypoint rsa newdata
%cpuid valdata-olddata
rsa newdata ONLine
%cpuid
Note: If you have more than one keypoint to patch (or if you have more than
one patch for a keypoint), use this line as many times as you need. Each
time you use it, start the next occurrence on a new line.
Figure 21. @KEYPOINT control statement section of the loader input file
defaultloc
is the default location for the @KEYPOINT control statement section, where
defaultloc 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.
►◄
►◄
►◄