*------------------------------------------------------------------------------* * P/390 VM/ESA Application Development CD-ROM Version 2.1.0 1/26/96 * * John A. Hupcey * PKVMWFB1(HUPCEY) * hupcey@vnet.ibm.com * USIB2TWT at IBMMAIL * * c Copyright International Business Machines Corporation 1996 * Licenced Material - Program Property of IBM. All rights Reserved. *------------------------------------------------------------------------------* *------------------------------------------------------------------------------* * OVERVIEW OF CONTENTS Subdirectory Package file *------------------------------------------------------------------------------* A. VM/ESA (ESA Feature) 2.1.0 RSU9502 s:\VMESA VMESA.PAC B. VM Maintenance disks s:\VMSRC VMSRC.PAC C. VM Program Products s:\VMPP VMPP.PAC D. VM Program Product Source s:\VMPPSRC VMPPSRC.PAC E. P/390 VM Host Server program s:\VMESA AWSHOST.PAC F. Notes on the Device Map d:\VMESA G. IPLing standalone utilities d:\VMESA H. P/390 Sample configurations d:\VMESA There is a top-level package file in the root subdirectory called VMADCD.PAC. Note: Before running any of the install programs on this disk you MUST already have installed the P/390 Program diskettes. We urge you to install the latest version of these diskettes. Throughout this document "s:" refers to the drive letter assigned to the CD-ROM in your system; "d:" refers to the hard disk partition onto which you are installing the programs. *------------------------------------------------------------------------------* A. VM/ESA (ESA Feature) 2.1.0 s:\VMESA VMESA.PAC *------------------------------------------------------------------------------* These are VM CP and CMS minidisks, such as SYSRES.300, OPERATOR.191, etc. 1. Insert the Starter System disk into your optical disk drive ('s:'), open an OS/2 command prompt, maximize it, and type: s:\INSTALL You will be prompted for the source and destination drives for the VM Starter System disks. 2. The Starter System disks are copied to your hard drive. 3. Certain CP volumes (paging, spool, and tdisk space) are allocated. 4. You will then be asked if you wish to install the VM Source disks. The default is to continue with B.2, below. If you answer "No", then you may install them at a later time by following the instructions in B.1, below. 5. You will then be asked if you wish to install any VM Program Products. The default is to continue with C.2, below. If you answer "No", then you may install them at a later time by following the instructions in C.1, below. 5. After you have finished VM installation, then continue with the installation procedure in the PC Server System/390 Installation Guide for VM/ESA. Also read the d:\P390\README.AWS file. *------------------------------------------------------------------------------* B. VM Maintenance disks s:\VMSRC VMSRC.PAC *------------------------------------------------------------------------------* These are MAINT userid's minidisks that are required to modify CP or CMS, or to apply service (RSU tapes/CDs). 1. Insert the Starter System disk into your optical disk drive ('s:'), open an OS/2 command prompt, maximize it, and type: s:\INSTSRC You will be prompted for the source and destination drives for the maintenance disks. 2. The minidisks will be copied to the \VMSRC subdirectory on your chosen drive. 3. Bring up the P/390 Configurator and use F9 to display files not found. If there is anything in this list that you need, use the Configurator F2 Update System Devices screen to look at and solve the problem. Just to be sure, go to the F3 Update User Data screen for user MAINT, look at his minidisks (F3) and make sure they are all there and have a non-blank "file size". If not, check the drive letters in the "path" fields for each disk. *------------------------------------------------------------------------------* C. VM Program Products s:\VMPP VMPP.PAC *------------------------------------------------------------------------------* These are products such as HLASM, EREP, etc. (See VMPP.PAC) 1. Insert the Starter System disk into your optical drive ('s:'), open an OS/2 command prompt, maximize it, and type: s:\INSTVMPP You will be prompted for the source and destination drives for the VM Program product disks. 2. You then choose whether you wish to install VM Program Product run-time disks, or source/maintenance disks. Choose "run-time". 3. A menu of the available VM Program Products is presented. Follow the instructions to choose the ones that you want. The minidisks will be copied to the \VMPP subdirectory on your chosen drive. 4. The amount of disk space required and the amount you have on the destination drive are displayed. If all the products you want to install will not fit, this command may be run multiple times, specifying different destination drive letters each time. 5. Runtime code for VM Program Products are already installed on the MAINT 19E Y-disk, if appropriate. 6. You can create your own "tools" disk by creating a MAINT 19F minidisk, and adding links in USERPROF and SYSPROF directory profiles for 19F. The 19F disk, if present, will automatically be accessed as filemode W. *------------------------------------------------------------------------------* D. VM Program Product Source s:\VMPPSRC VMPPSRC.PAC *------------------------------------------------------------------------------* These are source/maintenance minidisks that are required to rebuild the products or to apply service (RSU tapes/CDs). *** We strongly urge you to install the source disks corresponding to the program products installed on your system. If you wish to copy additional products at a later time, or to install them on a different OS/2 drive, you can run this install program repeatedly: 1. Insert the Starter System disk into your optical drive ('s:'), open an OS/2 command prompt, maximize it, and type: s:\INSTVMPP You will be prompted for the source and destination drives for the VM Program Product source disks. 2. You then choose whether you wish to install VM Program Product run-time disks, or source/maintenance disks. Choose "source". 3. A menu of the available VM Program Product source is presented. Follow the instructions to choose the ones that you want. The minidisks will be copied to the \VMPPSRC subdirectory on your chosen drive. 4. The amount of disk space required and the amount you have on the destination drive are displayed. If all the products you want to install will not fit, this command may be run multiple times, specifying different destination drive letters each time. *------------------------------------------------------------------------------* E. P/390 Host Server program s:\VMESA AWSHOST.PAC *------------------------------------------------------------------------------* These are the files that need to be uploaded to your VM host mainframe in order to run Transparent File Access (TFA & HLINK commands) on the P/390 under VM/CMS. This package will be copied along with the base VM/ESA files when you run INSTALL in A., above. See the AWSHOST.PAC file for upload instructions. Follow them carefully! *------------------------------------------------------------------------------* F. Notes on the Device Map d:\VMESA\DEVMAP.1VM *------------------------------------------------------------------------------* Note: An annotated, readable copy of DEVMAP is contained in DEVMAP.NME. You might want to print this file. 1. The P/390 <-> VM device map (DEVMAP.1VM) that is on the CD-ROM is copied to d:\VMESA on your system and then updated to reflect the actual drive letter that "d:" represents. You should ALWAYS run the P/390 Configurator to check to see if all the minidisks that you need have been located. a. Press F9 from the Configurator main menu. This will list the files that were not found. b. Go to the F2 Update System Devices menu. Any DASD device that does NOT has blanks in the "Size" field, has not been found at the OS/2 drive, path, and filename specified in the field called "FN/P" on the far right. c. Correct this OS/2 file specification to point to the actual location of the file, and press ENTER. The size should appear. 2. If you have a LAN adapter installed in your PC Server, then you will want to "activate" the device entries that are LAN-related. Excluded devices are shown on the F2 Update System Devices menu in DARK BLUE, with a device manager number of "0". The LAN devices contained in the Starter System DEVMAP are: - 204-207 LAN3274: 3270 sessions over the LAN on OS/2 clients. - 440-447 LAN3088: CTCA links via LAN between P/390 processors. - 448 AWS3172: VTAM 3172 emulation - e.g. for DOS 3270 clients. - 44A-44B LCS3172: TCP/IP 3172 emulation To activate excluded devices, position the cursor on the first device and press ALT+F5. See the documentation or online help (F1) for additional details. 3. If you receive the following "pop-up" message: +-------------------------------------------+ | P/390 Error | +-------------------------------------------+ | AWSDEV908E CU=SCSI348: RC=006E | | opening device driver, DD=SCSI3480 | +-------------------------------------------+ this means that you need to activate the SCSI3480.SYS device driver in CONFIG.SYS. This device entry is in the default DEVMAP: - 590 SCSI3480: 3480 tape on 4mm DAT cartridge If this entry is active but the device driver is not, then you get the error message. Since every PC Server S/390 has a 4mm DAT tape drive, you should edit CONFIG.SYS and make sure the "rem " characters are deleted from this line: rem DEVICE=d:\P390\SCSI3480.SYS 00,00 Reboot OS/2 and look for the SCSI3480 message during boot. 4. Local Time Offset from GMT Be sure to set the GMT offset in both the P/390 Configurator F4 Update System Environment menu and in the SYSTEM CONFIG file on MAINT's 300 and 400 disks. 5. When you press "F9 Display Files Not Found" in the P/390 Configurator, you will see several file names displayed. This is because these files are defined in the Starter System DEVMAP, but are not on your hard disk. If you did not install EVERYTHING from the CD (including optional VM Program Products and their Source), then you will see names like D:\VMPP\EREP\EREP.XXX After you run the INSTVMPP.CMD program from the CD and select this product, then this message will go away. The following DEVMAP devices are for future use: d:\VMESA\210RES.123 | Fullpack 9336 for VM/ESA tape install d:\VMESA\210W01.124 | " " " " " " D:\VSE\DOSRES.140 | For VSE under VM D:\VSE\SYSWK1.141 | " " " " D:\MVS\MVSV5R.120 | For MVS under VM D:\MVS\MVSV5D.121 | " " " " D:\MVS\SCPMV5.122 | " " " " D:\MVS\P390DX.123 | " " " " D:\MAINT.292 | Prototype for a minidisk on a floppy d:\VMESA\SPOOL2.309 | Extra SYSOWN volume name You do not need these disks to run the VM/ESA Starter System. *------------------------------------------------------------------------------* G. IPLing standalone utilities d:\VMESA\*.IPL *------------------------------------------------------------------------------* We have provided stand-alone versions of: - ICKDSF16.IPL : ICKDSF version 16.0A - you MUST use this version for CKD volumes!! - DDRXA.IPL : VM/ESA 2.1.0 version - DDR370.IPL : 370 mode version These are all on the CD-ROM and on your hard drive in d:\VMESA. They are in AWSTAPE format. Instructions for IPLing any *.IPL file: 1. Bring up the P/390 Configurator. Go to F2 Update System Devices menu. 2. Put d:\VMESA\name.IPL in the "FN/P" field for device 580. Press ENTER. (d: = your hard drive, name = ICKDSF16, DDRXA, or DDR370). 3. Save and exit the Configurator. 4. At an OS/2 prompt: D: CD D:\P390 IPL 580 CLEAR 5. To give the initial 3270 console interrupt, go to the first local CM/2 session, make it active, and then press the right-hand mouse button. Select "ATTN" from the pop-up menu. *------------------------------------------------------------------------------* H. P/390 Sample configurations d:\VMESA *------------------------------------------------------------------------------* Two minidisks are provided that contain sample configuration files for the P/390 environment: d:\VMESA\RSCS.191 RSCS configuration files d:\VMESA\VTAM.191 VTAM configuration files The sample configuration files will get you started easily with P/390 RSCS and VTAM connectivity. The Starter System DEVMAP already has entries for system nodeids SYS2, SYS3, and SYS4. Your system is (by default) SYS1. Also provided (for VTAM) is a remote host mainframe: WFB4. If you change your nodeid from SYS1 to something else, or are interconnecting multiple P/390s, the files you need to alter are: o DEVMAP.1VM - Use P/390 Configurator F4 menu for you nodeid and CPU ID. - Use F2 menu for other P/390's nodeids you connect via LAN3088. o RSCS - follow directions in RSCS CONFIG on RSCS.191 disk. o VTAM - follow directions in README on VTAM.191 disk.