PC Server S/390 Preconfigured System for MVS/ESA - Version 5.2.2 (9/95) _______________________________________________________________________ Thank you for using the Preconfigured System for MVS/ESA 5.2.2. The system is designed to help you get a running MVS system quickly, so you can concentrate on getting your work done. CONTENT OF CD _____________ Please see the file MVS522.PAC on the CD-ROM for a list of the contents of this CD-ROM. The pre-configured system contains the following program products: Product PID Version ____________ ________ _______ MVS/ESA JES2 5655-068 5.2.2 TIOC 5752-VS2 3.8.0 HLASM 5696-234 1.2.0 DFSMS/DFP 5695-DF1 1.2.0 ICKDSF 5655-257 1.16.0 ACF/VTAM ESA 5695-117 4.2.0 EREP 5658-260 3.5.0 TSO/E 5685-025 2.4.0 ISPF 5655-042 4.1.0 SMP/E 5668-949 1.8.1 BUILD STRUCTURE _______________ This system has been built specially for the PC Server System/390 from a CBIPO base. It resides on these emulated 3380 DASD volumes: o MVSV5R This 3380E (double-density) volume contains the base MVS system software target, or run-time, libraries, and other system data sets required to IPL the system and use TSO/E and ISPF. The SMP/E target zone CSI (Con- solidated Software Inventory) VSAM data set also resides on this volume. This is the MVS IPL volume. This volume is set up in the DEVMAP (Device Map) as address 120, and is defined to MVS as device number 120. The OS/2 file size for this volume is 1,264,205,312 bytes (1177 MB). o MVSV5D This 3380E volume contains the base MVS system software distribution libraries. It contains the SMP/E Global and DLIB (Distribution Library) zone CSI. This volume need not be present to IPL, but is needed to install service or products on the MVS system using SMP/E. The MVS system does not have a backup RACF database. Also, SMF reporting is disabled. This has been done to reduce I/O, and thus improve MVS per- formance on the P/390. This volume is set up in the DEVMAP as address 121, and defined to MVS as device number 121. The OS/2 file size for this volume is 1,264,205,312 bytes (1177 MB). o MVSWK1 This 3380D (single density) volume is a predefined working volume avail- able for your use. It does not contain any MVS program products. It is currently set up at address 122. The OS/2 file size for this volume is 632,102,912 bytes (603 MB). INSTALLATION PROCESS ____________________ These volumes must be installed on your PC Server System/390. To begin the install process insert the MVS/ESA CD-ROM, open an OS/2 window, MAXIMIZE the window, and then type: x:\install Where x is the drive letter assigned to your CD-ROM drive. You will be prompted for the destination drive (d:) where you want MVS/ESA installed. To accept the default (D:) just press ENTER. The install process unpacks and copies the MVSV5R.120, MVSV5D.121, and MVSWK1.122, and sets d:\MVS\DEVMAP.MVS as the current DEVMAP. IPLING MVS __________ Reminder: Make sure you have installed Communications Manager/2 and that 4 DFT sessions are configured to LOCAL, using the P/390 Configurator "F7 Update 3270 LT Sessions" menu. Also, you must start Communications Manager/2 prior to IPLing the MVS system. The first DFT session configured as LOCAL will become the MVS Console. You must IPL using the MVSV5R pack. There are a couple of ways to do this: IPL ICON The IPL Address can be set up in the P/390 Configurator, via "F4 Update System Environment" menu. It can also be overridden using the optional parameters in the "IPL P/390" icon Settings notebook. It has already been set to address 120. To IPL: Double Click on the "IPL P/390" icon OS/2 WINDOW At an OS/2 prompt, enter the following: (the \P390 subdirectory must be the current subdirectory) d: CD d:\P390 IPL 120 Once you have IPLed MVS, you can find additional information about the MVS system in the logon messages and in the data set SYS1.P390.CNTL. RESPONSES _________ As the system is IPLing, you will need to enter the following responses on the MVS Console: +--------------------------------------------------------+------------------+ | MESSAGE | RESPONSE | +--------------------------------------------------------+------------------+ | IEA101A SPECIFY SYSTEM PARAMETERS FOR RELEASE 03.8 | ENTER | | ,VER=SP5.2.2 HBB45520 | | +--------------------------------------------------------+------------------+ | *01 $HASP426 SPECIFY OPTIONS - JES2 SP 5.2.2 | r 01,warm,noreq | +--------------------------------------------------------+------------------+ As the system is running, if you may wish to do some of the following from the MVS Console: +--------------------------------------------------+------------------------+ | ACTION | COMMAND | +--------------------------------------------------+------------------------+ | Display DASD Volumes | PF 1 | +--------------------------------------------------+------------------------+ | Display Tape Units | PF 2 | +--------------------------------------------------+------------------------+ | Clear Top of Screen | PF 3 | +--------------------------------------------------+------------------------+ | Create a 10-line Display Area | PF 4 | +--------------------------------------------------+------------------------+ | Display Address Space Information | PF 5 | +--------------------------------------------------+------------------------+ | Display Outstanding Reply Requests and Error | PF 6 | | Messages | | +--------------------------------------------------+------------------------+ | Display PF Keys | PF 7 | +--------------------------------------------------+------------------------+ | Scroll Display Area | PF 8 | +--------------------------------------------------+------------------------+ | Display TSO Users | PF 9 | +--------------------------------------------------+------------------------+ | Display Active Address Spaces | PF 10 | +--------------------------------------------------+------------------------+ | Display Active Jobs | PF 11 | +--------------------------------------------------+------------------------+ | Clear Bottom Screen | PF 12 | +--------------------------------------------------+------------------------+ | Shutdown JES | $P JES2,abend | +--------------------------------------------------+------------------------+ MESSAGES ________ Due to the asynchronous way the system comes up, you will often see messages about TCAS, APPC/ASCH, and VTAM. They should resolve themselves as the system continues to IPL. However, you will need to respond to some as indi- cated. For instance: *02 IKT003D TCAS UNABLE TO ACCEPT LOGONS, REASON CODE=0092 REPLY 'RETRY' OR 'TERM' requires the response: r 02,retry You can log onto the TSO accounts when you see the following message: IKT007I TCAS ACCEPTING LOGONS USERIDS _______ The following TSO Userids and Passwords have already been set up on your system: +-------------------------------------+-------------------------------------+ | USERID | PASSWORD | +-------------------------------------+-------------------------------------+ | P390 | P390 | +-------------------------------------+-------------------------------------+ | IBMUSER | IBMUSER | +-------------------------------------+-------------------------------------+ P/390 DEVMAP SET-UP ___________________ The device map in the P/390 Configurator has already been set up for the MVS system you are receiving. It is located at d:\MVS\DEVMAP.MVS. Some of the devices and addresses that have been set up are: +------------------------+------------------------+-----------------------+ | DEVICE TYPE | ADDRESS | DESCRIPTION | +------------------------+------------------------+-----------------------+ | 2540 | 00C | emulated card reader | +------------------------+------------------------+-----------------------+ | 1403 | 00E | OS/2 printer | +------------------------+------------------------+-----------------------+ | 1403 | 00F | OS/2 printer | +------------------------+------------------------+-----------------------+ +------------------------+------------------------+-----------------------+ | 3380E | 120 | MVSV5R | +------------------------+------------------------+-----------------------+ | 3380E | 121 | MVSV5D | +------------------------+------------------------+-----------------------+ | 3380D | 122 | MVSWK1 | +------------------------+------------------------+-----------------------+ +------------------------+------------------------+-----------------------+ #| 3480 | 560 | SCSI-attached tape | | | | drive | +------------------------+------------------------+-----------------------+ | 3420 | 580 | tape emulated on disk | +------------------------+------------------------+-----------------------+ +------------------------+------------------------+-----------------------+ | 3278 | 700 | MVS Master Console | +------------------------+------------------------+-----------------------+ | 3278 | 701 | Local TSO Session 1 | +------------------------+------------------------+-----------------------+ | 3278 | 702 | Local TSO Session 2 | +------------------------+------------------------+-----------------------+ | 3278 | 900 | Local TSO Session 3 | +------------------------+------------------------+-----------------------+ | 3278 | 901 | Local TSO Session 4 | +------------------------+------------------------+-----------------------+ *| 3278 | 902 | LAN TSO Session 1 | +------------------------+------------------------+-----------------------+ *| 3278 | 903 | LAN TSO Session 2 | +------------------------+------------------------+-----------------------+ +------------------------+------------------------+-----------------------+ *| 3088 | E20 | 3172 for TCP/IP (even)| +------------------------+------------------------+-----------------------+ *| 3088 | E21 | 3172 for TCP/IP (odd) | +------------------------+------------------------+-----------------------+ *| 3088 | E40 | 3172 for VTAM | +------------------------+------------------------+-----------------------+ # = See "Pop-up message", below. * = Device is "excluded" in DEVMAP because it requires a LAN adapter to be installed and configured in OS/2 LAPS. If you have a LAN adapter installed in your PC Server, then you may want to 'activate' the device entries that are LAN-related. Excluded devices are shown on the P/390 Configurator F2 Update System Devices menu in DARK BLUE. The LAN devices contained in this DEVMAP are: - 902-903 LAN3274: 3270 sessions over the LAN on OS/2 clients - E20-E21 LCS3172: TCP/IP 3172 emulation - E40 AWS3172: VTAM 3172 emulation - e.g. for DOS 3270 clients 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. Pop-up message during IPL P/390 _______________________________ 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. There is a device entry in DEVMAP for SCSI-attached tape: - 560 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 the beginning of this line: rem DEVICE=d:\P390\SCSI3480.SYS 00,00 Reboot OS/2 and look for the SCSI3480 message during boot. See the file d:\P390\SCSI3480.DOC for more information. Local Time Offset from GMT __________________________ Be sure to set the GMT offset in both the P/390 Configurator "F4 Update System Environment" menu and where appropriate in your MVS/ESA operating system. USING STAND-ALONE ICKSDF ________________________ If you create additional 3380 volumes, you will need to initialize them using ICKDSF. The stand-alone version of ICKDSF (16.0A) is included on this CD in a file called ICKDSF.IPL. Instructions for IPLing ICKDSF.IPL: 1. Bring up the P/390 Configurator. Go to "F2 Update System Devices" menu. 2. Put d:\MVS\ICKDSF.IPL in the "FN/P" field for device 580. Press ENTER. (d: = your hard drive). 3. Save and exit the Configurator. 4. At an OS/2 prompt, enter the following: 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. 6. Enter the following commands, pressing enter after each line: (Note: '_' is a leading blank) CONSOLE CONSOLE _INIT_UNIT(yyy)_NOCHECK_NOVALIDATE_VTOC(10,0,1)_VOLID(zzzzz)_NOVERIFY U Where: - yyy is the unit address of the DASD volume to be initialized (120 + for this system) - zzzzzz is the volser of the DASD volume being initialized (e.g. MVSWK2)