z/TPF Program Management - IBM

More documents

Recommendations

Info

66 z/TPF Program Management v CTBX v CTXO v COMS v CPP1 v CTAD v COMX v CTHD v CTDF v CJ00. For example, to call a function from a CSO named CRDT from the BILL CSO, add the following line to the makefile: LIBS := CRDT You can add additional libraries by separating the names by blanks on the same line, or by adding additional LIBS += XXXX lines. g. To call functions from an archive, the referenced archive must be listed in the calling makefile. For example, to call a function from an archive named TaxFunctions, add the following line to the makefile: ARCHIVES := TaxFunctions You can add additional archives by separating the names by blanks on the same line, or adding additional ARCHIVES += ArchiveName lines. Note: A function that is called from a CSO is dynamically loaded at run time, but a function that is included from the archive is statically linked in the calling CSO. h. To change the assemble, compile, or link options, use flags (ASMFLAGS, CFLAGS, CXXFLAGS, or LDFLAGS) in your makefile or maketpf.cfg file. For example, when you are migrating to the z/TPF system, you might want to load programs below the 2-GB bar. v To load a single program below the 2-GB bar, add the following statement to an individual makefile: LDFLAGS_(pgm) := -Xlinker --defsym -Xlinker CGCC_31BIT=0 where pgm is the name of the makefile. v To load real-time programs below the 2-GB bar, add the following statement as an overall configuration option to the maketpf configuration file (maketpf.cfg) before building the shared object: LDFLAGS_USER := -Xlinker --defsym -Xlinker CGCC_31BIT=0 Note: All programs that are built after this flag is added are loaded below the 2-GB bar. 2. Create two source segments named /home/joe/mywork/billing/rt/src/ billing1.c and /home/joe/mywork/billing/rt/src/billing2.c. 3. Update the user control file with a new entry for the new program: a. Create a copy of the control file in your working directory: cp /tpf/z11/local_mod/base/cntl/usr.cntl /home/joe/mywork/base/cntl/ usr.cntl b. Edit the file that you just copied and add a new entry for the program named BILL. Enter the following information on one line: BILL;APP;billing/rt/src/bill.mak;1;ALL;OBJ;TPF_SBALL;LOADONLINE;NOSTUB;DEMAND;DEBUG; 50;PROGRAM;NOGRP;IBM_DEFT;BPAUTH;RESTRICT;MONTC;KEY0;NOCMB;TIMESLICE;;;;;;;;;;;;; See “Control files” on page 103 for more information about the control file fields and values.
| | 4. Enter the maketpf command to build the program. This assumes that a file named maketpf.cfg exists in the /home/joe/mywork/build directory. cd /home/joe/mywork/build maketpf bill See “maketpf utility” on page 6 for more information about the maketpf command and its options. See Compiler and system levels by PUT for more information about the supported compiler levels for each program update (PUT). Create an archive for online programs To create and build an archive for online programs, follow these steps: 1. Create a new makefile (/home/joe/mywork/billing/rt/src/TaxFunctions.mak) as shown in the following example: ARCHIVE := TaxFunctions C_SRC := addtax.c maketpf_env := billing maketpf_env += base_rt include maketpf.rules 2. Create a source segment named /home/joe/mywork/billing/rt/src/addtax.c. 3. Update the user control file and add a new entry for the archive named TaxFunctions. Enter the following information on one line. TaxFunctions;ARCHIVE;billing/rt/src/TaxFunctions.mak;1;ALL;OBJ;TPF_SBALL;NOLOAD; NOSTUB;;;;;;;;;;;;;;;;;;;;;;;;; Note: You must add this archive to the control file before any program that calls it. In our example tasks, this means that the entry for TaxFunctions must appear before online program BILL. See “Control files” on page 103 for more information about the control file fields and values. 4. Enter the maketpf command to build the program. This assumes that a file named maketpf.cfg exists in the /home/joe/mywork/build directory. cd /home/joe/mywork/build maketpf TaxFunctions Create an offline Linux program See “maketpf utility” on page 6 for more information about the maketpf command and its options. To create and build an offline Linux program (EXE), follow these steps: 1. Create a new makefile (/home/joe/mywork/billing/linux/src/ CustomerSummary.mak) as shown in the following example: Note: This program will use functions from an archive named Receipts. EXE := CustomerSummary TPF_OL := Linux ARCHIVES := Receipts CXX_SRC := list.cpp maketpf_env := billing_linux maketpf_env += base_rt include maketpf.rules 2. Create a source segment named /home/joe/mywork/billing/linux/src/ list.cpp. Assemble, compile, and link (build) application programs 67
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:
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 24 and 25: 18 z/TPF Program Management
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 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 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?