z/TPF Program Management - IBM

More documents

Recommendations

Info

zos/ obj/ src/ bin/ lst/ obj/ src/ This directory structure is defined to the MakeTPF tools independent from a parent, or root directory. This enables the MakeTPF tools to associate the directory structure to one or more root directories at build (assemble, compile, and link) time and provides the capability of concatenating directory structures in much the same way that data sets can be concatenated in JCL. The root directories that will be used are defined in your configuration file by the APPL_ROOT variable and are referenced in the environment file examples that follow. For more information about configuration files, see “Configuration files” on page 3 and “Set up a configuration file” on page 59. For the billing application example, three corresponding environment files are needed: one for the real-time applications, one for the Linux offline applications, and one for the z/OS offline applications. The contents of each environment file follow, mapping the directory names to the MakeTPF variables that are used for each of the file types. Each environment file needs only to define the variables that pertain to that application type. GNU make syntax is shown in each environment file. The for each statement expands the directory structure listed previously in this section for each of the root directories listed in the APPL_ROOT variable, providing the concatenation. The directories do not need to exist before you run MakeTPF because nonexistent input directories will be ignored by the tools and output directories will be created as needed. Note: For output directories, the first root directory in the APPL_ROOT list will be considered the output root directory, and listings, objects, and other build output files will be written under that root directory. Real-time environment file: maketpf.env_billing # Input files ROOTASMDIRS := $(foreach d,$(APPL_ROOT),$d/billing/rt/src) # asm source files ROOTCDIRS := $(foreach d,$(APPL_ROOT),$d/billing/rt/src) # C source files ROOTCXXDIRS := $(foreach d,$(APPL_ROOT),$d/billing/rt/src) # C++ source files ROOTEXPDIRS := $(foreach d,$(APPL_ROOT),$d/billing/rt/exp) # export files ROOTINCDIRS := $(foreach d,$(APPL_ROOT),$d/billing/include) # include files ROOTMACDIRS := $(foreach d,$(APPL_ROOT),$d/billing/macro) # macro files ROOTCPYDIRS := $(foreach d,$(APPL_ROOT),$d/billing/rt/src) # copy files # Output files ROOTLIBDIRS := $(foreach d,$(APPL_ROOT),$d/billing/rt/lib) # real-time libraries ROOTLOADDIRS := $(foreach d,$(APPL_ROOT),$d/billing/rt/load) # real-time loadables ROOTLSTDIRS := $(foreach d,$(APPL_ROOT),$d/billing/rt/lst) # listings ROOTOBJDIRS := $(foreach d,$(APPL_ROOT),$d/billing/rt/obj) # object files Linux offline environment file: maketpf.env_billing_linux 58 z/TPF Program Management # Input files ROOTASMDIRS := $(foreach d,$(APPL_ROOT),$d/billing/linux/src) # asm source files ROOTCDIRS := $(foreach d,$(APPL_ROOT),$d/billing/linux/src) # C source files ROOTCXXDIRS := $(foreach d,$(APPL_ROOT),$d/billing/linux/src) # C++ source files ROOTINCDIRS := $(foreach d,$(APPL_ROOT),$d/billing/include) # include files ROOTMACDIRS := $(foreach d,$(APPL_ROOT),$d/billing/macro) # macro files ROOTCPYDIRS := $(foreach d,$(APPL_ROOT),$d/billing/linux/src) # copy files
# Output files ROOTBINDIRS := $(foreach d,$(APPL_ROOT),$d/billing/linux/bin) # linux executables ROOTLSTDIRS := $(foreach d,$(APPL_ROOT),$d/billing/linux/lst) # listings ROOTOBJDIRS := $(foreach d,$(APPL_ROOT),$d/billing/linux/obj) # object files z/OS offline environment file: maketpf.env_billing_zos Set up a configuration file # Input files ROOTASMDIRS := $(foreach d,$(APPL_ROOT),$d/billing/zos/src) # asm source files ROOTCDIRS := $(foreach d,$(APPL_ROOT),$d/billing/zos/src) # C source files ROOTCXXDIRS := $(foreach d,$(APPL_ROOT),$d/billing/zos/src) # C++ source files ROOTINCDIRS := $(foreach d,$(APPL_ROOT),$d/billing/include) # include files ROOTMACDIRS := $(foreach d,$(APPL_ROOT),$d/billing/macro) # macro files ROOTCPYDIRS := $(foreach d,$(APPL_ROOT),$d/billing/zos/src) # copy files # Output files ROOTBINDIRS := $(foreach d,$(APPL_ROOT),$d/billing/zos/bin) # z/OS executables ROOTLSTDIRS := $(foreach d,$(APPL_ROOT),$d/billing/zos/lst) # listings ROOTOBJDIRS := $(foreach d,$(APPL_ROOT),$d/billing/zos/obj) # object files # Output Link PDS LINKPDS := $(subst *,LINK,$(word 1,$(APPL_ROOTPDS))) Note: For the z/OS offline programs, in addition to the directories, a LINK partition data set (PDS) is required as the repository for the executables. In this example, the syntax shown will replace an asterisk (*) with the string LINK. It chooses only the first string provided in the APPL_ROOTPDS variable, which also is defined in the configuration file. For our example, we have set up the billing applications so that each of the environment files is independent of one another, and all three refer to the macro and include directory. This was done so that each makefile would need to list only the environment file related to its type (real-time, Linux or z/OS). As an alternative, we could have created a fourth environment file named maketpf.env_billing_common that contained only the macro and include variable definitions, and removed those definitions from each of the other three files. Each makefile would have to reference both the common and corresponding program-type makefile. Both approaches work equally well. The approach that you use really depends on how you want to set up and manage your directory structures. Note: Environment files are intended to be set up with respect to either an application root directory or a z/TPF root directory. The environment files that are supplied by z/TPF are set up to reference the TPF_ROOT variable, while application environment files are expected to reference the APPL_ROOT variable. Use the configuration file to define the build space and to identify: v The root directory names where the application and z/TPF code reside. You can specify multiple root directory names and each will be concatenated. The files will be pulled on a topdown, first-found basis. v The z/TPF system or subsystem being built. v User overrides to compile, assemble, and link flags. v User overrides to process options, such as whether to keep clean listings. For the remainder of this information, we define the configuration file as shown in the following example and expect the file to reside under the name /home/joe/mywork/build/maketpf.cfg: Assemble, compile, and link (build) application programs 59
Page 1:
z/Transaction Processing Facility E
Page 4 and 5:
| | | | | Common deployment . . . .
Page 6 and 7:
vi z/TPF Program Management Linux l
Page 8 and 9:
2 z/TPF Program Management
Page 10 and 11:
Makefiles Control files 4 z/TPF Pro
Page 12 and 13:
| | | | | | | | loadtpf utility Rel
Page 14 and 15: 8 z/TPF Program Management There ar
Page 16 and 17: 10 z/TPF Program Management
Page 18 and 19: Figure 2. BAL repackaging Entry poi
Page 20 and 21: 14 z/TPF Program Management Individ
Page 22 and 23: Transfer vectors Program linkage 16
Page 26 and 27: Images Loadsets 20 z/TPF Program Ma
Page 28 and 29: present, the program or programs ar
Page 30 and 31: ELF objects and libraries from the
Page 32 and 33: ELF objects and libraries from the
Page 34 and 35: Data loader Pilot Tape (SDF) ZSLDR
Page 36 and 37: Alternate FCTB loader benefits Use
Page 40 and 41: | | | | | | | | | | | | | | | | | |
Page 44 and 45: | | | | | | | | | | | | | | | | | |
Page 46 and 47: | | | | | | | | | | | | | | | 40 z/
Page 52 and 53: | | | | | | | | | | | | | | | | | |
Page 56 and 57: | | | | | | | | | | | | | | | | | |
Page 66 and 67: APPL_ROOT := /home/joe/mywork APPL_
Page 68 and 69: Create a single-segment BSO using a
Page 70 and 71: Adding the line APP_EXPORT := LIST
Page 72 and 73: 66 z/TPF Program Management v CTBX
Page 74 and 75: 3. Update the user control file and
Page 76 and 77: Update export files this, when an e
Page 78 and 79: 72 z/TPF Program Management Note: I
Page 80 and 81: 3. The JCL also references the form
Page 84 and 85: To logically copy CIMR components f
Page 88 and 89: offldr programs, as necessary, to c
Page 90 and 91: 84 z/TPF Program Management User: Z
Page 94 and 95: Activate a loadset of E-type progra
Page 96 and 97: v All loadsets containing a particu
Page 98 and 99: Terminal Addr Index into Selective
Page 100 and 101: | | | | | | | | | | | | | | | | | |
Page 102 and 103: | | | | | | | | | | | | | | | | | |
Page 110 and 111: | 104 z/TPF Program Management For
Page 114 and 115:
108 z/TPF Program Management Table
Page 116 and 117:
110 z/TPF Program Management Table
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
118 z/TPF Program Management user e
Page 126 and 127:
120 z/TPF Program Management -outpu
Page 128 and 129:
0 8 0 v A return code indicating th
Page 130 and 131:
124 z/TPF Program Management The fo
Page 132 and 133:
►► 126 z/TPF Program Management
Page 134 and 135:
@CIMR 128 z/TPF Program Management
Page 136 and 137:
The default location is searched fo
Page 138 and 139:
@CTKX 132 z/TPF Program Management
Page 140 and 141:
@DEFINE 134 z/TPF Program Managemen
Page 142 and 143:
136 z/TPF Program Management Additi
Page 144 and 145:
IMGCLEAR specifies whether image-re
Page 146 and 147:
-d specify this parameter, the sour
Page 148 and 149:
@GFKEYPOINT 142 z/TPF Program Manag
Page 150 and 151:
144 z/TPF Program Management v CTKM
Page 152 and 153:
►► @IPL 146 z/TPF Program Manag
Page 154 and 155:
@KEYPOINT Note: The length of the d
Page 156 and 157:
%cpuid loads the specified keypoint
Page 158 and 159:
152 z/TPF Program Management defaul
Page 160 and 161:
information must begin on a new lin
Page 162 and 163:
Page 164 and 165:
Input files The following examples
Page 166:
show all

z/TPF Program Management - IBM

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?