z/TPF Program Management - IBM

More documents

Recommendations

Info

0 8 0 v A return code indicating the level of success of the loading phase of the offline load. The return code for the entire offline load is the greater of the two return codes. The following defines the return code values. Explanation: No errors occurred; no warnings were generated. System action: The offline load is completed. User response: Use the appropriate online loader to load the components or programs to your z/TPF system: 1. If you did an offline E-type load, use the ZOLDR command. 2. If you did an offline general file load, ACPL will start automatically when you IPL the loader general file. 3. If you did an offline image load, use the ZTPLD command. See z/TPF Operations for more information about the ZOLDR and ZTPLD commands. See “Online general file loader component (ACPL)” on page 23 for more information about the ACPL program. 4 Explanation: An error occurred because there was an unexpected line in the loader input file. For example, this return code is generated for the following errors: v A line started with a slash-asterisk (/*) indicating that the line is a comment. A closing asterisk-slash (*/) was not found before the end of the file. The offline loader assumes that the end of the file is the end of the comment. v The @INCLUDE control statement was started with @INCLUDE, but a file was not specified. v A processor was specified for something other than a processor-unique keypoint. v An object file was specified for a control statement other than @APPLICATION. v A control statement was misspelled; for example, @APPLICATOIN rather than @APPLICATION. v A control statement includes extra text that was not expected. System action: The offline loader program makes assumptions about the unexpected lines and completes the load. User response: Complete the following steps: 1. Review the errors and determine if the assumptions made by the loader were correct. 2. Do one of the following: 122 z/TPF Program Management 8 v If the assumptions made by the offline loader were correct, use the appropriate online loader to load the components to your z/TPF system: a. If you did an offline E-type load, use the ZOLDR command. b. If you did an offline general file load, ACPL will start automatically when you IPL the loader general file. c. If you did an offline image load, use the ZTPLD command. See z/TPF Operations for more information about the ZOLDR and ZTPLD commands. See “Online general file loader component (ACPL)” on page 23 for more information about the ACPL program. Consider correcting the loader input file so that these errors are not repeated in the future. v If the assumptions made by the offline loader were incorrect, make the necessary corrections to the loader input file and run the offline load again. Explanation: An error occurred that impacts the output of the offline load. For example, this return code is generated for the following error: v There is an entry point name that is exported by more than one shared object. System action: If this return code is for the parsing phase of the load, the loading phase is not completed. If this return code is for the loading phase, the load is completed without the component that caused the error. User response: Do one of the following: v If the error occurred during the parsing phase, complete the following steps: 1. Review the error message and correct the loader input file. 2. Run the offline load again. The loading phase will not begin until the parsing phase has completed with a return code of 0 or 4. v If the error occurred during the loading phase, complete the following steps: 1. Review the error message and make the necessary corrections. 2. If your load requires the component that caused the error, run the offline load again.
12 Explanation: An error occurred that prevents the load from being completed. For example, this return code is generated for the following errors: v The loader input file could not be opened. v The loader input file is empty. v There are multiple occurrences of the load type parameter in the JCL. For example, ’TLDR,ALDR’ or ’TLDR,TLDR’. v There are multiple occurrences of the trace parameter in the JCL. For example, ’TRACE(ON),TLDR,TRACE(OFF)’ or ’TRACE(ON), TRACE(ON)’. Comment conventions v There is not enough space for one or more structures. v A parameter specified in the JCL is not valid. v An error occurred while opening, writing to, or reading one of the output files. System action: The load is not completed. User response: Complete the following steps: 1. Review the error messages and make the necessary corrections. 2. Run the offline load again. When you create the loader input file for the offline loader, you can include comments that use the following conventions: v To denote that an entire line is a comment, ensure that the first nonblank character on the line is an asterisk (*). v To denote a comment in a line, place a slash-asterisk (/*) before the start of your comment and an asterisk-slash (*/) after the end of your comment. These inline comments can span multiple lines. Note: When your loader input file is inline with your JCL (that is, you are using the LDRLOAD DD * DD statement), a slash-asterisk (/*) in the first column indicates the end of the input file. Accordingly, any comments in that inline loader input file cannot start in the first column. v To associate a comment with a program, place the comment text in parentheses after the program specification. The comment is displayed in the output report. v To associate a comment with a loadset, place the comment text in parentheses on the line following the @LOADSET statement. The parentheses cannot be nested and you cannot use a closing parentheses as part of a comment. Examples The following example shows: v The text of a loadset-level comment in parentheses on the line following the @LOADSET LOADTEST statement v The text of an inline comment contained between a /* and /* v The text of a program-associated comment contained in parentheses v The text of a comment on an entire line denoted by an *. @LOADSET LOADTEST /home/dfallon/proj/maketpf_load (Place your loadset-level comment here.) PRG2bin parentheses.so /* comment in line */ PRG1.so PRG3.so (This is a program-associated comment.) @@PRG1.so 044 0047 this is a patch to PRG1.so * Comment line - include a file in this loadset @FILE -s /u/dfallon -o tpfdfltu -g tpfdfltg myfile.txt @LOADSET LOADTXT @FILE -s /u/dfallon -o tpfdfltu -g tpfdfltg filebase1.txt 12 z/TPF offline loader 123
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: 76 z/TPF Program Management
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 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 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?