z/TPF Program Management - IBM

More documents

Recommendations

Info

3. Update the user control file and add a new entry for the offline Linux program named CustomerSummary. Enter the following information on one line. CustomerSummary;OL;billing/linux/src/CustomerSummary.mak;1;LINUX; NOOBJ;;;;;;;;;;;;;;;;;;;;;;;;;;;; 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 a that file named maketpf.cfg exists in the /home/joe/mywork/build directory. cd /home/joe/mywork/build maketpf CustomerSummary See “maketpf utility” on page 6 for more information about the maketpf command and its options. Create an archive for offline Linux programs To create and build an archive for offline Linux programs, follow these steps: 1. Create a new makefile (/home/joe/mywork/billing/linux/src/Receipts.mak) as shown in the following example: ARCHIVE := Receipts TPF_OL := Linux CXX_SRC := receipts.cpp maketpf_env := billing_linux maketpf_env += base_rt include maketpf.rules 2. Create a source segment named /home/joe/mywork/billing/linux/src/ receipts.cpp. 3. Update the user control file and add a new entry for the archive named Receipts. Enter the following information on one line. Receipts;ARCHIVE;billing/linux/src/Receipts.mak;1;LINUX; NOOBJ;;;;;;;;;;;;;;;;;;;;;;;;;;;; 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 Receipts must appear before offline program CustomerSummary. 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 Receipts Create an offline z/OS program 68 z/TPF Program Management See “maketpf utility” on page 6 for more information about the maketpf command and its options. To create and build a new makefile for an offline z/OS program (EXE), follow these steps: 1. Create a new makefile (home/joe/mywork/billing/zos/src/custsumm.mak) as shown in the following example:
Create an export file EXE := custsumm TPF_OL := OS/390 C_SRC := list.c maketpf_env := billing_zos maketpf_env += base_rt include maketpf.rules Note: z/OS programs do not support the use of archives and, because the programs are written to a PDS, the program name must be 8 characters or less. 2. Create a source segment named /home/joe/mywork/billing/zos/src/list.c. 3. Update the user control file and add a new entry for the offline Linux program named custsumm. Enter the following information on one line. custsumm;ARCHIVE;billing/zos/src/custsumm.mak;1;OS/390; NOOBJ;;;;;;;;;;;;;;;;;;;;;;;;;;;; Note: The control file entry uses the value OS/390 ® rather than z/OS. This was done for compatibility reasons with TPF 4.1 and the terms are considered interchangeable. 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 custsumm See “maketpf utility” on page 6 for more information about the maketpf command and its options. The following task shows you how to create an export file for a CSO or BSO. Export files are used to control the entry points that are exported globally and the ones that are kept local to the object. Export files are required whenever you code APP_EXPORT := LIST in the program makefile. (An alternate way to change the scope of symbols that are global for a shared object is to use the -fvisibility compiler option. Specify -fvisibility=default to indicate that the functions in the CSO (or C/C++ functions in a BSO) are global for the shared object. Specify -fvisibility=hidden to indicate that all C/C++ functions are local except where they are coded with __attribute__((visibility(default))). ) Note: Although we are using a CSO for an example, you can follow the same steps to create an export file for a BSO. If you have created a CSO named BILL as described in “Create a C shared object” on page 64 and have coded APP_EXPORT := LIST in the /home/joe/mywork/billing/ rt/src/bill.mak makefile, you can create an export file by following these steps: 1. Run maketpf to create a preliminary version of the export file. cd /home/joe/mywork/build maketpf bill Note: Export files present a “what came first” problem; you must link the program to be able to generate the export file, but when you code APP_EXPORT := LIST, you need an export file at link time. To work around Assemble, compile, and link (build) application programs 69
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 72 and 73: 66 z/TPF Program Management v CTBX
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 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?