z/TPF Program Management - IBM

More documents

Recommendations

Info

IMGCLEAR specifies whether image-related records are cleared. YES clears and initializes various image-related records. When IMGCLEAR=YES is specified, IPLA, IPLB, CTKX, and all the CIMR components need to be loaded. Attention: When IMGCLEAR=YES is specifed, all image definitions are NO cleared from the online system. does not clear or initialize various image-related records. Attention: Do not use this line for the @DEFINE control statement section when performing an OLDR load. If you do, you will receive an error message and a return code of 8. See “Return codes” on page 121 for more information about offline loader return codes. Note: If you specify this line for the @DEFINE control statement section when performing a TLDR load, it is ignored. You will receive a return code of 4. See “Return codes” on page 121 for more information about offline loader return codes. OVERLAY_IPAT specifies whether to merge or replace the program attribute table (PAT). YES replaces the PAT in core and requires that all programs get reloaded. NO merges the existing PAT with the PAT that is being loaded. Attention: Use this line for the @DEFINE control statement section only when performing a TLDR load. PROGCLEAR specifies whether a program base is cleared. YES 138 z/TPF Program Management clears and reinitializes the master extra program record for the target image so that all extra program records (#XPRGn fixed file records, where n is the program base number for the image you are loading to) are available to be dispensed. Additionally, the program base unique file directory (/sys/tpf_pbfiles) is cleared. If get file storage (GFS) is not active when the online load is performed, the target program base indicates that its program base unique file directory has not been cleared. In this case, the directory will be cleared the next time GFS activation occurs on any processor. If GFS activation does not occur before an initial program load (IPL) is performed on the target image, the program base unique file directory is cleared when GFS is activated following the IPL of the target image. References to program base unique files that occur before GFS activation are intercepted by the z/TPF system and the directory appears empty to an application. Note: Only files in the program base unique file directory are cleared. Other files that are loaded by using the loader are not part of the program base and are not cleared.
@FILE NO does not clear or reinitialize the master extra program record or the program base unique file directory. Attention: Use this line for the @DEFINE control statement section only when performing a TLDR load. Note: 1. You must specify PROGCLEAR=YES to initialize a program base before you can load any real-time programs to an image for the first time. 2. All real-time programs must be reloaded when you specify PROGCLEAR=YES. Use the @FILE control statement to specify one or more files to be loaded. This control statement is valid for OLDR and TLDR files. Note: REP cards are not supported for files. The following figure shows the syntax for the @FILE control statement section of the loader input file. In this figure, the double arrowhead (►►) indicates that the information must begin on a new line. ►► @FILe ► ► -d /sys/tpf_pbfiles -s default-sourcedir -d default-targetdir -p default-permission -o default-owner -g default-group -t NONE -t ATOE -ONL Note: This must be the first line of the @FILE control statement section. ►► sourceloc ► -t NONE -t ATOE -ONL Note: targetloc -p permission -o owner -g group (comment) v You can specify any number of files. v When listing programs after files in an E-type loader input file, you must use a @LOADSET control statement (without specifying a loadset name) to indicate the end of files and start of programs. Figure 17. @FILE control statement section of the loader input file -s default-sourcedir is the default source location when relative paths are specified. If you do not z/TPF offline loader input file control statements 139 ► ► ►◄ ► ►◄
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:
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: 98 z/TPF Program Management
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 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: 160 z/TPF Program Management
show all

z/TPF Program Management - IBM

Create successful ePaper yourself

Delete template?

Save as template?