PC Server S/390 and R/390 Application Development System for OS/390 Release 4 (1/98) Thank you for using the Application Development System for OS/390 Release 4. The system is designed to help you get a running MVS system up quickly, so you can concentrate on getting your work done. We have attached a survey to the end of this file for you to communicate your experience and needs to us. Please take a few minutes and let us know how you feel about this CD. CONTENT OF CD-ROM Please see the file OS390R4.PAC on the CD-ROM for a list of the contents of this CD-ROM. And SYS1.README on your OS/390 system for details. The application development system contains the following program products: IBM PC SERVER SYSTEM/390 - ---------------------------------------------------------------------------- OS/390 V2.4 APPLICATION DEVELOPMENT CD - North America Version >>LCD 4-0382-04 ______________________________________________________________ OS/390 R4 BASE 5645-A01 System Services o MVS/ESA SP - BCP - JES2 - OS/390 Base UNIX System Services o ESCON(R) Director support o MICR/OCR support o #Bulk Data Transfer (BDT) base o DFSMSdfp(TM) Version 1 Release 4.0 o EREP/MVS Version 3 Release 5 o High Level Assembler Version 1 Release 2 o ICKDSF Release 16 o ISPF o TSO/E o 3270 PC File Transfer Program 1.1.1 Systems Management o HCD o ICSF Version 2.1 o SMP/E o SystemView for MVS Base v1.1 Application Enablement o Language Environment o SOMobjects for MVS Runtime Library o VisualLift RTE o DCE AS o Encina Executive Toolkit o OS/390 Application Enabling Technology Distributed Computing o DFSMS/MVS Version 1 Release 4 Network File System Feature o DCE Base Services (OSF DCE level 1.1) o DCE Distributed File Service (DFS) (OSF DCE level 1.1.1) Communications Server o FFST/ESA Version 1 Release 2 o VTAM(TM) Version 4 Release 4 o TIOC o TCP/IP Version 3 Release 2 - TCP/IP CICS Sockets - TCP/IP IMS Sockets o TCP/IP for OS/390 UNIX System Services Network Computing Services o Domino Go Webserver 4.6 for OS/390 - NetQuestion - ICSS 2.2 o Lan Services - LANRES/MVS - LAN SERVER for MVS - OSA Support Facility Release 1.2 UNIX System Services o OS/390 UNIX System Services Application Services o OS/390 UNIX System Services Shell and Utilities o OS/390 UNIX System Services Debugger Softcopy Publications Support o BookManager(R) READ R3 o Softcopy Print Solutions and Fonts o BookManager BookServer Version 2.1 o GDDM Version 3 Release 2 (including PCLK and OS/2 Link) Plus the following optional features: System Services o JES3 o Bulk Data Transfer (BDT) File-to-File o Bulk Data Transfer (BDT) JES3 SNA NJE Systems Management o DFSMSdss(TM) Version 1 Release 4 o DFSMShsm(TM) Version 1 Release 4 o DFSMSrmm(TM) Version 1 Release 4 o RMF o SDSF o HCM Security Server o DCE Security Server at OSF DCE level 1.1 o RACF Application Enablement o C/C++ (with Debug tool) o DFSORT Release 13 o GDDM-PGF Version 2 Release 1.3 o GDDM REXX Version 3 Release 2 o HLASM Toolkit Version 1 Release 2 o Language Environment Data Decryption (DES) - North America only o SOMobjects for MVS Application Development Environment(ADE) o VisualLift ADE Version 1.1.2 o IP Printway/Netspool (PSF/MVS Version 2.2) Distributed Computing o DCE User Data Privacy (DES) North America only Communications Server o TCP/IP Kerberos DES Version 3 Release 2 North America only o TCP/IP Network Print Facility Version 3 Release 2 o TCP/IP Offload to OS/2 Version 3 Release 2 Network Computing Services o Domino Go Webserver 4.6 for OS/390 ES - ICSS 2.2 NA Secure Softcopy Publications Support o BookManager BUILD Release 3 Plus the following additional program products: o ADSM for MVS V2R1 5655-119 o ADSM OE Client V2R1 5655-119 o DITTO/ESA for MVS V1R2 5655-103 o MQSeries for MVS/ESA R1.1.4 5695-137 o Netview CS V3 5655-007 o VisualGen V1R1 5648-078 o VisualLift V1R1.1 5648-109 o Print Service Facility V2R2 5695-040 o COBOL for OS/390 V2R1 5648-A25 o IBM PL/1 for MVS/ESA V1R1.1 5688-235 o Cooperative Dev Environ/370 V1R2 5688-194 o CICS/ESA V4.1 5655-018 o CICS Web Interface (opt on R4) o IMS/ESA Transaction & DB Server V5 5655-158 o Database 2 (DB2) V5 5655-DB2 o DB2 Perf. Monitor V4R1 5655-102 o QMF V3R2 5706-254 o Internet Bonus Pak II 5655-156 o REXX Compile/370 R3.0 5695-013 o REXX Library 5695-014 NOTE: If you require additional features for MQSeries you will need to order the latest release 1.2. It was not available at the time of this build. BUILD STRUCTURE --------------- This system has been built specially for the PC Server System/390 from a ServerPak. It has been designed for ease of system software replacement . It resides on these emulated 3390 DASD volumes: o OS39R4 This 3390-3 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 (Consolidated 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 A80, and is defined to MVS as device number A80. o OS3R4A This 3390 minidisk of 1500 cylinders is an extension of the SYSRES volume OS39R4. It is also required for IPL. Release 4 utilizes the extended indirect cataloging feature with &SYSR2 in the master catalog representing OS3R4A. This volume is set up in the DEVMAP (Device Map) as address A82, and is defined to MVS as device number A82. o OS39D4 These 3390-3 volume contains the base MVS system software distribution libraries. It contains the 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 requires 1,091,866,624 bytes of storage. OS39D4 volume is set up in the DEVMAP as address A81, and defined to MVS as device number A81. o OS39H4 This 3380 minidisk (550 Cyl) volume contains all HFS files for OpenEdition components of OS/390 and other products. It is SMS-managed. This volume need not be present to IPL, but is required for OpenEdition, TCPIP, and ICSS. This volume is set up in the DEVMAP as address 124, and defined to MVS as device number 124 with 550 cylinders. 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(OS390.Master.Catalog), the SMP/E Global Zone CSI (MVS5.GLOBAL.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. o P390DX This 3390-3 volume contains the database product system software target and distribution libraries for CICS, IMS, and DB2. This volume also contains 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. >> This volume requires 1,091,866,624 bytes of storage. This volume requires 1,897,620,992 bytes of storage. This volume is set up in the DEVMAP as address A83, and defined to MVS as device number A83. If you are migrating from a previous release the address of P390DX has changed. You will have to manually remove the old reference from your DEVMAP map if you are migrating. For example: SYS1.SDFHAUTH for CICS 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 OS39R4. 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(PRODDOC)): o Only IBM-supplied system software should reside on OS39R4, OS3R4A and OS39D4. These volumes are intended to be replaced. You should try to use alternatives 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. And back-up your system on a regular scheduled basis. 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 in dataset SYS1.MIGRATE.R4 on OS39R4. This migration process is described in MIGRATE.DOC on this CD-ROM and in SYS1.MIGRATE.R4. ****************************************************** ***** Back-up your system before migrating. ***** ****************************************************** 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 ServerPac. For more information, please see the SYS1.README data set. All MVS products are installed at minimum through the end of the ServerPac generated jobs, and service from the service tape has been RECEIVEd (existing customers can RECEIVE this service using migration job MIGSVC) All CICS and DBS products are installed through the end of the CBIPO Installation Guide. Note that most CICS and DBS products have had some customization done to them. They are ready for use. Please review SYS1.README(DBS) for details. Additional details are provided in SYS1.README(INSTALL and CUSTOMIZ). CD-ROM INSTALLATION PROCESS --------------------------- These volumes must be installed on your PC Server System/390. You will need 10.2 Gig to install the complete CD-R package. To begin the install program, insert the OS/390 Release 2 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 OS/390 installed. To accept the default (d:) just press ENTER. You will be prompted to load OS/390 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:\OS390 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 OS/390 R2 Application Development system. ****************************************************************** ***** ***** ***** BACKUP YOUR CURRENT SYSTEM ***** ***** ***** ****************************************************************** NOTE: Migration is designed to step from one release to the next. For example: If you are currently running OS390 Release 2 you must go through the migration to release 3 before you can migrate to release 4. - You should backup (for example, on tape) all of the files in the d:\OS390 subdirectory so you can regress to your current level. - You must manually erase any OS/2 files that need to be erased to make room for new volumes. You may choose to optionally keep or erase SCPMV5.122 and/or P390DX.A83. If you keep your existing 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 - 3 GB) so you might 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 OS39D4, 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 OS/390 CD-ROM disk 1 and open an OS/2 window. 2. Examine the file x:\OS390R4.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 * * \OS390 * OS39R4.ZIP, crc date time OS39R4_1.A80 * etc. 3. Insert the CD-ROM disk containing the desired volume. 4. Type: UNZIP x:\OS390\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 OS/390 ------------- 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 OS/390 system. The first DFT session configured as LOCAL will become the OS/390 Master Console. You must IPL using the SCPMV5 for the load parms and OS39R4 and OS3R4A packs for the system datasets including SYS1.ADCD04.PARMLIB. There are le 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 A80, with load parameter 0122CS. This will do a Cold start to JES2 and reload CLPA. ****** Please review SYS1.README(IPL) for further IPL options. 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 A80 /PARM 0122CS Once you have IPLed OS/390, you can find additional information about the system in the logon messages and in the data set SYS1.README. RESPONSES --------- The system is setup to auto-IPL. You not not have to respond to any messages. There are various options we have set up for you to choose to IPL with. LOADPARM WS does a warm start of JES CS does a CLPA and cold start of JES DC does a CLPA and cold start of JES and accesses/starts Database systems. DB does a warmstart to JES2 and starts the Database systems. 03 concatenates IEASYS parmlib members 00,xx NOTE: JES2 should be cold started the first time you bring up the system. LoadParm is preset to 0122CS. As the system is running, you may wish to do some of the following from the Master 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 ³ $PJES2 ³ +--------------------------------------------------+------------------------+ To bring your system down you can issue S SHUTDOWN from the Master Console. This will bring everything down except RACF and JES2. Issue Force RACF,arm to bring RACF down and $PJES2 to stop JES or just end P/390. JES2 and RACF can handle to crash. MESSAGES -------- During the IPL you may receive these messages regarding JES2 COLD startup. * 12.29.18 *$HASP436 CONFIRM COLD START ON * CKPT1 - VOLSER=SCPMV5 DSN=SYS1.HASPCKPT * CKPT2 - NOT IN USE * SPOOL - PREFIX=SCPMV DSN=SYS1.HASPACE *12.29.18 *02 $HASP441 REPLY 'Y' TO CONTINUE INITIALIZATION OR * 'N' TO TERMINATE IN RESPONSE TO MESSAGE HASP436 Reply: R 02,Y You can log onto the TSO accounts when you see the following message: IKT007I TCAS ACCEPTING LOGONS OUTSTANDING WTOR ---------------- *03 ISTEXC200 - DYN COMMANDS MAY BE ENTERED The following commands may be entered in reply to the outstanding WTOR (message ISTEXC200) issued by the Dynamic XID Exit. Please note that the command will not be processed and another WTOR will not be issued until next time that the exit is called by VTAM. o R XX,RELOAD - The current Dynamic XID mapping table is reloaded. o R XX,DYNTAB= - The Dynamic XID mapping table
becomes the current table. For further information see SYS1.README(VTAM). 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:\OS390\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 ³ ³ +-----------------------+-----------------+----------------------+ ³ 3380K ³ 121 ³ ³ +-----------------------+-----------------+----------------------+ ³ 3380E ³ 122 ³ SCPMV5 ³ +-----------------------+-----------------+----------------------+ ³ 3380K ³ 124 550C ³ OS39H4 ³ +-----------------------+-----------------+----------------------+ +-----------------------+-----------------+----------------------+ # ³ 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 ³ +-----------------------+-----------------+----------------------+ ³ 3390-3 ³ A80 ³ OS39R4 ³ +-----------------------+-----------------+----------------------+ ³ 3390-3 ³ A81 ³ OS39D4 ³ +-----------------------+-----------------+----------------------+ ³ 3390 ³ A82 ³ OS3R4A ³ +-----------------------+-----------------+----------------------+ ³ 3390-3 ³ A83 ³ P390DX ³ +-----------------------+-----------------+----------------------+ * ³ 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. If you receive the following "pop-up" message" +-------------------------------+ ³ P/390 Error ³ +-------------------------------+ ³ AWSLCS350S Open error / ³ ³ AWSLCSDD Device Driver ³ ³ (Dos open / 110 ) ³ +-------------------------------+ this means that you need to activate the LCS3174.SYS device driver in CONFIG.SYS. There is a device entry in DEVMAP for an channel station for TCP/IP-attached. The device type is 3088. - E20 LAN3174: 3480 tape on 4mm DAT cartridge If this entry is active but the device driver is not, you will get the error message. Since TCP/IP is configured on OS390 you should edit CONFIG.SYS with the following characters at the end of your CONFIG.SYS. DEVICE=d:\P390\AWSLCSDD.SYS Re-boot OS/2 and look for the AWSLCS350S message during boot. See the file d:\P390\LCS3172.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.0H) 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:\OS390\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.3 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:\OS390\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 (OS39R3, OS3R3A, OS39D3 P390DX, SCPMV5 are used for the OS/390 Release 3 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. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ADCD Customer Satisfaction Survey Name:_________________________________________________ Company Name: ________________________________________ Address: _____________________________________________ _____________________________________________ Date you received your ADCD __________________________ Are you a first time user _____Yes _____No Did you have any installation problems: ______________ ______________________________________________________ ______________________________________________________ ______________________________________________________ Please list products you would have liked to have been included in this ADCD. ________________________ ____________________ ________________________ ____________________ ________________________ ____________________ ________________________ _____________________ ________________________ _____________________ Please list products contained on this CD that you will never use. ________________________ _____________________ ________________________ _____________________ ________________________ _____________________ ________________________ _____________________ ________________________ _____________________ Please return this form to: Karen M. Miller IBM Corporation - P527 Customized Solutions 522 South Road Poughkeepsie, New York 12601 or e-mail kmmiller@us.ibm.com