IBM Program Directory for Open Systems Adapter Support Facility for VM Function Level 2.2.0 Program Number 5739-A03 for Use with z/vm Version 4 Document Date: October 2001 GI10-4726-01
Note! Before using this information and the product it supports, be sure to read the general information under Notices on page 65. This program directory, dated October 2001, applies to Open Systems Adapter Support Facility for VM, Function Level 2.2.0 (OSA/SF for VM), Program Number 5739-A03. A form for reader's comments appears at the back of this publication. When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. Copyright International Business Machines Corporation 1996, 2001. All rights reserved. Note to U.S. Government Users Documentation related to restricted rights Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp.
Contents 1.0 Introduction................................................... 1 1.1 Program Description............................................... 1 2.0 Program Materials............................................... 3 2.1 Basic Machine-Readable Material....................................... 3 2.2 Optional Machine-Readable Material..................................... 3 2.3 Program Publications.............................................. 3 2.3.1 Basic Program Publications........................................ 3 2.3.2 Optional Program Publications...................................... 3 2.4 Microfiche Support................................................ 4 2.5 Publications Useful During Installation.................................... 4 3.0 Program Support................................................ 6 3.1 Preventive Service Planning.......................................... 6 3.2 Statement of Support Procedures....................................... 6 4.0 Program and Service Level Information.................................. 7 4.1 Program Level Information........................................... 7 4.2 Service Level Information............................................ 7 4.3 Cumulative Service Tape............................................ 7 5.0 Installation Requirements and Considerations.............................. 8 5.1 Hardware Requirements............................................ 8 5.2 Program Considerations............................................ 8 5.2.1 Operating System Requirements..................................... 8 5.2.2 Other Program Product Requirements.................................. 8 5.2.3 Program Installation/Service Considerations............................. 10 5.3 DASD Storage and User ID Requirements................................. 11 6.0 Installation Instructions........................................... 14 6.1 VMSES/E Installation Process Overview.................................. 14 6.2 Allocate/Review OSA/SF for VM Resources................................ 15 6.2.1 Additional Resources........................................... 15 6.2.2 CP System Directory Updates..................................... 16 6.2.3 (Optional) Changing or Moving the Default OSA/SF for VM Resources............. 16 6.3 (OPTIONAL) Set Up Security, e.g. RACF, Permits............................ 17 6.4 Update PROFILE EXEC and NAME Files................................. 18 6.5 Setting Up the GUI (OS/2 or Windows) for OSA/SF for VM....................... 21 6.5.1 Setting Up APPC on the VM Host................................... 21 6.5.2 Setting Up the Windows GUI for OSA/SF............................... 22 6.5.3 Setting Up the OS/2 GUI for OSA/SF................................. 22 6.5.4 Updating the CONFIG.SYS File on a Non-Requester Machine.................. 25 Copyright IBM Corp. 1996, 2001 iii
6.5.5 Updating a Requester Machine..................................... 26 6.5.5.1 Updating a Requester Machine Using SI............................ 26 6.5.5.2 Updating a CONFIG.SYS File on a Requester Machine.................... 29 6.5.6 Installing the OSA/SF GUI on OS/2 Without CM/2.......................... 29 6.6 Place OSA/SF for VM Into Production................................... 32 6.6.1 Copy OSA/SF for VM Files Into Production.............................. 32 7.0 Service Instructions............................................. 34 7.1 VMSES/E Service Process Overview.................................... 34 7.2 Servicing OSA/SF for VM........................................... 35 7.2.1 Prepare to Receive Service....................................... 35 7.2.2 Receive the Service........................................... 37 7.2.3 Apply the Service............................................. 38 7.2.4 Update the Build Status Table..................................... 39 7.2.5 Build Serviced Objects.......................................... 41 7.3 Place the New OSA/SF for VM Service Into Production......................... 42 7.3.1 Copy the New OSA/SF for VM Serviced Files Into Production................... 42 7.3.2 Copy the New OSA/SF for VM GUI Serviced Files Into Production................ 42 7.3.3 Service the Windows GUI for OSA/SF................................. 42 7.3.4 Service OS/2 GUI for OSA/SF..................................... 43 7.3.4.1 Finding Out What the Current Level Is.............................. 45 7.3.5 Place Serviced Sample Files Into Production............................. 46 Appendix A. Applying an RSU Tape for OSA/SF for VM......................... 47 A.1 Apply OSA/SF for VM RSU......................................... 48 A.1.1 Prepare Your System for Service Refresh.............................. 48 A.1.2 Receive the Preapplied, Prebuilt Service............................... 50 A.1.3 Process Additional Service....................................... 52 A.1.4 Build the New Service Level and Place Into Production...................... 53 A.2 Determine RSU Service Level........................................ 53 Appendix B. Restoring Preceding Level and Deleting OSA/SF GUI Files............... 54 B.1 Restoring the Preceding Level........................................ 54 B.2 Deleting the OSA/SF GUI Files....................................... 54 Appendix C. Moving OSA/SF for VM to SFS Directories and Creating PPF Override........ 56 C.1 Setup SFS File Pool and Directories.................................... 57 C.2 Copy Minidisk (or SFS) Files to SFS Directories............................. 59 C.3 Create Product Parameter File (PPF) Override.............................. 59 Appendix D. z/vm Express Users Only Service Instructions..................... 62 Notices........................................................ 65 Trademarks and Service Marks.......................................... 66 Reader's Comments................................................ 67 iv OSA/SF for VM Program Directory
Figures 1. Optional Material: Program Publications - Not New Editions...................... 4 2. Publications Useful During Installation / Service on z/vm Version 4................. 4 3. PSP Upgrade and Subset ID........................................ 6 4. Component IDs............................................... 6 5. DASD Storage Requirements for Target Minidisks........................... 12 Figures v
vi OSA/SF for VM Program Directory
1.0 Introduction This program directory is intended for the system programmer responsible for program installation and maintenance. It contains information concerning the material and procedures associated with the installation of OSA/SF for VM. You should read all of this program directory before installing the program and then keep it for future reference. The program directory contains the following sections: 2.0, Program Materials on page 3 identifies the basic and optional program materials and documentation for OSA/SF for VM. 3.0, Program Support on page 6 describes the IBM support available for OSA/SF for VM. 4.0, Program and Service Level Information on page 7 lists the APARs (program level) and PTFs (service level) incorporated into OSA/SF for VM. 5.0, Installation Requirements and Considerations on page 8 identifies the resources and considerations for installing and using OSA/SF for VM. 6.0, Installation Instructions on page 14 provides detailed installation instructions for OSA/SF for VM. 7.0, Service Instructions on page 34 provides detailed servicing instructions for OSA/SF for VM. Appendix A, Applying an RSU Tape for OSA/SF for VM on page 47 provides detailed Recommended Service Upgrade instructions for OSA/SF for VM. Appendix B, Restoring Preceding Level and Deleting OSA/SF GUI Files on page 54 provides information on restoring and deleting OSA/SF for VM graphical user interface (GUI) files. Appendix C, Moving OSA/SF for VM to SFS Directories and Creating PPF Override on page 56 describes how to move OSA/SF for VM into SFS and how to create a Product Parameter File (PPF) override. Appendix D, z/vm Express Users Only Service Instructions on page 62 provides detailed servicing (RSU and COR) instructions for z/vm Express Users for OSA/SF for VM. Before installing OSA/SF for VM, read 3.1, Preventive Service Planning on page 6. This section tells you how to find any updates to the information and procedures in this program directory. 1.1 Program Description Open Systems Adapter Support Facility for VM lets one customize the integrated Open Systems Adapter (OSA) hardware feature for the OSA modes, change the settable OSA port parameters, and obtain status about the OSA. OSA/SF for VM has an Operating System/2 (OS/2) interface, which is called the OSA/SF graphical user interface (OSA/SF GUI). Copyright IBM Corp. 1996, 2001 1
Through the System Authorization Facility (SAF) interface of the system image on which it is running, OSA/SF lets you use the Resource Access Control Facility (RACF ), or equivalent, to authorize or deny access to OSA/SF commands. 2 OSA/SF for VM Program Directory
2.0 Program Materials An IBM program is identified by a program number. The program number for Open Systems Adapter Support Facility for VM, Function Level 2.2.0 is 5739-A03. The program announcement material describes the features supported by OSA/SF for VM. Ask your IBM marketing representative for this information if you have not already received a copy. The following sections identify: basic and optional program materials available with this program publications useful during installation. 2.1 Basic Machine-Readable Material 1 Open Systems Adapter Support Facility for VM is distributed pre-installed on the z/vm Version 4 System 1 DDRs. Refer to the applicable z/vm Version 4 Software Annoucement for information on ordering z/vm 1 Version 4 and its features. 2.2 Optional Machine-Readable Material There are no optional machine-readable materials for OSA/SF for VM. 2.3 Program Publications The following sections identify the basic and optional publications for OSA/SF for VM. 2.3.1 Basic Program Publications There are no basic program publications that come with z/vm for OSA/SF for VM. 2.3.2 Optional Program Publications Figure 1 on page 4 identifies the optional program publications for OSA/SF for VM. The publications are available on the VM Collection kit CD-ROM in BookManager and Adobe Protable Document Format (PDF). One copy of the VM collection kit CD-ROM is included when you order the basic materials for z/vm Version 4. The OSA/SF publications can also be found in Adobe Portable Document Format off of the z/vm home page: http://www.ibm.com/eserver/zseries/zvm Copyright IBM Corp. 1996, 2001 3
They can be ordered separately for a fee using the specific publication number through the IBM Publication Center at : http://www.ibm.com/shop/publications/order The Publications Center is a world wide central repository for IBM product publications and marketing material. Furthermore, a large number of publications are available online in various file formats (e.g. Adobe PDF), which can currently be downloaded free of charge. Figure 1. Optional Material: Program Publications - Not New Editions Publication Title Planning for the System/390 Open Systems Adapter Feature VM/ESA: Open Systems Adapter Support Facility User's Guide S/390: Open Systems Adapter-Express Customer's Guide and Reference Form Number GC23-3870 SC28-1992 SA22-7403 1 zseries 900: Planning for Open Systems Adapter-2 Feature GA22-7477 1 zseries 900: Open Systems Adapter-Express Customer's Guide and Reference SA22-7476 2.4 Microfiche Support There is no microfiche for OSA/SF for VM. 2.5 Publications Useful During Installation The publications listed in Figure 2 may be useful during the installation of OSA/SF for VM. To order copies, contact your IBM representative. Figure 2. Publications Useful During Installation / Service on z/vm Version 4 Publication Title z/vm: VMSES/E Introduction and Reference z/vm: Service Guide z/vm: Planning and Administration z/vm: CMS Command and Utility Reference z/vm: CMS File Pool Planning, Administration, and Operation z/vm: System Messages and Codes Other z/vm: System Messages and Codes CMS z/vm: System Messages and Codes CP z/vm: Installation Guide Form Number GC24-5994 GC24-5993 SC24-5995 SC24-6010 SC24-5949 GC24-6032 GC24-6031 GC24-6030 GC24-5992 4 OSA/SF for VM Program Directory
Notes: 1. The OSA/SF for VM GUI (graphical user interface) provides online help. 2. You can also refer to the Redbook titled OSA-2 Implementation Guide, SG24-4470. Program Materials 5
3.0 Program Support This section describes the IBM support available for OSA/SF for VM. 3.1 Preventive Service Planning Before installing OSA/SF for VM, check with your IBM Support Center or use IBMLink (Service Link) to see whether there is additional Preventive Service Planning (PSP) information. To obtain this information, specify the following UPGRADE and SUBSET values: Figure 3. PSP Upgrade and Subset ID COMPID RETAIN Release Upgrade Subset 565510400 220 VMOSASF220 OSASF 565510400 220 VMOSASF220 yynnrsu 565510400 220 VMOSASF220 RSU-BY-LVL 565510400 220 VMOSASF220 RSU-BY-APAR 565510400 220 VMOSASF220 RSU-BY-PTF RSU-BY-LVL information can also be obtained from the z/vm serivce RSU web site at url: http://www.ibm.com/eserver/zseries/zvm/service/rsu 3.2 Statement of Support Procedures Note: With Open Systems Adapter Support Facility for VM you are entitled to support under the basic 1 warranty for z/vm Version 4. To receive zseries service that you are accustomed to, IBM highly 1 recommends ordering the z/vm Software Subscription and Support, 5739-SWS. Refer to the applicable 1 z/vm V4 Software Announcement for ordering information. Report any difficulties you have using this program to your IBM Support Center. If an APAR is required, the Support Center will provide the address to which any needed documentation can be sent. Figure 4 identifies the component ID (COMPID), RETAIN Release and Field Engineering Service Number (FESN) for OSA/SF for VM. Figure 4. Component IDs COMPID RETAIN Release Component Name FESN 565510400 220 OSA/SF for VM 2.2.0 0401298 6 Copyright IBM Corp. 1996, 2001
4.0 Program and Service Level Information This section identifies the program and any relevant service levels of OSA/SF for VM. The program level refers to the APAR fixes incorporated into the program. The service level refers to the PTFs shipped with this product. Information about the cumulative service tape is also provided. Note: If you have access to the IBM Problem Solving Database, APARs/PTFs, (for example through the SIS function in ServiceLink or from the S/390 Software Support web page) be aware that you need to have your search look in the MVS Library or S/390 Operating Systems product. The reason VM OSA/SF is in the MVS library is to allow an OSA/SF APAR to be shared across different platforms. 4.1 Program Level Information No APARs have been incorporated into OSA/SF for VM. 4.2 Service Level Information After the installation of the z/vm System DDRs, OSA/SF for VM is at Service Level RSU 0101. If you received an RSU with your z/vm System DDRs and you installed it, then OSA/SF for VM will be at that RSU level. Check the VMOSASF220 PSP bucket for any additional PTFs that should be installed or any additional install information. 4.3 Cumulative Service Tape Cumulative service for OSA/SF for VM Function Level 2.2.0 is available through a periodic Recommended Service Upgrade (RSU) tape. See upgrade bucket VMOSASF220 subset yynnrsu (where yynn is the RSU service level) for the latest RSU level available. For the list of PTF's included on the RSU tape, see the service memo from the tape or the PSP subsets sorted by PTF, APAR or RSU level (LVL). 1 The RSU can be ordered using the PTF number UM974n0; where n indicates the release of z/vm Version 1 4. This is a stacked RSU. It will contain service for all of the components, features or products, in VMSES/E format, that are pre-installed on the z/vm V4 System DDR. (Non-Express z/vm installations can still use the individual OSA RSU, PTF number UW99220 (APAR OW31407) or the new stacked RSU.) Copyright IBM Corp. 1996, 2001 7
5.0 Installation Requirements and Considerations The following sections identify the system requirements for installing and activating OSA/SF for VM. 5.1 Hardware Requirements Please refer to the Planning for the System/390 Open Systems Adapter Feature manual for more information on the hardware requirements needed on the host and workstation. 5.2 Program Considerations The following sections list the programming considerations for installing OSA/SF for VM and activating its functions. Note: The OSA/SF for VM deliverable with z/vm V4 is the same as with z/vm 3.1.0 or VM/ESA 2.2.0 or higher. In the following you need to use the release of the product requirement that is applicable to the operating system you are using. 5.2.1 Operating System Requirements OSA/SF for VM supports the following VM operating systems: 1 z/vm Version 4 5.2.2 Other Program Product Requirements OSA/SF for VM has the following minimum requisite: z/vm Version 4 Release 1.0 (which has IBM Language Environment for VM 1.8 pre-installed) If the OSA/SF for VM OS/2 or GUI interface is to be used then you also need the following requisites: IBM OS/2 3.0 or higher One of the following communications protocols: TCP/IP, which requires Transmission Control Program/Internet Protocol (TCP/IP) Version 3 Release 1 for VM (5735-FAL) or higher on the host and TCP/IP 2.0 or higher for OS/2 on the workstation. EHLLAPI (3270), which requires ACF/VTAM Version 4 Release 2 for VM/ESA and the 3270 PC File Transfer Program (5664-281) on the host plus Communications Manager/2 Version 1 Release 11 or Personal Communications 4.1, with the PTF for APAR IC14272, at the workstation. Note: The following ACF/VTAM Version 4 Release 2 APARs should be applied: - VM59237 (OSA emulating LCS VM/ESA) 8 Copyright IBM Corp. 1996, 2001
- VM60877 (OSA emulating LCS VM/ESA additional stations support - VM60853 (I/O errors) APPC, or CPI-C, which requires ACF/VTAM Version 4 Release 2 for VM/ESA on the host, plus Communications Manager/2 Version 1 Release 11 or Personal Communications 4.1, with the PTF for APAR IC14272, at the workstation. Note: The following ACF/VTAM Version 4 Release 2 APARs should be applied: - VM59237 (OSA emulating LCS VM/ESA) - VM60877 (OSA emulating LCS VM/ESA additional stations support - VM60853 (I/O errors) If the OSA/SF for VM OS/2-J GUI interface is to be used then you also need the following requisites: PTF resolution to OSA/SF for VM APAR OW28838 IBM OS/2-J 3.0 WARP or higher One of the following communications protocols: TCP/IP, which requires Transmission Control Program/Internet Protocol (TCP/IP) Version 3 Release 1 for VM (5735-FAL) or higher on the host and TCP/IP 2.0 or higher for OS/2 on the workstation. EHLLAPI (3270), which requires ACF/VTAM Version 4 Release 2 for VM/ESA and the 3270 PC File Transfer Program (5664-281) on the host plus Communications Manager/2-J Version 1 Release 11 or Personal Communications 4.1, with the PTF for APAR IC14272, at the workstation. Note: The following ACF/VTAM Version 4 Release 2 APARs should be applied: - VM59237 (OSA emulating LCS VM/ESA) - VM60877 (OSA emulating LCS VM/ESA additional stations support - VM60853 (I/O errors) APPC, or CPI-C, which requires ACF/VTAM Version 4 Release 2 for VM/ESA on the host, plus Communications Manager/2-J 1.11 or Personal Communications 4.1, with the PTF for APAR IC14272, at the workstation. If the OSA/SF for VM Windows GUI interface is to be used then you also need the following requisites: PTF resolution to OSA/SF for VM APAR OW36927 Windows 95 or higher or Windows NT One of the following communications protocols: TCP/IP, which requires TCP/IP 2.0 for OS/2 on the workstation EHLLAPI (3270), which requires the 3270 PC File Transfer Program FTP (5665-311) on the host plus Personal Communications/3270 4.3 or higher or Communications Manager/2 1.11 at the workstation. APPC, or CPI-C, which requires Personal Communications/3270 4.1, with the PTF for APAR IC14272 or Communications Manager/2 1.11 at the workstation. Installation Requirements and Considerations 9
To run HPDT ATM Native mode you need: PTF resolution to OSA/SF for VM APAR OW36927 z/vm V4 TCP/IP (which comes with z/vm) The following product is optional and may be helpful in running OSA/SF for VM: RACF Version 1 Release 9.2 (5740-XXH) or higher to provide access control for OSA/SF for VM commands. 5.2.3 Program Installation/Service Considerations This section describes items that should be considered before you install or service OSA/SF for VM. The Planning for the System/390 Open Systems Adapter Feature manual should be reviewed before installing OSA/SF for VM. VMSES/E is required to install and service this product. OSA/SF for VM is pre-installed on the z/vm Version 4 System DDRs. It is optionally installable at z/vm initial install time for non-express z/vm installations. Therefore, if you did not choose to install OSA/SF for VM at z/vm initial installation you can still install it off of the z/vm System DDRs by following the instructions in the z/vm Installation Guide, Appendix "Post Install Load of Optional Items". If multiple users install and maintain licensed products on your system, there may be a problem getting the necessary access to MAINT's 51D disk. If you find that there is contention for write access to the 51D disk, you can eliminate it by converting the Software Inventory from minidisk to Shared File System (SFS). See the VMSES/E Introduction and Reference manual, section 'Changing the Software Inventory to an SFS Directory', for information on how to make this change. Caution - z/vm Express Users If you installed VM using the z/vm Express Procedure than you should not do any of the things stated in the next two bullets. If you do, then you will not be able to use the VMSES/E SERVICE and PUT2PROD commands. Customers will no longer install and service OSA/SF for VM strictly using the MAINT user ID, but will use a new user ID--2VMVMV20. This is the IBM suggested user ID name. You are free to change this to any user ID name you wish; however, a PPF override must be created. Refer to C.3, Create Product Parameter File (PPF) Override on page 59 and the VMSES/E Introduction and Reference manual for information on creating a PPF override. If you choose to move OSA/SF for VM from minidisk to SFS (Shared File System), if you did not do it at initial z/vm DDR install time, or if you want to change from the default SFS file pool or directories, then you will need to follow the steps in Appendix C, Moving OSA/SF for VM to SFS Directories and 10 OSA/SF for VM Program Directory
Creating PPF Override on page 56, as pointed to in the 6.2, Allocate/Review OSA/SF for VM Resources on page 15 section in the installation chapter of this program directory. These steps will have you create the SFS directories, move the files to the SFS directories and create a PPF override. RSU tapes will be supplied as necessary. Service between RSU tapes can be obtained through CORrective service. 5.3 DASD Storage and User ID Requirements Figure 5 lists the user IDs and minidisks that are used to install and service OSA/SF for VM. Important Installation Notes: Important information on setting up the 70cc minidisks for each processor type can be found in the Planning for the System/390 Open Systems Adapter Feature manual. You should review this manual before performing the installation step 6.2, Allocate/Review OSA/SF for VM Resources on page 15. User ID(s) and minidisks shown in Figure 5 are already defined after you install OSA/SF for VM from the z/vm System DDR. The exception to this is the OSASF user ID's 70cc minidisks. Those minidisks still need to be defined. 2VMVMV20 is a default user ID and can be changed. Also the administrator ID's, OSADMINx, and the server machine, OSASF, can be any user ID. If you choose to change any of these user IDs you need to create a Product Parameter Override (PPF) to reflect this change. Refer to C.3, Create Product Parameter File (PPF) Override on page 59 and the VMSES/E Introduction and Reference manual for information on creating a PPF override. (This bullet applies only to Z/VM Non-Express users.) The OSASF user ID needs to run with a LDRTBLS value of 6 or higher. You need to make sure that the OSASF PROFILE EXEC sets LDRTBLS to 6 or higher. The OSAMAINT user ID SHOULD NOT be changed. OSA/SF for VM requires that a user ID of OSAMAINT exist. If you choose to install OSA/SF for VM on a common user ID the default minidisk addresses for OSA/SF for VM may already be defined. If any of the default minidisks required by OSA/SF for VM are already in use you will have to create a PPF override to change the default minidisks for OSA/SF for VM so they are unique. The storage requirements for some minidisks may be revised over time, which may require existing minidisk sizes to be increased. The minidisks changes will be indicated in updated levels of this document by revision characters in the left margin of Figure 5. Some minidisk storage requirement changes will need to be accessed locally, for your specific environment. For example, the capacity of the DELTA minidisk (2VMVMV20 2D2, by default), periodically may need to be increased, based on the specific preventive and corrective service applied to your system. An updated version of this document will show the size of the minidisk as shipped on the latest z/vm System DDRs. Installation Requirements and Considerations 11
Figure 5 (Page 1 of 2). DASD Storage Requirements for Target Minidisks Minidisk owner (user ID) Default Address 2VMVMV20 2B2 3390 3380 9345 2VMVMV20 2C2 3390 3380 9345 2VMVMV20 2D2 3390 3380 9345 2VMVMV20 2A6 3390 3380 9345 2VMVMV20 2A2 3390 3380 9345 2VMVMV20 100 3390 3380 9345 2VMVMV20 300 3390 3380 9345 2VMVMV20 7F00 3390 3380 9345 2VMVMV20 191 3390 3380 9345 Storage in Cylinders FB-512 SFS 4K Usage DASD CYLS Blocks Blocks Default SFS Directory Name 15 18 18 4 4 4 200 240 240 5 6 6 5 6 6 50 60 60 23 27 27 10 12 12 10 12 12 21600 2700 Contains all the base code shipped with OSA/SF for VM. VMSYS:2VMVMV20.OSA.OBJECT 4800 600 Contains customization files. This disk also will be used for local modifications. VMSYS:2VMVMV20.OSA.SAMPLE 288000 36000 Contains serviced files. VMSYS:2VMVMV20.OSA.DELTA 7200 900 Contains AUX files and software inventory tables that represent the test service level of OSA/SF for VM. VMSYS:2VMVMV20.OSA.APPLYALT 7200 900 Contains AUX files and software inventory tables that represent the service level of OSA/SF for VM that is currently in production. VMSYS:2VMVMV20.OSA.APPLYPROD 72000 9000 Test build disk. This disk will be copied to OSA/SF for VM's production code build disk. VMSYS:2VMVMV20.OSA.TBLDCODE 32400 4050 Test build IMAGE file disk. This disk will be copied to OSA/SF for VM's IMAGE production build disk. VMSYS:2VMVMV20.OSA.TBLDIMAGE 14499 NOSFS Test build common LPAR disk. This disk will be copied to OSA/SF for VM's common LPAR production build disk. This disk MUST be address 7F00. 14400 1800 2VMVMV20 user ID's 191 minidisk. VMSYS:2VMVMV20. Notes: 1. Cylinder values defined in this table are based on a 4K block size. 2. FB-512 block and SFS values are derived from the 3380 cylinder values in this table. The FBA blocks are listed as 1/2K but should be CMS formatted at 1K size. 3. A total 68100 SFS 4K blocks are needed for the addresses that can be defined in SFS for an SFS install. 12 OSA/SF for VM Program Directory
Figure 5 (Page 2 of 2). DASD Storage Requirements for Target Minidisks Minidisk owner (user ID) Default Address OSASF 200 3390 3380 9345 OSASF 400 3390 3380 9345 OSASF 70cc 3390 3380 9345 OSASF 191 3390 3380 9345 OSAMAINT 7F00 3390 3380 9345 OSAMAINT 191 3390 3380 9345 OSADMIN1 191 3390 3380 9345 OSADMIN2 191 3390 3380 9345 OSADMIN3 191 3390 3380 9345 Storage in Cylinders FB-512 SFS 4K Usage DASD CYLS Blocks Blocks Default SFS Directory Name 50 60 60 23 27 27 5 6 6 10 12 12 10 12 12 10 12 12 10 12 12 10 12 12 10 12 12 72000 9000 Production build disk. Contains OSA/SF for VM's executable code. VMSYS:2VMVMV20.OSA.PBLDCODE 32400 4050 OSA/SF for VM's IMAGE file production build disk. VMSYS:2VMVMV20.OSA.PBLDIMAGE 7200 NOSFS Set of minidisks that correspond to each OSA-2 CHPID being used. (cc = OSA-2 CHPID) 14400 NOSFS OSASF user ID's 191 minidisk. 14400 NOSFS OSA/SF for VM's common LPAR production build disk. This disk MUST be address 7F00. 14400 NOSFS OSAMAINT user ID's 191 minidisk. 14400 NOSFS OSADMIN1 user ID's 191 minidisk. 14400 NOSFS OSADMIN2 user ID's 191 minidisk. 14400 NOSFS OSADMIN3 user ID's 191 minidisk. Notes: 1. Cylinder values defined in this table are based on a 4K block size. 2. FB-512 block and SFS values are derived from the 3380 cylinder values in this table. The FBA blocks are listed as 1/2K but should be CMS formatted at 1K size. 3. A total 68100 SFS 4K blocks are needed for the addresses that can be defined in SFS for an SFS install. Installation Requirements and Considerations 13
6.0 Installation Instructions This chapter describes the installation methods and the step-by-step procedures to complete the installation and activation of OSA/SF for VM. If you plan on using OSA/SF for VM then you NEED TO FINISH THE INSTALLATION as documented in this chapter. OSA/SF for VM is pre-installed, using VMSES/E, on the z/vm System DDRs. For non-express z/vm Installations, OSA is optionally installable at initial z/vm DDR install time. This chapter assumes that OSA/SF for VM was installed during initial installation of z/vm. If you did not choose to install OSA/SF for VM at z/vm install time you can do so at this time. Follow the instructions in the z/vm Installation Guide, Appendix "Post Install Load of Optional Items" and then return back to here to complete the OSA/SF for VM installation. The step-by-step procedures are in two column format. The steps to be performed are in bold large numbers. Commands for these steps are on the left hand side of the page in bold print. Additional information for a command may exist to the right of the command. For more information about the two column format see 'Understanding Dialogs with the System' in the z/vm Installation Guide. Each step of the installation instructions must be followed. Do not skip any step unless directed to do so. Throughout these instructions, the use of IBM-supplied default minidisk addresses and user IDs is assumed. If you use different user IDs, minidisk addresses, or SFS directories to install OSA/SF for VM, adapt these instructions as needed for your environment. Note The sample console output presented throughout these instructions was produced on a z/vm system. 6.1 VMSES/E Installation Process Overview The following is a brief description of the main steps to complete the installation of OSA/SF for VM using VMSES/E. Allocate Resources Some resources still need to be allocated for OSA/SF for VM. Other resources need to be reviewed to see if any changes are needed for your installation. Perform Post-installation Tasks 14 Copyright IBM Corp. 1996, 2001
Information about file tailoring and initial activation of the program is presented in 6.4, Update PROFILE EXEC and NAME Files on page 18 through 6.5, Setting Up the GUI (OS/2 or Windows) for OSA/SF for VM on page 21. Place OSA/SF for VM Files into Production Once the product files have been tailored and the operation of OSA/SF for VM is satisfactory, the product files are copied from the test BUILD disk(s) to production BUILD disk(s). 6.2 Allocate/Review OSA/SF for VM Resources OSA/SF for VM has been installed on the z/vm System DDRs using VMSES/E. This means that several of the VMSES/E installation steps have been performed on your behalf. Among these are the: addition of the OSA/SF for VM installation user ID, 2VMVMV20, entry to the VM CP system directory addition of the OSASF, OSAMAINT, OSADMIN1, OSADMIN2, and OSADMIN3 user ID entries to the VM CP system directory creation of the 2VMVMV20 user ID PROFILE EXEC. This PROFILE EXEC contains the accesses to the VMSES/E code disk, MAINT 5E5, and the VMSES/E Software Inventory disk, MAINT 51D. allocation of most of the OSA/SF for VM minidisks (or SFS subdirectories) loading of the OSA/SF for VM product files to the minidisks (or SFS subdirectories), using VMSES/E commands installation of the OSA/SF for VM RSU; if one available There are still some additional resources that need to be defined. There are also some other resources that may need to be changed or defined, depending on your installation environment. The following sections talk about these resources. 6.2.1 Additional Resources The following resources need to be defined. 1 You need to add the appropriate 70cc minidisk addresses to the OSASF user ID. You need to have a 70cc minidisk address to correspond to each OSA-2 CHPID utilized in the specified processor (cc = OSA-2 CHPID). Refer to Figure 5 on page 11 for the size of the 70cc minidisks. Notes: a. Important information on setting up the 70cc minidisks for each processor type can be found in the Planning for the System/390 Open Systems Adapter Feature manual. You should review this manual to help you to set up the 70cc minidisks in this step. b. If the OSA-2 channel path is defined as being shared among logical Installation Instructions 15
partitions, the minidisks should be defined on Cross System Extensions (CSE) DASD. c. You must format the 70cc minidisks before you continue the installation of OSA/SF for VM. 6.2.2 CP System Directory Updates Depending on your system environment there may be some other CP directory changes that need to be made for the OSA/SF for VM user IDs. Note: If you make any of the following changes do not forget to place the new CP directory online. 1 If the administrator user ID, OSADMINx, is going to be used as a server for TCP/IP connectivity then the user ID has to have a privilege class of B. 1 2 If using any security product, that makes use of the RACROUTE interface, 1 e.g. RACF, then you must add the following statement to the CP directory for the OSASF user ID and for any administrator user ID, OSADMINx, that will have a TCP/IP connection. IUCV ANY PRIORITY MSGLIMIT 255 1 If you want to limit the communications authorization to only the security 1 product, e.g. RACF, service virtual machine, replace the 'ANY' operand with the user ID of the security, e.g. RACF, service virtual machine (e.g., RACFVM). 3 If necessary, change the passwords for the 2VMVMV20, OSASF, OSAMAINT, OSADMIN1, OSADMIN2 and OSADMIN3 user IDs from the default passwords to a valid password, in accordance with your security guidelines. Where to Next - z/vm Express Users Only Continue with 6.3, (OPTIONAL) Set Up Security, e.g. RACF, Permits on page 17 in this program directory. 6.2.3 (Optional) Changing or Moving the Default OSA/SF for VM Resources If you want to change any of the default OSA/SF for VM user IDs, minidisks or SFS directories you should do so at this time. In order to do this you will need to create an override to the Product Parameter File (PPF). If you want to use SFS for OSA/SF for VM, because you did not choose it during initial installation of z/vm, you will have to create the SFS directories, move the code to those directories and reflect these new directories in a PPF override. 16 OSA/SF for VM Program Directory
Refer to Appendix C, Moving OSA/SF for VM to SFS Directories and Creating PPF Override on page 56 for instructions on moving OSA/SF for VM into SFS and creating a PPF override. 6.3 (OPTIONAL) Set Up Security, e.g. RACF, Permits 1 OSA/SF for VM communicates with a security product using the RACROUTE interface. 1 If you are using a security product, e.g. RACF, then you need to set up the permits to the test build disks 1 of 2VMVMV20 to the administrator (OSADMINx) user IDs. 1 Note: If you are not using the RACF security product, but a different one that uses the RACROUTE 1 interface, then refer to that product's documentaion to accomplish the equivalent RACF steps below. Otherwise continue with 6.4, Update PROFILE EXEC and NAME Files on page 18. 1 Logon to the installation user ID 2VMVMV20. Note: This user ID must be authorized to issue RAC commands. 2 Issue the RACF permit command to give read access to all of the OSADMINx user IDs to 2VMVMV20's product test build disk (100). racfperm Fill in the panels to give read access to all of the OSADMINx user IDs to 2VMVMV20's product test build disk (100). rac rdefine facility ichconn uacc(none) 3 Define a profile named ICHCONN in class FACILITY (if it does not already exist). 4 Give UPDATE authority to ICHCONN in the FACILITY class to OSASF. rac permit ichconn class(facility) id(osasf) access(update) rac setropts classact(facility) 5 Activate the FACILITY class (if it is not already active). Installation Instructions 17
6.4 Update PROFILE EXEC and NAME Files The PROFILE EXEC and NAME files for each of the OSA/SF for VM server and administration user IDs need to be set up. 1 Logon to the installation user ID 2VMVMV20. 2 Copy sample profile exec and names file to OSASF's 191 A-disk. a If using minidisks access 2C2 e access 291 f copyfile ioaosasf sampprof e profile exec f (olddate replace copyfile $server$ sampname e = names f (olddate replace b If using SFS access vmsys:2vmvmv20.osa.sample e access 291 f copyfile ioaosasf sampprof e profile exec f (olddate replace copyfile $server$ sampname e = names f (olddate replace If you are not using the default SFS names then substitute your SFS name in the access command. 3 Update the PROFILE EXEC on OSASF's 191 A-disk. Make any updates to reflect: Set the loader tables to 6 or higher (SET LDRTBLS 6). If you have changed any of the minidisk addresses for the OSA/SF for VM production build disks or are using SFS for those disks, you need to change the addresses in the corresponding 'ACC' or access statements. Set up any link and accesses to your own tools disks. If you do not have a MAINT 19A then you need to change that or remove that statement. Remove command lines or information in command lines for products you are not using. For example if you are not using TCP/IP then remove the 'EXEC VMLINK TCPIP <592 H>' statement. Also remove COMMTXT from the GLOBAL TXTLIB command. Set up correct location of disks for products that you are using. For example change the information in the 'EXEC VMLINK TCPIP <592 H>' statement or change the whole statement to use LINK and ACCESS, if you do not use VMLINK. 18 OSA/SF for VM Program Directory
1 If a security product, e.g. RACF, is not being used, remove the RPIUCMS 1 INIT command. 4 For the server virtual machine (OSASF), a names file called $SERVER$ NAMES is needed. This is needed for APPC communications. The default names file is shipped with the following entry in it. You can update this names file to use any nickname but the nickname you choose also needs to be used on the :tpn. statement in the UCOMDIR names file that is on the administrator user IDs A-disk. :nick.ioaserv :list.osadmin1 OSADMIN2 OSADMIN3 :module.ioacmain 5 Copy sample profile exec and names file to all the administrator user ID's 191 A-disk. a Copy profile exec and names file to first administrator user ID, OSADMIN1. access 491 f copyfile ioaadmin sampprof e profile exec f (olddate replace copyfile ucomdir sampname e = names f (olddate replace b Update the PROFILE EXEC on OSADMIN1's 191 A-disk. Make any updates to reflect: If you have changed any of the minidisk addresses for the OSA/SF for VM production build disks or are using SFS for those disks, you need to change the addresses in the corresponding 'ACC' or access statements. Set up any link and accesses to your own tools disks. If you do not have a MAINT 19A then you need to change that or remove that statement. Remove command lines or information in command lines for products you are not using. For example if you are not using TCP/IP then remove the 'EXEC VMLINK TCPIP <592 H>' statement. Also remove COMMTXT from the GLOBAL TXTLIB command. Set up correct location of disks for products that you are using. For example change the information in the 'EXEC VMLINK TCPIP <592 H>' statement or change the whole statement to use LINK and ACCESS, if you do not use VMLINK. Installation Instructions 19
1 If a security product, e.g. RACF, is not being used, remove the 1 RPIUCMS INIT command. access 591 k copyfile profile exec f = = k (olddate replace copyfile ucomdir names f = = k (olddate replace access 691 k copyfile profile exec f = = k (olddate replace copyfile ucomdir names f = = k (olddate replace c Copy profile exec and names file to second, OSADMIN2 and third, OSADMIN3, administration user IDs 191 A-disks. 6 For the requestor virtual machines, OSADMIN1 through OSADMIN3, a names file called UCOMDIR NAMES is needed. This is needed for APPC communications. The default names file is shipped with the following entry in it. If you changed the nickname in the $SERVER$ NAMES file, in a previous step, then you need to update the :tpn. statement in the UCOMDIR NAMES file to reflect the change. :nick.ioaservr :luname. USERID OSASF :tpn.ioaserv Notes: a. *USERID is a keyword. Type it exactly as shown. Do not substitute a userid in its place. OSASF is a variable and can be changed if you used a User ID other than OSASF. b. In an ISFC environment, where different OSA devices are installed on individual systems, the OSASF server for each real system needs to be identified uniquely. The OSASF user ID in each CP directory needs to be changed to a unique name. The UCOMDIR NAMES file on each OSADMINx user ID needs to reflect the new user ID for the OSASF server in the :luname field. :nick.ioaservr :luname. USERID newname :tpn.ioaserv 7 Copy sample profile exec to OSAMAINT's 191 A-disk. access 391 f copyfile ioamaint sampprof e profile exec f (olddate replace 8 Update the PROFILE EXEC on OSAMAINT's 191 A-disk. Make any updates to reflect: 20 OSA/SF for VM Program Directory
Setting Up APPC If you have changed any of the minidisk addresses for the OSA/SF for VM production build disks or are using SFS for those disks, you need to change the addresses in the corresponding 'ACC' or access statements. Remove command lines or information in command lines for products you are not using. For example if you are not using TCP/IP then remove the 'EXEC VMLINK TCPIP <592 H>' statement. Set up correct location of disks for products that you are using. For example change the information in the 'EXEC VMLINK TCPIP <592 H>' statement or change the whole statement to use LINK and ACCESS, if you do not use VMLINK. Set up any link and accesses to your own tools disks. If you do not have a MAINT 19A then you need to change that or remove that statement. 9 Logoff of the installation user ID 2VMVMV20. 6.5 Setting Up the GUI (OS/2 or Windows) for OSA/SF for VM The OSA/SF for VM GUI files need to be downloaded and installed on the workstation. The GUI files are applicable for OS/2 or for Windows, with APAR OW36927 applied. 6.5.1 Setting Up APPC on the VM Host APPC is used to pass commands from the requestor virtual machine (OSA administrator) to the server virtual machine and to send the results back. The requestor ID and the server ID must be in the same VM system (logical partition). The set up for the APPC communications should have been done in previous install steps. They incorporated: Having the IUCV ALLOW statement in the CP directory entry for the server virtual machine (default user ID OSASF). The sample directory in the PLANINFO file has this statement in it. Having the $SERVER$ NAMES file set up under the server (OSASF) virtual machine. Having the UCOMDIR NAMES files set up under the administrator (OSADMINx) user IDs. Installation Instructions 21
Setting Up the OS/2 GUI for OSA/SF Where to next Continue with 6.5.2, Setting Up the Windows GUI for OSA/SF on page 22 if you are using Windows, and have the Windows support APAR, OW36927, applied or with 6.5.3, Setting Up the OS/2 GUI for OSA/SF on page 22 if you are using OS/2. 6.5.2 Setting Up the Windows GUI for OSA/SF Use the following instructions to download and install the OSA/SF GUI files from the host to a workstation using Windows. Note: APAR OW36927 needs to be applied in order to set up the GUI interface using Windows. 1 Transfer, in binary, the installation program, IOAWINST BIN from the host to a temporary directory of your choice on the workstation. Use any host to workstation transfer program. The file should be IOAWINST.EXE on the workstation. You will need to remember the name of the temporary directory. You will be prompted for a user data path when you start the OSA/SF Windows GUI for the first time. 2 Start IOAWINST.EXE, either by double-clicking the IOAWINST object in Windows Explorer, or by entering IOAWINST at a command prompt. Follow the prompts. 3 Continue with 6.6, Place OSA/SF for VM Into Production on page 32 to complete the install of OSA/SF for VM. 6.5.3 Setting Up the OS/2 GUI for OSA/SF This section provides instructions for downloading and installing the OSA/SF GUI files from the host to OS/2 on the workstation. Note If you do not have Communications Manager/2 installed or if the RECEIVE command does not work, go to 6.5.6, Installing the OSA/SF GUI on OS/2 Without CM/2 on page 29. The instructions in this section will use the RECEIVE command to download files from the host to the workstation. Use the following instructions to download and install the OSA/SF GUI files from the host to an OS/2 workstation. The instructions include steps to: Download an installation tool referred to as the Software Installer (SI/2) 22 OSA/SF for VM Program Directory
Setting Up the OS/2 GUI for OSA/SF Use Software Installer to download and install the OSA/SF GUI. Use these instructions after you have: Verified the RECEIVE command will work to transfer files from the host to workstation. The IND$FILE MODULE is required for RECEIVE to work. 1 Establish a host session on the OS/2 workstation. You may have to start Communications Manager/2 if no host sessions are started. 2 Log on to one of the OSA administration user IDs (OSADMIN1) that can access the OSA/SF product test build disk (100). link 2VMVMV20 100 100 rr acc 100 c Link and access the OSA/SF for VM's product code test build disk. If you are using SFS then change the access command to access the correct SFS product code test directory. 3 Make sure the VM user ID has the READY prompt. 4 To download the Software Installer bootstrap file, do the following from an OS/2 command line: RECEIVE IOAINENU.EXE a: IOAINENU BIN Replace the a with the host session identifier that you established in step 1. Note: If the download is successful, you will see the message, File transfer complete. 5 Install the Software Installer by entering: IOAINENU 6 Select Continue to start the installation. 7 Select the VM option to indicate the Host Operating System you are installing on. Then select Continue. 8 Select the ADMIN session you established. A window is displayed with the drive, subdirectory, and file name. We recommend you use these defaults for service updates. Software Installer Drive, Directory, Filename Installation Instructions 23
Setting Up the OS/2 GUI for OSA/SF 9 Select OK to start software installer installation. The Install - progress window is displayed. 10 When you see the Instructions window, select Continue to proceed with installing the OSA/SF GUI. 11 The Install window is displayed. 12 If you are installing or servicing on a LAN server or if you do not want SI to update your CONFIG.SYS file on your machine, do the following. Otherwise select OK and go to the next step. a. Deselect the Update CONFIG.SYS option. b. Select OK. c. Reply to the warning message that tells you SI will not update your CONFIG.SYS file. d. Select Yes. 13 When the Install - Directories window is displayed, either accept the defaults or enter your own. OSA/SF Drive and Subdirectory Note: If you want to check your disk space, select Disk Space. 14 Select Install... to start downloading OSA/SF GUI files. 15 Select OK when you see the message that indicates successful completion. 16 To exit SI, double-click on the system icon or select File and then select Exit 24 OSA/SF for VM Program Directory
Choose one of the following for your installation: 1. If you installed OSA/SF GUI on a LAN server, each requester on the LAN that accesses OSA/SF must now be updated. Continue at 6.5.5, Updating a Requester Machine on page 26. 2. If you did not install OSA/SF GUI on a LAN server and if you deselected the Update CONFIG.SYS option in step 12, you must update your CONFIG.SYS file. Continue at 6.5.4, Updating the CONFIG.SYS File on a Non-Requester Machine on page 25. 3. If you did not install OSA/SF GUI on a LAN server and you allowed software installer to update the CONFIG.SYS file, you will have to shut down your workstation and reboot it. The OSA/SF GUI install is complete. Continue with 6.6, Place OSA/SF for VM Into Production on page 32 to complete the install of OSA/SF for VM. 6.5.4 Updating the CONFIG.SYS File on a Non-Requester Machine You must update your CONFIG.SYS file if you deselected the Update CONFIG.SYS option when you installed OSA/SF GUI on your machine or after you applied a service level to OSA/SF GUI that affects the values in the CONFIG.SYS file. 1 Back up your current CONFIG.SYS file. 2 View the CONFIG.ADD file that was created during downloading and installing the OSA/SF GUI with software installer. The CONFIG.ADD file is a copy of your current CONFIG.SYS file with changes for OSA/SF. 3 Verify or change the drive and directory for OSA/SF in the following statements: SET PATH SET HELP LIBPATH 4 Verify or change the drive and directory for the following statements that were added: SET IOAERR=drive:\dir (IOAERR is for trace logs and error logs) SET IOAWORK=drive:\dir (The drive you choose for IOAWORK should have at least 7MB of free space. IOAWORK is the subdirectory from which the OSA/SF GUI creates other subdirectories and files.) SET IOAESIZE=2 (2 represents 2 KB of error log before wrapping.) SET HOSTPAGE= 037 for English Installation Instructions 25