z/TPF Program Management - IBM

More documents

Recommendations

Info

| | | | | | | | loadtpf utility Related reference: ZFCTB LOAD–Load an alternate FACE table ZODBR LOAD–Prepare for an online database reorganization Related information: “Update the FACE table” on page 71 The loadtpf utility (enter the loadtpf command to activiate) can generate an E-type load file by using the bldtpf command and the offldr command and transferring the file (by using FTP) to a z/TPF system. The loadtpf utility can load programs and files based on a control file, an E-type loader input file, an E-type load file, a program name, or a z/TPF shared object. Note: The loadtpf command requires a user ID and password that is specified in a .netrc file. For more information, see “Set up automated loading to remote z/OS systems” on page 60. For reference information, enter man loadtpf on your Linux build system. Related information: “Update the FACE table” on page 71 “bldtpf utility” on page 5 “Linux offldr command” on page 119 “Set up automated loading to remote z/OS systems” on page 60 maketpf_cntl_tdmdd_checker utility maketpf utility 6 z/TPF Program Management The maketpf_cntl_tdmdd_checker utility verifies the data model descriptor control file format and content. The utility checks each field in each entry of the cntl_tdmdd file by using the specifications defined in the prolog of the base/cntl/ tpf.cntl_tdmdd file. For reference information, enter man maketpf_cntl_tdmdd_checker on your Linux build system. The maketpf utility (enter the hmaketpf command to activiate) is a single-program builder for maketpf-format makefiles and drives the assemble, compile, and link of all z/TPF system and customer application programs, both online and offline. To build a program, enter maketpf followed by a program name or a makefile name. If you enter the maketpf command with a program name as an argument, the command tries to locate the program in the control files and uses the makefile specified there. If the program is not found, the command tries to locate and use a makefile with the same name as the program, but with a .mak extension. To build a single-source segment without a makefile, enter maketpf followed by the segment file name. You also can use maketpf to call targets in a build. For example, enter maketpf cmqs cmqapi.o to build cmqapi.o for program cmqs.
| | | | | | | | | | | | | | | | | | | | | | | | | | | tpfObjectConverter utility Local modifications For reference information, enter man maketpf on your Linux build system. Related information: “Assemble, compile, and link (build) application programs” on page 57 The tpfObjectConverter utility produces programming artifacts such as C header files, assembler DSECTS, and Java classes from a descriptor file that contains Object definitions. You can also use this utility to update the deployable rule request server enterprise archive (EAR) file to contain the new execution object model that corresponds to the input data model. All programming artifacts are produced and placed in subdirectories of the working directory by default. Programming artifact Subdirectory C headers ./include Assembler DSECTS ./macro Java ./java Note: When invoked by the bldtpf utility, which artifacts to create and which directories to place them in are defined in the cntl_tdmdd files. For reference information, enter man tpfObjectConverter on your Linux build system. Related reference: Data model descriptor The data model descriptor contains the definitions for a set of objects. Business event specification The business event specification is used to define a business event. This specialized XML file contains the name of the event, a definition of the data that is being provided for the event, and a list of business event dispatch adapters that are used to transmit the data to the event consumers. Related information: “bldtpf utility” on page 5 The MakeTPF build solution allows local modifications to code that is included with the z/TPF system. The MakeTPF build solution searches the local_mod/ directory for files before searching the z/TPF system directories. You can place modified copies of files that are included with z/TPF in this directory to prevent your changes (local modifications) from being overwritten when the files are updated. Assemble, compile, and link options Options, also known as flags, define how an assembly, compile, or link will run; for example, you can use them to set optimization levels, generate debug data, or hide warnings. A default set of assemble, compile, and link options is defined by the MakeTPF tools. MakeTPF build solution 7
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 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 56 and 57: | | | | | | | | | | | | | | | | | |
Page 62 and 63:
56 z/TPF Program Management
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:
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?