z/TPF Program Management - IBM

More documents

Recommendations

Info

Terminal Addr Index into Selective Activation Table ------------- ------------------ 020103 0 030567 0, 1 002203 1 292834 1, 2 Figure 11. Selective activation index example Create a disable command 92 z/TPF Program Management Note: Figure 11 contains a list of ECB origins (terminal addresses) and the associated index into the selective activation table. In this example, ECBs originating on terminal 292834 can enter programs and files from loadsets Sally or Fred1. The user-defined disable command should stop an ECB from using a loadset. This message should remove the index pointer for the selective activation index entry, and if there are no more index entries that reference the specified loadset, remove the associated selective activation table entry (if there are no more ECB origins that reference a loadset, there is no longer a need to maintain the activation number in the selective activation table). If there are no more loadsets enabled to be used by the specified ECB origin, then the index entry can be removed. By removing the table index from the index entry, ECBs originating from that origin will not have the specified loadset's activation number in their activation number list (which is used by Enter / Back to determine which version of a program or file to use). If a file copy of the mapping structure is maintained, then it will have to be updated to reflect the disable request. Note: It is entirely possible that the loadset name will not be found in either table. The user-written disable code should handle this condition. This can occur for 2 reasons: 1. The loadset was selectively activated, but never enabled. Here, a table entry for the loadset was never created. 2. It is possible that the loadset was enabled; however, the mapping structure is not recorded on file (for example, the enables do not survive an IPL). If an IPL were to occur after the enable and before the disable request, the disable code would not find the loadset in the tables.
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Using common deployment You must load your deployment descriptors to the z/TPF system with the E-type loader or the image loader. After the descriptors are loaded to the system, you can use the ZMDES command to deploy and undeploy the descriptor files. Related concepts: “Common deployment” on page 37 The z/TPF system uses a mechanism called common deployment to make deployment descriptors available for use. Related reference: ZMDES–Manage deployment descriptors Loading deployment descriptors Use this procedure to load your deployment descriptors to the z/TPF system with the E-type loader. About this task You can use the E-type loader or the image loader to load your deployment descriptors. This procedure is an example of how to load the descriptor files with the E-type loader. Procedure 1. On Linux, create an offline loader input file that defines where to find the deployment descriptors on Linux and where to place them on the z/TPF system. The following example shows the contents of an offline loader file called ddfiles.list: @DEFINE SYSID=BSS @LOADSET DESCRIPT @FILE /home/mydir/wodmDrvr.ilr.xml /sys/tpf_pbfiles/tpf-fdes/wodmDrvr.ilr.xml /home/mydir/wodmDrvr.ept.xml /sys/tpf_pbfiles/tpf-fdes/wodmDrvr.ept.xml /home/mydir/wodmDrvr.tdm.xml /sys/tpf_pbfiles/tpf-fdes/wodmDrvr.tdm.xml /home/mydir/bepDrvr.evspec.xml /sys/tpf_pbfiles/tpf-fdes/bepDrvr.evspec.xml /home/mydir/bepDrvr.evda.xml /sys/tpf_pbfiles/tpf-fdes/bepDrvr.evda.xml 2. On Linux, generate the OLDR format loader output file by entering the loadtpf command with the input file that you created in step 1 specified. For example, loadtpf ddfiles.list. The following messages are displayed. In this example, the files are transferred automatically to the z/TPF system based on a LOADTPF_IP parameter that is specified in the maketpf.cfg file. © Copyright IBM Corp. 2005, 2012 93
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: 42 z/TPF Program Management
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 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 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 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?