z/TPF Program Management - IBM

More documents

Recommendations

Info

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | export TPF_X_LIBS=/ztpf/tpfcross/build/tpf-06r1-13/H-s390x-linux-gnu/lib/gcc/s390x-ibm-tpf/4.1.2 export TPF_INFO=/ztpf/tpfcross/build/tpf-06r1-13/share/info export INFOPATH=$TPF_INFO:$INFOPATH For example, enter the following commands if you are using the GCC 4.6.3 ELF-compatible compiler: export PATH=/ztpf/tpfcross/build/tpf-11r1-8/H-s390x-linux-gnu/bin:${PATH} export TPF_X_GCC=/ztpf/tpfcross/build/tpf-11r1-8/include/c++/4.6.3 export TPF_X_LIBS=/ztpf/tpfcross/build/tpf-11r1-8/H-s390x-linux-gnu/lib/gcc/s390x-ibm-tpf/4.6.3 export TPF_INFO=/ztpf/tpfcross/build/tpf-11r1-8/share/info export INFOPATH=$TPF_INFO:$INFOPATH b. Optional: To offer a choice of GCC compiler versions to application programmers, customize the tpftools/include_ztpf/ maketpf_rules_cfg_REDHAT file to set four environment variables to define the installation location for each of the supported levels of the compiler: 1) Uncomment the export directives by removing the leading number sign (#). 2) Change the TPF_* variables to identify the directories where the versions are installed. For example, change #export TPF_X_LIBS:= to export TPF_X_LIBS:=/opt/gcc/current/libs 3) Prefix the PATH setting with the directory where the version is installed. For example: export PATH:=/opt/gcc/current/bin:$(PATH) A set of environment variables for GCC V4.1 and GCC V4.6 might look like this example: ifeq ($(TPFGCC_VERSION),41) export TPF_X_GCC:=/opt/gcc/current/tpf_x_gcc export TPF_X_LIBS:=/opt/gcc/current/libs export TPF_INFO:=/opt/gcc/current/info export PATH:=/opt/gcc/current/bin:$(PATH) endif ifeq ($(TPFGCC_VERSION),46) export TPF_X_GCC:=/cteam/jones/tpf-gcc-4.6.3-8/s390x-ibm-tpf/include/c++/4.6.3 export TPF_X_LIBS:=/cteam/jones/tpf-gcc-4.6.3-8/lib/gcc/s390x-ibm-tpf/4.6.3 export TPF_INFO:=/cteam/jones/tpf-gcc-4.6.3-8/share/info export PATH:=/cteam/jones/tpf-gcc-4.6.3-8/bin:$(PATH) endif c. Verify that the compiler was built successfully. Start a new Linux session and enter the following command: tpf-gcc -v If the compiler was unpacked successfully and the directories that are shown in the examples were used, the following information is displayed if you are using the GCC 4.1.2 compiler: Using built-in specs. Target: s390x-ibm-tpf Configured with: /ztpf/tpfcross/build/tpf-06r1-13/sources/tools/cross/configure --host=s390x-linux-gnu --target=s390x-ibm-tpf --build=s390x-linux-gnu --prefix=/ztpf/tpfcross/build/tpf-06r1-13 --exec-prefix=/ztpf/tpfcross/build/tpf-06r1-13/H-s390x-linux-gnu --enable-languages=c,c++ --program-prefix=tpf- --without-newlib --with-sysroot Thread model: tpf TARGET_SYSTEM_ROOT: /ztpf/tpfcross/build/tpf-cross-tools-4.1-tpf-06r1-13/H-s390x-linux-gnu/bin/../s390x-ibm-tpf/sys-root gcc version 4.1.2 20060724 (GNUPro 06r1-13) for z/TPF PUT05 50 z/TPF Program Management If you are using the GCC 4.6 compiler, the following example shows the output from the tpf-gcc -v command:
| | | | | | | | | | | | | | Using built-in specs. COLLECT_GCC=tpf-gcc COLLECT_LTO_WRAPPER=/opt/tpf-11r1-8/H-s390x-linux-gnu/bin/../libexec/gcc/s390x-ibm-tpf/4.6.3/lto-wrapper Target: s390x-ibm-tpf Configured with: /opt/redhat/tpf-11r1-8/sources/tools/cross/configure --disable-bootstrap --host=s390x-linux-gnu --target=s390x-ibm-tpf --build=s390x-linux-gnu --prefix=/opt/redhat/tpf-11r1-8 --exec-prefix=/opt/redhat/tpf-11r1-8/H-s390x-linux-gnu --enable-languages=c,c++ --program-prefix=tpf- --without-newlib --with-sysroot Thread model: tpf gcc version 4.6.3 20111128 (tpf-11r1-8) for z/TPF PUT09 or later (s390x-ibm-tpf) (GCC) 6. Set up access to the IBM2047 code page. For more information, see “Set up access to the IBM2047 code page” on page 53. Unpack the GNU compiler collection for the z/TPF system 51
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 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 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 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 106 and 107:
100 z/TPF Program Management
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

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

Delete template?

Save as template?