z/TPF Program Management - IBM

More documents

Recommendations

Info

108 z/TPF Program Management Table 6. Load file column definitions (continued) 1 Source path Free-form edit v The relative or absolute path of the file on Linux that is to be loaded to the z/TPF system. If the MakeTPF build solution determines that the file does not use the source path as an absolute path: – The files in the base/cntl/tpf.loadfile file are relative to the TPF_ROOT directory – The files in base/cntl/usr.loadfile are relative to the APPL_ROOT directory. v Pathnames for configuration-dependent files can use the string to represent the configuration dependent directory name. The MakeTPF build solution will replace with the directory name derived from the values of TPF_BSS_NAME, TPF_SS_NAME, and TPF_BAS_DIRNAME, defined in the maketpf configuration file. v Example names: /loadfiles/ data.txt,ztpf/prod/ loadfiles/data.txt, home/user/myprj// loadfiles/data.txt 2 Target path Free-form edit v The absolute path on a z/TPF system. v The program base unique files must be loaded to the /sys/tpf_pbfiles directory. 3 Permission See the permission parameter on the “@FILE” on page 139 control statement for more information. 4 Owner Free-form edit See the newowner parameter on the ZFILE chown command for more information. 5 Group Free-form edit See the newgroup parameter on the ZFILE chown command for more information.
Table 6. Load file column definitions (continued) 6 Source file data type v v BINARY TEXT v ONLINE 7 System allocation v ALL v BSS v EXC v ssname Specifies the data type of the file that is loaded to the z/TPF system. Explanation of the supported values: BINARY specifies that the source file contains binary data that does not require text translation when loaded on the z/TPF system. TEXT specifies that the source file contains text data that is translated to EBCDIC data when loaded on the z/TPF system. ONLINE specifies that the source path identifies an online file to be affiliated with the loadset. The ONLINE parameter applies to files that not included in loader input files that are generated for an OLDR load. Indicates the type of system to which a file is loaded. Explanation of the supported values: ALL BSS EXC specifies that the file is included in the loader input file for all subsystems. specifies that the file is included in the loader input file for the basic subsystem (BSS). specifies that the file is included in the loader input file for all subsystems except the BSS. ssname specifies that the file is included in the loader input file for a specified subsystem. Load files for version control 109
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:
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 38 and 39:
Page 40 and 41:
| | | | | | | | | | | | | | | | | |
Page 42 and 43:
Page 44 and 45:
| | | | | | | | | | | | | | | | | |
Page 46 and 47:
| | | | | | | | | | | | | | | 40 z/
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
| | | | | | | | | | | | | | | | | |
Page 54 and 55:
Page 56 and 57:
| | | | | | | | | | | | | | | | | |
Page 58 and 59:
Page 60 and 61:
Page 62 and 63:
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 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 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 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?