z/TPF Program Management - IBM

More documents

Recommendations

Info

Data loader Pilot Tape (SDF) ZSLDR LOAD DATA n E-type loader recycle interface user Internet server programs user exit (UERA) to specify the programs that comprise the Internet server application. If the E-type loader recycle interface detects a change in any standard library version, the caller is notified that a recycle is needed. The standard libraries are CFVS, CISO, CJ00, CLBM, COMS, COMX, CPP1, CTAD, CTAL, CTBX, CTDF, CTHD, CTIS, and CTXO. Use the E-type loader recycle interface user libraries user exit (UERL) to specify additional standard libraries. Related information: v See tpf_etype_loader_recycle_interface. v See ZOLDR ACCEPT and ZOLDR DELETE. v See ECB-controlled program user exits. Figure 9 shows how the ZSLDR command takes data from a pilot (SDF) tape and loads it to online modules. Data Loader Output Msg Primary Process Data Flow Online Module Online Module Figure 9. Loading fixed-file records using the ZSLDR command When system has been brought to 1052 state for the first time by a loader general file IPL, use the data loader to load it with fixed-file records. These records are used by the system and by the application programs. Offline loader support on Linux 28 z/TPF Program Management Online Module You can use the z/TPF offline loader on Linux to write offline image loader component (TLDR) and offline E-type loader component (OLDR) files to both tape devices and hierarchical file system (HFS) files. Use the file transfer protocol (FTP) to send the z/TPF offline loader files that are created in your HFS to a z/TPF
system. Programs and files that have been compiled and linked on Linux do not need to be moved to a z/OS ® system before the z/TPF offline loader is created. The virtual reader (VRDR) and general data set (GDS) files, which are currently supported on MVS, are not supported by the z/TPF offline loader on Linux. Programming considerations The following lists the programming considerations for using the z/TPF offline loader on Linux: v The maximum file sizes for a z/TPF loader file that is created in the Linux HFS are: – 2 gigabytes (GB) for the ext2 file system – A range of 2 GB - 32 GB for the ext3 file system depending on the block size that was specified when the file system was initialized – 2 exabytes (EB) for the file systems used less frequently (such as XFS and ReiserFS) – 2 GB for the HFS file system that is implemented on the z/TPF system. v The size of an offline loader tape data set is limited to the capacity of a single tape volume. v The Linux offldr command creates tapes with MVS standard label (SL) headers and trailers to provide the z/TPF system with SL tapes, which are not supported by Linux. See the “Linux offldr command” on page 119 and the Linux man page for more information about using the z/TPF offline loader on Linux. See “Linux labeltape command” on page 121 and the Linux man page for more information about using the z/TPF labeltape command on Linux. Alternate FCTB loader overview An alternate FACE table (FCTB) loader loads an FCTB to a z/TPF system without requiring an initial program load (IPL). The following ZFCTB commands support alternate FCTB processing: v ZFCTB LOAD Loads an alternate FCTB to the online system v ZFCTB ACTIVATE Activates an alternate FCTB v ZFCTB ACCEPT Accepts an activated alternate FCTB v ZFCTB DEACTIVATE Deactivates an activated alternate FCTB v ZFCTB DELETE Deletes a loaded or deactivated alternate FCTB. See z/TPF Operations for more information about the ZFCTB commands. See “Load an alternate FCTB” on page 83 for more information about the alternate FCTB loader. z/TPF loaders 29
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 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 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 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 86 and 87:
80 z/TPF Program Management
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?