PC Server S/390 Application Development System for MVS/ESA - Version 5.2.2 (11/95) 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴 Thank you for using the Application Development 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-ROM 컴컴컴컴컴컴컴컴� Please see the file MVS522AD.PAC on the CD-ROM for a list of the contents of this CD-ROM. The application development system contains the following program products: Product PID Version 컴컴컴컴컴컴컴컴컴컴� 컴컴컴컴 컴컴컴� | MVS/ESA JES 2 5655-068 V5R2.2 Includes the following features: Feature Feature Codes 컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 컴컴컴컴컴컴컴 Open Edition Feature 5811,5812,5708 OE Debugger Feature 5007,5008,5701 OE Shell/Utilities Feature 5004,5005,5700 LANRES/MVS 1.3.1 (Host) 5282,5283,5720 OpenEdition DCE Base Services 5891,5892,5713 | But NOT the following features: Feature Feature Codes 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 컴컴컴컴컴컴컴 | OpenEdition DCE User Data 5988,5989,5715 | Privacy Feature | MVS C/C++ + Data Decryption feature 5975,5976,5724 | ADSM for MVS 5655-119 V2R1 | ADSM OE Client 5655-119 V2R1 DFSMS/ MVS Full Func 5695-DF1 R2.0 | ISPF 5655-042 V4R2.0 SMP/E 5668-949 R8.1 TSO/E 5685-025 V2R4.0 | RACF 5695-039 V2R2 | ACF/VTAM ESA 5695-117 V4R3 High Level Assembler 5696-234 R2.0 DFSORT 5740-SM1 R12 MVS/DITTO for ESA 5655-103 V1R1 TIOC 5752-VS2 V3R8.0 ICKDSF 5655-257 R16 EREP 5658-260 V3R5.0 SDSF/MVS 5665-488 R5.0 RMF 5655-084 V5R2 GDDM 5695-167 V3R1 MQM/MVS/ESA 5695-137 R1.3 | SOMObjects for MVS 5696-822 V1R1 | SOMObjects Compiler 5696-822 V1R1 TCP/IP 5655-HAL V3R1 Includes the following features: Feature Feature Codes 컴컴컴컴컴컴컴컴컴� 컴컴컴컴컴컴컴 TCP/IP CICS 5831,5832,5703 TCP/IP NPF 5861,5862,5706 | TCP/IP Non-Kerberos 5821,5822,5702 TCP/IP XA/ESA 5801,5802,5700 TCP/IP IMS 5841,5842,5704 | But NOT the following features: Feature Feature Codes 컴컴컴컴컴컴컴컴컴� 컴컴컴컴컴컴컴 | TCP/IP DES Kerbeos 5701,5811,5812 Netview CS 5685-111 V2R4 | VisualLift 5648-109 V1R1.1 3270PC File Transfer 5665-311 R1.1 Print Service Fac (PSF)5695-040 V2R2 | AD/Cycle Lang Environ 5688-198 R5.0 | AD/Cycle COBOL/370 5688-197 V1R1 | IBM C/C++ for MVS/ESA 5655-121 V3R1.1 AD/Cycle PL/1 5688-235 V1R1.1 VisualGen 5648-078 V1 | DCE Application Sup 5655-064 V1R1 CICS 5655-018 V4R1.0 | IMS DM & TM 5695-176 V5R1 | Database 2 (DB2) 5685-DB2 V3R1 DB2 Prfmnce Monitor 5655-047 V3R2 QMF 5706-254 V3R1.1 | Changes from MVS 5.2 Pre-Configured System for Application Development BUILD STRUCTURE 컴컴컴컴컴컴컴� This system has been built specially for the PC Server System/390 from a CBIPO base. It has been designed for ease of system software replacement. It resides on these emulated 3380 DASD volumes: o MVSV5R This 3380K (triple-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 dataset 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,896,307,968 bytes. o MVSV5D This 3380K 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. 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,896,307,968 bytes. o SCPMV5 This 3380E volume contains data sets that you might change, either through normal use of the system or by directly altering them to affect how the system works. System control data sets, such as SYS1.PARMLIB and SYS1.VTAMLST reside on this volume, as do the RACF database, the MVS IODF (I/O Definition File), the system's master catalog, the SMP/E Global Zone CSI and data sets, and other required data sets. This volume is required to IPL. This volume is set up in the DEVMAP as address 122, and defined to MVS as device number 122. The OS/2 file size for this volume is 1,264,205,312 bytes. o P390DX This 3380E volume contains the database product system software target and distribution libraries for CICS, IMS, and DB2. This volume also con- tains the SMP/E Target and DLIB zone CSIs for these products. This volume need not be present to IPL, but is needed to use these products. For this release, new products have not been added, but several products have been updated (version/release). See above list. This volume is set up in the DEVMAP as address 123, and defined to MVS as device number 123. The OS/2 file size for this volume is 1,264,205,312 bytes. NOTE: If this volume is not available to MVS during IPL, messages will be issued because some Link List data sets that reside on this volume will not be found. These messages can be ignored. 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 performance on the P/390. Please see additional system information, guidelines, and hints in the dataset SYS1.README on MVSV5R. SYSTEM GUIDELINES 컴컴컴컴컴컴컴컴� The following guidelines will make it easier for you to replace this level of system software with new levels built the same way. (Additional details are provided in SYS1.README(STRUCTRE) on MVSV5R): o Only IBM-supplied system software should reside on MVSV5R and MVSV5D. These volumes are intended to be replaced. You should try to use alter- natives to updating these volumes when possible. All changes to these volumes will be **lost** when they are replaced, so you should keep a record of any changes made to them. o When you get new levels of the system software, you may choose whether or not to replace SCPMV5. We expect that most people will choose not to replace this volume. Sample jobs are provided for updating SCPMV5 to reflect the new system. This migration process is described in MIGRATE.DOC on this CD-ROM. o You will also be given the option of replacing P390DX when you receive new levels of system software. A minimum of customization data should reside on this volume. Keeping CICS, IMS, DB2 and QMF customization data elsewhere will make it easier to rebuild this volume after replacement. SYSTEM INSTALLATION INFORMATION 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� This system is based upon a CBIPO. The CBIPO installation jobs have been run, and some post-CBIPO installation steps have been done. All MVS products are installed at least through the end of the CBIPO Instal- lation Guide. In addition, all NLS English features have been installed, all products supplied on the CBIPO SERV tape have been SMP/E APPLYed and ACCEPTed, except NLS features for languages other than English, and service from the SERV tape has been RECEIVEd. All CICS and DBS products are also installed through the end of the CBIPO Installation Guide. Note that most CICS and DBS products are *not* ready to use as supplied, but require customization to be useful. However, the libraries needed for using these products have been added to the APF and LPA lists. Additional details are provided in SYS1.README(INSTALL) on MVSV5R. CD-ROM INSTALLATION PROCESS 컴컴컴컴컴컴컴컴컴컴컴컴컴� These volumes must be installed on your PC Server System/390. To begin the install program, insert the MVS/ESA CD-ROM Disk 1, open an OS/2 window, MAXIMIZE the window, and then type: x:\install Where x is the drive letter assigned to the 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. You will be prompted to load MVS/ESA CD-ROM Disk 2 after the first disk has been copied. If you are installing this CD-ROM over an existing MVS Preconfigured or Application Development system, you have two options: o Completely replace the existing MVS system. - You should backup (for example, on tape) all of the files in the d:\MVS subdirectory so you can regress to your current level. - You must manually erase all of these files. - Restart the install program. o Replace only part of an existing MVS 5.2 Application Development system NOTE: Please see BUILD STRUCTURE and SYSTEM GUIDELINES for information about SCPMV5 and P390DX. - You should backup (for example, on tape) all of the files in the d:\MVS subdirectory so you can regress to your current level. - You must manually erase the OS/2 files that contain the volumes you want to replace. You MUST erase MVSV5R.120 and MVSV5D.121. You may optionally keep or erase SCPMV5.122 and/or P390DX.123. If you do not replace SCPMV5, you must follow the migration instructions located in the file MIGRATE.DOC on the CD-ROM. - Restart the install program. The install program will NOT overlay any existing volumes; you must manually erase or move any files with the same names as the new volumes. Remember that these are VERY BIG files (1.2 - 1.8 GB) so you probably do not have enough room to keep backup copies on your PC Server hard disks, unless you use a program like PKZIP to archive compressed copies of these files. If at any time in the future, you wish to load any volumes from this CD-ROM (for instance, you decided to skip the loading of MVSV5D, but now you need the volume to apply service), the following manual procedure can be followed: MANUALLY LOADING MVS VOLUMES FROM THE CD-ROM 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴 1. Insert the MVS/ESA CD-ROM disk 1 and open an OS/2 window. 2. Examine the file x:\MVS522AD.PAC (where x: is the drive letter of your CD-ROM drive). This will tell you the names and locations of the OS/2 files that contain each of the MVS volumes. For example: * * CD-ROM Disk 1 * * \MVS * MVSV5R.ZIP, crc date time MVSV5R.120 * etc. 3. Insert the MVS/ESA CD-ROM disk containing the desired volume. 4. Type: UNZIP x:\MVS\fname.ZIP *.* -d d:\ where 'd:\' is the drive where you want to install the MVS volume and 'fname' is the MVS volume name. 5. If you Unzip the file to a different drive or subdirectory than you used during the initial MVS/ESA CD-ROM installation, use the P/390 Configurator "F2 Update System Devices" menu to correct the DEVMAP entry for that device. Just tab over to the "FN/P" field for the DASD device you want to change, and overtype the actual drive/path/filename and press ENTER. The "size" field (which would have been blank if the file was not found) should now show the size of the MVS volume. Press F10 and then F6 to Save and Exit the Configurator. IPLING MVS 컴컴컴컴컴 Reminder: Make sure you have installed Communications Manager/2 and that 5 DFT sessions are configured to LOCAL in the P/390 Configurator. 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 PF4 - Update the System Environment. 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, with load parameter 012200. To IPL: Double Click on the "IPL P/390" icon OS/2 WINDOW At an OS/2 prompt, enter the following: NOTE: the \P390 subdirectory must be the current subdirectory d: CD d:\P390 IPL 120 /PARM 012200 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 | +--------------------------------------------------------+------------------+ NOTE: JES2 may need to be cold started the first time you bring up the system. This reply is: r 01,cold. You will then need to start JES2 with "$s". As the system is running, 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 (RACF special authority) | P390 | +-------------------------------------+-------------------------------------+ | IBMUSER (RACF special authority) | SYS1 | +-------------------------------------+-------------------------------------+ | P390A - P390Z | TEST | +-------------------------------------+-------------------------------------+ | TESTER | TEST | +-------------------------------------+-------------------------------------+ IDs set up specially for MVS Open Edition users, using new SCPMV5 (their default logon PROC puts them into the OE Shell): +-------------------------------------+-------------------------------------+ | USERID | PASSWORD | +-------------------------------------+-------------------------------------+ | OPEN1 - OPEN 3 | SYS1 | +-------------------------------------+-------------------------------------+ 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 | +-----------------------+-----------------------+----------------------+ | 3380K | 120 | MVSV5R | +-----------------------+-----------------------+----------------------+ | 3380K | 121 | MVSV5D | +-----------------------+-----------------------+----------------------+ | 3380E | 122 | SCPMV5 | +-----------------------+-----------------------+----------------------+ | 3380E | 123 | P390DX | +-----------------------+-----------------------+----------------------+ +-----------------------+-----------------------+----------------------+ # | 3480 | 560 | SCSI-attached tape | | | | drive, non-IDRC | +-----------------------+-----------------------+----------------------+ | 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 | +-----------------------+-----------------------+----------------------+ Other address ranges and devices are set up in the MVS system you are receiving. These are listed in the dataset SYS1.P390.CNTL(MVSCP) on SCPMV5. # = See "Pop-up message" below IDRC-capable 3480 tapes are available at addresses 568 - 56F. When using the 4mm DAT drive, you can get a maximum of 4GB per tape without using IDRC, and a maximum of 10GB per tape when using IDRC (this assumes 120M tapes). * = 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, 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, you will 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 Re-boot 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-ROM 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 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 (ex. MVSWK2) - VTOC (10,0,1) may be used when initializing a volume you plan to restore over. The VTOC will become that of the restored volume. If you are initializing a volume for another purpose, we suggest using at least 30 tracks. The DSF Users' Guide and Reference, GC35-0033, provides information for calculating the VTOC size. DFSMSdss RESTORE 컴컴컴컴컴컴컴컴 A stand-alone version of DFSMSdss is provided to help you to restore 3480 or 4mm tape volumes. The stand-alone version of DFSMSdss Version 1.2 is included on this CD-ROM in a file called SADSS.IPL. Instructions for IPLing SADSS.IPL: 1. Bring up the P/390 Configurator. Go to F2 Update System Devices menu. 2. Put d:\MVS\SADSS.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) INPUT=CNSL _JOB _MSG TODEV=CNSL _RESTORE FROMDEV=tape,FROMADDR=xxx,TODEV=uuuu,TOADDR=yyy,VOLID=zzzzzz _END Where: - tape is 3480 - xxx is the tape unit address (560 for this system) - uuuu is the unit type of the DASD volume to be restored (ex. 3380) - yyy is the unit address of the DASD volume to be restored (120-123 are used for the preconfigured system) - zzzzzz is the volser of the DASD volume being restored (MVSV5R, MVSV5D, P390DX, SCPMV5 are used for the preconfigured system) NOTE: There are no informational or status messages as the tape is loaded in. 7. When DFSMSdss hits the end of a tape and there is more than one tape volume, the following message will appear: ADR561A END OF TAPE. MOUNT TAPE ON xxx. DEPRESS INTERRUPT KEY. Mount the next tape, then press Interrupt. This can be found in the P/390 Manual Operations Icon, under Control/External Interrupt 8. When DFSMSdss has completed processing the following message will appear on the console: ADR563A END OF JOB. The system will enter a X'EEEE' wait state. This means that DFSMSdss has completed its processing. Note: Follow these steps for each volume to be restored. When you re-IPL MVS, you may need to cold start JES2.