TCP/IP Version 2 Release 4 Program Directory - IBM

More documents

Recommendations

Info

Figure 4. Program Tape: File Content for Source Feature Tape File Content 1 Tape Header 2 Tape Header 3 Product Header 4 Product Memo 5 Service Apply Lists 6 PTFPARTs 7 Source Feature Service 8 Source Feature Service 9 TCP/IP V2 R4 for VM Source Files 2.2.2 Optional Machine-Readable Material for NFS Feature The distribution medium for this program is 9-track magnetic tape (written at 1600 or 6250 BPI), 3480 tape cartridge, or 4-mm tape cartridge. The tape or cartridge contains all the programs and data needed for installation. See 6.0, “Installation Instructions” on page 38 for more information about how to install the program. Figure 5 describes the tape or cartridge. Figure 6 describes the file content of the program tape or cartridge. Figure 5. Basic Material: Program Tape for NFS Feature Feature Number Medium Physical Volume Tape Content External Tape Label 5821 6250 tape 1 NFS Feature TCP/IP VM NFS 5822 3480 cart. 1 NFS Feature TCP/IP VM NFS 5752 4-mm cart. 1 NFS Feature TCP/IP VM NFS Figure 6 (Page 1 of 2). Program Tape: File Content for NFS Feature Tape File Content 1 Tape Header 2 Tape Header 3 Product Header 4 Product Memo 5 Service Apply Lists 6 PTFPARTs 6 TCP/IP V2 R4 for VM Program Directory
Figure 6 (Page 2 of 2). Program Tape: File Content for NFS Feature Tape File Content 7 NFS Feature Service 8 NFS Feature Service 9 NFS Feature Base Code 10 NFS Feature Executable Server Code 11 NFS Feature Executable Client Code 12 NFS Feature Source Files 2.2.3 Optional Machine-Readable Material for Kerberos US Feature The distribution medium for this program is 9-track magnetic tape (written at 1600 or 6250 BPI), 3480 tape cartridge, or 4-mm tape cartridge. The tape or cartridge contains all the programs and data needed for installation. See 6.0, “Installation Instructions” on page 38 for more information about how to install the program. Figure 7 describes the tape or cartridge. Figure 8 describes the file content of the program tape or cartridge. Figure 7. Basic Material: Program Tape for Kerberos US Feature Feature Number Medium Physical Volume Tape Content External Tape Label 5831 6250 tape 1 Kerberos US Feature TCP/IP VM Kerb(DES) 5832 3480 cart. 1 Kerberos US Feature TCP/IP VM Kerb(DES) 5753 4-mm cart. 1 Kerberos US Feature TCP/IP VM Kerb(DES) Figure 8 (Page 1 of 2). Program Tape: File Content for Kerberos US Feature Tape File Content 1 Tape Header 2 Tape Header 3 Product Header 4 Product Memo 5 Service Apply Lists 6 PTFPARTs 7 Kerberos US Feature Service 8 Kerberos US Feature Service Program Materials 7
Page 1 and 2: IBM Program Directory for IBM TCP/I
Page 3 and 4: Contents Notices . . . . . . . . .
Page 5 and 6: 6.4.4.1 Copy NFS Feature Files Into
Page 7 and 8: 7.5.4.1 Copy the New Kerberos US Fe
Page 9 and 10: I.5 DHCPD Subcommands . . . . . . .
Page 11 and 12: | K.1.3.2 Processing Notes for PQ05
Page 13 and 14: 43. VMSES/E Build Lists - Kerberos
Page 15 and 16: 1.0 Introduction This program direc
Page 17 and 18: IBM * Transmission Control Protocol
Page 19: Figure 2 (Page 2 of 2). Program Tap
Page 23 and 24: Figure 10 (Page 2 of 2). Program Ta
Page 25 and 26: 3.0 Program Support This section de
Page 27 and 28: Figure 17. Problem Documentation Ad
Page 29 and 30: 4.2 Program Level Information - NFS
Page 31 and 32: | - For VM/ESA Version 2 Release 2.
Page 33 and 34: Note: Certain minidisks must be def
Page 35 and 36: To determine which services (if any
Page 37 and 38: 5.3.1 DASD Requirements for TCP/IP
Page 39 and 40: Figure 19 (Page 3 of 4). DASD Stora
Page 41 and 42: 5.3.2 DASD Requirements for Source
Page 43 and 44: | 5.3.3.2 DASD Storage Requirements
Page 45 and 46: 5.3.4.2 DASD Storage Requirements f
Page 47 and 48: Figure 26. Additional DASD Storage
Page 53 and 54: sample files to the SAMPLE disk and
Page 55 and 56: link maint 51d 51d mr access 51d d
Page 57 and 58: Note! Complete this step only if yo
Page 59 and 60: For most installations, the relativ
Page 61 and 62: - If you install multiple NDBSRVnn
Page 63 and 64: set filepool vmsys: create director
Page 65 and 66: VMFINS276I VMFINS processing starte
Page 67 and 68: VMFINS276I VMFINS processing starte
Page 69 and 70: 6.2.3.1 Update Build Status Table f
Page 71 and 72:
| Note: If another user already has
Page 73 and 74:
Figure 31. Files to Copy into Produ
Page 75 and 76:
Figure 32 (Page 2 of 2). Files to C
Page 77 and 78:
vmfins install info (nomemo The NOM
Page 79 and 80:
6.3.2 Allocate Resources for Instal
Page 81 and 82:
Notes: If you've already created a
Page 83 and 84:
6.4 Installing TCP/IP V2 R4 for VM
Page 85 and 86:
Notes: a. If you change the PPF nam
Page 87 and 88:
6.4.2.1 PROFILE Directory Entries T
Page 89 and 90:
set filepool vmsys: create director
Page 91 and 92:
VMFINS276I VMFINS processing starte
Page 93 and 94:
The 5735FALL CATALOG file is used b
Page 95 and 96:
tcp2prod 5735fall {vmnfs | vmnfssfs
Page 97 and 98:
access 2b3 m copyfile fn ft m (unpa
Page 99 and 100:
Page 101 and 102:
Note! Complete this step only if yo
Page 103 and 104:
Add the directory entries for VMKER
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
The 5735FALN CATALOG file is used b
Page 111 and 112:
Note When you perform this step, yo
Page 113 and 114:
access 2b3 m copyfile fn ft m (unpa
Page 115 and 116:
Page 117 and 118:
Note! Complete this step only if yo
Page 119 and 120:
Add the directory entries for VMKER
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
The 5735FALP CATALOG file is used b
Page 127 and 128:
Page 129 and 130:
access 2b3 e copyfile fn ft e (unpa
Page 131 and 132:
All local service (mods) must be en
Page 133 and 134:
Quick Index for Service Instruction
Page 135 and 136:
Use tcpip or tcpipsfs if you instal
Page 137 and 138:
compname should be tcpip, tcpipsfs,
Page 139 and 140:
vmfview build Note Continued ... vm
Page 141 and 142:
link maint 51d 51d mr access 51d d
Page 143 and 144:
vmfview receive Use tcpip or tcpips
Page 145 and 146:
Note If a $PPF file has been servic
Page 147 and 148:
7.2.3.6 Test the New Service You sh
Page 149 and 150:
Page 151 and 152:
7.3 Servicing TCP/IP V2 R4 for VM -
Page 153 and 154:
service on the RSU. Use this to ens
Page 155 and 156:
vmfview apply 3 Re-work and re-appl
Page 157 and 158:
Note Continued ... copyfile 5735fal
Page 159 and 160:
link maint 51d 51d mr access 51d d
Page 161 and 162:
7.4.4.3 Apply the Service 1 Apply t
Page 163 and 164:
Page 165 and 166:
link maint 5e5 5e5 rr access 5e5 b
Page 167 and 168:
Note tcp2prod 5735fall {vmnfs | vmn
Page 169 and 170:
vmfsetup 5735faln {vmkerb | vmkerbs
Page 171 and 172:
Note If you receive message VMFAPP2
Page 173 and 174:
vmfview build 2 Use VMFVIEW to revi
Page 175 and 176:
6 Copy serviced TCP/IP for VM files
Page 177 and 178:
7.6 Servicing TCP/IP V2 R4 for VM -
Page 179 and 180:
7.6.2.2 Receive the Service Electro
Page 181 and 182:
Page 183 and 184:
link maint 5e5 5e5 rr access 5e5 b
Page 185 and 186:
Page 187 and 188:
A.1.3 Options TCP2PROD TEST causes
Page 189 and 190:
A.2 TCP/IP for VM CATALOG Files A.2
Page 191 and 192:
TCP/IP for VM CATALOG Files A.2.4 U
Page 193 and 194:
| where | ppfname is the name of t
Page 195 and 196:
| xedit appid $select fm-applyalt (
Page 197 and 198:
An overlay of the IBM Language Envi
Page 199 and 200:
4 (Optional) Erase any TCP/IP for V
Page 201 and 202:
Figure 40 (Page 2 of 2). VMSES/E Bu
Page 203 and 204:
Figure 43 (Page 2 of 2). VMSES/E Bu
Page 205 and 206:
| E.2 IBM Network Station Support R
Page 207 and 208:
| USER P735FALK P735FALK 16M 64M BG
Page 209 and 210:
| where fm-delta is the file mode o
Page 211 and 212:
Appendix F. DHCPD Server Support /
Page 213 and 214:
USER P735FALK P735FALK 16M 64M BG /
Page 215 and 216:
| Appendix G. Overriding the TFTPD
Page 217 and 218:
| Important Note! | Throughout the
Page 219 and 220:
| H.2 Update the BOOTPD Profile Exi
Page 221 and 222:
BOOTPD Command | STAYUP | indicates
Page 223 and 224:
BOOTPD Subcommands | TCPBOO6508I So
Page 225 and 226:
| H.7.2 Usage Notes | 1. This subco
Page 227 and 228:
| frequency | is an indication of w
Page 229 and 230:
| H.8.3 Usage Notes | 1. The opposi
Page 231 and 232:
| UNKNOWN | indicates that BOOT req
Page 233 and 234:
| TCPBOO0502E Target IP Address is
Page 235 and 236:
| H.13.1 Purpose | Use the LURK sub
Page 237 and 238:
| One line per statement. | Blank
Page 239 and 240:
| H.18 TRACE Subcommand | | ►►
Page 241 and 242:
I.2 Update the DHCPD Profile Exit /
Page 243 and 244:
fm is the file mode of the file to
Page 245 and 246:
TCPDHC0502E Target IP Address is mi
Page 247 and 248:
The CMS keyword is used to identify
Page 249 and 250:
ANY for any client or gateway forwa
Page 251 and 252:
6 token-ring tr / 7 arcnet / 8 hype
Page 253 and 254:
I.9.3 Usage Notes / 1. The opposite
Page 255 and 256:
I.11.3 Usage Notes / 1. Forwarding
Page 257 and 258:
I.12.2 Operands / The HELP subcomma
Page 259 and 260:
I.14.3 Messages / Error messages ma
Page 261 and 262:
and syntax as the DHCPD EXCLUDE, FO
Page 263 and 264:
3 ax.25 / 4 pronet / 5 chaos / 6 to
Page 265 and 266:
2. If the “REQUEST” operand is
Page 267 and 268:
4 pronet / 5 chaos / 6 token-ring t
Page 269 and 270:
STATUS SUBNET 9.1.57. / 9.1.57.11 A
Page 271 and 272:
DHCPD Machine Statements / I.21.1 P
Page 273 and 274:
option A 1 / option B 2 / option C
Page 275 and 276:
- If a class is specified at both a
Page 277 and 278:
every minute and instead use 15 min
Page 279 and 280:
I.24.1.11 Specifying Option 43 Vend
Page 281 and 282:
Usually, it is better to specify cl
Page 283 and 284:
###################################
Page 285 and 286:
This completes the machine file. Th
Page 287 and 288:
# option 3 -> Router IP addresses #
Page 289 and 290:
Figure 51 (Page 2 of 2). DHCPD Mach
Page 291 and 292:
The following is an example of Bala
Page 293 and 294:
4. A client that requests an IP add
Page 295 and 296:
4. The Client statement may be spec
Page 297 and 298:
I.34.1 Purpose / Use the LeaseExpir
Page 299 and 300:
I.36.1 Purpose / Use the Option sta
Page 301 and 302:
I.36.3 Usage Notes / 1. The Option
Page 303 and 304:
I.38.2 Operands / time / is the amo
Page 305 and 306:
comments / anything after the left
Page 307 and 308:
I.41.1 Purpose / Use the SupportUnl
Page 309 and 310:
I.43.2 Operands / vendor_name / is
Page 311 and 312:
Figure 52 (Page 2 of 3). DHCP Optio
Page 313 and 314:
Figure 53. DHCP Option Datatype For
Page 315 and 316:
Figure 54 (Page 3 of 15). DHCP Opti
Page 317 and 318:
Page 319 and 320:
Page 321 and 322:
Page 323 and 324:
Figure 54 (Page 11 of 15). DHCP Opt
Page 325 and 326:
Page 327 and 328:
Page 329 and 330:
| You should also verify that the M
Page 331 and 332:
| --------------------------------
Page 333 and 334:
| LIGHT | indicates that the TFTP d
Page 335 and 336:
| Figure 55 (Page 2 of 2). TFTPD Su
Page 337 and 338:
| pathname | is the name of the fil
Page 339 and 340:
| J.11.2 Operands | pathname | is t
Page 341 and 342:
| J.13 EXIT Subcommand | | ►►
Page 343 and 344:
| J.17.1 Purpose | Use the LOADUSER
Page 345 and 346:
| | J.22 XFERMODE Subcommand | ►
Page 347 and 348:
| Appendix K. Processing the IBM Ne
Page 349 and 350:
| Figure 56 (Page 2 of 3). NSTATION
Page 351 and 352:
| 6. Each IBM Network Station using
Page 353 and 354:
| K.1.6 Service Level Information F
Page 355 and 356:
| - this user ID is defined as a PO
Page 357 and 358:
| 4. Mount the Byte File System roo
Page 359 and 360:
| SCRN4 IBM Network Station | Setup
Page 361 and 362:
| Appendix L. BOOTPD Trace Records
Page 363 and 364:
Appendix M. DHCPD Trace Records / D
Page 365 and 366:
DHCPTYPE = msgtype / indicates the
Page 367 and 368:
| hh:mm:ss | is the time portion of
Page 369 and 370:
| N.2.4 TFTPD Trace Entry: 2500 | T
Page 371 and 372:
| errdesc | is the error descriptio
Page 373 and 374:
| rc is the return code set by the
Page 375 and 376:
| Figure 64. TFTPD APPLDATA Data |
Page 377 and 378:
Is this the first time your organiz
show all

TCP/IP Version 2 Release 4 Program Directory - IBM

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

Delete template?

Save as template?