z/TPF Program Management - IBM

More documents

Recommendations

Info

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | CSMP0097I 15.29.17 CPU-B SS-BSS SSU-HPN IS-01 CSMP0099I 15.29.17 010000-B ZMDES DISP+ CSMP0097I 15.29.17 CPU-B SS-BSS SSU-HPN IS-01 _ MDES0016I 15.29.17 DISPLAY OF ALL DEPLOYMENT DESCRIPTORS FOR PROCESSOR B IN-MEMORY FILE STATUS STATUS FILE NAME DEPLOYED DEPLOYED /sys/tpf_pbfiles/tpf-fdes/wodmDrvr.ept.xml DEPLOYED DEPLOYED /sys/tpf_pbfiles/tpf-fdes/wodmDrvr.ilr.xml _ DEPLOYED DEPLOYED /sys/tpf_pbfiles/tpf-fdes/wodmDrvr.tdm.xml DEPLOYED DEPLOYED /sys/tpf_pbfiles/tpf-fdes/bepDrvr.evspec.xml DEPLOYED DEPLOYED /sys/tpf_pbfiles/tpf-fdes/bepDrvr.evda.xml END OF DISPL Related reference: ZMDES–Manage deployment descriptors Related information: “E-type loader” on page 115 “Image loader” on page 113 Removing a deployment descriptor Use this procedure to remove a deployment descriptor from the z/TPF system. Procedure 1. Delete or accept any active or inactive loadsets that contain the deployment descriptor that you want to remove. Wait for the delete or accept operation to complete before you continue to the next step. 2. Undeploy the deployment descriptor. a. To undeploy the deployment descriptor on all inactive processors, enter ZMDES UNDEPLOY FILE-descriptor IPROC-ALL, where descriptor is the file name of the descriptor. b. To undeploy the deployment descriptor on all active processors, enter ALL//ZMDES UNDEPLOY FILE-descriptor, where descriptor is the file name of the descriptor. If the deployment descriptor is permanently deployed, an error is issued because you cannot undeploy a permanently deployed descriptor. If this error occurs, ensure that the deployment descriptor is no longer used before you continue to step 3. 3. Remove the deployment descriptor from the file system by entering ZFILE rm /sys/tpf_pbfiles/tpf-fdes/descriptor, where descriptor is the file name of the descriptor. Results 96 z/TPF Program Management In-memory structures that are associated with the deployment descriptor continue to exist until the next IPL. Additionally, the deployment descriptor file name remains in the common deployment status file until the next IPL. What to do next At your convenience, IPL the prime module and cycle the z/TPF system to NORM state to clean up memory and the common deployment status file.
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Related reference: ZMDES–Manage deployment descriptors Related information: “Work with loadsets” on page 87 Handling an error during IPL after common deployment is installed After common deployment is loaded on your z/TPF system, if you IPL an additional processor in your loosely coupled complex, you might receive errors during restart. About this task Before you load common deployment to the z/TPF system in a loosely coupled complex, you must ensure that the version control file index (VCFX), process pseudo-file system (PROCFS), and the system pseudo-file system (SYSFS) are all mounted on each processor. If you IPL an additional processor in the loosely coupled complex and these file systems are not mounted on that processor, you might receive errors during restart. In particular, you might receive message FDES0011W. Use this procedure to correct the problem. Procedure 1. In 1052 state, cycle up get file storage (GFS). Enter ZPOOL 1052 UP. 2. Mount the version control file index (VCFX). 3. Mount the process pseudo-file system (PROCFS). 4. Mount the system pseudo-file system (SYSFS). 5. Cycle down GFS. Enter ZPOOL 1052 DOWN. 6. IPL the processor again. 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: ZPOOL 1052–Cycle get file storage support up or down in 1052 state Related information: z/TPF file system support Using common deployment 97
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: 48 z/TPF Program Management
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 98 and 99: Terminal Addr Index into Selective
Page 100 and 101: | | | | | | | | | | | | | | | | | |
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

Create successful ePaper yourself

Delete template?

Save as template?