z/TPF Program Management - IBM

More documents

Recommendations

Info

3. The JCL also references the format cards produced by the FACE table generator (fmta.mac, fmtb.mac, and so on). You will need to change the referenced HFS to the text mount HFS name where the format cards reside or you will need to move the format cards to a PDS and then reference that PDS. 4. Submit the JCL for each of the online modules to be formatted. Create the general file loader input file Create a general file loader input file by entering bldtpf -ald controlfile, where controlfile is the path to tpf.cntl. See z/TPF and z/TPFDF System Generation for more information about creating a general file loader input file. See “ALDR input file” on page 158 for an example of a general file loader input file. Load system components to the loader general file Load fixed-file records 74 z/TPF Program Management Run the TPFLDR offline program with the ALDR parameter specified to load system components to the general file. You must load the following z/TPF components to the loader general file by using TPFLDR: v Core image restart (CIMR) area components. v CTKX. v IPLA. v IPLB. v Program attribute table (PAT). v Real-time components that are required in the loader general file and specified in the control file. See “Control files” on page 103 for more information about control files v Keypoints. Note: You must load all keypoints to the loader general file, but not necessarily to the online keypoint area. To avoid loading any particular keypoints to the online keypoint area, specify the keypoints on the @GFKEYPOINT control statement and do not specify them on the @KEYPOINT control statement. Sample JCL is provided in the base/samples/jcl directory. Complete the following steps to load fixed-file records: 1. Create a pilot tape (symbolic name = SDF) with the system test compiler (STC) program. See z/TPF Program Development Support Reference for information about the system test compiler program. Note: A maximum of 2 147 483 647 records can be read or written from a pilot tape. 2. Mount the pilot tape (SDF). This is the only input to the data loader. 3. Enter the ZSLDR command to activate the data loader. See z/TPF Operations for more information about the ZSLDR command. Note: Once records are loaded to the z/TPF database, no utility is available to remove the records from the database. If it is necessary to delete previously loaded records from the z/TPF database, you must create and load a new pilot tape that contains dummy records. If the number of
ecords decreases from one load to the next, the additional records from the first load will not be removed from the database. 4. Take either of the following two actions: a. If the loaded records are meant for main storage, perform an online module IPL to place the records there. b. The system can be cycled to NORM state without an online module IPL. An IPL will be required in the future to place the records in main storage. Note: 1. The data loader can be operated only while the z/TPF system is in 1052 state unless the ID of the pilot tape is N. If the ID of the pilot tape is N, the z/TPF system can be in any state. 2. In a loosely coupled facility, the subsystem cannot be above 1052 state in any processor unless the ID of the pilot tape is N. If the ID of the pilot tape is N, the subsystem can be in any state. Load system components to a new z/TPF system 75
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: 32 z/TPF Program Management
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 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 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

Create successful ePaper yourself

Delete template?

Save as template?