z/TPF Program Management - IBM

More documents

Recommendations

Info

152 z/TPF Program Management defaultloc is the default location for the @LOADSET control statement section, where defaultpath is one of the following types of paths: v The name of a search path that was defined previously in an @DEFINE control statement section (for example, &LDSTPATH) v An absolute path (for example, /u/ztpf/ldstpath) v A relative path (for example, ldstpath). Note: All relative paths are appended to the current working directory, which is defined by using the CWD parameter in the @DEFINE control statement section. Therefore, you must define the CWD parameter before you can specify a relative path. The default location is searched to locate the programs listed in the @LOADSET control statement section. You can override the default path for a particular program by specifying a specific path for that program. specificloc is the specific location for the program in the loadset, where specificpath is one of the following types of paths: v The name of a search path that was defined previously in an @DEFINE control statement section (for example, &LDSTPATH) v An absolute path (for example, /u/ztpf/ldstpath) v A relative path (for example, ldstpath). Note: All relative paths are appended to the current working directory, which is defined using the CWD parameter in the @DEFINE control statement section. Therefore, you must define the CWD parameter before you can specify a relative path. If you specify a specific location for a program, this location overrides any default location that may have been defined for the @LOADSET control statement section; that is, only the specific location is searched for the program. If the program is not found in the specific location, an error occurs. CWD is the value specified for the CWD parameter in the @DEFINE control statement section. If you do not specify a default location or a specific location, this is the only location that is searched. progname is the 4-character alphanumeric name of the program that you want to load to the z/TPF system. Program names must begin with a letter (A–Z). For example, if the linker creates a program called ctal51.so, the CTAL portion of the name is required. version is the 1- to 2-character alphanumeric version code for the program. For example, if the linker creates a program called ctal51.so, the 51 portion of the name is optional. .ext specifies an extension of the full program name as created by the linker, where ext is the appropriate extension. For example, if the linker creates a program called ctal51.so, the .so portion of the name is optional.
@VERIFY (progcmt) appends a comment for the program specified by progname that is displayed in the output report, where progcmt is the text that is appended. @@progname specifies a program to patch or to move, where progname is the 4-character name of the program that you want to patch or move. Program names must begin with a letter (A–Z). Note: If you want to patch a program, you must load the program in the current @LOADSET control statement section before you can patch it. If you are moving an entry point, you must ensure that it is being loaded in the current @LOADSET control statement section. .objfile specifies the object file name, where objfile is the 4-character alphanumeric name of the object file (within the program) that you want to patch on the z/TPF system. Object file names must begin with a letter (A–Z). rsa is the 1- to 6-digit hexadecimal relative starting address in the program or object file. The relative starting address specifies the offset into the program or object file where the patch will be applied. newdata is the new data (or patch) that will replace the old data in the program or object file, beginning at the relative starting address. The new data must be an even number of hexadecimal digits and cannot exceed 32 digits (16 bytes). valdata-olddata validates the data that is replaced by newdata, where olddata is an even number in hexadecimal format that does not exceed 32 digits (16 bytes). The data specified for olddata must match what is currently in the program. If it does not, the data in the program is not changed and an error occurs. If it does, the data in the program is replaced by newdata. For example, this parameter can help to verify that your patch is starting at the correct relative starting address. Note: The length of the data that you are validating can have fewer bytes or more bytes than the new data. If the validation is completed successfully, only the number of bytes in your new data will be replaced. MOVe indicates that the single entry BSO specified by @@progname has been moved into another BSO. The BSO that @@progname has been moved to must be included in the same loadset. Note: If the E-type loader is used to move an entry point, you cannot activate another loadset that moves the entry point again. The loadset that moved the entry point first must be deactivated or accepted before the entry point can be moved again. Use the @VERIFY control statement to specify a program attribute table (PAT) that includes all of the programs being loaded. The loader determines if each program being loaded exists in the specified PAT. The following figure shows the syntax for the @VERIFY control statement section of the loader input file. In this figure, the double arrowhead (►►) indicates that the z/TPF offline loader input file control statements 153
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:
Page 106 and 107:
Page 108 and 109: 102 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 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 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

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

Delete template?

Save as template?