z/TPF Program Management - IBM

More documents

Recommendations

Info

8 z/TPF Program Management There are two ways to add additional options or to override the default options that are set by the MakeTPF tools: v Update the maketpf configuration file (maketpf.cfg). Options that are stored in the configuration file are intended to be temporary because the configuration file is not stored or retained; it is part of the build space and can change from build to build. Specifying options in the configuration file is useful for testing new options before you formally update the makefile, for temporarily overriding debug levels, and so on. The following variables are supported in the configuration file: – ASMFLAGS_USER – CFLAGS_USER – CXXFLAGS_USER – PLIFLAGS_USER – LDFLAGS_USER. Options that are specified in the _USER variables apply to all assemblies, compiles, or links for any program. They take highest precedence and override the default options as well as any options that are specified in the makefile. v Update the makefile for the program. Options that are specified in the makefiles are intended for permanent changes to the default options because they are stored directly in the makefile. Options in the makefile can be specified at two levels: either applying to a specific source file, or applying to all source files of a given type (C, CXX, and so on). The following variables are supported in the makefile, where pgm is the case-sensitive program name specified by the primary target in the makefile (APP, EXE, and so on) and seg is the case-sensitive source file name, without the file extension, that is specified in the source file lists (C_SRC, ASM_SRC, and so on): – ASMFLAGS_pgm and ASMFLAGS_pgm_seg – CFLAGS_pgm and CFLAGS_pgm_seg – CXXFLAGS_pgm and CXXFLAGS_pgm_seg – PLIFLAGS_pgm and PLIFLAGS_pgm_seg – LDFLAGS_pgm Options that are specified in _pgm_seg take higher precedence over those specified in _pgm for source file _seg, and both take higher precedence over the default options that are set by the MakeTPF tools. In the following example, MY12 is the name of the program in the APP statement of the makefile. mycfile1.c, mycfile2.c, and mycfile3.c are source files. APP := MY12 C_SRC := mycfile1.c C_SRC += mcyfile2.c C_SRC += mycfile3.c CFLAGS_MY12 := -O0 CFLAGS_MY12_mycfile2 := -O3 In this example, the mycfile3.c and mycfile1.c source files would have -O0 as an override; however, the mycfile2.c source file would have -O3 as an override. Additional information:
LDFLAGS link options v See the tpftools/include_ztpf/maketpf.rules_set_flags* files for more information about options in the MakeTPF tools. v For more information about the maketpf configuration file, enter man maketpf.cfg on your Linux build system. v For more information about makefiles, enter man maketpf.mak on your Linux build system for a complete list of makefile variables that can be coded. The following link options can be set using the LDFLAGS _$(APP) variable in the makefile: v -Xlinker --defsym -Xlinker CGCC_31BIT=0 This option creates a symbol in the shared object that indicates the shared object must be loaded below the 2-GB bar and in a 31-bit core resident program area (CRPA) virtual address area. This option gets propagated online through the program ordinal (ORDN) record header without being set in the program attribute table (PAT). v -Xlinker --defsym CGCC_FastPathStub=0 This option creates a symbol in the shared object that can be used to flag a condition in the program. The fast path indicator is a core-only value in the PAT and gets propagated online through the program ordinal (ORDN) record header. The fast path indicator is valid in the PAT when the program is fetched. When this option is applied to shared objects that contain library functions, the linkage path is reduced when calling these functions. This reduction of path length provides the following benefits: – Improved system performance. – The trace name field CE3TRNAME is not changed across function calls, which are viewed as extensions of the calling shared object. Note: Only use this option for shared objects that contain fast path linkage libraries. v -Xlinker --defsym -Xlinker CGCC_COW_CRPA=0 This option creates a symbol in the shared object that indicates the shared object must be loaded in the 31-bit or 64-bit standard CRPA virtual address area. Note: Do not use this option for programs that update static data, import data from other programs, or have global constructors. v -Xlinker --defsym -Xlinker CGCC_COW_CRPA=1 This option creates a symbol in the shared object that indicates the shared object must be loaded in the 31-bit or 64-bit copy-on-write CRPA virtual address area. For more information about Makefiles, enter man maketpf.mak on your Linux build system for a complete list of Makefile variables that can be coded. MakeTPF build solution 9
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 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 64 and 65:
zos/ obj/ src/ bin/ lst/ obj/ src/
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 82 and 83:
76 z/TPF Program Management
Page 84 and 85:
To logically copy CIMR components f
Page 86 and 87:
Page 88 and 89:
offldr programs, as necessary, to c
Page 90 and 91:
84 z/TPF Program Management User: Z
Page 92 and 93:
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 104 and 105:
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
| 104 z/TPF Program Management For
Page 112 and 113:
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

Create successful ePaper yourself

Delete template?

Save as template?