z/TPF Program Management - IBM

@INCLUDE
@IPL
data in the keypoint is replaced by newdata. For example, this parameter can
help to verify that your patch is starting at the correct relative starting address.
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 @INCLUDE control statement to specify one or more files that contain a
list of components or programs to load.
The following figure shows the syntax for the @INCLUDE control statement section
of the loader input file. In this figure, the double arrowhead (►►) indicates that the
information must begin on a new line.
►► ▼ @INCLUDE
loc
is the location for the file being included, where loc is one of the following:
v An absolute path name (for example, /u/ztpf/inclpath/filename)
v A relative path name (for example, inclpath/filename).
CWD
CWD
loc
Note: If you have more than one file to include, use this line as many times as
you need. Each time you use it, start the next occurrence on a new line.
Figure 19. @INCLUDE control statement section of the loader input file
Note: All relative path names 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.
For more information about the structure of an include file, go to “Input files” on
page 158.
is the value specified for the CWD parameter in the @DEFINE control
statement section. If you do not specify a location, this is the only location that
is searched.
Use the @IPL control statement to specify which IPL programs are to be loaded.
The following figure shows the syntax for the @IPL control statement section of the
loader input file. In this figure, the double arrowhead (►►) indicates that the
information must begin on a new line.
z/TPF offline loader input file control statements 145
►◄