TCP/IP Level 410 Program Directory - z/VM - IBM

More documents

Recommendations

Info

TCP/IP for z/VM maintenance purposes, suitable PPF override changes must be implemented toreflect your changes.Note: If you choose to use an existing or “common-use” user ID (such as the MAINT user ID) toinstall and maintain TCP/IP for z/VM, minidisks may already be defined which have addresses thatconflict with TCP/IP for z/VM minidisk defaults. If such minidisks exist, you will need to create a PPFoverride to change the TCP/IP default minidisk addresses so they are unique within your environment.3. The minidisks that are associated with the 4TCPIP10, TCPMAINT, and TCPIP user IDs (or yourchosen equivalents) must be maintained in order to provide TCP/IP services within your environment.The remaining user IDs listed in Figure 9 are associated with servers and clients that provide optionalTCP/IP for z/VM services. If you choose to not use a particular optional service, you need notmaintain the user IDs and production minidisks associated with that service.4. If you choose to use user IDs for TCP/IP server virtual machines that differ from the IBM-supplied userIDs shown in Figure 9, ensure you review the section titled “Implications of Assigning Different ServerVirtual Machine Names” in Chapter 1 of z/VM: TCP/IP Level 3A0 Planning and Customization.5. Note the following, with regard to the user ID and minidisk information provided in Figure 9:Specific Minidisk RequirementsCertain minidisks must be defined for the TCP/IP server machines you choose to use, as well asfor maintaining TCP/IP for z/VM in your environment. Such minidisks cannot be replaced with anequivalent SFS directory.Minidisks to which this requirement applies are listed in Figure 9 with boldface virtual addresses.In addition, no default SFS directory names or SFS 4K block values are provided for theseminidisks.6. All 4TCPIP10 test build minidisks must be maintained. If the 4TCPIP10 minidisks for optionalservices are not maintained, problems will be encountered during installation and service.To identify TCP/IP services that are not required for your environment, review the service descriptionsprovided in z/VM: TCP/IP Level 3A0 Planning and Customization (SC24-5981). The server-specificconfiguration chapters of this publication may also help you with your determination.Also, if you omit resources that correspond to an optional service, you should not attempt to place anyof the files associated with that service into production (during step 6.2.3.4, “Copy TCP/IP for z/VMRun-time Files Into Production” on page 33). In such cases, the 4TCPIP10 CATALOG file should bemodified so any files not used in your environment are bypassed during TCP2PROD commandprocessing. See Appendix A, “TCP/IP Installation and Service Utilities” on page 70 for informationabout the TCP2PROD command and TCP/IP for z/VM catalog files.7. Additional storage may need to be allocated for a given user ID or server minidisk, depending on yourenvironment. Some examples of minidisks that may need to increased, and possible reasons for sodoing, are listed in Figure 7. Note that certain minidisks (not cited here) may also need to beincreased to accommodate the logging of tracing or other activities.20 TCP/IP for z/VM Program Directory
Figure 7. Alternative Minidisk Storage RequirementsUser ID / MinidiskSMTP 191VMNFS 191DHCPD 191LPSERVE 191SSLSERV 2014TCPIP10 2D2Rationale for Storage RevisionAllow for SMTP processing of a high volume of e-mailProvide support for a large number of NFS clientsProvide support a large number of DHCP clientsAllow for LPD processing of sizeable print jobsFacilitate installation of a Linux kernel and file systemFacilitate maintenance of multiple service levels of (binary) system files used by theSSL server8. The storage requirements for various TCP/IP minidisks may be revised over time to account forTCP/IP for z/VM content changes. In some cases, this may require the size of existing minidisks to beincreased.When applicable, storage requirement changes for specific minidisks will be identified in Figure 9, inupdated levels of this document. Such changes will be noted through the use of revision characters(usually a vertical bar — “|” in the left margin of a page).For other minidisks, storage requirement changes will need to be assessed locally, for your specificenvironment. For example, the capacity of the DELTA minidisk (4TCPIP10 2D2, by default),periodically may need to be increased, based on the specific preventive and corrective service appliedto your system.9. If you choose to provide Network Database services, you may find the need to define multiple virtualmachines, named NDBSRV01, NDBSRV02, etc. Each NDBSRVnn virtual machine you create shouldbe defined similar to NDBSRV01, which has been defined as part of the installed z/VM Version 4Release 1.0 System DDR.10. If you choose to provide remote execution services through use of the rexec daemon (REXECD), youmay find the need to define multiple agent virtual machines, named RXAGENT1, RXAGENT2, etc.Each RXAGENTn virtual machine you create should be defined similar to RXAGENT1, which hasbeen defined as part of the installed z/VM Version 4 Release 1.0 System DDR. However, note thatthe RXAGENTn virtual machines do not “own” any minidisks.11. To use the Secure Socket Layer (SSL) server, a suitably configured Linux kernel and file system mustbe installed on your z/VM system. Information about Linux requirements and preparing Linux for usewith the SSL server is available at the TCP/IP for z/VM home page on the World Wide Web. TheURL for this home page is:http://www.vm.ibm.com/related/tcpip/Installation Requirements and Considerations 21
Page 8 and 9: viiiTCP/IP for z/VM Program Directo
Page 10: Appendix I, “Service Instructions
Page 14 and 15: 3.0 Program SupportThis section des
Page 16 and 17: 3.3.2 Communicating Your Comments t
Page 19 and 20: 5.0 Installation Requirements and C
Page 23 and 24: you to supply an exit which is spec
Page 25 and 26: chapter titled “Configuring the S
Page 27: 5.2.4.9 Printing5.2.4.9.1 Changes I
Page 31 and 32: 5.3.1 DASD Requirements for TCP/IP
Page 33 and 34: Figure 9 (Page 3 of 5). DASD Storag
Page 35 and 36: Figure 9 (Page 5 of 5). DASD Storag
Page 37 and 38: 6.2 Installing TCP/IP for z/VMNote
Page 39 and 40: Figure 11 (Page 2 of 2). Default Us
Page 41 and 42: TCPSYSFILENotes:Non-customizable TC
Page 43 and 44: 7 Copy TCP/IP for z/VM files into p
Page 45 and 46: 6.2.3.6 Configure TCP/IP for z/VM f
Page 47 and 48: Figure 12 (Page 2 of 2). Files to C
Page 49 and 50: Figure 13 (Page 2 of 2). Files to C
Page 51 and 52: 7.0 Service InstructionsNote — z/
Page 53 and 54: 7.2 Servicing TCP/IP for z/VM7.2.1
Page 55 and 56: 3 If necessary, establish the appro
Page 57 and 58: If receiving the RSU from an envelo
Page 59 and 60: Note - $PPF ServiceIf a $PPF file h
Page 61 and 62: 7.2.2.6 Test the New ServiceAll new
Page 63 and 64: need issue the appropriate LINK and
Page 65 and 66: vmfrec ppf 4tcpip10 {tcpip | tcpips
Page 67 and 68: Note - $PPF ServiceIf a $PPF file h
Page 69 and 70: detach the 591 and 592 production m
Page 75 and 76: Use tcpip if the TCP/IP for z/VM de
Page 77 and 78: access 592 fmnetstat levelwhere fm
Page 79 and 80:
ctlg_section is the definition sect
Page 81 and 82:
The TCP2PROD $MSGLOG is cumulative,
Page 83 and 84:
►►──┬─────┬
Page 85 and 86:
A.3 TCPCMLST►►──TCPCMLST─
Page 87 and 88:
8Explanation: Errors encountered; p
Page 89 and 90:
3 If necessary, establish the appro
Page 91 and 92:
8 Make your changes to the displaye
Page 93 and 94:
minidisk. Do not continue with thes
Page 95 and 96:
Appendix D. Making Local Modificati
Page 97 and 98:
4 Create a usable PPF file.Note: Th
Page 99 and 100:
xedit fn ft-src fm-src (ctl tcpipwh
Page 101 and 102:
list changes that will accommodate
Page 103 and 104:
D.1.3.3 Create the Updated Replacem
Page 105 and 106:
Appendix E. Modifying TCP/IP for z/
Page 107 and 108:
Appendix F. TCP/IP for z/VM Build L
Page 109 and 110:
Appendix G. Moving TCP/IP for z/VM
Page 111 and 112:
4 Use the CREATE DIRECTORY command
Page 113 and 114:
2 Create (or modify as required) th
Page 115 and 116:
An example of this latter case is c
Page 117 and 118:
Appendix I. Service Instructions
Page 119 and 120:
ipl cmsput2prodThis will copy all c
Page 121 and 122:
IBM CorporationMail Station P32455
Page 123 and 124:
Reader's CommentsTCP/IP for z/VMYou
Page 126:
IBM®Program Number: 5739-A03Printe
show all

TCP/IP Level 410 Program Directory - z/VM - IBM

Create successful ePaper yourself

Delete template?

Save as template?