View
55
Download
5
Category
Preview:
Citation preview
TS7700 Bits and Pieces
TS7700 User Day
29. November 2016
Katja Denefleh
ATS – European Competency Center
IBM SystemsIBM Systems
Organisation first
New Whitepaper for Performance is released (V2)
Whitepaper and Information in Techdocs are not all in „Virtualization Engine“ any more – please
use also TS7700
| 2
IBM SystemsIBM Systems
Organisation - Requirement gathering
The next „try“ – a new approach for requriement gathering
Every 2 month, the key „CTS“ employes are invited to a requirement gathering meeting.
In this meeting, the requirement will be discussed internally by region (EMEA, AP, AG) and be
prioritized.
Then the host of this meetings will have a meeting to prioritize and discuss these requriements
worldwide with development participation.
Development will discuss new ideas with the host – and they will transport this information to the
key CTS – for input.
So we try to give more customer feedback into development, and on the other hand, by
worldwide participation, we try to get more transparency for future deliverance.
Please support us in that process – Talk to your CTS !
Without your input – we dont know what you really need.
This is a european initiative - help us to make that a success. BUT ... No promises !
| 3
IBM SystemsIBM Systems
Housekeep and the TS7700
RMM does a normal „housekeep“ processing – volumes expire, release, release confirmed,
scratch
RMM „update“ the TCDB, and the update is transferred via OAM to the TS7700
•OAM does not need to be up and running – however, this is NOT recommended.
•The TCDB switch from PRIVATE to SCRATCH status
•The TS7700 change the category for the volume from the „Private“ in the DEVSUPxx to the MEDIA1 or
MEDIA2 category from the DEVSUPxx where the housekeep runs
•Housekeep does not send „all scratch“ volumes, but only the ones which are expired in this run
•The housekeep does not change the ownership of a volume.
The Volume in the TS7700 is not deleted, and all information are kept, as long
•The volume is not overwritten (when no expire delete is set)
•The expire delete timer is elapsed
•Then all information are deleted, also the constructs.
| 4
IBM SystemsIBM Systems
OA48240 – speed up housekeep
•OA48240: New Function - Enhancement to limit the number of I/O calls to the library during return to scratch
processing
•Today this call is made during return to scratch processing (private to scratch transitions) for each volume
being returned to scratch. With this call disabled, the category count call (and scratch threshold processing)
is still done during job procesing (scratch to private transitions).
•To disable the category count call:
• LIBRARY DISABLE,CATCOUNT
•To re-enable the category count call for volumes beingreturned to scratch, issue the following operator
command:
• LIBRARY RESET,CATCOUNT
•With this I/O call disabled the category count (and scratch threshold processing) is still obtained every ten
minutes. It is only applicable for private to scratch.
| 5
IBM SystemsIBM Systems
SAA ... A reminder
SAA is wonderful – if you want to route different workload to different clusters.
Enabling SAA is usually without any problems
In our redbook is a wrong description (just found out Friday) – and we do our best to correct that
before it is released
Once SAA is enabled, and none of the SAA clusters is available, the Mount can not be satisfied
from other clusters.
Therefore IBM recommends to disable SAA before maintenance
However, if during this situation an OAM restart or an IPL occur, it might happen that the SAA is
enabled again, this is not picked up in all of the attached z/OS LPARs.
If so, please do an OAM restart on this specific system
•There is no failure message – so you will see that SAA is not working perfectly, only because you see
remote mounts, wrong I/O selection, etc. In the log and VEHSTATS
| 6
IBM SystemsIBM Systems
SAA ...SAA is not TVC selection
Usually, SAA and TVC selection looks the same, because your copy policies and the „Scratch
mount candidates“ are in sync:
In this case, SAA and TVC selection are the same.
| 7
IBM SystemsIBM Systems
SAA ...SAA is not TVC selection
If Cluster 0 is not available – or just the devices are offline - , you will see the following:$HASP373 DENETT1 STARTED - INIT 1 - CLASS A - SYS
IEF403I DENETT1 - STARTED - TIME=14.42.20
IEF244I DENETT1 STEP0 - UNABLE TO ALLOCATE 1 UNIT(S) 503
AT LEAST 1 OFFLINE UNIT(S) NEEDED.
IEF877E DENETT1 NEEDS 1 UNIT(S) 504
FOR STEP0 AUS1
LIBRARY: HYDRAG LIBRARY STATUS: ONLINE
OFFLINE
2200-22FF
However, that behavior change, if you change the SAA selection, but not change the Copy
policy:
| 8
IBM SystemsIBM Systems
SAA ...SAA is not TVC selection
If Cluster 0 devices are offline, but the cluster is available – then the job will run and use a
remote mount to store the data in cluster 0 cache.
If Cluster 0 is not available (service mode, defekt), but cluster 1 devices are online, you will see
the following error:
IEF233A M 2559,PRIVAT,SL,DENETT1,STEP0,DENEKA.HG.DUMP0
CBR4195I LACS retry possible for job DENETT1: 000
IEE763I NAME= CBRLLACS CODE= 140394
CBR4000I LACS WAIT permanent error for drive 2559.
CBR4171I Mount failed. LVOL=A10001, LIB=HYDRAG, PVOL=??????, RSN=10.
IEE764I END OF CBR4195I RELATED MESSAGES
60 CBR4196D Job DENETT1, drive 2559, volser SCRTCH, error code 140394. Reply 'R‘
| 9
IBM SystemsIBM Systems
VEHSTATS ...
Currently we are fixing a lot of minor issues in VEHSTATS
•Unclear „migrate“ or „premigrate“ statements
•Missing Summary fields (H30TVC „all cache content“)
•Unprecise documentation
• E.g. When data is gathered (end of interval, average, etc.)
• In Statistics whitepaper or decoder
Therefore we are releasing more updates than usual
Please help us during this quality program
• Install the newest load moduls
•Let me know, if you find a problem
| 10
IBM SystemsIBM Systems
DR-Flash Testing
If you plan to do a DR Flash, please
•Ensure that all microcodes are on the same level.
•Wait that every command is processed and acknowledge by the system before you submit the DRSETUP
command.
Known issues
• If you eject the DR volumes as part of the process, please ensure before the eject, that all volumes have
definitely the category you expected. Otherwise, you may run into the situation, the this eject of a „write
protect“ volume will be not executed, but put the volume in transit to RMM. This can be fixed by changing
the location in RMM again.
• VPD exchanging may work not properly under certain circumstances. In this case, the DR Flash might not
be disabled for all clusters in a DR Family. If you experience this, please involve CE/PFE.
| 11
IBM SystemsIBM Systems
Bits and pieces MIH-IOS and RUN copies
•Under very seldom circumstance, a RUN Copy can be converted to a Deferred, without being flagged as
IMMED-Deferred.
• RUN copy experience an MIH event -with the according IOS message.
• Copy was waiting for the copy - but not yet actively processed.
•Ensure that the 45 MIH is set if you use RUN.
If you use „DISABLE,COPY“ - all remote mounts are still allowed
•That is not only SYNC, but also if you would have „DN“ – and „N“ would be used as the I/O cluster, and the
links from either CL0 or CL1 are disabled. The remote mount would still be processed.
Autoremoval
•Please be aware, that if you allow autoremoval in a cluster, you will reduce the number of the available (and
originally requested) copies.
• If all your copies are placed in disk-only or TS7700T CP0, you could end up in a situation, where
• Only one valid copy left
• All valid copies are only in one location
•Please keep that in mind if you use Autoremoval
| 12
IBM Systems
IBM Systems
IBM SystemsIBM Systems
Disclaimers
15
Copyright© 2015 by International Business Machines Corporation.
No part of this document may be reproduced or transmitted in any form without written permission from IBM Corporation.
The performance data contained herein were obtained in a controlled, isolated environment. Results obtained in other operating environments may vary significantly. While IBM has reviewed each item for accuracy in a specific situation, there is no guarantee that the same or similar results will be obtained elsewhere. These values do not constitute a guarantee of performance. The use of this information or the implementation of any of the techniques discussed herein is a customer responsibility and depends on the customer's ability to evaluate and integrate them into their operating environment. Customers attempting to adapt these techniques to their own environments do so at their own risk.
Product data has been reviewed for accuracy as of the date of initial publication. Product data is subject to change without notice. This information could include technical inaccuracies or typographical errors. IBM may make improvements and/or changes in the product(s) and/or programs(s) at any time without notice. Any statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only
References in this document to IBM products, programs, or services does not imply that IBM intends to make such products, programs or services available in all countries in which IBM operates or does business. Any reference to an IBM Program Product in this document is not intended to state or imply that only that program product may be used. Any functionally equivalent program, that does not infringe IBM's intellectually property rights, may be used instead. It is the user's responsibility to evaluate and verify the operation of any on-IBM product, program or service.
THE INFORMATION PROVIDED IN THIS DOCUMENT IS DISTRIBUTED "AS IS" WITHOUT ANY WARRANTY, EITHER EXPRESS OR IMPLIED. IBM EXPRESSLY DISCLAIMS ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT.
IBM shall have no responsibility to update this information. IBM products are warranted according to the terms and conditions of the agreements (e.g. IBM Customer Agreement, Statement of Limited Warranty, International Program License Agreement, etc.) under which they are provided. IBM is not responsible for the performance or interoperability of any non-IBM products discussed herein.
Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products in connection with this publication and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
The provision of the information contained herein is not intended to, and does not, grant any right or license under any IBM patents or copyrights. Inquiries regarding patent or copyright licenses should be made, in writing, to:
IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.
IBM SystemsIBM Systems
Trademarks
16
The following terms are trademarks or registered trademarks of the IBM Corporation in either the United States, other countries or both.– IBM, GDPS, Spectrum Storage, Spectrum Archive, Spectrum Scale, System Storage, System z, Virtualization Engine
Linear Tape File System, Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo are trademarks of HP, IBM Corp. and Quantum in the U.S. and other countries.
Other company, product or service names may be trademarks or service marks of others
Recommended