z/TPF Program Management - IBM

More documents

Recommendations

Info

136 z/TPF Program Management Additional syntax for an OLDR or a TLDR load: DEBUGFILES=YES DEBUGFILES=NO Additional syntax for a TLDR load: ► ELDRCLEAR=NO ELDRCLEAR=YES FCTBCLEAR=NO FCTBCLEAR=YES OVERLAY_IPAT=NO OVERLAY_IPAT=YES Additional syntax for an ALDR load: IMGCLEAR=NO IMGCLEAR=YES PROGCLEAR=NO PROGCLEAR=YES Figure 16. Additional syntax for specific uses of the @DEFINE control statement section &searchpath specifies the name of a path, where searchpath is the name you want associated with the path. The path must start with an ampersand (&). If you specify more than one directory, use a colon (:) to separate directories. path is an absolute or relative directory that you can specify to search. &previouslydefinedsearchpath is an absolute or relative directory that was defined previously with the @DEFINE control statement section to search. The following example shows a path named &CIMRPATH that has three path definitions. @DEFINE &CIMRPATH=/u/ztpf/cp:/u/ztpf/fctb:/u/ztpf/cimrobj Using this definition, if you specify the path name of &CIMRPATH anywhere in the loader input file, the offline loader will attempt to locate the object that it applies to by searching the following directories in order: 1. /u/ztpf/cp 2. /u/ztpf/fctb 3. /u/ztpf/cimrobj Note: Path names are case sensitive. CWD=path specifies the current working directory, where path is the name of the absolute directory that relative directories are appended to. For other control statements, the following apply: ►
v Any relative paths are assumed to be relative to this directory. v The directory specified here is used as the search directory if neither a default location nor a specific location is specified for the control statement. Note: You can specify CWD as both a system setting in the @DEFINE control statement and as a command-line argument when you are performing an offline load on Linux. However, if you specify both the command-line argument and the system setting, these values must be consistent. SYSID specifies the subsystem ID. bssname is the name of the basic subsystem (BSS). You can define your own BSS name by specifying the BSSNAME parameter on the SSDEF macro; see z/TPF and z/TPFDF System Generation for more information about the SSDEF macro. ssname is the name of the subsystem. DEBUGFILES specifies whether the shared object with debug data will be written to the desired storage medium. YES writes the shared object with debug data to the desired storage medium. NO does not write the shared object with debug data to the desired storage medium. ELDRCLEAR specifies whether E-type loader record definitions are cleared. YES clears and reinitializes all E-type loader records and versioned files for the target image. Attention: When ELDRCLEAR=YES is specified, all programs and files that were loaded using the E-type loader (except those that were accepted) are cleared from the online system. NO does not clear or reinitialize E-type loader record definitions. Attention: Use this line for the @DEFINE control statement section only when performing a TLDR load. FCTBCLEAR specifies whether the alternate FACE table (FCTB) is cleared. YES clears the alternate FCTB for the target image. Attention: When FCTBCLEAR=YES is specified, the alternate FCTB that was loaded using the ZFCTB LOAD command is cleared from the online system unless it had already been accepted. See z/TPF Operations for more information about the ZFCTB LOAD command. NO does not clear the alternate FCTB. Attention: Use this line for the @DEFINE control statement section only when performing a TLDR load. z/TPF offline loader input file control statements 137
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: 86 z/TPF Program Management
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 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: 160 z/TPF Program Management
show all

z/TPF Program Management - IBM

Create successful ePaper yourself

Delete template?

Save as template?