z/TPF Program Management - IBM

%cpuid
loads the specified keypoint to a processor, where cpuid is the identifier for the
processor. If a processor identifier is not specified and the keypoint is
processor-specific, the identifier defaults to the first processor that was defined.
(progcmt)
appends a comment for the specified keypoint that is displayed in the output
report, where progcmt is the text appended.
@@keypoint
patches a keypoint, where keypoint is one of the following keypoints:
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.
rsa
is the 1- to 6-digit hexadecimal relative starting address in the keypoint. The
relative starting address specifies the offset into the keypoint where the patch is
applied.
newdata
is the new data (or patch) that will replace the old data in the keypoint,
beginning at the relative starting address. The new data must be an even
number of hexadecimal digits and cannot exceed 32 digits (16 bytes).
valdata-olddata
validates the data that is replaced by newdata, where olddata is an even
number in hexadecimal format that does not exceed 32 digits (16 bytes). The
data specified for olddata must match what is currently in the keypoint. If it does
not, the data in the keypoint is not changed and an error occurs. If it does, the
data in the keypoint is replaced by newdata. For example, this parameter can
help verify that your patch is starting at the correct relative starting address.
Note:
150 z/TPF Program Management
1. 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.
2. This parameter is ignored if the patch is for an online keypoint.