Benutzeranleitung / Produktwartung SG24-5360-00 des Produzenten IBM
Zur Seite of 84
IBML RAMAC Virtual Array, Peer-to-Peer Remote Copy, and IXFP/SnapShot for VSE/ESA Alison Pate Dionisio Dychioco Guenter Rebmann Bill Worthington International Technical Support Organization http://www.redbooks.ibm.com This book was printed at 240 dpi (dots per inch).
.
International Technical Support Organization RAMAC Virtual Array, Peer-to-Peer Remote Copy, and IXFP/SnapShot for VSE/ESA January 1999 SG24-5360-00 IBML.
Take Not e! Before using this information and the product it supports, be sure to read the general information in Appendix E, “Special Notices” on page 6 5 . First Edition (January 1999) This edition applies to Version 6 of VSE Central functions, Program Number 5686-066, Version 2, Release 3.
Contents Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii The Team That Wrote This Redbook ......................... vii Comments Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii Chapter 1.
4.3.3 Subsystem Summary Report ........................ 31 Chapter 5. Peer-to-Peer Remote Copy ........................ 33 5 . 1 PPRC and VSE/ESA Software Requirements ................. 34 5 . 2 PPRC Hardware Requirements ......................... 35 5 .
ITSO Redbook Evaluation ................................ 73 Contents v.
vi RAMAC Virtual Array, Peer-to Peer Remote VSE/ESA.
Preface This redbook provides a foundation for understanding VSE/ESA ′ s support for the IBM 9393 RAMAC Virtual Array (RVA). It covers existing support and the recently available IXFP/SnapShot for VSE/ESA and peer-to-peer remote copy support for the RVA.
Comments Welcome Your comments are important to us! We want our redbooks to be as helpful as possible. Please send us your comments about this or other redbooks in one of the following ways: • Fax the evaluation form found in “ITSO Redbook Evaluation” on page 7 3 t o the fax number shown on the form.
Chapter 1. The IBM RAMAC Virtual Array In this chapter we describe the RAMAC Virtual Array (RVA) and the support that VSE/ESA delivers for it. 1. 1 What Is an IBM RAMAC Virtual Array? We explain functions here on a level that is needed to understand how data is stored and organized on an RVA.
The functional track directory (FTD) is the collective name for two tables that together map each functional track to an area in the RVA ′ s physical storage: − Functional track table The functional track table (FTT) contains the host-related pointers, that is, the functional-device-related track pointers of the FTD.
1.2 VSE/ESA Support for the RVA The RVA has been supported by VSE/ESA since its introduction. Because the RVA presents itself as logical 3380 or 3390 direct access storage devices (DASD) attached to a logical 3990 Model 3 storage control, releases of VSE/ESA supporting this logical environment have functioned with the RVA.
Figure 2. Data Snapping. SnapShot creates a logical copy by copying the F TD pointers. Only when either the original or the copied track is updated is its associated FTD pointer changed to point to the new data location. The other FTD pointer remains unchanged.
1.2.3.2 Reporting Functions The IXFP/SnapShot for VSE/ESA reporting functiion displays logical volume utilization, such as space allocated and data stored on the volume. It can also display a summary of the entire subsystem and its NCL, freespace, capacity allocated and used, and the compression and compaction ratio.
6 RAMAC Virtual Array, Peer-to Peer Remote VSE/ESA.
Chapter 2. RVA Benefits for VSE/ESA In this chapter we describe how VSE/ESA ′ s support for the RVA assists in managing storage, affects batch window characteristics, improves application development, and increases the availability of data to the applications running on the host system.
disk architecture, for the same physical space. Thus you can spread data over more volumes to improve performance and data availability of the subsystem. The hardware design of the RVA allows you to upgrade physical disk space to 726 GB without any subsystem outage time and without any change to the logical device configuration.
2.2.1 RAMAC Virtual Array The RVA ′ s virtual disk architecture enables performance improvement in batch processing. This new architecture, coupled with data compression and self-tuning capabilities, improves disk capacity utilization. Data from all logical volumes is written across all the physical disks the array.
• Report generation A large part of batch processing is often dedicated to generating output reports from production data. Often read access only is required by the applications.
All necessary repair actions due to a hardware failure are performed concurrently with customer operation. With the RVA, data availability is also maintained during upgrades. Upgrading disk arrays or cache size can be done concurrently with subsystem operation, without impact or performance degradation.
12 RAMAC Virtual Array, Peer-to Peer Remote VSE/ESA.
Chapter 3. VSE/ESA Support for the RVA In this chapter we cover several utilities and the VSE/ESA Base Programs that support the RVA. 3.1 Prerequisites The RVA has been supported since VSE/ESA Version 1.4 and RVA microcode level of LIC 03.00.00 or higher.
3.2 Volumes With VSE/ESA and the RVA, the subsystem volumes can be defined in different emulation modes. This makes the RVA absolutely adaptable to your needs. The following device type emulations are supported with the RVA: • 3380 model J, K, and KE (KE is a 3380K compatible device with the same number of cylinders (1770) as a 3380E).
3 .4 ICKDSF Once the 9393 is installed and the functional devices are defined on the operator panel (see Appendix A, “RVA Functional Device Configuration” on page 41) the only initialization neede.
16 RAMAC Virtual Array, Peer-to Peer Remote VSE/ESA.
Chapter 4. IXFP/SnapShot for VSE/ESA IXFP/SnapShot for VSE/ESA is a combination of software and RVA microcode functions. It has three main functions, namely, SnapShot, DDSR, and Report. SnapShot is the data duplication utility that exploits the RVA ′ s virtual disk architecture to achieve instantaneous copy without actually using resources.
2. From a batch job You can code the function you want to invoke in the PARM field of the VSE-provided DTRIATTN module and submit the batch job for execution. Figure 7 illustrates the report function (IXFP REPORT) being invoked by a batch job using DTRIATTN.
* $$ JOB JNM=IXFPREXX,CLASS=0,DISP=D // JOB IXFPREXX // LIBDEF *,SEARCH=(PRD2.CONFIG,PRD1.BASE) // EXEC REXX=IXFPREXX,PARM= ′ IXFP REPORT#<your-console-cmd-2> ′ /& * $$ EOJ Figure 9.
Figure 10 displays the RVA subsystem status on the operator console. ixfp report AR 0015 SUBSYSTEM 1321117 AR 0015 *** DEVICE DETAIL REPORT *** AR 0015 <---FUNC. CAPACITY (MB)---> <---CAPACITY (%)---> PHYS. COMP. AR 0015 CUU DEF ALLOC STORED UNUSED ALLOC STORED UNUSED USED(MB) RATIO AR 0015 80E 2838.
4. 1 I XFP SNAP SNAP identifies this command as a SNAP function. Figure 12 shows the syntax of the IXFP SNAP command. ┌┐ ─,───────────────────────.
AR 0015 1I40I READY ixfp snap,80e:80f,vol1=patev3 AR+0015 IXFP23D SNAP FROM CUU=80E CYL= ′0000′ TO CUU=80F CYL= ′0000′ NCYL= ′0 D0B - REPLY ′ YES ′ TO PROCEED 15 yes AR 0015 IXFP.
4.1.2 A Range of Cylinders You copy a range of cylinders by identifying the device address or VOL1 label of the source and target in the IXFP SNAP command. In addition, the decimal start cylinder (scyl) and end cylinder (-scyl) or number of cylinders (,ncyl) are specified in parentheses and appended to the source specification.
The source and the target device must be of the same type and must be within the same RVA subsystem. (If you are using test partitions, the source and the target must also be in the same partition.
4 .2 IXFP DDSR DDSR identifies this command as a DDSR function. DDSR causes the release of the physical storage space associated with: • Expired files • A total volume • A range of cylinders •.
Notes: When you do DDSR for expired files, VSE performs checking on the online (up) units. DDSR checks only those RVA devices managed by the VSE system.
The NOPROMPT parameter is included to prevent decision-type messages from being issued. Otherwise, decision-type messages are issued for the operator to verify and confirm (similar to Figure 16). Notes: The device should belong to the RVA subsystem managed by the VSE system.
┌┐ ── ─────── ──IXFP─ ─ ── ─ ─ ─REPORT ─ ── ┴ ┬┬ ───── ────────────────────────.
ixfp report AR 0015 SUBSYSTEM 1321117 AR 0015 *** DEVICE DETAIL REPORT *** AR 0015 <---FUNC. CAPACITY (MB)---> <---CAPACITY (%)---> PHYS. COMP. AR 0015 CUU DEF ALLOC STORED UNUSED ALLOC STORED UNUSED USED(MB) RATIO AR 0015 80E 2838.
STORED This field contains the percentage of the defined functional capacity that contains stored data (occupying disk array storage) for the device or subsystem.
4.3.2 Device Summary Report CAPACITY This column covers the capacity groups that are being differentiated. <-----TOTAL-----> This column covers the total capacity in megabytes that has been allocated to the appropriate group in that line. The capacity is the sum of all the devices that were selected for the report.
32 RAMAC Virtual Array, Peer-to Peer Remote VSE/ESA.
Chapter 5. Peer-to-Peer Remote Copy In this chapter we describe the VSE/ESA support for the RVA and the PPRC. As part of the continuing effort to meet customer requirements for 24-hour 7-day availability, the RVA Model T82 provides remote copy for disaster and critical volume protection.
Figure 20 on page 34 shows the data flow between the host and the two RVAs. This would be the sequence of a write operation to the primary RVA: 1 . Th e host application issues a write request to a file, a nd t he VSE/ESA supervisor converts the request to a start subchannel request to the RVA.
5. 2 PPRC Hardware Requirements The hardware requirements for both the primary and secondary RVAs to support PPRC are: • RVA Model T82 • Feature code 7001 • PPRC-enabling LIC (LIC level T04.05.xx is the minimum level) • Remote Service capability Note: We recommend that 4 GB of cache be installed on the RVAs to maximize performance.
5.4 SnapShot Considerations The RVA provides the unique ability to combine SnapShot functions with PPRC functions. There are some considerations regarding the interaction of SnapShot with volumes that are part of a PPRC pair. You cannot use SnapShot to copy data onto any volume that is part of a PPRC pair.
In the examples that follow, the short form of some of the parameters is used. The long form of these parameters is: • NoVeriFY • PRIMary • SECondary • UNITaddress 5.5.1 Setting Up PPRC Paths and Pairs The sequence of tasks for setting up PPRC at the primary site is: 1.
PPRCOPY SUSPEND(SEC) UNIT(D48) PRIM(X ′0057′,7390007, X ′07′) SEC(X ′053 F ′,7390014, X ′0 F ′) 2. Check o n t h e secondary device, using QUERY a t t h e recovery site: PPRCOPY QUERY UNIT(D8C) 3.
5.6.1 Determining the Logical Control Unit Number for RVA You can calculate the LCU number by using the CUADD value used in the IOCP configuration for each LCU.
40 RAMAC Virtual Array, Peer-to Peer Remote VSE/ESA.
Appendix A. RVA Functional Device Configuration The procedure presented here describes the steps to configure functional devices through the 9393 operator panel. Figure 21 shows the steps required to get to the Functional Device Configuration screen. Figure 21.
Figure 22. Functional Device Configuration Screen CD23 1. Move t h e cursor up or down to select the device you want to modify and press Enter to get to Modify Functional Device screen CD32 (Figure 23). Figure 23. Modify Functional Device Screen CD32 2 .
Appendix B. IXFP Command Examples In this appendix we present the syntax and use of the various IXFP commands. B.1 SNAP Command In this section we present examples of the IXFP SNAP command. The command syntax is followed by examples of using the command.
access method (SAM) files, however, can be relocated to a different, single extent disk location on the target device. In this case, the tcyl operand must be supplied, but the device must not be a VM partial pack minidisk. The proper label information (single FORMAT-1 label) will be created and added to the target VTOC.
NOPROMPT Prevents decision-type messages from being issued. Some messages require an operator reply before the specified function is initiated. The specification of the NOPROMPT keyword causes the system to bypass this decision-type message and initiates the function without any additional notice.
ixfp report AR 0015 SUBSYSTEM 1321117 AR 0015 *** DEVICE DETAIL REPORT *** AR 0015 <---FUNC. CAPACITY (MB)---> <---CAPACITY (%)---> PHYS. COMP. AR 0015 CUU DEF ALLOC STORED UNUSED ALLOC STORED UNUSED USED(MB) RATIO AR 0015 80E 2838.
Notes: In Figure 25, in the DEVICE DETAIL REPORT, the data stored for device 80F reflects snapping the data from 80E. Also, the physical used capacity reflects its source on device 80E. The key indicator is the NET-CAPACITY-LOAD (%), which shows that the PROD capacity of the RVA has remained constant at 51.
ixfp snap,80e(dsn= ′ test.data.1 ′):80 f(1000),noprompt AR 0015 IXFP22I SNAP TO CUU= 80F STARTED AT 18:52:48 11/17/1998 AR 0015 IXFP20I SNAP FUNCTION COMPLETED AT 18:52:48 11/17/1998 AR 0015 1I40I READY ixfp snap,80e(dsn= ′ test.
B.2 DDSR Command In this section we present examples of the IXFP DDSR command. Remember: Before you can use the DDSR option against a volume, you must bring it offline by using the DVCDN VSE/ESA command.
UP (DVCUP) state, the file will be deleted unconditionally and the space returned to the RVA freespace. I f the device is DOWN (DVCDN), the command will be rejected and an error message provided. Processing multivolume files is the responsibility of the operator, such that the DDSR command should be repeated for all volumes containing file extents.
ixfp report,80f AR 0015 SUBSYSTEM 1321117 AR 0015 *** DEVICE DETAIL REPORT *** AR 0015 <---FUNC. CAPACITY (MB)---> <---CAPACITY (%)---> PHYS. COMP. AR 0015 CUU DEF ALLOC STORED UNUSED ALLOC STORED UNUSED USED(MB) RATIO AR 0015 80F 2838.
ixfp report,80e,80f AR 0015 SUBSYSTEM 1321117 AR 0015 *** DEVICE DETAIL REPORT *** AR 0015 <---FUNC. CAPACITY (MB)---> <---CAPACITY (%)---> PHYS. COMP. AR 0015 CUU DEF ALLOC STORED UNUSED ALLOC STORED UNUSED USED(MB) RATIO AR 0015 80E 2838.
and they were all on channel 8, ″ IXFP REPORT,8 ″ would show all the devices in the RVA, because a storage control address was not specified. Note: The REPORT function, if used under VM, only works for full-pack minidisks or dedicated devices. B.3.
ixfp report AR 0015 SUBSYSTEM 1321117 AR 0015 *** DEVICE DETAIL REPORT *** AR 0015 <---FUNC. CAPACITY (MB)---> <---CAPACITY (%)---> PHYS. COMP. AR 0015 CUU DEF ALLOC STORED UNUSED ALLOC STORED UNUSED USED(MB) RATIO AR 0015 80E 2838.
INIT SYSNAME(SYS004) NOVERIFY PURGE VOLID(PATEV1) /* // ASSGN SYS004,80F,SHR // EXEC ICKDSF,SIZE=AUTO INIT SYSNAME(SYS004) NOVERIFY PURGE VOLID(PATEV2) /* /& Figure 37 shows the console log from the above job stream. Notice that we used DDSR to free any extraneous space on the disks.
ixfp report AR 0015 SUBSYSTEM 1321117 AR 0015 *** DEVICE DETAIL REPORT *** AR 0015 <---FUNC. CAPACITY (MB)---> <---CAPACITY (%)---> PHYS. COMP. AR 0015 CUU DEF ALLOC STORED UNUSED ALLOC STORED UNUSED USED(MB) RATIO AR 0015 80E 2838.
/* // DLBL OUTPUT, ′ TEST.DATA.1 ′,1998/300, SD // EXTENT SYS005,PATEV1,1,1,135,450 // LOG * BUILD EXPIRED SEQUENTIAL FILE ON 80E * 5,000 RECORDS, 4,000 BYTES LONG, ″1″ FILL CHARACTER // NOLOG.
ixfp report AR 0015 SUBSYSTEM 1321117 AR 0015 *** DEVICE DETAIL REPORT *** AR 0015 <---FUNC. CAPACITY (MB)---> <---CAPACITY (%)---> PHYS. COMP. AR 0015 CUU DEF ALLOC STORED UNUSED ALLOC STORED UNUSED USED(MB) RATIO AR 0015 80E 2838.
Appendix C. VSE/VSAM Considerations VSE/VSAM support is not included in IXFP/SnapShot for VSE/ESA. This does not mean however that you cannot take advantage of IXFP/SnapShot for VSE/ESA with VSE/VSAM data sets.
Warning This approach may not work with VSAM files that specify share options 2 or 4 . The reason for the problem here is that, with SHROPTN(2), or SHROPTN(4), VSE/VSAM ′ s method of enqueuing the file (to protect it during a write) uses the file ID of the VSAM catalog and the volume serial number of the volume.
LPAR to a test LPAR. We would quiesce the files as above. And we would also make the SnapShot copy. But, this time, the volume serial number of the source would be retained on the target. Because the target volume for a SNAP copy is always in a DVCDN condition, the duplicate volume serial number would not interfere with the production system.
62 RAMAC Virtual Array, Peer-to Peer Remote VSE/ESA.
Appendix D. IOCDS Example IOCDS must have an LCU defined for each group of 64 functional devices. Each LCU should have two CNTLUNIT macros, one for each cluster.
64 RAMAC Virtual Array, Peer-to Peer Remote VSE/ESA.
Appendix E . Special Notices This publication is intended to help IBM, Business Partner, and customer personnel understand how VSE/ESA provides support for the RAMAC Virtual Array.
operating environments may vary significantly. Users of this document should verify the applicable data for their specific environment. Reference to PTF numbers that have not been released through the normal distribution process does not imply general availability.
Appendix F. Related Publications The publications listed in this section are considered particularly suitable for a more detailed discussion of the topics covered in this redbook. F.1 International Technical Support Organization Publications For information on ordering these ITSO publications see “How to Get ITSO Redbooks” on page 6 9 .
68 RAMAC Virtual Array, Peer-to Peer Remote VSE/ESA.
How to Get ITSO Redbooks This section explains how both customers and IBM employees can find out about ITSO redbooks, redpieces, and CD-ROMs. A form for ordering books and CD-ROMs by fax or e-mail is also provided. • Redbooks Web Site http://www.redbooks.
IBM Redbook Fax Order Form Fax your redbook orders to: Please send me the following: United States (toll free) 1-800-445-9269 Canada 1-403-267-4455 Outside North America (+45) 48 14 2207 (long distanc.
Index B batch application processing 10 data set reorganization 9 incremental backup 9 interim backup 10 report generation 1 0 C catalog implications 4 CKD 1 compaction 2 compression 2 configuration d.
PPRC (continued) distance 3 3 hardware requirements 3 4 operation 3 3 PPRCOPY command 3 5 recovery 3 7 SnapShot considerations 36 software requirements 3 4 PPRCOPY command parameters 3 5 R REPORT comm.
ITSO Redbook Evaluation RAMAC Virtual Array, Peer-to-Peer Remote Copy, SG24-5360-00 Your feedback is very important to help us maintain the quality of ITSO redbooks. Please complete this questionnaire and Fax it to: USA International Access Code + 1 914 432 8264 or: • Use the online evaluation form found at http://www.
SG24-5360-00 Printed in the U.S.A. RAMAC Virtual Array, Peer-to-Peer Remote Copy, SG24-5360-00 and IXFP/SnapShot for VSE/ESA IBML.
Ein wichtiger Punkt beim Kauf des Geräts IBM SG24-5360-00 (oder sogar vor seinem Kauf) ist das durchlesen seiner Bedienungsanleitung. Dies sollten wir wegen ein paar einfacher Gründe machen:
Wenn Sie IBM SG24-5360-00 noch nicht gekauft haben, ist jetzt ein guter Moment, um sich mit den grundliegenden Daten des Produkts bekannt zu machen. Schauen Sie zuerst die ersten Seiten der Anleitung durch, die Sie oben finden. Dort finden Sie die wichtigsten technischen Daten für IBM SG24-5360-00 - auf diese Weise prüfen Sie, ob das Gerät Ihren Wünschen entspricht. Wenn Sie tiefer in die Benutzeranleitung von IBM SG24-5360-00 reinschauen, lernen Sie alle zugänglichen Produktfunktionen kennen, sowie erhalten Informationen über die Nutzung. Die Informationen, die Sie über IBM SG24-5360-00 erhalten, werden Ihnen bestimmt bei der Kaufentscheidung helfen.
Wenn Sie aber schon IBM SG24-5360-00 besitzen, und noch keine Gelegenheit dazu hatten, die Bedienungsanleitung zu lesen, sollten Sie es aufgrund der oben beschriebenen Gründe machen. Sie erfahren dann, ob Sie die zugänglichen Funktionen richtig genutzt haben, aber auch, ob Sie keine Fehler begangen haben, die den Nutzungszeitraum von IBM SG24-5360-00 verkürzen könnten.
Jedoch ist die eine der wichtigsten Rollen, die eine Bedienungsanleitung für den Nutzer spielt, die Hilfe bei der Lösung von Problemen mit IBM SG24-5360-00. Sie finden dort fast immer Troubleshooting, also die am häufigsten auftauchenden Störungen und Mängel bei IBM SG24-5360-00 gemeinsam mit Hinweisen bezüglich der Arten ihrer Lösung. Sogar wenn es Ihnen nicht gelingen sollte das Problem alleine zu bewältigen, die Anleitung zeigt Ihnen die weitere Vorgehensweise – den Kontakt zur Kundenberatung oder dem naheliegenden Service.
