Home

Managing HSC and VTCS 7.1

1. SNAPSHOT PIT COPY 2 COPY EXEC PGM SLUPCOPY REGION 4M 3 STEPLIB DD 4 SLSCNTL DD 5 SYSPRINT DD 6 SYSTERM DD TRANS 7 SYSMDUMP DD 8 OUTSNAP DD PARM HSCX COPY SNP OPT RR DSN XXXX LINKLIB DISP SHR DSN XXXX S08610 SLSCNTL DISP SHR SYSOUT SYSOUT DSN HSC SACLINK DISP SHR DSN XXXX S08610 SYSMDUMP DISP DELETE CATLG UNIT SYSALLDA SPACE CYL 100 RLSE VOL SER SW8D12 DSN XXXX SOS610 SNAPPED LIKE XXXX SOS610 SLSCNTL DISP CATLG DELETE VOL SER SW8D12 UNIT SYSALLDA SPACE CYL 25 9 SYSIN DD 700011 XXXX LAST ACCESS AT 12 05 57 ON THURSDAY MARCH 29 2007 2361 ALLOC FOR XXXXPSNP COPY IEF2371 3EC4 ALLOCATED TO STEPLIB IEF2371 8A45 ALLOCATED TO SLSCNTL IEF2371 JES2 ALLOCATED TO SYSPRINT IEF2371 JES2 ALLOCATED TO SYSTERM IGD100I 8D12 ALLOCATED TO DDNAME SYSMDUMP DATACLAS IGD100I 8012 ALLOCATED TO DDNAME OUTSNAP DATACLAS IEF2371 JES2 ALLOCATED TO SYSIN IEF2371 3D5C ALLOCATED TO SYS00001 IEF285I SYS1 PARMLIB KEPT IEF285I VOL SER NOS XXXXRS IEF2371 3D5C ALLOCATED TO SYS00002 IEF285I SYS1 PARMLIB KEPT IEF285I VOL SER NOS XXXXRS IEF2371 3D5C ALLOCATED TO SYS00003 IEF2371 8800 ALLOCATED TO SYS00004 2851 SYS1 PARMLIB KEPT IEF285I VOL SER NOS XXXXRS IEF2371 8A45 ALLOCATED TO SYS00005 IEF2371 8D12 ALLOCATE
2. E22915 01 Revision 01 SLUPCOPY Backs up the primary CDS point in Using the SLUPCOPY Utility to time Back Up the CDS on page 11 UNSELECT Resets volume selected status Errant and Selected Volumes on page 54 VOLRPT Provides physical volume reports Using a Volume Report on page 54 Chapter 1 3 TABLE 1 1 The HSC Toolkit This tool does the following and is used to do these tasks Diagnostics Generalized Trace Facility The Generalized Trace Facility GTF Using Software Diagnostics on provides a low level history of the page 72 recent past Supervisor Call and Abnormal SVC and ABEND dumps are taken End Dumps ABEND where appropriate to diagnose software failures Error Recording Data Set Records Software failures are logged into these error recording data sets 4480 Cartridge Subsystem and 3278 Terminal Subsystem Error Recording Data Set ERDS records are written by MVS routines HSC LIST Command LIst command is used to display an HSC data structure and to provide for diagnostic support for the HSC Use this command under the direction of StorageTek support personnel 4 Managing HSC and VTCS April 2011 Revision 01 E22915 01 TABLE 1 1 The HSC Toolkit This tool does the following and is used to do these tasks HSC Performance Tools Activities report Produces a detailed report identifying performance values for va
3. Category 3 Has been Cross TapePlex Replicated The first remote TapePlex encountered that contains a copy of the VTV is used to recover the VTV If you requested recovery commands EEXPORT ULINKMVC commands are generated These commands must be run from the remote TapePlex where the VTV currently resides Comments in the COMMANDS data set show the TapePlex where these commands must be run The command unlinks the VTV from the lost or damaged MVCs and then Cross TapePlex Replicates the VTV back to the local TapePlex Category 4 Was previously linked to one or more MVC copies that may still contain the VTV data One of the previously linked MVCs is selected as the recovery MVC These MVC copies were found in the log files and may still contain a copy of the VTV You must audit the selected recovery MVC The best previously linked MVC copy to do the recovery from is selected based on the same factors as alternate MVCs If you requested recovery commands AUDIT commands are generated to audit the MVC and to attempt to link it to the VTV MVCMAINT READONLY ON commands are generated for AUDIT MVCs Category 5 Is unrecoverable Unrecoverable copies only existed on the lost or damaged MVCs are no longer selected for recalls or migrates Note If you requested recovery commands MVCMAINT commands are also generated for Categories 1 2 and 3 and 4 These statements mark the lost or damaged MVCs
4. LS7057E MAINLINE DEQ FAILED R1 XXXXXXXX RI5ZXXXXXXXX LS7058E DETACH FAILED R15zXXXXXXXX LS7059E MAINLINE CLOSE FAILED R15zXXXXXXXX 157060 ADRDSSU LOAD FAILED R1 XXXXXXXX RI5ZXXXXXXXX LS7061E FDRSNAP LOAD FAILED R1 XXXXXXXX RI5ZXXXXXXXX 157062 SIBBATCH LOAD FAILED R1 XXXXXXXX R15 XXXXXXXX LS7063E UNABLE TO ACQUIRE RESERVE LS7101E LVT ADDRESS DOES NOT POINT TO AN LVT LS7103E ASCB ADDRESS FROM HSC LVT IS ZERO LS7105E DPV EYECATCHER DOES NOT MATCH LS7110E MISSING DD dddddddd LS7150E CDS DPV READ FAILED 15 LS7151E CDS DPV WRITE FAILED R15 XXXXXXxXxX S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S SLS7152E CDS DPV RESTORE FAILED R15zXXXXXXXX E22915 01 Revision 01 AppendixB 161 Vital Diagnostic Information If the AB option is specified and any of the preceding error conditions occurs a Vital Diagnostic Information report is output as part of the SLUPCOPY output eee desee eee eee eee eee eee fee de ee eee eee ee eee e III RII III III IIIS III IAAI III III I IASI IASI eee ee eee eee eee eee e IIIS ISI AI AI ISAS IIA IISA IA IIS SLUPCOPY VERSION 6 20 COPYRIGHT 2006 2007 StorageTek INC ALL RIGHTS RESERVED VITAL DIAGNOSTIC INFO RUN DATE 03 26 07 RUN TIME 14 45 38 SYSTEM NAME XXXX JES NAME JES2 CVT PRODN SP7 0 5 FMID HBB7708 DFAR 03010500 FT14 FF7F737F 56 A0300000
5. SYSPRINT DD SYSOUT SYSMDUMP DD DSN HSC SLUPCOPY SYSMDUMP DISP DELETE CATLG UNIT SYSALLDA SPACE CYL 100 RLSE VOL SER VVVVVV SYSIN DD DSN HSC LIB CNTL PITDSSI DISP SHR HSC LIB CNTL PITDSST COPY DATASET INCLUDE HSC PRIMARY CDS RENUNC HSC PRIMARY CDS HSC PITFLASH CDS FASTREPLICATION REQUIRED CANCELERROR SHARE TOL ENQF TGTALLOC CYL u OUTDYNAM TTTTTT CATALOG FIGURE 2 4 SLUPCOPY DFSMSdss FlashCopy JCL Example The requirements for SLUPCOPY with DFSMSdss FlashCopy are 2 ADRDSSU must be in the system linklist The HSC CDS must reside on IBM hardware with the FlashCopy feature enabled to be eligible for a DFSMSdss FlashCopy operation The source and target data sets must be on the same IBM disk subsystem otherwise a physical copy is attempted Both source and target volumes must be online Volume or data set copy is supported but a data set copy is recommended DFSMSdss must be at DFSMS 1 3 or later this corresponds roughly to OS 390 V1R3 See Implementing ESS Copy Services Redbook for the complete list of FlashCopy pre requisites FlashCopy Version 1 microcode only supports volume FlashCopy 2 FlashCopy Version 2 microcode is required for data set FlashCopy Make sure that the CDS name on the SLSCNTL DD matches the data set names on the INCLUDE parameter and the first RENUNC sub parameter on the DFSMSdss COPY command The SHARE parameter
6. JESTYPE 7 52 ECVT PNAM z OS VRM 010500 PSEQ 01010500 VM NAME XXXXXMVS PROC P302A FF0XXXXX2084 SUBSYSTEM NAME HSCX LVT ADDR 433B1000 SSCT ADDR 00963124 SSVT 433040 0 SUSE 433 1000 SUS2 2445D4C7 FLG1 40000000 HARIKA de ee eee eee eee eee eee ee eee de ee eee III eee eee eee eee eee ee dee ede ee eee ede eee eee de ee eee e dee ee eee SII IIA IIA II IAI III IIIA IAI ISIS A IASI IIIA For a SLS7008E error the HSC subsystem information will be blank This is normal Required Diagnostic Information All of the following information is required before a SLUPCOPY problem can be diagnosed SLUPCOPY output JES log JCL and substitution messages t Allocation deallocation messages SYSPRINT SYSTERM output Vital Diagnostic Information report F System Name LPAR Name Blank if z OS is running as a guest under z VM VM Name Non blank if z OS running as a guest under z VM Operating System Type includes Product name FMID Operating System Release Level JES Name and Type JES2 or JES3 DFSMS release level and feature bytes HSC subsystem information The SLUPCOPY SYSMDUMP data set The SYSLOG listing from 5 minutes before to 5 minutes after the problem occurred 162 Managing HSC and VTCS April 2011 Revision 01 E22915 01 sample Output The following sections show the output from runs of SLUPCOPY E22915 01 Revision 01 Append
7. You use the VTVMAINT utility to change a VTV s Management Class Also note that while you cannot use VTVMAINT to directly change a VTV s Storage Class you can use VTVMAINT to change a VTV s Management Class which can reference a different Storage Class Use only the minimum Storage Classes required to define the policies you want to implement Excessive Storage Classes can impact VSM performance due to the MVC mount dismount overhead incurred In addition an MVC can only contain VTVs in a single Storage Class so excessive Storage Classes can underuse MVC space If you decide to delete a Management Class definition run a VTV Report to make sure that the Management Class is no longer assigned to any VTVs otherwise unpredictable results will occur E22915 01 Revision 01 ChapterG 123 Leading Edge Techniques You Can Do with Management and Storage Classes The following isn t an exhaustive list just the most common tasks you can do with Management and Storage Classes Using the STORclas MEDIA Parameter for MVC Media Preferencing Yes we give you defaults for MVC media preferencing but you can adjust them any way you want For more information see Managing HSC and VTCS 2 Grouping Multiple Workloads on Shared on page 125 This was our introductory example and is a good one if your company owns the data center and you want to optimize use of your available resources by Duplexing critical data
8. 4 Update your POLICY TAPEREQ output parameters as required For example if you created a new Management Class in Step 3 update create your TAPEREQ or POLICY statements to point to the new Management Class 5 Do you need to define VT Vs If so go to Defining VTVs on page 96 Otherwise go to Validating and Applying the Volume Definitions on page 96 E22915 01 Revision 01 Chapter5 95 Defining VTVs To define VTVs 1 Create POOLPARM VOLPARM statements to define the VTVs For example to define two ranges of VTVs for use by hosts MVS1 and MVS2 POOLPARM NAME SYS1VTV1 TYPE SCRATCH VOLPARM VOLSER V5000 V5499 MEDIA VIRTUAL POOLPARM NAME SYS1VTV2 TYPE SCRATCH VOLPARM VOLSER V5500 V5999 MEDIA VIRTUAL 2 Go to Validating and Applying the Volume Definitions on page 96 Validating and Applying the Volume Definitions 1 Run SET VOLPARM to validate the VOLPARM POOLPARM statements SET VOLPARM APPLY NO APPLY NO validates the statements without loading them If you like the results go to Step 2 Otherwise rework your volume definitions then go to Step 2 2 Run SET VOLPARM to load the VOLPARM POOLPARM statements SET VOLPARM APPLY YES 3 Physically enter any real cartridges into the ACS 4 For more information see Entering Cartridges on page 61 96 Managing HSC and VTCS April 2011 Revision 01 E22915 01 Removing MVCs from the Pool Why would you remove MVCs from the
9. COPY EXEC PGM SLUPCOPY REGION 4M PARM 5555 STEPLIB DD DSN HSC LINKLIB DISP SHR SLSCNTL DD DSN HSC PRIMARY CDS DISP SHR SLSVDI DD SYSOUT SYSPRINT DD SYSOUT SYSMDUMP DD DSN HSC SLUPCOPY SYSMDUMP DISP DELETE CATLG UNIT SYSALLDA SPACE CYL 100 RLSE VOL SER VVVVVV SYSIN DD DSN HSC LIB CNTL PITMMM DISP SHR FIGURE 2 1 Example SLUPCOPY JCL All PIT Methods JCL PARM parameter is required and must be specified as follows 5555 0000000000000 Subsystem name 5555 is required and must be specified in positions 1 4 This is the 4 character name that is specified in the IEFSSNxx member of SYSx PARMLIB to define the HSC as a user of the z OS Sub System Interface SSI 5 comma is required in positions 5 and 10 A function FFFF is required and must be specified in positions 6 9 2 COPY performs an actual PIT copy TEST simulates a PIT copy and outputs additional diagnostic messages A PIT copy method MMM is required and must be specified in positions 11 13 2 SNP uses SIBBATCH SnapShot 2 DSS uses ADRDSSU DFSMSdss FDR uses FDRSNAP 2 Options are of course optional and if specified a comma 18 required in position 14 One two or all three options can be specified in positions 15 27 in the form OPT 0 0 03 where 0 05 0 are one or more
10. CUSTB2 ACS 01 MEDIA STK2P MGMT CUSTA MIGPOL CUSTA MGMT NAME CUSTB 5 1 05 2 MGMT NAME PROD MIGPOL LOC FIGURE 6 11 Storage Classes Management Classes for Workload Segregation According to FIGURE 6 11 everything in Management Class PROD should have ended up on 9840 media in the local ACS but in fact they re all on 9940 media in the remote ACS almost as if they were in the wrong Storage Class On closer examination my production Management Class actually looks like this MGMT NAME PROD MIGPOL CUSTA which is not good for another reason because it means my production data is co resident on the same MVCs that are supposed to be dedicated to one of my customers Time to run RECONcil right Well not quite RECONcil only moves VTVs out of the wrong Storage Class and right now according to the way I wrote my Management Class statement CUSTA is the right Storage Class So before run RECONCcil I have to go back and fix the Management Class thusly MGMT NAME PROD MIGPOL LOC E22915 01 Revision 01 Chapter G 131 Now I can run RECONcil as shown in FIGURE 6 10 as follows Move VTVs in Management Class PROD to their updated correct location in Storage Class LOC Set MAXMVC to 60 CONMVC to 8 and ELAPSE to 60 for the RECONcil job RECONCIL EXEC PGM SLUADMIN STEPLIB DD DSN hlq SEALINK DISP SHR SLSPRINTDD SYSOUT SLSIN DD RECON MGMT
11. FIGURE 6 5 Storage Classes for Workload Segregation FIGURE 6 6 defines the following Management Classes Management Class CUSTA specifies the CUSTA Storage Class on the MIGPOL parameter VTCS simplexes VTVs in this Management Classes to only the CUSTA Storage Class 9840 media in the local ACS because that s what this customer wants Customer B wants more protection namely duplexing to the local and remote ACSs so Management Class CUSTB points to both the CUSTB1 and CUSTB2 Storage Classes Finally local ACS 9840 media is just fine for your own production data so that s what Management Class PROD does What probably also do is set up an Archive Policy for this Management Class see Archiving Data on page 129 so I can move it to Deep Storage eventually MGMT NAME CUSTA MIGPOL CUSTA MGMT NAME CUSTB MIGPOL CUSTB1 CUSTB2 MGMT NAME PROD MIGPOL LOC FIGURE 6 6 Management Classes for Workload Segregation FIGURE 6 7 defines tape policies that specify virtual media and respectively assign Management Classes PAY ACCOUNT and PROD POLICY NAME PCUSTA MEDIA VIRTUAL MGMT CUSTA POLICY NAME PCUSTB MEDIA VIRTUAL MGMT CUSTB POLICY NAME PPROD MEDIA VIRTUAL MGMT PROD FIGURE 6 7 Policies for Workload Segregation E22915 01 Revision 01 ChapterG 127 128 Finally FIGURE 6 8 shows the corresponding TAPEREQ statements and policy assignments Data sets with HLQ CUSTA
12. IEF2851 SYS07088 T130622 RA000 XXXXPFDR R0100610 KEPT IEF285I VOL SER NOS SW8A45 IEF1421 XXXXPFDR COPY STEP WAS EXECUTED COND CODE 0012 IEF2851 XXXX LINKLIB KEPT IEF285I VOL SER NOS 50020 IEF2851 XXXX SOS610 SLSCNTL KEPT IEF285I VOL SER NOS SW8A45 IEF2851 XXXX XXXXPFDR JOB07750 D0000102 SYSOUT IEF2851 XXXX SLUPCOPY SYSMDUMP DELETED IEF285I VOL SER NOS SW8D12 IEF2851 XXXX XXXXPFDR JOB07750 D0000101 SYSIN AE E HE AE E E AE E E AE E A E E E E DEVICE DEVICE EXCP DDNAME CLASS ADDRESS COUNT aude lepus STEPLIB DASD 3EC4 00000002 SLSCNTL DASD 8A45 00000004 SYSPRINT JES2 00000000 SYSMDUMP DASD 8D12 00011927 TAPE1 JES2 00000000 SYSIN JES2 00000000 D SW8A45 DASD 8A45 00000004 THSW8A45 DASD 8A45 00000000 AE E E A E E AE E A EROR RE E OE LADLE NREL EEE EE RR IEF3731 STEP COPY IEF3741 STEP COPY SYS 7356K IEF375I JOB XXXXPFDR START 2007088 1306 76 JOB XXXXPFDR STOP 2007088 1306 CPU START 2007088 1306 STOP 2007088 1306 CPU OMIN 00 57SEC SRB OMIN 00 16SEC VIRT OMIN 00 57SEC SRB OMIN 00 16SEC 228K SYS 300K EXT 1808K 1FDROO1 FDR INSTANT BACKUP FDRSNAP VER 5 4 30P INNOVATION DATA PROCESSING DATE 2007 088 PAGE 1 OFDR303 CARD IMAGE SNAP TYPE FDR ENQ OFF FDR303 CARD IMAGE MOUNT VOL SW8AA45 SNAPUNIT 8D14 OFDRO40 VOLUME
13. SLSPRINT DD SYSOUT SLSIN DD LOGUTIL LOGDD LOGIN FOR LOSTMVC MVC DMV509 COMMANDS RECVCMD 116 Managing HSC and VTCS April 2011 Revision 01 E22915 01 2 Review the LOGUTIL FOR LOSTMVC report from Step 1 Select the VTVs you want to recover and rerun LOGUTIL FOR LOSTMVC specifying the VTVs you want to recover from the lost or damaged MVC For example JOBLOGR job account programmer REGION 1024k S1 EXEC PGM SLUADMIN PARM MIXED STEPLIB DD DSN hlq SEALINK DISP SHR LOGIN DD DSN FEDB VSMLMULT LOGFILE OFFLOAD 2 DISP OLD DD DSN FEDB VSMLMULT LOGFILE OFFLOAD 1 DISP OLD DD DSN FEDB VSMLMULT LOGFILE OFFLOAD 0 DISP OLD RECVCMD DD DSN FEDB VSMLMULT RECVCMD DISP CATLG DELETE 77 UNIT SYSDA SPACE CYL 1 1 RLSE DCB RECFM FB LRECL 80 BLKSIZE 27920 SLSPRINT DD SYSOUT SLSIN DD LOGUTIL LOGDD LOGIN FOR LOSTMVC MVC DMV509 VTV DX009 COMMANDS RECVCMD Note If you specify a VTV that was not on the lost or damaged MVC this VTV is ignored If you want to recover all specified VTVs on the damaged MVC continue with Step 3 3 To recover the specified VTV s run the commands in the recovery data set specified in Step 2 Note The commands in the recovery data set should be run using standard SLUADMIN JCL as soon as possible after running FOR LOSTMVC to ensure their accuracy 2 StorageTek recommends that you run the re
14. You can use Storage and Management Classes to group multiple workloads on a shared set of MVCs For example the STORclas statements in FIGURE 6 1 define Storage Classes LOCI LOC2 and 2 STORCLAS NAME LOC1 ACS 00 MEDIA STK1R STORCLAS NAME LOC2 5 00 MEDIA STK1R STORCLAS NAME REM1 ACS 01 MEDIA STK2P ZCART STORCLAS NAME REM2 ACS 01 MEDIA STK2P ZCART FIGURE 6 1 Storage Classes for Workload Grouping FIGURE 6 2 defines the following Management Classes Management Classes PAY and ACCOUNT both specify the LOCI and Storage Classes on the MIGPOL parameter The VTVs in PAY and ACCOUNT therefore are duplexed and grouped on the MVCs defined by Storage Classes LOCI and REMI Management Class PROD specifies the LOC2 and REM2 Storage Classes on the MIGPOL parameter The VTVs in PROD therefore are duplexed and grouped on the MVCs defined by Storage Classes LOC2 and REM2 which are separate from those for PAY and ACCOUNT MGMT NAME PAY MIGPOL LOC1 REM1 MGMT NAME ACCOUNT MIGPOL LOC1 REM1 MGMT NAME PROD MIGPOL LOC2 REM2 FIGURE 6 2 Management Classes for Workload Grouping FIGURE 6 4 defines tape policies that specify virtual media and respectively assign Management Classes PAY ACCOUNT and PROD POLICY NAME PPAY MEDIA VIRTUAL MGMT PAY POLICY NAME PACCOUNT MEDIA VIRTUAL MGMT ACCOUNT POLICY NAME PPROD MEDIA VIRTUAL MGMT PROD FIGU
15. Fortunately VTCS provides detailed information about migration failures as described in the following sections Messages Enhancements on page 140 Display STORCLas on page 141 Enhanced MVC Pool Validation on page 141 2 Enhanced Storage Class Validation on page 142 Messages Enhancements To provide greater detail about migration failures message SLS6700E is replaced by the following messages SLS6853E Migration failed Storage Class stor clas name ACS acs id VTSS vtss name MVCPool poolname is not defined SLS6854E Migration failed Storage Class stor clas name ACS acs id VTSS vtss name no MVCs found for specified media SLS6855E Migration failed Storage Class stor clas name ACS acs id VTSS vtss name no MVCs found for specified media SC ACS SLS6856E Migration failed Storage Class stor clas name ACS acs id VTSS vtss name no usable MVCs found for specified media SC ACS SLS6857E Migration failed Storage Class stor clas name ACS acs id VTSS vtss name no RTDs for requested media and ACS SLS6858E Migration failed Storage Class stor clas name ACS acs id VTSS vtss name all RTDs for requested media and ACS are offline SLS6859E Migration failed Storage Class stor clas name ACS acs id VTSS vtss name unknown reason In addition message SLS6860I is always output after any of the preceding messages are issued to provide details of the Storage Class If applicable SLS6860I also reports any
16. STEP WAS EXECUTED COND CODE 0000 IEF285I XXXX LINKLIB KEPT IEF285I VOL SER NOS 50020 IEF285I XXXX SOS610 SLSCNTL KEPT 174 Managing HSC and VTCS April 2011 Revision 01 E22915 01 Kok kk FO I RI IO IO RIK TOK IK ke ko ke kk oko ke kk ko k ek ke ko ke kk IEF285I VOL SER NOS SW IEF2851 XXXX XXXXPFDR J IEF2851 XXXX SLUPCOPY S IEF2851 VOL SER NOS SW IEF2851 XXXX XXXXPFDR J DDNAME epee Be STEPLIB SLSCNTL SYSPRIN SYSMDUM 1 SYSIN D SW8A4 THSW8A4 FOI I II II III II III II II I IOI II III 6116211102066 START 2007088 1308 IEF3731 STEP COPY IEF3741 STEP COPY STO SYS 7308K IEF375I IEF376I JOB XXXXPFDR STO 1FDROO1 FDR INSTANT OFDR303 CARD IMAGE FDR303 CARD IMAGE OFDRO40 VOLUME IN USE 0 FDROO7 STARTING TIME OF FDR231 FDROO7 ENDING TIME OF OFDR122 OPERATION STATIST FDR122 FDR122 FDR122 FDR122 FDR122 FDR122 FDR122 FDR122 FDR122 FDR122 FDR122 FDROO2 FDR DUMP SUCCESS FDR999 FDR SUCCESSFULLY 8A45 OB07751 D0000102 SYSOUT YSMDUMP DELETED 8D12 OB07751 D0000101 SYSIN DEVICE DEVICE EXCP CLASS ADDRESS COUNT DASD 3EC4 00000002 DASD 8A45 00000003 T JES2 00000000 P DASD 8D12 00000000 JES2 00000000 JES2 00000000 5 DASD 8 45 00000007 5 DASD 8 45 00000000 P 2007088 1308 CPU OMIN 00 03SEC SRB JOB XXXXPFDR START 2007088 1308 P 2007088 1308 CPU P FDRSNAP VER SNAP TYPE FDR ENQ OFF MOUNT VOL SW
17. a a the As Needed Tasks List For example let s say that this is the week you decide to run DELETSCR to zero out a list of scratched VTVs that are tying up major amounts of your valuable VTSS and MVC space Great job well done How long do you think it s going to be before you have to run the same operation Especially if you don t change your delete on scratch policies Answer It might be a day a month or a year but you ll get to do it again No worries however We re here to help with useful procedures to pare down the Must Do Sometime List and as you ve already seen from reading Using the VTCS Dashboard on page 73 if you keep a close eye on your MVC and VTV reports you may not even need a list because they will tell you when it s time to do the Must Do As Needed chores There is also another class of Must Do Sometime chores that are almost policy decisions but we ll include them here because a they re proactive in nature which makes them doubly valuable as Best Practices As Needed chores and b they re operating techniques you can use back out and reintroduce as they benefit or not your shop at any point in time Having said that let s lead off with three of our favorites in this category as described in Doing Demand Space Reclamations Migrations and Recalls on page 90 E22915 01 Revision 01 89 Doing Demand Space Reclamations Migrations and Recalls These tasks are optional but
18. 0 09 11 08 2010 0 09 11 08 1 1 X01021 3 90 0 2010 0 09 21 11 2010 0 09 21 11 1 1 SLUADMIN 7 1 0 STORAGETEK VTCS SYTEM UTILITY TIME 06 59 03 UNAVAIL FENCED VTV REPORT VTV SIZE COMP lt CREATION gt lt USED gt R VOLSE MB DATE TIME DATE TIME R X01280 FENCE D X04762 FENCE D X04776 FENCE D X02019 FENCE D X10066 FENCE D X10068 FENCE D SC RE RE RT SD PL SC RE RE RT SD PL S R 5 lt 2 E lt SC RE RE RT SD PL FIGURE 4 10 Example output from VTVRPT UNAVAIL option E22915 01 Revision 01 PAGE 002 DATE 2010 03 20 MGM MVC1 MVC2 MVC3 MVC4 MAX T CLA VTV SS M9 38 PAGE 003 DATE 2010 03 20 MGM MVCI MVC2 MVC3 MVC4 MAX T CLA VTV SS PAGE 004 DATE 2010 03 20 MGM MVCI MVC2 MVC3 MVC4 MAX T CLA VTV SS Chapter4 83 VTSS NAME HBVTS S16 VTSS NAME HBVTS S16 HBVTS S16 HBVTS S16 HBVTS S16 VTSSN AME Obviously if you have had any reports of jobs or VTCS being unable to access VTVs that you thought were resident OPTION UNAVAIL is the way to go Let s also talk about the flexibility you get with XML output from the VTVRPT utility You can generate for selected reports and utilities output in either Structured XML or Comma Separated Variables CSV XML What s the difference between Structured XML and CSV output Consider this Structured XML contains all of the
19. 000 VOL SER NOS WORKO2 5 507088 130417 000 VOL SER NOS WORKO8 5 507088 130419 000 VOL SER NOS SW8A45 5 507088 130413 000 VOL SER NOS SW8D12 SYMPTOM DUMP OUTPUT XXXXPDSS XXXXPDSS XXXXPDSS XXXXPDSS XXXXPDSS XXXXPDSS XXXXPDSS XXXXPDSS XXXXPDSS XXXXPDSS XXXXPDSS XXXXPDSS DATACLAS DATACLAS DATACLAS DATACLAS DATACLAS DATACLAS DATACLAS DATACLAS DATACLAS DATACLAS DATACLAS R0100595 R0100596 R0100597 R0100598 R0100599 R0100600 R0100601 R0100602 R0100603 R0100604 R0100605 R0100594 DELETED DELETED DELETED DELETED DELETED DELETED DELETED DELETED DELETED DELETED KEPT KEPT 2007 E22915 01 Revision 01 Appendix B 181 182 Managing HSC and VTCS April 2011 Revision 01 E22915 01 USER COMPLETION CODE 0555 TIME 13 04 26 SEQ 00397 CPU 0000 ASID 002A PSW AT TIME OF ERROR 07801000 00008B22 ILC 2 INTC ACTIVE LOAD MODULE ADDRESS 00007000 OFFSET 00001B22 NAME SLUPCOPY DATA AT PSW 00008 1 00181610 OAODBFBF 00050 0 GR 0 C0000000 1 C000022B 2 00009A20 3 006 4 00009488 5 000097B3 6 00009000 7 0000 000 8 006 9 00000064 A 00008000 B 0000AB4A 00007000 D 0000 000 E 500080EE 00000000 END OF SYMPTOM DUMP IEA9931 SYSMDUMP TAKEN TO XXXX SLUPCOPY SYSMDUMP IEF472I XXXXPDSS COPY COMPLETION CODE SYSTEM 000 USER 0555 REASON 00000000 IEF2851 XXXX
20. 07755 SLS7028I ABEND OPTION IS ENABLED 13 10 40 JOB07755 SLS7028I RESERVE RETRY WTOR OPTION IS ENABLED 13 10 40 20 07755 SLS7070I READ JFCB SUCCESSFUL FOR SLSCNTL DD 13 10 40 20 07755 SLS7010I SSCVT LOCATED FOR SUBSYSTEM 5 13 10 40 20 07755 SLS7011I ASCB FOR HSC JOB NAME HSCX HAS ASID 001D 13 10 40 20 07755 51571021 HSC QNAME HSCXLSQN 13 10 40 JOB07755 SLS7025I PRIMARY CDS NAME XXXX SOS610 SLSCNTL 13 10 40 20 07755 SLS7015I CDS NAME MATCHES PRIMARY CDS 13 10 40 JOB07755 0033 SLS7090A REPLY Y TO INITIATE POINT IN TIME COPY 13 10 48 JOBO7755 R 33 Y 13 10 48 20 07755 SLS7071I OPEN SUCCESSFUL FOR SLSCNTL DD 13 10 48 JOB07755 SLS7104I UCB LOCATED SUCCESSFULLY 13 10 48 20 07755 SLS7072I RESERVE SUCCESSFUL FOR SLSCNTL DD 13 10 48 20 07755 SLS7073I CDS DHB READ SUCCESSFUL 13 10 48 20 07755 SLS7021I JCL CDS NAME MATCHES DHB CDS 13 10 48 20 07755 51571701 CDS DPV READ SUCCESSFUL 13 10 48 20 07755 51571061 ORIGINAL LAST BACKUP DATE AND TIME 2007032913 10 13 13 10 48 20 07755 SLS7171I CDS DPV WRITE SUCCESSFUL 13 10 48 20 07755 51571071 UPDATED LAST BACKUP DATE AND TIME 2007032913 10 48 13 10 48 JOB07755 SLS7074I ATTACH SUCCESSFUL 13 11 04 JOB07755 SLS7075I TCB USER CC 0000 SYSTEM CC 0008 13 11 04 20 07755 SLS7108I DPV RESTORE REQUIRED 13 11 04 20 07755 SLS7172I CDS DPV RESTORE SUCCESSFUL 13 11 04 20 07755 51570761 DETACH SUCCESSFUL 13 11 04 20 07755 SLS7077I MAINLINE DEQ SUCCESSFUL FOR SL
21. DCB RECFM FB LRECL 80 BLKSIZE 27920 SLSPRINT DD SYSOUT SLSIN DD RECONCIL VTV DX009 118 Managing HSC and VTCS April 2011 Revision 01 E22915 01 CHAPTER 6 Leading Edge Solutions with Management and Storage Classes E22915 01 Revision 01 119 VTCS CDS Levels A critical item re leading edge solutions is know your CDS VTCS level and what it can and cannot do TABLE 6 1 describes the CDS levels and the features they enable TABLE 6 1 is valid for these VTCS NCS versions 6 0 6 1 6 2 7 0 6 2 7 0 7 1 CDS Levels for Supported VTCS Versions and this VTSS hardware VSM2 and VSM3 VSMA VSMS with up to 256 VTDs per VTSS and or up to 16 RTDs per VTSS RTD sharing except for paired RTDs a paired RTD shares a CIP with another Nearlink connection either an RTD or a CLINK and provides these enhancements 4 MVC copies 800 Mb VTVs Near Continuous Operations NCO Bi directional clustering Improved CDS I O performances reduces the I O required to manage virtual scratch sub pools 400Mb 800Mb 2Gb 4Gb VTVs Standard Large VTV Pages 65000 VTVs per MVC 74 Dynamic Reclaim Autonomous Device Support 120 Managing HSC and VTCS April 2011 Revision 01 E22915 01 What are Management and Storage Classes VTCS Management and Storage Classes which are the building blocks of a lot of leading edge implementa
22. DSN SYS07024 T130601 RA000 HSCFLASH R0152621 STORCLAS SCTEMP MGMTCLAS DATACLAS VOL SER NOS SIP016 IGD1011 SMS ALLOCATED TO DDNAME SYS00007 DSN SYS07024 T130601 RA000 HSCFLASH R0152622 STORCLAS SCTEMP MGMTCLAS DATACLAS VOL SER NOS 6 005 IGD1011 SMS ALLOCATED TO DDNAME SYS00008 DSN SYS07024 T130601 RA000 HSCFLASH R0152623 STORCLAS SCTEMP MGMTCLAS DATACLAS VOL SER NOS SIP002 IGD1011 SMS ALLOCATED TO DDNAME SYS00009 DSN SYS07024 T130601 RA000 HSCFLASH R0152624 STORCLAS SCTEMP MGMTCLAS DATACLAS VOL SER NOS SIP027 IGD1011 SMS ALLOCATED TO DDNAME SYS00010 DSN SYS07024 T130601 RA000 HSCFLASH R0152625 STORCLAS SCTEMP MGMTCLAS DATACLAS VOL SER NOS SIP032 IGD1011 SMS ALLOCATED TO DDNAME SYS00011 DSN SYS07024 T130601 RA000 HSCFLASH R0152626 STORCLAS SCTEMP MGMTCLAS DATACLAS VOL SER NOS SIP025 168 Managing HSC and VTCS April 2011 Revision 01 E22915 01 EF2371 2000 ALLOCATED TO SYS00012 IEF2371 2001 ALLOCATED TO SYS00013 IGD1051 S YS07024 T130601 RA000 HSCFLASH R0152617 DELETED DDNAME SYS00002 IGD1051 S YS07024 T130601 RA000 HSCFLASH R0152618 DELETED DDNAME SYS00003 IGD1051 S YS07024 T130601 RA000 HSCFLASH R0152619 DELETED DDNAME SYS00004 IGD1051 SYS07024 T130601 RA000 HSCFLASH R0152620 DELETED DDNAME SYS00005 IGD1051 S YS07024 T130601 RA000 HSCFLASH R0152621 DELETED DDNAME SYS00006 IGD1051 S YS07024 T130601 RA000 HSCFLASH R0152622 D
23. E22915 01 Contents Preface iii Audience iii Prerequisites About This Book iv 1 The Toolkit s 1 The HSC Toolkit 2 The VTCS Toolkit 6 2 Managing the CDS 9 Backing Up the CDS 10 Frequency of Backup 10 Using the SLUPCOPY Utility to Back Up the CDS 11 Requirements 11 SLUPCOPY Procedure 13 General JCL Requirements All PIT Methods 14 SVAA SnapShot JCL Example 16 DFSMSdss SnapShot JCL Example 19 DFSMSdss FlashCopy JCL Example 21 FDRSNAP JCL Example 23 Using the BACKup Utility to Back Up the CDS 24 Managing CDS Logging 25 Periodically Offloading Log Files 25 Expanding or Reallocating Log Files 26 Manually Switching to Another CDS Copy 27 E22915 01 Revision 01 Expanding the CDS 28 Rotating the CDSs 29 Renaminga CDS 30 Renaming a CDS Using the CDS Disable and Enable Commands RelocatingaCDS 31 Relocating an Uncataloged CDS Copy 31 SwappingaCDS 32 Restoring the CDS 33 Restoring the CDS from a Backup Copy 34 3 Managing TapePlex 41 Managing Library Hardware 42 Managing ACSs 42 Managing SL8500 Redundant Electronics 43 Dual Library Controller Configuration 43 SL8500 Redundant Electronics Environment 45 SL8500 LC Operation 46 Managing CAPs 52 Defining Manual RTDs 53 Managing Library Volumes 54 Using a Volume Report 54 Errant and Selected Volumes 54 Unmatched VOLPARM and External Label Status 55 Volumes not included in VOLPARM 55 Managing Scratch Subpools 56 Managing Cleaning Cartridges 57 Optimizing Moun
24. PROD MAXMVC 60 CONMVC 8 ELAPSE 360 MOVEVTV FIGURE 6 12 Example JCL for the RECONcil utility RECONcil Usage Notes To select the VTVs to reconcile you can specify one of the following parameters MGMTclas to move the VTVs to the Storage Class es specified by the MIGpol parameter This is what we did in RECONcil Example on page 131 Management Class points to the wrong Storage Class get it pointed toward the right Storage Class run RECONcil against the updated Management Class STORclas to move the VTVs to the specified Storage Class es probably use this when an ACS is unavailable for a considerable period of time MVC to reconcile the VTVs on a list or range of The VTVs are moved to the Storage Class es specified by he MIGpol parameter of the MGMTclas statement s for the VTVs use this or the VTV option as onesies twosies kind of fix ups VTV to reconcile a list or range of VTVs The VTVs are moved to the Storage Class es specified by the MIGpol parameter of the Management Class es for the VTVs Note If you do not specify a value for MGMTclas or VTV VTCS scans all VTVs Because reconciling VTVs can be resource intensive you typically run RECONCil during non peak processing periods You can also use the RECONcil utility to override the CONFIG RECLAIM THRESHLD MAXMVC and CONMVC settings to optimize reconcile performance You can also specify the maximum time for the r
25. Per MVS Programming Authorized Assembler Services Reference under the Restrictions section for RESERVE the operating system should DEQ the Primary CDS when the SLUPCOPY task ends Per MVS Programming Assembler Services Guide under the Freeing of Virtual Storage section in Chapter 11 the operating system should CLOSE the Primary CDS when the SLUPCOPY task ends 160 Managing HSC and VTCS April 2011 Revision 01 E22915 01 AB Option If the AB option is specified the occurrence of any of the following error conditions causes message SLS7112I to be issued followed by a User 555 abend LS7005E LOGIC ERROR INVALID FUNCTION LS7006E CVTJESCT ADDRESS IS ZERO LS7007E JESSSCT ADDRESS IS ZERO LS7008E SUBSYSTEM ssss NOT ACTIVE LS7009E ASCB NOT FOUND 157012 DCV ADDRESS IS ZERO LS7013E DCV PRIMARY INFO ADDRESS IS ZERO LS7014E JCL CDS NAME DOES NOT MATCH PRIMARY CDS NAME LS7016E QNAME IS BLANK OR BINARY ZEROS 157018 LVT ADDRESS IS ZERO LS7020E JCL CDS NAME DOES NOT MATCH DHB CDS NAME LS7022E DEB ADDRESS IS ZERO LS7023E UCB ADDRESS IS ZERO LS7024E SLSCNTL DD IS DUMMIED LS7029E SUBSYSTEM ASID IS ZERO LS7035E POINT IN TIME COPY INVALID LS7050E ESTAE FAILED 15 LS7051E RDJFCB FAILED R15zXXXXXXXX LS7052E LOCASCB FAILED 15 LS7053E ATTACH FAILED R15zXXXXXXXX LS7054E OPEN FAILED R15zXXXXXXXX LS7055E RESERVE FAILED R1zXXXXXXXX R15 XXXXXXXX LS7056E CDS DHB READ FAILED 15
26. To return the MVC to the MVC pool enter an MVCDRain for the MVC Entering MVCDRain without the EJect parameter for the MVC makes it available again For example to run the MVCDRain to drain the MVCs in Storage Class STORCL1 and return after the request is submitted enter the following MVCDRAIN STORCLAS STORCL1 NOWAIT Note As an alternative you can use MVCMAINT to mark an MVC as read only This prevents VTCS from selecting the MVC for migrates but does not remove the VTVs from the MVC You can also use MVCMAINT to turn off read only If using VOLPARM POOLPARM definitions the NOMIGRAT option can be specified on the POOLPARM statement to prevent MVCs from being used for new migrations E22915 01 Revision 01 Chapter5 99 Draining MVCs Use MVCDRain to drain an MVC recall all VTVs on the MVC You typically drain an MVC for the following reasons An MVC report or Display shows data check errors for the MVC VSM will not migrate to the MVC and you should remove it from the MVC pool An MVC report or Display shows errors other than data check errors for the MVC A Storage Class or Named MVC Pool is no longer in use and you want to remove or reuse the associated MVCs To select the MVCs to drain you can specify one of the following parameters MVCid to drain or more MVCs by volser MVCPOOL to drain the MVCs in a Named MVC Pool See ELS Command Control Statement and Utility Reference for more i
27. and HSC can no longer report MWL for that volume while it remains outside the library However the mount count is maintained in the MIR and the next time the volume is entered into the library and mounted and dismounted at least once HSC can again report MWL for that volume while it resides in the library If a transport cannot read or write the MIR the drive can reinitialize a new MIR elsewhere on the volume Errors processing a MIR are rare and although the drive will reconstruct a new MIR if it must it is possible the drive might not be able to transfer the mount count from the failed MIR to the replacement MIR in which case the drive will initialize the mount count to zero in the replacement MIR If you observe a non zero mount count go to zero for a volume for example by monitoring the MWL on a volume report you should examine the SYSLOG for data checks on this volume and have the tape drive examined and you should also consider retiring this volume The Media Warranty Life feature requires the following 2 Tape library LMU compatibility level 21 2 T9x40 transports with 1 42 drive firmware Note T9840B is not supported because of memory constraints T10000A and T10000B with 1 38 drive firmware 2 PTF SES700 LIH154V You have cleaning cartridges that have exceeded their useful life and must be replaced Manually Ejecting Used Cleaning Cartridges on page 65 Ejecting Scratch Volumes To eject scratch volume
28. especially in the case of Demand Space Reclamations highly recommended Best Practices for reasons that will soon become obvious Doing Demand MVC Space Reclamations As you already know VSM automatically reclaims space only one MVC at a time on each host running reclamations the key word being automatically That means that space reclamation is always out there looking for work and although it is a background task if you ve got a lot of fragmented MVCs the space reclamation work can seriously interfere with migration recall especially during peak processing periods If your MVC summary report or Display MVCPool shows a high level of fragmentation on your system s MVCs and this level is below the value specified on the CONFIG RECLAIM THRESHLD parameter or the MVCPool THRESH parameter you may want to schedule demand MVC space reclamation as an off hours batch job You do demand MVC space reclamation with RECLaim Open up your ELS Command Control Statement and Utility Reference and you ll see some useful tools you can use to optimize demand reclamation and run it most efficiently You can use one only of the MVCPOOL STORCLAS ACSid or MVC parameters to filter the list of MVCs to process Your MVC and VTV reports as described in Using the VTCS Dashboard on page 73 help you narrow the list of likely candidates to an MVC Pool Storage Class specific ACS or range or list of MVCs Input this list into RECLaim and you re using the r
29. 83 CLNO40 STK2W STK2P 00 01 03 03 00 R 20100418 18 31 18 20100911 00 53 51 2 63 CLNO28 STK2W STK2P 00 00 01 09 01 R 20100418 16 41 51 20100717 15 52 46 2 15 FIGURE 3 4 Volume Report Cleaning Cartridges The clean use count is actually the field labeled Times Selected at the far right The field labeled Cln Use in the middle of the report indicates Y when a cleaner is overuse E22915 01 Revision 01 Chapter3 57 Optimizing Mount Performance Optimal mount performance is measured by how quickly you can get real tape volumes mounted and dismounted Here your best tool is the Activities Report which pulls data from SMF records and provides information that helps you balance mount dismount activity across ACSs and LSMs This report shows Total Mount and Dismount activity broken out as follows Scratch mount total mounts and average time per mount 2 Nonscratch mounts total mounts and average time per mount Scratch mounts in a different LSM total mounts average time per mount and average number of pass thrus 2 Nonscratch mounts in a different LSM total mounts average time per mount and average number of pass thrus If the Activities Report uncovers performance problems due to scratch mounts you can use the HSC Scratch Redistribution utility or LCM to redistribute scratch volumes across the LSMs within a particular ACS If you re running low on scratch volumes you can run scratch synchronization to scratch vo
30. 8801 CHANIF OI RTD NAME VTS18802 DEVNO 8802 CHANIF 1A RTD NAME VTS18803 DEVNO 8803 CHANIF 1I RTD NAME VTS18811 DEVNO 8811 CHANIF 0E RTD NAME VTS18813 DEVNO 8813 CHANIF 1E VTD LOW 8900 HIGH 893F VTSS NAME VTSS2 FIGURE 5 1 CONFIG example updating configuration to deny host access to a physically removed VTSS 104 Managing HSC and VTCS April 2011 Revision 01 E22915 01 Working with VTVs This section consists of the most likely tasks you might have to do on an as needed basis deleting scratch VTVs and changing VTV attributes Deleting Scratch VTVs There are two ways you can delete scratch VTVs Via policy by specifying DELSCR YES on a VTV s Management Class and using HSC or LCM scratch synchronization to do the actual scratch Ad hoc using the DELETSCR utility DELETSCR deletes scratch VTVs from VTSSs and unlinks any migrated VTVs from MVCs Deleted VTVs are marked as non initialized although versioning information is retained We re going to leave the policy discussion of deleting scratch VTVs to Installing ELS and stick to the ad hoc version After all ad hoc is basically as needed in Latin and that s the theme of this book Before we tell you how to do it let s dispense with the obligatory warning which is Caution When you use DELETSCR to delete scratch VTVs any data on those VTVs is gone and cannot be recovered Okay so deleting VTVs is not something you do beca
31. CDSs must have only a single extent 3 Re enable each CDS with the CDS ENABLE command 4 Enter the CDS EXpand command All CDSs that are known to the HSC that is are enabled are expanded at the same time with a single invocation of the CDS EXpand command 28 Managing HSC and VTCS April 2011 Revision 01 E22915 01 Rotating the CDSs CDS names do not change as the result of a CDS automatic or manual switch You can use a sequence of CDS Disable and Enable commands to restore the order and match the data set names to their expected roles To rotate the CDSs 1 Enter a Display CDS command to view the current status and assignment of the CDSs SYS000001 ELS SYSCNTL2 PRIVOL PRODO2 FLAGS 40 ACTIVE SYS000002 ELS SYSCNTL SECVOL PRODO1 FLAGS 40 ACTIVE The display shows that SYSCNTL the original Primary is now the Secondary and SYSCNTL2 the original Secondary is now the Primary 2 Disable the current Primary CDS DISABLE PRIMARY ELS SLSCNTL2 is disabled and ELS SLSCNTLT becomes the new Primary 3 Re enable ELS SLSCNTL2 as the new active Secondary CDS ENABLE DSN ELS SLSCNTL2 4 Enter Display CDS command to confirm that the CDSs are rotated SYS000001 ELS SYSCNTL PRIVOL PRODO2 FLAGS 40 ACTIVE SYS000002 ELS SYSCNTL2 SECVOL PRODO1 FLAGS 40 ACTIVE E22915 01 Revision 01 Chapter2 29 Renaming a CDS There are two methods for renaming a CDS Use the CDS
32. ENDED NAME XXXXXXXX TOTAL CPU TIME 13 06 41 JOBO7750 HASP395 XXXXPFDR ENDED cene JES2 JOB STATISTICS 29 MAR 2007 JOB EXECUTION DATE 19 CARDS READ 149 SYSOUT PRINT RECORDS E 0 SYSOUT PUNCH RECORDS 9 SYSOUT SPOOL KBYTES 0 35 MINUTES EXECUTION TIME 1 XXXXPFDR JOB XXXXXX XXXXXXXX CLASS A MSGCLASS 1 2 COPY EXEC PGM SLUPCOPY REGION 4M PARM HSCX COPY FDR RR STEPLIB DD DSN XXXX LINKLIB DISP SHR SLSCNTL DD DSN XXXX SOS610 SLSCNTL DISP SHR SYSPRINT DD SYSOUT 3 17098 0 44 0 0 0 00 TOTAL ELAPSED 3 JOB07750 188 Managing HSC and VTCS April 2011 Revision 01 E22915 01 EA995I SYMPTOM DUMP OUTPUT USER COMPLETION CODE 0502 TIME 13 06 22 SEQ 00398 CPU 0000 ASID 002A PSW AT TIME OF ERROR 07800000 80035A48 ILC 2 INTC OD ACTIVE LOAD MODULE ADDRESS 00034000 OFFSET 00001A48 NAME FDRSNAPA DATA AT PSW 00035A42 411001F6 0 009110 10104700 AR GR 0 8094FB3E 00000000 1 00000000 000001F6 2 00000000 006BFD20 3 00000000 441B24B8 4 00000000 006CDF44 5 00000000 00029000 6 00000000 00036C50 7 00000000 00006604 8 00000000 00006550 9 00000000 00037000 A 00000000 00036000 B 00000000 80035A42 C 00000000 00035000 D 00000000 00034000 E 00000000 80036ABE F 00000000 00000000 END OF SYMPTOM DUMP IEA9931 SYSMDUMP TAKEN TO XXXX SLUPCOPY SYSMDUMP IEF285I SYS07088 T130622 RA000 XXXXPFDR R0100609 KEPT IEF285I VOL SER NOS SW8A45
33. IN USE 002 OPENED DCBS FDROO7 STARTING TIME OF SNAPSHOT DUMP 13 06 22 UNIT 3390 IN D SW8A45 OUTPUT TAPE1 FDR230 FDRSNAP ERROR UNIT 8D14 REASON 8 TARGET UNIT IS NOT OFFLINE FDR997 FDR ABNORMALLY TERMINATED VOL SW8A45 FDR319 FDR OPERATION ABNORMALLY TERMINATED VOL SW8A45 COMP CODE S000 U0502 FDR998 FDR COMPLETED WITH ERRORS E22915 01 Revision 01 AppendixB 189 190 Managing HSC and VTCS April 2011 Revision 01 E22915 01 Index A ABEND dumps 4 AUDIT 110 129 B BACKup utility description 11 24 function 11 24 backup CDS 11 24 C Cartridge Access Port CAP clearing RECOVERY status on Display Cap command 68 cartridges entering into the LSM duplicate VOLSERs 67 with missing or unreadable labels 67 CD See Cartridge Drive CDS See control data set CDS Disable command 29 30 CDS See Control Data Set COMMPath command and control statement usage 70 communications restoring 70 control data set CDS rename procedure 30 swapping 32 copy CDS with rename 30 D Database Heartbeat DHB record reassigning CDSs using CDS Enable Disable 29 30 diagnostics program dumps 72 Display command 72 dump E22915 01 Revision 01 program 72 E entering cartridges into the LSM duplicate and unreadable VOLSERs 67 with missing or unreadable labels 67 F freeing an allocated CAP 69 H history event GTF tracing 4 host restoring host to host communications 70 Host Software Component HSC diag
34. MIGpol parameter on the MGMTclas statement to point to the original ACS and run RECONcil specifying the updated MGMTcelas or STORclas statement s to move the VTVs to the original ACS Notice that we re talking about using RECONcil to um reconcile a incorrect Storage Class incorrect MVC media ACS location or both What if you wanted to move VTVs whose data is now less frequently accessed from access centric media such as T9840 cartridges to storage centric media such as T9940 cartridges and an Extended Store ACS or offsite In that case you typically set up an Archive Policy via the ARCHAge ARCHPol parameters of the MGMTCLAS statement and the VTV movement then occurs automatically according to the ARCHPol specification when the ARCHAge value is exceeded and when the VTV is recalled and remigrated An automatic Archive Policy therefore is like an automatic migration Both happen over time and time is what you don t have if one or more VTVs are truly in the wrong place In this case use RECONCcil 110 Managing HSC and VTCS April 2011 Revision 01 E22915 01 Running a RECONCGIl Job To change ACS media with RECONcil 1 To select the VTVs to validate i e Do they need reconciliation or not you can specify one of the following RECONcil parameters STORclas Specifies one or more Storage Classes Here RECONCII does the following Looks up the ACS and media definition for the specifi
35. MVCs MVCMAINT READONLY OFF is the tool LOST ON or OFF How does an MVC get lost For example can MVCs get lost Believe it or not they can For example if a VTCS initiated mount of an MVC fails to complete as opposed to completes with an error VTCS marks the MVC as lost in the CDS and depreferences it Multiplexed VTVs that reside on a lost MVC are recalled from an alternate MVC VTCS does not attempt to use lost MVCs for migration unless there are no other valid MVCs When an MVC in lost status is successfully mounted the lost status is removed from the MVC record Okay what if you know the MVC isn t really lost Answer You can use MVCMAINT to turn off the LOST status There is an interesting use of MVCMAINT that deserves a mention What if you have an LSM that s temporarily in manual mode You might want to temporarily depreference MVC selection in that LSM which you can do with LOST ON Then when the LSM is back in automatic mode reverse the process with LOST OFF ERROR ON or OFF An MVC can erroneously go into Error status for several reasons for example 2 does not recognize the volume mounted the RTD as an MVC This can be caused by some MVS job overwriting the MVC Determine what happened to the MVC If it no longer contains valid VTV data reinitialize the volume and return it to the MVC pool The MVC is not writeable which can be caused by the thumb wheel bei
36. MVCs with invalid MIRs determine the cause of the error which may be caused by media or drive problems and fix the error To recover an MVC with an invalid MIR do the following 1 Drain the MVC with EJECT MVCDRAIN volser RECALWER EJECT 2 Use MVCMAINT to set INVLDMIR to OFF MVCMAINT MVC volser INVLDMIR OFF 3 Redrain the MVC without EJECT MVCDRAIN MVC volser RECALWER NO At this point the data is completely off of the MVC if it was removable in the first place and the CDS is cleared of any error status At the next migration the MVC generates another MIR error for the mount read volser open of the tape However the MVC will get written to from the beginning of tape which corrects the actual hardware MIR Finally rerun Step 1 through Step 3 to reset the MVC status 146 Managing HSC and VTCS April 2011 Revision 01 E22915 01 Recovering an MVC with a Data Check This is a very specific instance of the general bad MVC woes and you know it s required when you see an MVC data check error on your MVC and VTV reports To recover an MVC with a Data Check 1 Run an MVC audit against the MVC The audit attempts to read the VTV metadata sequentially from the MVC The audit fails when it encounters the data check which leaves the MVC in an auditing state This prevents VTCS from selecting this MVC for output 2 Run an MVCDRain Eject for the MVC This causes all the available VTVs to be recalle
37. RTV utility Converts VTVs contained on MVCs to data sets on Nearline volumes real tape volumes Using the RTV Utility on page 148 SET MIGOPT Changes the following migration Checking Virtual Tape Status parameters Daily on page 74 Maximum and minimum Doing Demand VTV concurrent automatic migration Migrations on page 91 immediate migration and migrate to threshold tasks High and low AMTSs VARY RTD Changes RTD state Checking Nearline Tape Status Daily on page 78 Working with RTDs on page 92 VARY VTSS Changes VTSS states on all hosts Working with VTSSs on page 103 E22915 01 Revision 01 Chapter 1 7 8 Managing HSC and April 2011 Revision 01 E22915 01 CHAPTER 2 Managing the CDS Managing the CDS a key task because of the critical data that the CDS contains The following sections tell how to safeguard the CDS and how to recover it if you lose one or more copies of the CDS For information about planning and creating the CDS see Configuring HSC and VTCS E22915 01 Revision 01 9 Backing Up the CDS If all copies of the CDS fail that is you lose the Primary Secondary and Standby copies you must restore the CDS from a backup You can back up the CDS using non ELS facilities such as disk mirroring third party backup software such as IBM DFSMSdss and Innovation FDR or third party Point In Time Copy software such as IBM FlashCopy Storage
38. Refer to OPTION Command and Control Statement in ELS Command Control Statement and Utility Reference for details on command syntax and parameters You can enter duplicate volumes into a Streamline library as long as the library is partitioned and the duplicate volumes are entered into different partitions Entering Cartridges With Missing or Unreadable External Labels Tape cartridges with unreadable labels cannot be entered into a library through a CAP If you attempt to enter a cartridge without a label or with a label the robot cannot read the following HSC message is issued UnNamed Cartridge in CAP CELL AA LL RR CC reply V volser or EJECT Do one of the following Reply V volser to enter the cartridge by assigning it a VOLSER The specified VOLSER is permanently assigned to the cartridge in the CDS Note If any unlabeled cartridges or cartridges with unreadable labels are manually entered into a library they will be ejected during an audit StorageTek recommends that users provide an external media label for all cartridges Reply EJECT and remove the cartridge from the CAP when the is unlocked E22915 01 Revision 01 Chapter3 67 Clearing Recovery Status On A CAP When a CAP status is RECOVERY use the following procedure to force CAP recovery Note If this procedure does not clear recovery status try Freeing An Allocated CAP on page 69 To clear recovery status on
39. SLS7028I DFSMSDSS METHOD IS IN EFFECT 13 06 01 SLS7028I ABEND OPTION IS ENABLED 13 06 01 SLS7070I READ JFCB SUCCESSFUL FOR SLSCNTL DD 13 06 01 SLS7010I SSCVT LOCATED FOR SUBSYSTEM HSCO 13 06 01 SLS7011I ASCB FOR HSC JOB NAME HSCD22 HAS ASID 0086 13 06 01 SLS7102I HSC QNAME STKALSON 13 06 01 SLS7025I PRIMARY CDS NAME XXXXHSC SLS DBASEPRM 13 06 01 SLS7015I JCL CDS NAME MATCHES PRIMARY CDS NAME 13 06 01 SLS7071I OPEN SUCCESSFUL FOR SLSCNTL DD 13 06 01 SLS7072I RESERVE SUCCESSFUL FOR SLSCNTL DD 13 06 01 SLS7073I READ SUCCESSFUL FOR SLSCNTL DD 13 06 01 SLS7021I JCL CDS NAME MATCHES DHB CDS NAME 13 06 01 SLS7074I ATTACH SUCCESSFUL 13 06 02 SLS7075I TCB USER CC 0000 SYSTEM CC 0000 13 06 02 SLS7076I DETACH SUCCESSFUL 13 06 02 SLS7077I MAINLINE DEQ SUCCESSFUL FOR SLSCNTL DD 13 06 02 SLS7078I MAINLINE CLOSE SUCCESSFUL FOR SLSCNTL DD 13 06 02 SLS7031I POINT IN TIME COPY SUCCESSFUL 13 06 02 SLS7111I SLUPCOPY VERSION X XX PROCESSING ENDS 13 06 02 IEF404I HSCFLASH ENDED TIME 13 06 02 HSCFLASH JOB XXXXXXX XXXXXXX XXXXXXX MSGCLASS T REGION 0M MSGLEVEL 1 1 NOTIFY XXXXXXX MAIN CLASS D22 k k k k k k k K k K k K K KOK KOK R KOR KOR OR R KOR KOR KOR R K OR KOR KOK OK KK w ww w w SLUPCOPY CDS FLASHCOPY TOK ke ko ko kk TOR IRR OR oko kk kk koe kk Kok koe Kok oko TOK ke KK DFDSS EXEC PGM SLUPCOPY REGION 4M PARM HSCO COPY DSS OPT AB STEPLIB DD DISP SHR DSN DMMBASE SLUPCOP
40. StorageTek or customer personnel who are responsible for managing ELS Prerequisites To perform the tasks described in this guide you should already understand the following The MVS operating environment JES2 or JES3 Enterprise Library Software ELS E22915 01 Revision 01 iii About This Book This book is designed for anybody whose job is to keep HSC and VTCS up and running HSC VTCS is basically a server and like all servers if you install and configure it correctly construct effective policies and provide a reasonable amount of conscientious management it pretty much takes care of itself HSC and VTCS share some common tasks such as maintaining the CDS and have some parallel but separate tasks such as working with real volumes versus working with VTVs and MVCs For information about managing the third member of the trio see Managing SMC So what kind of conscientious management is required What does it take to manage HSC and VTCS The following list describes the sections of this book and the corresponding management tasks 2 The Toolkit s on page describes in table format the tools you use to manage HSC and VTCS The Toolkit s describes the specific tasks and functions for these tools For the details you ll want to have within easy reach ELS Command Control Statement and Utility Reference Managing the CDS on page 9 tells how to safeguard the CDS and how to recover it if you lo
41. a CAP 1 Issue the following command ENTER cap id where cap id is the CAP you want to recover The following occurs 1 The LSM robot moves to the CAP and performs a CAP catalog 2 If cartridges are detected in the CAP HSC issues a message instructing the operator to remove the cartridges 3 HSC issues the message Open CAPid AA LL CC for entering when unlocked 4 The CAP ENTER indicator lights up or Enter appears on the display panel 2 Issue the DRAin command against that CAP The CAP is locked and the status is set to INACTIVE 68 Managing HSC and April 2011 Revision 01 E22915 01 Freeing An Allocated CAP Caution Use this procedure only if the CAP is not in use Releasing a CAP from an active command or utility may produce unpredictable results Examples of these are CAP cleanup errant cartridges cartridges still in the CAP that are unknown to HSC If a host terminates without performing recovery while an active process is using a CAP the CAP remains allocated to the host and is unavailable to all other hosts If HSC is brought back up on that host it releases the CAP after initialization Otherwise you can free the CAP by issuing the following command from any connected host RELEASE cap id where cap id specifies the CAP you wish to release HSC issues a message prompting you to confirm that the CAP is to be released 2 Reply N to cancel the release To proceed wi
42. a file that contains an alternate set of MGMTclas statements Tip This is basically a valuable what if tool that says Let s say I changed some VTV Management Classes per Changing VIV Management Class and Unlinking VTVs from MVCs on page 107 including their Storage Class specifications and then ran RECONcil What would that look like Well now you can find out before you actually change a VTV s Management Class Note VTCS and HSC must be active to process a RECONcil request except when you specify the POLICY dd parameter 112 Managing HSC and VTCS April 2011 Revision 01 E22915 01 4 Okay you ve done all the what ifs fine tuning and off peak schedule required Dow it s time to make it happen FIGURE 5 3 shows example JCL to run RECONcil as follows 2 Reconcile VTVs in Management Classes LOCALPRODI and LOCALPROD2 2 Set MAXMVC to 60 CONMVC to 8 and ELAPSE to 60 for the RECONcil job RECONCIL EXEC PGM SLUADMIN STEPLIB DD DSN hlq SEALINK DISP SHR SLSPRINTDD SYSOUT SLSIN RECON MGMT LOCALPROD1 LOCALPROD2 MAXMVC 60 CONMVC 8 ELAPSE 360 MOVEVTV FIGURE 5 3 Example JCL for the RECONcil utility And of course you get an after action RECONcil report that tells you how smoothly or not things went so you can readjust and rerun the process if necessary E22915 01 Revision 01 Chapter5 113 Using FOR LOSTMVC to Recover VTVs You can use the LOGU
43. add additional statements to define the Named MVC Pools If you do not specify the POOLPARM NAME parameter VTCS does not create a Named MVC Subpool and assigns the specified volumes to the default pool DEFAULTPOOL You cannot create Named MVC Pools with the reserved names DEFAULTPOOL and ALL You can use the optional MVCFREE MAXMVC THRESH and START parameters to specify values for the Named MVC Pool that override the global values specified on CONFIG For example the following VOLPARM POOLPARM statements defines a range of T10000 Full volumes to be encrypted for Named Pool SYS1MVCT1 with reclamation parameter values that override the CONFIG global values VOLPARM VOLSER T10K2000 T10K2999 MEDIA T10000T1 RECTECH T1AE POOLPARM SYS1MVCT1 40 MAXMVC 4 THRESH 60 START 70 2 Run the SET VOLPARM to apply the volume pool definitions SET VOLPARM APPLY YES 3 Define Storage Classes and associate them with Named MVC Pools For example the following STORclas statement defines STORCL and associates this Storage Class with Named MVC Pool CUSTIPOOL Requests to use MVCs for storage class STORCI will result in MVCs being selected only from the named pool SYS1MVCT1 STOR NAME STORCL1 MEDIA T AE MVCPOOL SYS1MVCT1 4 Create Management Classes that specify the Storage Classes you defined in Step 3 and specify these Management Classes when you route data to the Named MVC Pool For more informa
44. and Utility Reference Note Special precautions should be taken for running BACKup and RESTore when local remote linked libraries run CDSs independent of each other These precautions should be followed when the link connecting the local and remote libraries is disrupted See ELS Legacy Interfaces Reference for more information If you are using log files for recovery continue with Step 4 Otherwise go to Step 9 E22915 01 Revision 01 Chapter2 35 4 Ensure that the restored CDS is referencing the correct log file information Run SET LOGFILE OFF SETLOG JOB account REGION 1024K S1 EXEC PGM SLUADMIN PARM execution parameters STEPLIB DD DSN hlq SEALINK DISP SHR SLSPRINT DD SYSOUT SLSIN DD SET LOGFILE OFF Run the FMTLG utility to reformat the log files FMTLOG JOB account REGION 1024K 51 EXEC PGM SLUADMIN PARM execution parameters STEPLIB DD DSN hlq SEALINK DISP SHR SLSLOG1 DD DSN hlq CDSLOG1 DISP CATLG DELETE UNIT SYSDA SPACE CYL 100 SLSLOG2 DD DSN hlq CDSLOG2 DISP CATLG DELETE UNIT SYSDA SPACE CYL 100 SLSPRINT DD SYSOUT SLSIN DD FMTLOG Run SET LOGFILE again specifying the names of the newly initialized log files SETLOG JOB account REGION 1024K S1 EXEC PGM SLUADMIN PARM execution parameters STEPLIB DD DSN hlq SEALINK DISP SHR SLSPRINT DD SYSOUT SLSIN DD SET LOGF
45. and are trademarks or registered trademarks of SPARC International Inc UNIX is a registered trademark licensed through X Open Company Ltd This software or hardware and documentation may provide access to or information on content products and services from third parties Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third party content products and services Oracle Corporation and its affiliates will not be responsible for any loss costs or damages incurred due to your access to or use of third party content products or services ii Managing HSC and VTCS April 2011 Revision 01 E22915 01 Preface Oracle s StorageTek Enterprise Library Software ELS is a solution consisting of the following base software 2 StorageTek Storage Management Component SMC StorageTek Host Software Component HSC StorageTekTM Virtual Tape Control Software VTCS StorageTekTM Concurrent Disaster Recovery Test CDRT Additionally the following software is provided with the ELS package StorageTek Library Content Manager LCM formerly ExLM LCM includes enhanced version of the product formerly known as Offsite Vault Feature 2 StorageTek Client System Component for MVS Environments MVS CSC StorageTekTM LibraryStation Refer to the publication Introducing ELS for an overview of the ELS solution Audience This guide is for
46. are assigned policy PCUSTA Data sets with HLQ CUSTB are assigned policy PCUSTB All other data sets are assigned policy PPROD TAPEREQ DSN CUSTA POLICY PCUSTA TAPEREQ DSN CUSTB POLICY PCUSTB TAPEREQ DSN POLICY PPROD FIGURE 6 8 TAPEREQ Statements for Workload Segregation Caution You cannot use the default Storage Class the name of the last VTSS that wrote to the MVC for reclamation or migration to segregate workloads Managing HSC and VTCS April 2011 Revision 01 E22915 01 Archiving Data You can use the ARCHAge and ARCHPol parameters of the MGMTclas statement to set an Archive Policy for VIVs in a Management Class When the VTV s age exceeds the ARCHAge value the VTV is eligible for archive per the Storage Class es specified on the ARCHPol parameter The actual archive occurs in one of two ways Automatically the next time the is recalled and remigrated On demand via the ARCHIve utility So a what if for this might be to ensure compliance It turns out that I have data that I have to retain for 7 years for external auditors but my internal auditors might like to look at it once a year as well Here s what that solution looks like TAPEREQ DSN COMPLY POLICY PCOMPLY POLICY NAME PCOMPLY MEDIA VIRTUAL MGMT COMPLY MGMT NAME COMPLY IMMMED DELETE MIGPOL LOC1 ARCHAGE 365 ARCHPOL REMDEEP STOR NAME LOC1 ACS 00 MEDIA STK1R STOR NAME REMDEEP A
47. command Managing VTVs Replicated via Cross TapePlex Replication CTR You can use VTVMAINT to change the status of VTVs replicated via CTR as follows Use VTVMAINT OWNRPLEX to change the VTV s owning TapePlex Use VTVMAINT DELEXpot to remove the name of a TapePlex that references a VTV Use VTVMAINT ADDEXpot to add the name of a TapePlex that references For more information see ELS Disaster Recovery and Offsite Data Management Guide E22915 01 Revision 01 Chapter5 109 Changing VTV Storage Class with RECONcil As described in Changing VTV Management Class and Unlinking VTVs from MVCs on page 107 you can use VTVMAINT to change a VTV s Management Class which could of course change its Storage Class Or what if you want to explicitly move the VTV from one Storage Class to another Answer use RECONCcil Before we fire off our first RECONcil job SLUADMIN utility only let s figure out why we want to change a VTV s Storage Class There are basically three reasons As above you re explicitly changing the VTV s Management Class Storage Class The VTVs are on the wrong media in the wrong ACS or both An ACS is unavailable for a considerable period of time then is brought back online In this case you would first change the MIGpol parameter on the MGMTclas statement for the affected VTVs to point to a different ACS and media if desired When the original ACS comes back online you then change the
48. does no data movement but merely reports the VTVs that are candidates for reconciliation You can guess the reason for this but we ll explicitly state it anyway Caution Because reconciling VTVs can be resource intensive StorageTek strongly recommends that you run RECONcil without MOVEVTV first then adjust the job as needed before specifying MOVEVTV E22915 01 Revision 01 Chapter5 111 3 If needed adjust the RECONcil job Okay let s say you ran the report per Step 2 and it looks like you ll be reconciling for a long time Well consider doing the following Run RECONcil during non peak processing periods just as you would a demand MVC space reclamation 2 Use the RECONcil utility parameters to override the CONFIG RECLAIM THRESHLD MAXMVC and CONMVC settings to optimize reconcile performance 2 Specify the maximum time for the reconcile in minutes on the ELAPSE parameter Note There are multiple limiting factors that influence reconciliations for example MAXMVC and ELAPSE VTCS enforces the strictest limiting factor For example if you run RECONcil and specify ELAPSE equal to 5 hours and MAXMVC equal to 10 and VTCS reconciles 10 MVCs in one hour then VTCS terminates the reconciliations before the ELAPSE value expires There is also a RECONcil POLICY dd option that is also available on the ARCHive utility and can be a useful diagnostic POLICYdd which enforces producing only a report points to
49. errors with regard to satisfying the migration requirements Ifthe MVC Pool is undefined Ifthe MVC Pool contains none of the specified media Ifthe MVC Pool contains no free MVCs of the specified media If the VTSS ACS has no suitable RTD defined to write the migration MVC Ifall suitable RTDs are offline The result is that you re now getting greater granularity of information and more specific recommendations for fixes when migration failures do occur 140 Managing HSC and VTCS April 2011 Revision 01 E22915 01 Display STORCLas Display is enhanced with the STORCLas parameter whose output is 2 2 The characteristics of the Storage Class ACS MVC Pool and Media VTVs waiting migration to the Storage Class from any VTSS Requirements of the MVCs to be used for migration The device type s of the RTDs needed to write to the migration MVCs Any errors with regard to satisfying the migration requirements Once again VTCS provides information about a critical element Storage Classes in the migration scenario Enhanced MVC Pool Validation Validation of MVC Pools is enhanced to check for common set up errors 2 Has at least one valid MVC Pool been defined If not message SLS6845E is issued VTCS functionality is severely degraded because no migrations can occur If you receive this message you must define appropriate MVC Pools See the next bullet Does the default MVC Pool DEF
50. method where host id specifies the host which the command affects method specifies the method you want to be made current Managing HSC and VTCS April 2011 Revision 01 E22915 01 Resolving Possible Lost Mount Requests Mounts may be lost due to one of several reasons If SMC is inactive while HSC is active then MVS and or TMS messages are not intercepted 2 If HSC is inactive while the SMC is active then MVS and or TMS messages are intercepted but there is no Automated Library Control system to receive the mount request A hardware LMU error can occur In general to resolve these problems use the SMC RESYNC command to redrive all lost mount requests Resolving Lost Mount Responses ORH Occasionally a mount request gets stuck on one of the HSC queues due to a response not being received from the LMU When this happens the volume is left in a selected status and the operator is notified by the Overdue Response Handler ORH Overdue Response Handler Every 30 seconds the ORH scans all queues for each ACS to identify requests with sequence numbers whose response wait time intervals have expired When a time interval expires HSC issues the message ORH interval expired and the ORH checks the request type code For all request type codes other than mount dismount move and swap the ORH automatically extends the request s wait time another increment of 3 5 10 or 60 minutes and issues the message O
51. need to vary the VTSS offline to VTCS If MVS boxed the VTDs and dismounted any mounted VTVs go to Step 3 Otherwise continue with Step 2 2 Dismount the VTV MVS perspective You cannot remount the VTV on a VTD in another VTSS if MVS still considers it mounted in the offline VTSS Do either of the following Usethe MVS UNLOAD command to dismount the VTV 2 Use the VARY OFFLINE to vary offline the VTD where the VTV is mounted which will also dismount the VTV 3 Run VTVMAINT specifying the offline VTSS and VTV s you want to logically dismount For example to logically dismount VTVs VV6823 VV6825 and VV6688 in offline 5501 code the following SLSIN DD statement in your JCL VTVMAINT DISMOUNT VTV VV6823 VV6825 VV6688 VISS VTSSO1 If migrated copies of the dismounted VTVs exist that an online VTSS can access you can now use this VTSS to access the VTVs Caution If the VTV copy mounted in the offline VTSS was modified and not migrated the MVC copy that you recall to an alternate VTSS is not current Therefore StorageTek strongly recommends that you do not recall these non current MVC copies 108 Managing HSC and VTCS April 2011 Revision 01 E22915 01 Tip When the offline VTSS is ready to be brought back online StorageTek strongly recommends that you audit the VTSS before running production jobs that use the VTSS Also ensure that you clear any boxed VTD conditions before issuing the VTSS VARY ONLINE
52. of the following the order of the options is irrelevant AB enables an abend on occurrence of an eligible error condition see AB Option on page 161 PC enables the WTOR for an actual SLS7090A or simulated 7091A PIT copy RR enables the WTOR for RESERVE retry SLS7092A All JCL PARM options are considered disabled unless explicitly specified WTORs are not issued and operator interaction is not required for normal operation Example PARM HSCZ COPY SNP OPT RR PC AB specifies that the HSC subsystem name is HSCZ that an actual PIT copy is to be performed using native SnapShot and that all options are to be enabled ASLSCNTL DD is required and must specify the Primary HSC CDS name The D CDS command can be used to display the CDS status Use the data set name associated with the PRIVOL entry in the output of the command as the data set name for the SLSCNTL DD 14 Managing HSC and VTCS April 2011 Revision 01 E22915 01 The JCL CDS name is compared to the in memory CDS name of the HSC subsystem Ifthe Primary CDS is not specified SLS7025I identifying the Primary CDS and SLS7014E identifying the error messages are issued 2 The JCL CDS name is also compared to self describing information within the CDS 2 DISP SHR is required on the SLSCNTL DD otherwise a conflict occurs and the PIT will have to be cancelled SLSVDI DD is required A Vital Diagnostic Information report is ge
53. on MVCs by changing these policies E22915 01 Revision 01 Chapter4 81 Looking at the Big Picture Weekly This one isn t too complicated and basically consists of running your other two primary status tools MVC Report and VTV Report on a weekly basis Using the VTV Report Note The VTV report is run via one of the following commands VTVRPT BASIC which shows all VTV copies migrated to MVCs via the EXPORT command VTVRPT COPIES which shows all copies migrated to MVCs via the EXPORT command and additionally all VTV copies migrated via the EEXPORT command Let s start with a VTV Report which looks like FIGURE 4 9 SLUADMIN 7 1 0 STORAGETEK VTCS SYTEM PAGE 0002 UTILITY TIME 06 32 03 5 VTV REPORT DATE 2010 03 20 VIV SIZE COMP lt CREATION gt LAST USED gt MIG SC RE RE MGM MVC2 MVC3 MAX VTSS R RT SD PL T NAME VOLSE MB DATE TIME DATE TIME CLA VTV R ss 00 00 0 04 84 201070116 05 02 08 2010JULI9 05 41 00 M R 02255 022551 022552 022553 8 VTSS16 VCL4 0 X00002 lt MOUN 2010JUL14 06 54 35 2010JULI9 07 43 06 R 03355 033551 033552 033553 8 VTSS17 T gt VCL4 0 X00003 15 60 84 201070114 10 05 05 2010JULI9 05 41 28 M R 04455 044551 4 VTSS16 VCL2 0 X00004 0 36 84 2010 2 08 51 20 201070119 05 41 30 M 5 R 02255 022551 022552 8 VTSS16 8 VCL3 0 X00005 15 60 84 201070114 10 05 14 2010 1119 05 41 31 M R 03355 4 VTSS16 V
54. pool Lots of reasons where a typical scenario might be that you re swapping out older drives for a technology refresh for your RTDs and you want to retire the old media in which case you get to add new MVCs to the pool as described in Adding MVCs on page 95 and then remove the old media as described in Permanently Removing on page 98 Note that there are occasions where you might want to temporarily remove MVCs from the pool For example you ve got some bad media or suspected bad media You want to remove the bad media and put in replacements basically under the same volsers as described in Temporarily Removing MVCs on page 99 E22915 01 Revision 01 Chapter5 97 Permanently Removing MVCs To permanently remove MVCs from the pool do the following 1 Enter MVCDRain to drain the MVCs For example to run the MVCDRain to drain the MVCs in Storage Class STORCLI virtually eject the MVCs and return after the request is submitted enter the following MVCDRAIN STORCLAS STORCL1 EJECT NOWAIT 2 If the MVCs are no longer required in an ACS use an HSC Eject command to eject the MVCs from the ACS 3 Remove the security restrictions and tape management system restrictions you defined for the MVC If you use VOLPARM POOLPARM definitions and the virtual CDS level is G or above continue with Step 4 Otherwise go to Step 5 4 If you want to reuse the tape volser for Nearline non VTCS usage and use VOLP
55. s VTSS VTDs and VTVs are operating normally Think of the Nearline component of VSM RTDs and MVCs the place where VTVs are being migrated to and recalled from with some MVC space reclamation going on in the background and you ll agree that this area deserves your full attention too To check Nearline Tape status 1 Enter a Display RTD A good picture might be something like FIGURE 4 5 RTD STATUS MOUNT ALLOC HOST B200 ONLINE FREE B201 ONLINE FREE 0B79 ONLINE FREE OB7A RECALL VIV DMV051 DMV051 EC20 1600 MVS1 z e MIGRATE 1601 MVS1 MIGRATE VTSS HBV SS16 5516 HBV SS16 HBV SS16 FIGURE 4 5 Example output from VT Display RTD command is well 78 Managing HSC and VTCS April 2011 Revision 01 E22915 01 In FIGURE 4 5 on page 78 things are moving along smartly because there s a good balance of RTDs migrating recalling and available for new work which is not true in FIGURE 4 6 RTD STATUS ALLOC HOST VTSS B200 MVS1 MIGRATE B201 MVS1 MIGRATE 0B79 MVS2 MIGRATE E 0B7A MVS2 MIGRATE 1600 MVS1 MIGRATE 1601 MVS1 MIGRATE FIGURE 4 6 Example output from a VT Display RTD command RTDs in Distress If FIGURE 4 6 is a result of the kind of emergency measures employed in Step 2 then there s not much you can do other than
56. tags and structures shown for each command or utility which you can then process as desired using a programming language of your choice CSV output lets you select only the tags and their order that you want Each output line contains a fixed number of fields separated by commas which can then be input into spreadsheets or report writers for customizable analysis or reports So you now have two ways you can effectively customize a basic VTV Report for your shop s needs For more information on this topic see ELS Programming Reference Finally you should be aware that LCM provides enhanced management and reporting capabilities that correspond to ELS VTCS functions including the VTCS MVC and VTV Reports For more information see LCM Control Statements on page 153 84 Managing HSC and April 2011 Revision 01 E22915 01 Using the MVC Report Finally let s look at an MVC Summary Report which looks like FIGURE 4 11 SLUADMIN 7 1 0 STORAGETEK VTCS SYTEM UTILITY PAGE 0002 TIME 09 26 54 VTCS MVC SUMMARY REPORT DATE 2010 04 13 MVC NUMBER USED AVAIL FRAG MEDIA TIMES STATUS lt LAST MOUNTED gt A OWNER S VOLSER OF VTVS SIZE MB MOUNT IBLDRUTM DATE TIME VTSS I CONSOLIDA ED D TE TIME EVS99 200 10 80 84 57 4 63 2000 310 I U M 2010MARI 03 20 23 VTSS8 0 SI 5 0 EVS100 0 0 00 100 00 0 00 UNKNOW 206 L U 2010MARI 05 24 04 VTSS8 N 0 EVS101 1009 99 00 0 00 1 00 400 306 I U 2010MARI
57. the VTSS do the following You do not need to empty a VTSS prior to deletion What you do need to ensure is that all VTVs are fully migrated Also consider changing other parameters for example TAPEREQ statements so that new work is not routed to the removed VTSS Ifremoving all of one device type ACS combination from VTSS also ensure that all VTVs are fully migrated first As above consider changing other parameters to reflect the changed migration capabilities of the VTSS for example Management Classes which point to Storage Classes that specify ACS and media 2 Vary the VTSS to Quiesced state After it goes offline continue with Step 3 3 Remove the VTSS then rerun CONFIG to logically remove it FIGURE 5 1 shows example JCL to run CONFIG to update the configuration to deny host access to VTSS2 that you physically removed from your configuration In this example you respecify the VTSS statement for VTSS2 with no parameters to deny host access to this VTSS UPDATECFGEXEC PGM SLUADMIN PARM MIXED STEPLIB DD DSN hlq SEALINK DISP SHR SLSCNTL DD DSN FEDB VSMLMULT DBASEPRM DISP SHR SLSCNTL2 DD DSN FEDB VSMLMULT DBASESEC DISP SHR SLSSTBY DD DSN FEDB VSMLMULT DBASETBY DISP SHR SLSPRINT DD SYSOUT SLSIN DD CONFIG GLOBAL MAXVTV 32000MVCFREE 40 RECLAIM THRESHLD 70MAXMVC 40 START 35 VTSS NAME VTSS1 LOW 70 HIGH 80 3 RETAIN 5 RTD NAME VTS18800 DEVNO 8800 CHANIF 0A RTD NAME VTS18801 DEVNO
58. to request the XML and CSV formats and explanations of the outputs as well as for command syntax details You may want to run the VOLRPT on a periodic basis to display and resolve volume exception conditions or just display volume status such as described in the following sections Errant and Selected Volumes on page 54 Unmatched VOLPARM and External Label Status on page 55 2 Volumes not included in VOLPARM on page 55 Managing Scratch Subpools on page 56 Managing Cleaning Cartridges on page 57 There are many other uses for VOLRPT See ELS Command Control Statement and Utility Reference for other ways to select volumes and sort the VOLRPT output Errant and Selected Volumes Sample VOLRPT control card VOLRPT SORT LOC INCLUDE SEL ERR This request produces a report of all errant and selected cartridges in location sequence The selected status is normally transient and represents a cartridge being scratched or moved from one location to another For each selected volume on the report you should issue a DISPLAY VOLUME console command to determine if the volume has become unselected If the volume remains selected it may represent an abnormal termination of a host while the volume was selected If you are certain that the volume is not currently in use you can run the UNSELECT utility to reset the selected status An errant volume is one that is not in its last known location Attempting to
59. via your TMS is just part of the solution What also has to happen is that somebody in VSM land has to mark the VTV data non current and therefore writeable and in the case of VTSS resident VTVs delete them from the buffer Because actually deleting VTV data is a significant decision data gone never to return we re going to make a judgement call and say it s an as needed task so if you go this route turn to Deleting Scratch VTVs on page 105 Use POOLPARM VOLPARM to add VTVs This is your next best option and you do it when you really do not have any VTVs with non current data It turns out that it s not just POOLPARM VOLPARM you also have to do the appropriate TMS definitions and so forth Again this is all described in Installing ELS Change your TAPEREQ statements or SMS routines to temporarily reroute tape work to Nearline HSC processing until you can define additional VTVs This is probably your least desirable option because you re essentially sending data directly to Nearline tape that you originally intended to send to VSM so cleaning up the mess is not trivial Still if you have Nearline resources available and you have an immediate need to write data to scratch volumes this is the temporary way to go E22915 01 Revision 01 Chapter4 77 Checking Nearline Tape Status Daily In Checking Virtual Tape Status Daily on page 74 we talked about how important it is to ensure that your system
60. you are certain that the cartridge is not in the library The cartridge is deleted logically ejected from the CDS Reply I if you do not know the location of the cartridge to leave the cartridge in errant status An audit trail is maintained for the cartridge which can be helpful if it becomes necessary to manually locate the cartridge If the cartridge is located at a later time HSC recognizes it as errant and removes it from errant status The cartridge is either returned to its home cell location or marked selected for a request 66 Managing HSC and VTCS April 2011 Revision 01 E22915 01 Entering Duplicate And Unreadable VOLSERS Entering Duplicate Volumes When you try to enter a volume that is already recorded in the CDS HSC attempts to locate the original cartridge by checking its home cell location or destination location If the volume is found the duplicate cartridge is rejected by HSC If the volume is not found the HSC response is determined by the OPTion ENTdup command setting 2 ENTdup is set to Auto HSC automatically deletes the original volume from the CDS and enters the new volume ENTdup is set to Manual HSC requests operator assistance by issuing the following message ENTER of volume VVVVVV encountered missing duplicate volser Logically Delete or Ignore D I Reply D to delete the original volume from the CDS and enter the new volume Note
61. you can lower the high AMT to effectively force a demand migration Doing Demand VTV Recalls VTCS provides an automatic recall process which starts when a job requests a data set on a VTV that is migrated to tape but not VTSS resident What if however you have the reverse of the above situation For example you re doing end of year processing and know there s a bunch of jobs that will want to read data from VTVs that are on tape only Demand recall is the solution RECALL provides you with all the granularity of control you need As with MIGRATE you can recall VTVs by volser Management Class or associated data set name You can specify the VTSS where you want to recall the VIVs Otherwise the default is the VTSS of creation there are some considerations associated with the VTSS recall policy see ELS Command Control Statement and Utility Reference for details RECALWER lets you specify whether you want to recall VTVs with read data checks and there is a NOWAIT option to speed things up E22915 01 Revision 01 Chapter5 91 Working with RTDs There s a lot of RTD management that we ll confine to Finding and Fixing VTCS Problems because they re almost exclusively error recovery scenarios Best Practices for RTDs would be to have enough of them and keep all of the above up and running Remember RTDs get used for migrates recalls and reclaims so keeping the right mix of RTDs for all of these jobs is a cri
62. 00003 EE AEE E EE AEE IEF3731 STEP COPY START 2007088 1302 IEF3741 STEP COPY STOP 2007088 1303 CPU OMIN 00 15SEC SRB OMIN 00 01SEC VIRT 1884K SYS 400K EXT 788K SYS 7484K IEF3751 JOB XXXXPDSS START 2007088 1302 IEF3761 JOB XXXXPDSS STOP 2007088 1303 CPU OMIN 00 15SEC SRB OMIN 00 01SEC 1PAGE 0001 5695 DF175 DFSMSDSS V1R05 0 DATA SET SERVICES 2007 088 13 02 COPY DATASET INCLUDE XXXX SOS610 SLSCNTL RENUNC XXXX SOS610 SLSCNTL XXXX S08610 DFSMSDSS FASTREPLICATION REQUIRED CANCELERROR SHARE TOL ENQF TGTALLOC CYL OUTDYNAM SW8D12 CATALOG ADR1011 R I RI01 01 TASKID 001 HAS BEEN ASSIGNED TO COMMAND ADR109I 01 01 2007 088 13 02 53 INITIAL SCAN OF USER CONTROL STATEMENTS COMPLETED ADRO16I 001 PRIME 01 RACF LOGGING OPTION IN EFFECT FOR THIS TASK OADROOGI 001 STEND 01 2007 088 13 02 54 EXECUTION BEGINS OADR3951 001 NEWDS 01 DATA SET XXXX SOS610 SLSCNTL ALLOCATED WITH NEWNAME XXXX SOS610 DFSMSDSS ON VOLUME S SW8D12 172 Managing HSC and VTCS April 2011 Revision 01 E22915 01 OADR806I 001 TOMI 01 OADR465I 001 CNVSM 01 OADR801I 001 DDDS 01 FAILED FOR OADR454I 001 DDDS 02 0 OADROOGI 001 STEND 02 OADRO131 001 CLTSK 01 OADRO121 SCH DSSU 01 DATA SET XXXX SOS610 SLSCNTL COPIED USING A FAST REPLICATION FUNCTION DATA SET XXXX SOS610 DFSMSDSS HAS BEEN CATALOGED IN CATALOG CATALOG I
63. 03 20 23 VTSS8 0 SI 5 0 EVS102 5 8 25 91 75 0 00 400 6 I U 2010MARI 04 23 04 VTSS8 0 S3 5 0 EVS103 EXPVTV 0 12 99 88 0 00 400 194 I J 2010MARI 03 20 28 5510 0 VTSSIO 5 0 EVS104 0 0 00 100 00 0 00 400 5 I RC 2010MARI 03 49 14 VTSS8 0 2010APRI2 8 0 03 49 14 EVS104 200 10 80 84 57 4 63 02040 254 I RUT 2010MARI 04110 00 VTSS8 0 8 0 EVS105 300 15 80 54 57 4 63 02040 154 I RUW 2010MARI 04110 00 VTSS8 0 8 0 EVS106 0 0 00 100 00 0 00 400 202 I C 2010MARI 03 49 20 VTSS8 0 8 0 EVS107 0 0 00 100 00 0 00 400 171 I RE 2010MARI 04 13 00 VTSS8 0 8 0 137 Initialized MVCs processed 8 Non Initialized MVCs processed FIGURE 4 11 Example MVC summary report The MVC Summary Report is a lot like the stock VTV Report nice if you know what you re looking for Too Much Information otherwise E22915 01 Revision 01 Chapter4 85 What s perhaps more useful in a Big Picture sense are the additional fields you get from an MVC Detailed Report as shown in FIGURE 4 12 SLUADMIN 7 1 0 STORAGETEK VTCS SYTEM UTILITY PAGE 0003 TIME 11 28 30 MVC EVS102 DETAIL REPORT DATE 2010 06 03 VTV SIZE BLOCK MANAGEMENT MIGRATION BLOCK MESSAGE VOLS MB ID CLASS DATE COUNT ER X2004 76 00 00000000 M5 20107 08 10 1 2004 76 00 134009 5 9 3 7 2004 76 00 2A40138 M5 20107 08 9 4 D X2004 76 00 C6401D5 M3 10 5 3 X2004 76 00 A540271 M3 10 7 9 5 VTVS FOUND FOR MVC EVS102 WARNING VTV COUNT 5 DOES NOT MATCH M
64. 06 20 13 06 22 20 07750 SLS7100I SLUPCOPY VERSION 6 20 PROCESSING BEGINS 13 06 22 20 07750 SLS7028I HSC SUBSYSTEM NAME 5 13 06 22 20 07750 SLS7028I COPY FUNCTION IS IN EFFECT 13 06 22 20 07750 SLS7028I FDRSNAP METHOD IS IN EFFECT 13 06 22 20 07750 51570281 RESERVE RETRY WTOR OPTION IS ENABLED 13 06 22 20 07750 SLS7070I READ JFCB SUCCESSFUL FOR SLSCNTL DD 13 06 22 20 07750 SLS7010I SSCVT LOCATED FOR SUBSYSTEM 5 13 06 22 20 07750 SLS7011I ASCB FOR HSC JOB NAME HSCX HAS ASID 001D 13 06 22 20 07750 SLS7102I HSC QNAME HSCXLSQN 13 06 22 20 07750 SLS7025I PRIMARY CDS NAME XXXX SOS610 SLSCNTL 13 06 22 20 07750 SLS7015I JCL CDS NAME MATCHES PRIMARY CDS NAME 13 06 22 20 07750 51570711 OPEN SUCCESSFUL FOR SLSCNTL DD 13 06 22 20 07750 SLS7104I UCB LOCATED SUCCESSFULLY 13 06 22 20 07750 51570721 RESERVE SUCCESSFUL FOR SLSCNTL DD 13 06 22 20 07750 SLS7073I CDS DHB READ SUCCESSFUL 13 06 22 20 07750 SLS7021I JCL CDS NAME MATCHES DHB CDS 13 06 22 20 07750 SLS7170I CDS DPV READ SUCCESSFUL 13 06 22 20 07750 51571061 ORIGINAL LAST BACKUP DATE AND TIME 2007032913 02 53 13 06 22 20 07750 51571711 CDS DPV WRITE SUCCESSFUL 13 06 22 JOB07750 SLS7107I UPDATED LAST BACKUP DATE AND TIME 2007032913 06 22 13 06 22 20 07750 51570741 ATTACH SUCCESSFUL 13 06 40 20 07750 IEA995I SYMPTOM DUMP OUTPUT 018 018 USER COMPLETION CODE 0502 018 TIME 13 06 22 SEQ 00398 CPU 0000 ASID 002A 018 PSW AT TIME OF ERROR 078D0000
65. 285I VOL SER NOS WORKO8 2851 SYS07088 T130257 RA000 XXXXPDSS R0100589 DELETED IEF285I VOL SER NOS WORKO1 IEF285I SYS07088 T130258 RA000 XXXXPDSS R0100590 DELETED IEF285I VOL SER NOS WORKO1 IEF285I 5 507088 130300 000 88 0100591 KEPT IEF285I VOL SER NOS SW8A45 IEF285I SYS07088 T130253 RA000 XXXXPDSS R0100580 KEPT IEF285I VOL SER NOS SW8D12 IEF1421 XXXXPDSS COPY STEP WAS EXECUTED COND CODE 0000 IEF2851 XXXX LINKLIB KEPT IEF285I VOL SER NOS 50020 IEF2851 XXXX SOS610 SLSCNTL KEPT IEF285I VOL SER NOS SW8A45 2851 XXXX XXXXPDSS JOB07747 D0000102 SYSOUT 2851 XXXX SLUPCOPY SYSMDUMP DELETED IEF285I VOL SER NOS SW8D12 IEF2851 XXXX XXXXPDSS JOB07747 D0000101 SYSIN JO III IIIS IIIS III IIIS EI III III SI III E A E A III ICICI SI II I III I I I I I I I DEVICE DEVICE EXCP DDNAME CLASS ADDRESS COUNT REN STEPLIB DASD 3EC4 00000002 SLSCNTL DASD 8A45 00000003 SYSPRINT JES2 00000000 SYSMDUMP DASD 8D12 00000000 SYSIN JES2 00000000 SYS00002 DASD 3EF1 00000000 SYS00003 DASD 3DAC 00000000 SYS00004 DASD 3CF1 00000000 SYS00005 DASD 3DAC 00000000 SYS00006 DASD 3DAC 00000000 SYS00007 DASD 3EF1 00000000 SYS00008 DASD 3EF1 00000000 SYS00009 DASD 3EF1 00000000 SYS00010 DASD 3CF1 00000000 SYS00011 DASD 3CF1 00000000 SYS00012 DASD 8A45 00000003 SYS00001 DASD 8D12 000
66. 2915 01 Revision 01 vii Working with 95 Adding MVCs 95 Defining VTVs 96 Validating and Applying the Volume Definitions 96 Removing MVCs from the Pool 97 Permanently Removing MVCs 98 Temporarily Removing MVCs 99 Draining MVCs 100 Changing MVC Attributes with MVCMAINT 101 Working with VTSSs 103 Removinga VTSS 104 Toremovea VTSS 104 Working with VTVs 105 Deleting Scratch VTVs 105 DELTSCR JCL Example 106 Changing VTV Attributes with VTVMAINT 107 Changing VTV Management Class and Unlinking VTVs from MVCs 107 Logically Dismounting VTVs in an Offline VTSS 108 Managing VTVs Replicated via Cross TapePlex Replication CTR 109 Changing VTV Storage Class with RECONCil 110 2 Running a RECONcil Job 111 Using FOR LOSTMVC to Recover VTVs 114 FOR LOSTMVC Recovery Procedure 116 6 Leading Edge Solutions with Management and Storage Classes 119 VTCS CDS Levels 120 What are Management and Storage Classes 121 Creating and Using VTCS Management and Storage Classes The Basics 122 create and use VSM Management and Storage Classes 122 Maintaining Management and Storage Classes 123 Leading Edge Techniques You Can Do with Management and Storage Classes 124 Grouping Multiple Workloads on Shared MVCs 125 Segregating Individual Workloads on Separate Sets of MVCs 127 Archiving Data 129 E22915 01 Revision 01 viii Archive Usage Notes 129 Reconciling VTV Media and Location 131 RECONcil Example 131 RECONcil Usage Notes 1
67. 32 Named MVC Pools or Not 134 Creating and Using Named MVC Pools 135 7 Finding and Fixing VTCS Problems 137 Fixing Common Problems 138 Poor Mount Performance 138 Poor Migration Performance 139 Migration Failures 140 Messages Enhancements 140 Display STORCLas 141 Enhanced MVC Pool Validation 141 Enhanced Storage Class Validation 142 RTD MVC Failures 143 Okay It s a Bad MVC 144 Recovering an MVC with a Data Check 147 Using the RTV Utility 148 What the RTV Utility Can Recover 148 General Usage Guidelines 149 Security Considerations 149 JCL Examples 150 Listing the VTVs onan MVC 150 Converting a Single VTV by Specifying Its Volser 150 Converting a Single VTV by Specifying Its Volser and Block ID 151 A LCM Control Statements 153 B Additional SLUPCOPY Information 155 SLUPCOPY Processing 156 SLUPCOPY Return Codes 157 SLUPCOPY Problem Reporting Determination and Resolution 158 Problem Reporting Procedure 158 E22915 01 Revision 01 ix Common Problem Symptoms and Remedies 158 DFSMSdss SnapShot Problem Symptoms and Remedies 158 Region Problem Symptoms and Remedies 159 Advanced Diagnostic Techniques 160 AB Option 161 Vital Diagnostic Information 162 Required Diagnostic Information 162 Sample Output 163 Example 1 Successful SnapShot PIT Copy 164 Example 2 Successful DFSMSdss FlashCopy PIT Copy on a JES3 System 167 Example Successful DFSMSdss SnapShot PIT 171 Example 4 Successful FDRSNAP PI
68. 5 47 29 Subpool Totals all Ranges Subpool ID Label Type Range Limits NON VOLPARM SL N A N A Non ACS LSM SCRATCH SCRATCH Media 00 00 00 21 1 STK1R 00 01 5 23 STK2P ACS total 26 24 01 01 00 10 3 STK1R 01 01 13 8 STK2P ACS total 27 Id Library total 53 35 DRTEST No Rectech STK1R DRTEST No Rectech STK1R STK2P STK1R STK2P PAGE 00001 DATE 2010 09 29 PAGE 00002 DATE 2010 09 29 FIGURE 3 5 Volume Report Scratch Subpools 56 Managing HSC and VTCS April 2011 Revision 01 E22915 01 Managing Cleaning Cartridges You can produce a report containing only cleaning cartridges sorted by use count using the following o oo VOLRPT VOL CLN SORT USE DESCEND Sample output is shown in FIGURE 3 4 SLUADMIN 7 1 0 StorageTek Automated Cartridge System Utility PAGE 00002 TIME 16 23 09 Volume Report Utility DATE 2010 09 29 Volume Cell Loc Err Ext Cln Inserted Last Used Times MWL Serial Media Rectech AA LL Pa Ro Co Scr Sel Lbl Use Subpool ID Date Time Date Time Selected CLNO07 STANDARD LONGITUD 00 00 03 07 04 R 20100418 16 29 11 20100425 20 11 19 26 50 CLNO81 STANDARD LONGITUD 00 01 03 13 01 R 20100418 18 22 40 20100825 12 13 17 17 47 CLN082 STANDARD LONGITUD 01 00 03 03 01 R 20100419 14 31 01 20100603 11 24 27 5 75 CLNO41 STK1U STKIRABC 00 01 01 37 01 R 20100418 16 41 48 20100427 13 56 48 3 86 CLNO03 STK2W STK2P 00 00 00 00 15 R 20100418 16 29 11 20100501 14 19 20 2
69. 6 because even though the CDS was updated the error occurred after a successful PIT copy Message 7172 The PIT copy is invalid in this case SVAA was not previously initialized 51570721 RESERVE SUCCESSFUL FOR SLSCNTL DD SLS70731 CDS DHB READ SUCCESSFUL SLS70211 JCL CDS NAME MATCHES DHB CDS NAME 51571701 CDS DPV READ SUCCESSFUL SLS71061 ORIGINAL LAST BACKUP DATE AND TIME 2007032915 44 27 5157171 CDS DPV WRITE SUCCESSFUL 51571071 UPDATED LAST BACKUP DATE AND TIME 2007032915 45 29 SLS70741 ATTACH SUCCESSFUL SLS70751 TCB USER CC 0000 SYSTEM CC 000C SLS71081 DPV RESTORE REQUIRED SLS71721 CDS DPV RESTORE SUCCESSFUL 51 57076 DETACH SUCCESSFUL SLS70771 MAINLINE DEQ SUCCESSFUL FOR SLSCNTL DD SLS70781 MAINLINE CLOSE SUCCESSFUL FOR SLSCNTL DD SLS7035E POINT IN TIME COPY INVALID SLS7111I SLUPCOPY VERSION 6 20 PROCESSING ENDS Message 7172 is issued indicating that the date and time of the last backup in the Primary CDS is successfully restored to its original value as previously displayed by message 7106 because the PIT copy is invalid 180 Managing HSC and VTCS April 2011 Revision 01 E22915 01 ICH700011 XXXX LAST ACCESS AT 13 02 53 ON THURSDAY MARCH 29 236 237 237 237 IGD100I IEF237I IEF237I IGD100I IGD100I IGD100I IGD100I IGD1001I IGD100I IGD100I IGD100I IGD100I IGD100I IEF237I IEF285I IEF285I IEF285I IEF285I IEF285I IEF285I IEF285I IEF285I IEF285I IEF285I
70. 6 21 59 20100321 16 35 21 139 50 STK1R 03 00 00 20 00 x R GENERAL 20100113 10 56 15 20100321 16 35 21 54 49 STK1R 03 00 02 06 01 Y R NON VOLPARM 20050607 16 22 04 20100321 16 35 21 138 15 STK1R 03 00 03 05 02 X R NON VOLPARM 20050607 16 22 14 20100321 16 35 21 138 28 5 03 00 00 04 02 Y NON VOLPARM 20050607 16 21 45 20100321 16 35 21 138 47 FIGURE 3 2 Volume Report Unmatched VOLPARM and External Label Volumes not included in VOLPARM If your subpool totals only VOLRPT shows volumes in the NON VOLPARM pool you will want to get a detailed list of these volumes There is no special control card to select these volumes but the INCLUDE NONMEDEQ can be used You will also see any volumes where the VOLPARM media does not match the media on the volume label E22915 01 Revision 01 Chapter3 55 Managing Scratch Subpools You can obtain a report showing subpool totals by subpool library location and media type without listing individual volumes by running the command VOLRPT SUMM SUBPOOL NOVOL Sample output of this command is shown in FIGURE 3 3 SLUADMIN 7 1 0 StorageTek Enterprise Library Software Utility TIME 15 47 29 Subpool Totals all Ranges Subpool ID Label Type Range Limits GENERAL SL N A N A Non ACS LSM SCRATCH SCRATCH Media 00 00 00 0 0 00 01 0 0 ACS total 0 0 01 01 00 98 1 STK1R 01 01 0 0 ACS total 98 1 Library total 98 1 SLUADMIN 7 1 0 StorageTek Enterprise Library Software Utility TIME 1
71. 7 StorageTek INC ALL RIGHTS RESERVED VITAL DIAGNOSTIC INFO RUN DATE 03 29 07 RUN TIME 13 04 26 5 5 JES 4 52 PRODN SP7 0 5 FMID HBB7708 DFAR 03010500 FT14 FF7F737F FT56 A0300000 LPAR NAME JES TYPE JES2 ECVT PNAM z OS VRM 010500 PSEQ 01010500 VM NAME XXXXXMVS PROC P302A CPID FFXXXXXX2084 SUBSYSTEM NAME HSCX LVT ADDR 433B1000 55 ADDR 00963124 SSVT 433040 0 SUSE 433B1000 SUS2 2445D4C7 FLG1 40000000 IK IR IK ke kk ek IK TOK IK IK IK IK IK IKI koe ko ke kk oko ke ko ke kk ek IK II IR 184 Managing HSC and VTCS April 2011 Revision 01 E22915 01 Example 6 Failed DFSMSdss SnapShot PIT Copy Duplicate Target Data Set JES2 JOB LOG SYSTEM XXXX NODE 13 10 38 JOB07755 THURSDAY 29 MAR 2007 13 10 38 20 07755 IRRO10I USERID XXXX IS ASSIGNED TO THIS JOB 13 10 38 20 07755 ICH700011 LAST ACCESS AT 13 10 13 ON THURSDAY MARCH 29 2007 13 10 39 20 07755 HASP373 XXXXPDSS STARTED INIT CLASS A SYS XXXX 13 10 39 JOB07755 403 XXXXPDSS STARTED TIME 13 10 39 13 10 40 20 07755 SLS7100I SLUPCOPY VERSION 6 20 PROCESSING BEGINS 13 10 40 JOB07755 SLS7028I HSC SUBSYSTEM NAME HSCX 13 10 40 20 07755 SLS7028I COPY FUNCTION IS IN EFFECT 13 10 40 JOB07755 SLS7028I DFSMSDSS METHOD IS IN EFFECT 13 10 40 JOB07755 SLS7028I PIT COPY WTOR OPTION IS ENABLED 13 10 40 20
72. 7032913 02 53 04 13 20 07749 SLS71711 CDS DPV WRITE SUCCESSFUL 04 13 20 07749 SLS71071 UPDATED LAST BACKUP DATE AND TIME 2007032913 04 13 04 13 20 07749 SLS70741 ATTACH SUCCESSFUL 04 26 JOBO7749 SLS7075I TCB USER CC 0000 SYSTEM CC 0008 04 26 JOBO7749 SLS71081 DPV RESTORE REQUIRED 04 26 JOBO7749 SLS71721 CDS DPV RESTORE SUCCESSFUL 04 26 JOBO7749 SLS70761 DETACH SUCCESSFUL 04 26 JOBO7749 SLS70771 MAINLINE DEQ SUCCESSFUL FOR SLSCNTL DD 04 26 JOBO7749 SLS70781 MAINLINE CLOSE SUCCESSFUL FOR SLSCNTL DD 04 26 JOBO7749 SLS7035E POINT IN TIME COPY INVALID 04 26 20 07749 SLS71121 SLUPCOPY VERSION 6 20 ABENDED BY REQUEST 04 47 JOBO7749 IEA9951 SYMPTOM DUMP OUTPUT 975 975 USER COMPLETION CODE 0555 975 TIME 13 04 26 SEQ 00397 CPU 0000 ASID 002A 975 PSW AT TIME OF ERROR 07801000 00008B22 ILC 2 INTC OD 975 ACTIVE LOAD MODULE ADDRESS 00007000 OFFSET 00001B22 975 NAME SLUPCOPY 975 DATA PSW 00008 1 00181610 OAODBFBF 00050 0 975 GR 0 0000000 1 000022 975 2 00009420 3 006 975 4 00009488 5 000097B3 975 6 00009000 7 0000 000 975 8 006 9 00000064 975 00008000 B 0000 4 975 00007000 D 0000 000 975 E 500080EE F 00000000 975 END OF SYMPTOM DUMP 04 47 JOB07749 IEA9931 SYSMDUMP TAKEN TO XXXX SLUPCOPY SYSMDUMP 04 47 JOBO7749 IEF450I XXXXPDSS COPY ABEND S000 U0555 REASON 00000000 977 977 TIME 13 04 47 04 48 20 07749 SYSTEM RELEASE SP7 0 5 HBB7708 04 48 20 07749 TIM
73. 7746 51571061 ORIGINAL LAST BACKUP DATE AND TIME 2007032815 08 35 13 01 31 JOBO7746 SLS71711 CDS DPV WRITE SUCCESSFUL 13 01 31 JOBO7746 SLS71071 UPDATED LAST BACKUP DATE AND TIME 2007032913 01 31 13 01 31 JOBO7746 SLS70741 ATTACH SUCCESSFUL 13 01 37 JOBO7746 SLS70751 TCB USER CC 0000 SYSTEM 0000 13 01 37 JOBO7746 51570761 DETACH SUCCESSFUL 13 01 37 JOBO7746 51570771 MAINLINE DEQ SUCCESSFUL FOR SLSCNTL 13 01 37 JOBO7746 51570781 MAINLINE CLOSE SUCCESSFUL FOR SLSCNTL DD 13 01 37 JOBO7746 SLS70311 POINT IN TIME COPY SUCCESSFUL 13 01 37 JOBO7746 51571111 SLUPCOPY VERSION 6 20 PROCESSING ENDS 13 01 38 JOB07746 SYSTEM RELEASE SP7 0 5 HBB7708 13 01 38 JOBO7746 TIMINGS MINS PAGING COUNTS 13 01 38 JOBO7746 JOBNAME STEPNAME PROCSTEP RC EXCP CPU SRB CLOCK SERV PG PAGE SWAP VIO SWAPS 13 01 38 70807746 XXXXPSNP COPY 00 627 00 00 22 2675 0 0 0 0 0 13 01 38 JOB07746 IEF4041 XXXXPSNP ENDED TIME 13 01 38 13 01 38 JOBO7746 XXXXPSNP ENDED TOTAL CPU TIME 00 TOTAL ELAPSED 2 13 01 38 JOB07746 SHASP395 XXXXPSNP ENDED aces Se JES2 JOB STATISTICS 29 MAR 2007 JOB EXECUTION DATE E 23 CARDS READ E 143 SYSOUT PRINT RECORDS 0 SYSOUT PUNCH RECORDS 8 SYSOUT SPOOL KBYTES 0 20 MINUTES EXECUTION TIME 164 Managing HSC and VTCS April 2011 Revision 01 E22915 01 XXXXPSNP JOB XXXXXX XXXXXXXX CLASS A MSGCLASS 1 JOB07746
74. 80035A48 ILC 2 INTC OD 018 ACTIVE LOAD MODULE ADDRESS 00034000 OFFSET 00001A48 018 NAME FDRSNAPA 018 DATA PSW 00035A42 411001F6 0 009110 10104700 018 AR GR 0 8094FB3E 00000000 1 00000000 000001F6 018 2 00000000 006BFD20 3 00000000 441B24B8 018 4 00000000 006CDF44 5 00000000 00029000 018 6 00000000 00036C50 7 00000000 00006604 018 8 00000000 00006550 9 00000000 00037000 018 A 00000000 00036000 B 00000000 80035A42 018 C 00000000 00035000 D 00000000 00034000 018 E 00000000 80036ABE F 00000000 00000000 018 END OF SYMPTOM DUMP 13 06 40 20 07750 99 SYSMDUMP TAKEN TO XXXX SLUPCOPY SYSMDUMP 13 06 40 20 07750 SLS7075I TCB USER CC 0000 SYSTEM CC 0378 13 06 40 20 07750 SLS7108I DPV RESTORE REQUIRED 13 06 40 20 07750 SLS7172I CDS DPV RESTORE SUCCESSFUL 13 06 40 20 07750 SLS7076I DETACH SUCCESSFUL 13 06 40 20 07750 SLS7077I MAINLINE DEQ SUCCESSFUL FOR SLSCNTL DD 13 06 40 20 07750 SLS7078I MAINLINE CLOSE SUCCESSFUL FOR SLSCNTL DD 13 06 40 20 07750 5157035 POINT IN TIME COPY INVALID 13 06 40 20 07750 SLS7111I SLUPCOPY VERSION 6 20 PROCESSING ENDS 13 06 41 20 07750 SYSTEM RELEASE SP7 0 5 HBB7708 13 06 41 20 07750 TIMINGS 5 PAGING COUNTS 13 06 41 20 07750 JOBNAME STEPNAME PROCSTEP RC EXCP CPU SRB CLOCK SERV PG PAGE SWAP VIO SWAPS 13 06 41 20 07750 XXXXPFDR COPY 12 12066 00 00 13 06 41 20 07750 404 XXXXPFDR ENDED TIME 13 06 41 13 06 41 20 07750 XXXXPFDR
75. 8A45 SNAPUNIT 8D14 02 OPENED DCBS SNAPSHOT DUMP OMIN 00 03SEC SRB 5 4 30P 13 08 22 UNIT 3390 OMIN 00 00SEC VIRT OMIN 00 00SEC INNOVATION DATA PROCESSING IN D SW8A45 OUTPUT TAPE1 FDRSNAP COMPLETED SUCCESSFULLY VOL SW8A45 TO SNAPUNIT 8D14 SNAPSHOT DUMP 13 08 23 UNIT 3390 IN D SW8A45 OUTPUT TAPE1 ICS FOR 3390 VOLUME SW8A45 CYLINDERS ON VOLUME 3 339 DATASETS 8 5 BYTES READ FROM DASD s 333 900 DASD TRACKS BACKED UP 45 BACKUP BLOCKS WRITTEN 0 DASD EXCPS9 4345 u EUER ele ra Bab lis 13 BACKUP FILE 5 0 CPU TIME SECONDS 0 006 ELAPSED TIME 0 1 BACKUP TIME EXCLUDING MOUNTS 0 1 BACKUP COPY 1 DUMMY FULLY COMPLETED VOL SW8A45 COMPLETED DSN NULLFILE 228K SYS 300K EXT DATE 2007 088 PAGE 1800K 1 E22915 01 Revision 01 Appendix B 175 Example 5 Failed DFSMSdss SnapShot PIT Copy SVAA not initialized J 13 13 13 234 13 13 13 13 nus 13 13 d 13 13 13 13 13 13 13 13 134 13 13 135 13 36 13 13 Taz Z3 13 13 183 13 13 13 13 13 13 176 ES2 JOB LOG SYSTEM XXXX NODE 04 06 20 07749 THURSDAY 29 MAR 2007 04 06 JOBO7749 IRRO1OI USERID XXXX IS ASSIGNED T
76. 9488 5 000097B3 6 00009000 7 0000 000 8 006 9 00000064 00008000 0000 4 00007000 D 0000 000 500080 00000000 END OF SYMPTOM DUMP IEA9931 SYSMDUMP TAKEN TO XXXX SLUPCOPY SYSMDUMP IEF472I XXXXPDSS COPY COMPLETION CODE SYSTEM 000 USER 0555 REASON 00000000 IEF285I XXXX LINKLIB KEPT IEF285I VOL SER NOS 50020 IEF285I XXXX SOS610 SLSCNTL KEPT IEF285I VOL SER NOS SW8A45 IEF285I XXXX XXXXPDSS JOB07755 D0000102 SYSOUT IEF285I XXXX SLUPCOPY SYSMDUMP CATALOGED IEF285I VOL SER NOS SW8D12 IEF285I XXXX XXXXPDSS JOB07755 D0000101 SYSIN 186 Managing HSC and VTCS April 2011 Revision 01 E22915 01 TOK ke kk kk ek oko IK I oko ke kk koe ko IK IK IK IK IR IK DEVICE DEVICE EXCP DDNAME CLASS ADDRESS COUNT COMM 006 r STEPLIB DASD 3EC4 00000002 SLSCNTL DASD 8A45 00000004 SYSPRINT JES2 00000000 SYSMDUMP DASD 8D12 00011474 SYSIN JES2 00000000 SYS00002 DASD 3DAC 00000000 SYS00003 DASD 3EF1 00000000 SYS00004 DASD 3CF1 00000000 5 500005 DASD 3CF1 00000000 SYS00006 DASD 3CF1 00000000 SYS00007 DASD 3EF1 00000000 SYS00008 DASD 3EF1 00000000 SYS00009 DASD 3DAC 00000000 SYS00010 DASD 3DAC 00000000 SYS00011 DASD 00000000 5 500012 DASD 8 45 00000003 SYS00001 DASD 8D12 00000003 FOI eK II I II RR CK RR RO KORR Re KC II IO RR eK Kok de Kok Ree I Ree IEF3731 S
77. AINT commands while HSC VTCS is not active 7 Set the MVCSs to be audited to read only status Execute the MVCMAINT READONLY ON commands for the MVCs to be audited with HSC VTCS inactive This will ensure that the MVCs are not used when HSC VTCS is active JOBAUDIT job account programmer REGION 1024K S1 EXEC PGM SLUADMIN PARM execution parameters STEPLIB DD DSN hlq SEALINK DISP SHR SLSPRINT DD SYSOUT SLSIN DD MVCMAINT READONLY ON MVC mvc2 mvcn 8 If LOGPOL REQUIRED is required in the VTCS configuration Specify LOGPOL REQUIRED in the CONFIG GLOBAL statement and run CONFIG if LOGPOL OPTIONAL was temporarily specified at Step 6 above 9 Restart HSC on one hosts but do not start tape activity E22915 01 Revision 01 Chapter2 37 10 To recover the non VSM portion of the CDS run SLUADMIN AUDIT on all ACSs JOBAUDIT job account programmer REGION 1024k S1 EXEC PGM SLUADMIN PARM execution parameters STEPLIB DD DSN hlq SEALINK DISP SHR SLSPRINT DD SYSOUT SLSIN DD AUDIT ALL Note Once the library audit is started you can simultaneously run Step 11 Step 12 and Step 13 11 Audit all VTSSs JOBAUDITV job account programmer REGION 1024k S1 EXEC PGM SLUADMIN PARM execution parameters STEPLIB DD DSN hlq SEALINK DISP SHR SLSPRINT DD SYSOUT SLSIN DD AUDIT VTSS VTSSO VTSS1 38
78. ARM POOLPARM definitions a Update the POOLPARM VOLPARM statements for the MVCs you want to remove b Run SET VOLPARM APPLY YES all hosts to apply the changes c Run the HSC SCRAtch command to scratch the volumes that are no longer MVCs 5 If you want to reuse the tape volser for Nearline non VTCS usage you do not use VOLPARM POOLPARM you need to do one of the following a Issue an HSC EJECT command to remove the MVCs from the ACS b Change the external bar code label on the cartridge You must change the external bar code label because the original MVC volsers are retained in the CDS and these volsers are only available for use as MVCs c ENTER the cartridges back into the ACS OR a Create a new set of CDS data sets b Run the HSC MERGECDS utility specifying DELVirt to remove unwanted MVC ranges Note All HSCs must be stopped when using this option as new CDS data sets will be created 98 Managing HSC and VTCS April 2011 Revision 01 E22915 01 Temporarily Removing MVCs To temporarily remove MVCs from the pool 1 Enter MVCDRain Eject for the MVC For example to run the MVCDRain to drain the MVCs in Storage Class STORCLI virtually eject the MVCs and return after the request is submitted enter the following MVCDRAIN STORCLAS STORCL1 EJECT NOWAIT This does the following Recalls all VTVs on the MVC and remigrates them to new MVCs Makes the MVC non selectable for VTCS migrates 2
79. AULTPOOL exist DEFAULTPOOL is used when migrating to a Storage Class that does not specify a Named MVC Pool and in error situations with Storage Class ERROR If DEFAULTPOOL does not exist message SLS6846W is issued You indicate migrations to a Storage Class should use a particular MVC Pool by coding MVCPool pool name on the STORCLAS statement If MVCPool pool name is not coded VTCS treats the STORCLAS as though MVCPool DEFAULTPOOL was coded E22915 01 Revision 01 Chapter7 141 Enhanced Storage Class Validation To continue in this theme validation of Storage Classes is enhanced to check for common set up errors 2 If you specify a Named MVC Pool on a Storage Class STORCLAS NAME stor clas name MVCPOOL poolname VTCS checks that the Named MVC Pool is defined Therefore if you code STORCLAS NAME stor clas name MVCPOOL poolname ensure that the Named MVC Pool exists If not VTCS issues message SLS6848W If you get this message define the Named MVC Pool change your Storage Class definition or both Similarly if you do not specify a Named MVC Pool on a Storage Class STORCLAS NAME stor clas name VTCS checks that the DEFAULTPOOL is defined Therefore if you code STORCLAS NAME stor clas name ensure that there is at least one MVCPOOL statement that does not create Named MVC Pool If not VTCS issues message SLS6846W If you get this message code at least one MVCPOOL statement that does not create a Named MVC Pool c
80. BA720W Target data set datasetname DSCB was updated SIB46171 09 20 19 SnapShot completed rc 4 E22915 01 Revision 01 Chapter2 17 The above causes SLUPCOPY to end with a Point In Time copy invalid message SLS7035E and an RC 12 To dynamically allocate a target data set instead of static JCL allocation remove the OUTDDNAME parameter and associated JCL DD statement specify the target data set name using the TARGET parameter and specify the target volume using the VOLUME parameter PITSNP2 PROC COPY EXEC PGM SLUPCOPY REGION A4M PARM SSSS COPY SNP OPT AB STEPLIB DD DSN HSC LINKLIB DISP SHR SLSCNTL DD DSN HSC PRIMARY CDS DISP SHR SLSVDI DD SYSOUT SYSPRINT DD SYSOUT SYSTERM DD SYSOUT SIBCTRAN DD DSN HSC SACLINK DISP SHR CTRANS DD DSN HSC SACLINK DISP SHR SYSMDUMP DD DSN HSC SLUPCOPY SYSMDUMP DISP DELETE CATLG UNIT SYSALLDA SPACE CYL 100 RLSE VOL SER VVVVVV SYSIN DD DSN HSC LIB CNTL PITSNPI2 DISP SHR HSC LIB CNTL PITSNPI2 SNAP DATASET INDDNAME SLSCNTL TARGET HSC PITSNAP CDS VOLUME HOSTCOPYMODE SHARED REPLACE YES TOLENQF Y YES TOLENQF Y This approach also conveniently avoids allocation of the target data set when using the TEST function to simulate a PIT copy If the VOLUME parameter does not specify a volume on the same SVA hardware as the CDS the following will occur SIB4762E SnapShot is not supported between di
81. BEND OPTION IS ENABLED 13 02 50 20 07747 SLS70281 RESERVE RETRY WTOR OPTION IS ENABLED 13 02 50 20 07747 SLS70701 READ JFCB SUCCESSFUL FOR SLSCNTL DD 13 02 50 20 07747 SLS70101 SSCVT LOCATED FOR SUBSYSTEM 5 13 02 50 JOBO7747 SLS70111 ASCB FOR HSC JOB NAME HSCX HAS ASID 001D 13 02 50 20 07747 SLS71021 HSC QNAME HSCXLSQN 13 02 50 20 07747 SLS70251 PRIMARY CDS NAME XXXX SOS610 SLSCNTL 13 02 50 JOBO7747 SLS70151 JCL CDS NAME MATCHES PRIMARY CDS NAME 13 02 50 20 07747 0029 SLS7090A REPLY Y TO INITIATE POINT IN TIME COPY 13 02 53 JOBO7747 R 29 Y 13 02 53 JOBO7747 SLS70711 OPEN SUCCESSFUL FOR SLSCNTL DD 13 02 53 20 07747 SLS71041 UCB LOCATED SUCCESSFULLY 13 02 53 JOBO7747 SLS7072I RESERVE SUCCESSFUL FOR SLSCNTL DD 13 02 53 JOBO7747 SLS70731 CDS DHB READ SUCCESSFUL 13 02 53 20 07747 SLS70211 JCL CDS NAME MATCHES DHB CDS 13 02 53 20 07747 SLS71701 CDS DPV READ SUCCESSFUL 13 02 53 20 07747 SLS71061 ORIGINAL LAST BACKUP DATE AND TIME 2007032913 01 31 13 02 53 20 07747 SLS71711 CDS DPV WRITE SUCCESSFUL 13 02 53 20 07747 SLS71071 UPDATED LAST BACKUP DATE AND TIME 2007032913 02 53 13 02 53 20 07747 SLS70741 ATTACH SUCCESSFUL 13 03 10 20 07747 SLS70751 TCB USER CC 0000 SYSTEM CC 0000 13 03 10 20 07747 SLS70761 DETACH SUCCESSFUL 13 03 10 JOBO7747 SLS70771 MAINLINE DEQ SUCCESSFUL FOR SLSCNTL DD 13 03 11 20 07747 SLS70781 MAINLINE CLOSE SUCCESSFUL FOR SLSCNTL DD 13 03 11 20 07747 SLS70311 POINT IN TIME COPY
82. CAP in Step 4 to set the CAP preference to zero always required for PCAPs and mode to Automatic CAPPREF 0 00 00 02 AUTO Use ENTER to make the CAP ready for cartridge entry mode stays Manual For example for the PCAP in Step 4 to make the CAP ready for entry and set scratch status on for the entered cartridges ENTER 00 00 02 SCRATCH E22915 01 Revision 01 Chapter3 65 Solving Problems Recovering Errant Cartridges A cartridge becomes errant when HSC is uncertain of the location of the volume in the LSM The following conditions may cause a cartridge to become errant An operator modifies an LSM offline using the FORCE option The volume is not located in the cell location specified by the CDS 2 An unrecoverable error occurs in the LMU An unrecoverable error occurs in the LSM Errant volume recovery is performed automatically Any time HSC attempts to use a cartridge that is marked as errant When an ACS is connected When an LSM is modified online 2 When cross host recovery is performed HSC issues the following message Attempting to locate errant volume VVVVVV If the cartridge is located by checking its original source location or its destination location HSC removes it from errant status If the cartridge cannot be located the operator is prompted by the following message Volume VVVVVV not found Eject or Ignore E I Respond with one of the following Reply if
83. CLI 0 X00006 15 60 84 201070114 10 08 23 2010JULI9 08 45 31 C 04455 044551 044552 044553 8 VTSS17 VCL4 0 FIGURE4 9 Example output from VTVRPT At first glance the VTV Report looks overwhelming and non intuitive a lot lines of data each describing everything you ever wanted to know about each and every VTV in your system What are some ways you can make a VTV Report more useful to your situation To start with you can run the VTVRPT utility against a list of volsers a volser range or even an individual volser So if you have specific VTVs in mind that you want examine use one of these selection options 82 Managing HSC and VTCS April 2011 Revision 01 E22915 01 Second the VTVRPT utility also provides the OPTION UNAVAIL parameter which produces a report on unavailable VTVs that looks like FIGURE 4 10 SLUADMIN 7 1 0 STORAGETEK VTCS SYTEM UTILITY TIME 06 59 03 UNAVAIL MOUNTED VTV REPORT VTV SIZE COMP lt CREATION gt lt LAST USED gt R VOLSE MB DATE TIME DATE TIME R Y09053 lt MOUN 2010MARI 09 34 14 2010MAR2 05 55 44 T gt 9 0 SLUADMIN 7 1 0 STORAGETEK VTCS SYTEM UTILITY TIME 06 59 03 UNAVAIL RESIDENT VTV REPORT VTV SIZE COMP lt CREATION gt lt USED gt R VOLSE MB DATE TIME DATE TIME R X01007 156 24 89 2010JANI 03 00 02 2010MARO 04 51 47 0 1 X01010 3 90 0 2010MARO 09 10 37 2010MARO 09 10 37 1 1 X01014 3 90 0 2010
84. CS 01 MEDIA STK2P FIGURE 6 9 Archiving Data For this scenario I did the following All compliance data is immediately migrated to the local ACS and grouped on 9840 media After the migration succeeds the VTVs are deleted from the VTSS The archive age for this data is 365 days in case the internal auditors want to see it in the next year After that the data is eligible to be archived moved to 9940 media in the remote ACS Result Compliance at the best possible cost while optimizing virtual resources Archive Usage Notes As noted above you have two methods to use for the actual archive wait until the VTV is recalled and migrated or do it on demand via the ARCHIve utility The problem with waiting for remigration is that we re talking about data that isn t likely to be accessed The chances are the best way to archive VTVs is to run the ARCHIve utility periodically or as needed So here s some tips for using the ARCHive utility To select the VTVs to archive you can specify one of the following parameters 2 MGMTelas to archive the VTVs in Storage Class es specified by the ARCHAge ARCHPol parameter of the specified Management Class es 2 VTV to archive a list or range of VTVs per the Management Class es for those VTVs Note If you do not specify a value for MGMTclas VTCS scans all VTVs probably do business via Management Class but I can see situations where you d wa
85. Classes The Basics You ll see this pattern a lot TAPEREQ gt POLICY gt MGMTelas gt STORclas so get to know it because it s the foundation for all the information in Leading Edge Techniques You Can Do with Management and Storage Classes on page 124 To create and use VSM Management and Storage Classes 1 Determine the definition data set that contains the STORclas and MGMTclas statements MGMTcelas and STORclas statements must reside in the same data set for cross validation 2 Define Storage Classes via the STORclas control statement 3 As desired adjust the migration policies with MIGRSEL and MIGRVTV statements 4 Define Management Classes with the MGMTcelas control statement Note that the MGMTclas control statement specifies Storage Classes on various parameters 5 Load the control statements with the HSC MGMTDEF command 6 Specify a tape policy on the SMC POLICY command 7 Specify the Policy name to VTCS on either of the following 2 The SMC TAPEREQ statement SMS routines that you write to the StorageTek DFSMS interface 122 Managing HSC and VTCS April 2011 Revision 01 E22915 01 Maintaining Management and Storage Classes Note the following Always use an SMC POLICY command to assign the Management Class to mounts You can specify a policy with either the TAPEREQ statement or SMS routines Use POLICY VALIDATE to ensure that your SMC POLICY statements all reference VALID MGMTCLAS names
86. D TO SYS00006 IEF2371 8D12 ALLOCATED TO SYS00007 IEF285I SYS07088 T130135 RA000 XXXXPSNP R0100577 KEPT IEF285I VOL SER NOS SW8A45 IEF285I SYS07088 T130135 RA000 XXXXPSNP RO100578 KEPT IEF285I VOL SER NOS SW8D12 IEF285I SYS07088 T130136 RA000 XXXXPSNP R0100579 KEPT IEF285I VOL SER NOS SW8D12 IEF285I SYS07088 T130133 RA000 XXXXPSNP R0100576 KEPT IEF285I VOL SER NOS SW8800 IEF1421 XXXXPSNP COPY STEP WAS EXECUTED COND CODE 0000 IEF2851 XXXX LINKLIB KEPT IEF285I VOL SER NOS TSO020 IEF2851 XXXX SOS610 SLSCNTL KEPT IEF285I VOL SER NOS SW8A45 2851 XXXX XXXXPSNP JOB07746 D0000102 SYSOUT 2851 XXXX XXXXPSNP JOB07746 D0000103 SYSOUT IEF2851 XXXX S08610 SYSMDUMP DELETED IEF2851 VOL SER NOS SW8D12 IEF2851 XXXX SOS610 SNAPPED CATALOGED IEF285I VOL SER NOS SW8D12 2851 XXXX XXXXPSNP JOB07746 D0000101 SYSIN JO IIIS IIIS III IIIS I E AE E A E III III I IIIS III III III III DEVICE DEVICE EXCP DDNAME CLASS ADDRESS COUNT it STEPLIB DASD 3EC4 00000002 SLSCNTL DASD 8A45 00000003 SYSPRINT JES2 00000000 SYSTERM JES2 00000000 SYSMDUMP DASD 8D12 00000000 OUTSNAP DASD 8D12 00000000 SYSIN JES2 00000000 SYS00001 DASD 3D5C 00000000 SYS00002 DASD 3D5C 00000000 SYS00003 DASD 3D5C 00000002 SYS00005 DASD 8A45 00000000 SYS00006 DASD 8D12 00000000 SYS00007 DASD 8D12 00000000 SYS00004 DASD 8800 00000000 JORIS III IIIS II II CII IIIT III II
87. Disable and Enable commands to do the rename without stopping HSC Stop HSC and use the BACKup and RESTore utilities to do the rename The obvious disadvantage to using the BACKup and RESTore utilities is that HSC must be stopped however the advantage is that a backup of the CDS is created Renaming a CDS Using the CDS Disable and Enable Commands To rename a CDS using commands 1 Disable the CDS you want to rename on all hosts For example CDS DISABLE DSN ACS DBASEOLD 2 Rename the data set that contains the CDS For example rename ACS DBASEOLD to ACS DBASECPY 3 Enable the CDS by its new name For example CDS ENABLE DSN ACS DBASECPY If the Enable command fails for the renamed CDS CDS definitions are restored to what they were before the command was issued Modify the CDSDEF control statement in the HSC PARMLIB to keep it consistent with the active CDS The CDS names are recorded in the Database Heartbeat DHB record During HSC initialization the data set names in the DHB are compared with the data set names specified on the CDSDEF control statement in the HSC PARMLIB If a data set name specified on the CDSDEF statement does not match any of the CDS names recorded in the DHB that CDS is disabled If all the specified CDSs are disabled the HSC will not initialize The specific assignment of enabled CDSs to the primary secondary and standby CDS s is made based on the CDS assignments recorded in the Database
88. ELETED DDNAME SYS00007 IGD1051 S YS07024 T130601 RA000 HSCFLASH R0152623 DELETED DDNAME SYS00008 IGD1051 SYS07024 T130601 RA000 HSCFLASH R0152624 DELETED DDNAME SYS00009 IGD1051 S YS07024 T130601 RA000 HSCFLASH R0152625 DELETED DDNAME SYS00010 IGD1051 S YS07024 T130601 RA000 HSCFLASH R0152626 DELETED DDNAME SYS00011 285 YS07024 T130601 RA000 HSCFLASH R0152627 KEPT IEF285I VOL SER NOS DHSC10 IEF285I YS07024 T130602 RA000 HSCFLASH R0152628 KEPT 285 VOL SER NOS DHSC11 IEF285I YS07024 T130601 RA000 HSCFLASH R0152616 KEPT IEF285I VOL SER NOS XX3679 SLS7075I TCB USER CC 0000 SYSTEM CC 0000 SLS70761 DETACH SUCCESSFUL SLS70771 MAINLINE DEQ SUCCESSFUL FOR SLSCNTL DD SLS70781 MAINLINE CLOSE SUCCESSFUL FOR SLSCNTL DD SLS70311 POINT IN TIME COPY SUCCESSFUL SLS71111 SLUPCOPY VERSION X XX PROCESSING ENDS IEF1421 HSCFLASH DFDSS STEP WAS EXECUTED COND CODE 0000 IGD1041 DMMBASE SLUPCOPY LINKLIB RETAINED DDNAME STEPLIB IGD1041 XXXXHSC SLS DBASEPRM RETAINED DDNAME SLSCNTL IGD1041 XXXXHSC SLS DBASESHD RETAINED DDNAME SLSCNTL2 IEF285I XXXXXXX HSCFLASH JOB23890 D000000A SYSOUT IGD1041 XXXXXXX SLUPCOPY SYSMDUMP RETAINED DDNAME SYSMDUMP IEF285I XXXXXXX HSCFLASH JOB23890 D0000009 SYSIN SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS S STEP NAVN DFDSS SLUT TID 13 06 03 ANVENDT STORAGE 1956 K S S STEP COND 0000 START TID 13 06 01 3033N 0 MIN 1 40 SEK S S S S CHANN UNITADDR EXCP DEV
89. EPLICATION REQUIRED VOLUME NOT SNAPSHOT ELIGIBLE 0 FAILED SERIALIZATION AND 0 CANCELERROR SHARE TOL ENQF TGTALLOC CYL gt OUTDYNAM 548012 CATALOG ADR101I 01 01 TASKID 001 HAS BEEN ASSIGNED TO COMMAND ADR109I R I RIO1 01 2007 088 13 04 13 INITIAL SCAN OF USER CONTROL STATEMENTS COMPLETED ADRO16I 001 PRIME 01 RACF LOGGING OPTION IN EFFECT FOR THIS TASK OADROOGI 001 STEND 01 2007 088 13 04 13 EXECUTION BEGINS OADR9181 001 ALLOC 04 FAST REPLICATION COULD NOT BE USED FOR DATA SET XXXX SOS610 SLSCNTL RETURN CODE 3 0 1 VOLUME WAS REJECTED FOR QFRVOLS VOLUME REASON CODE C8 OADR938E 001 ALLOC 10 FASTREPLICATION REQUIRED WAS SPECIFIED BUT FAST REPLICATION COULD NOT BE USED FOR DATA SET XXXX SOS610 SLSCNTL OADR801I 001 DDDS 01 DATA SET FILTERING IS COMPLETE 1 OF 1 DATA SETS WERE SELECTED FAILED FOR OTHER REASONS OADR455W 001 DDDS 02 THE FOLLOWING DATA SETS WERE NOT SUCCESSFULLY PROCESSED 0 XXXX SOS610 SLSCNTL OADROOGI 001 STEND 02 2007 088 13 04 26 EXECUTION ENDS OADRO131 001 CLTSK 01 2007 088 13 04 26 TASK COMPLETED WITH RETURN CODE 0008 OADRO121 SCH DSSU 01 2007 088 13 04 26 DFSMSDSS PROCESSING COMPLETE HIGHEST RETURN CODE IS 0008 FROM TASK 001 E22915 01 Revision 01 Appendix B 183 ck ek FR IR IR IO IR IK ke kk ek ke kk kk IK ke kk kk ko ke kk kk ko ke ko ke kk e koe TOR ek ke RK SLUPCOPY VERSION 6 20 COPYRIGHT 2006 200
90. Enterprise Library Software Managing HSC VTCS Version 7 1 E22915 01 S 4v Sun April 2011 Revision 01 Submit comments about this document to STP FEEDBACK Copyright O 2009 2010 Oracle and or its affiliates All rights reserved This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws Except as expressly permitted in your license agreement or allowed by law you may not use copy reproduce translate broadcast modify license transmit distribute exhibit perform publish or display any part in any form or by any means Reverse engineering disassembly or decompilation of this software unless required by law for interoperability is prohibited The information contained herein is subject to change without notice and is not warranted to be error free If you find any errors please report them to us in writing Ifthis is software or related software documentation that is delivered to the U S Government or anyone licensing it on behalf ofthe U S Government the following notice is applicable U S GOVERNMENT RIGHTS Programs software databases and related documentation and technical data delivered to U S Government customers are commercial computer software or commercial technical data pursuant to the applicable Federal Acquisition Regulation and agency specific suppleme
91. GD100I 3EF1 ALLOCATED TO DDNAME SYS00011 DATACLAS IEF2371 8A45 ALLOCATED TO SYS00012 IEF285I YS07088 T131049 RA000 XXXXPDSS R0100628 DELETED IEF285I VOL SER NOS WORKO2 IEF285I SYS07088 T131050 RA000 XXXXPDSS R0100629 DELETED IEF285I VOL SER NOS WORKO8 IEF285I SYS07088 T131050 RA000 XXXXPDSS R0100630 DELETED IEF285I VOL SER NOS WORKO1 IEF285I SYS07088 T131050 RA000 XXXXPDSS R0100631 DELETED IEF285I VOL SER NOS WORKO1 IEF285I SYS07088 T131051 RA000 XXXXPDSS R0100632 DELETED IEF285I VOL SER NOS WORKO1 IEF285I SYS07088 T131051 RA000 XXXXPDSS R0100633 DELETED IEF285I VOL SER NOS WORKO8 IEF285I YS07088 T131052 RA000 XXXXPDSS R0100634 DELETED IEF285I VOL SER NOS WORKO8 IEF285I YS07088 T131052 RA000 XXXXPDSS R0100635 DELETED IEF285I VOL SER NOS WORKO2 IEF285I YS07088 T131053 RA000 XXXXPDSS R0100636 DELETED IEF285I VOL SER NOS WORKO2 IEF285I YS07088 T131053 RA000 XXXXPDSS R0100637 DELETED IEF285I VOL SER NOS WORKO8 IEF285I SYS07088 T131055 RA000 XXXXPDSS R0100638 KEPT IEF285I VOL SER NOS SW8A45 IEF285I YS07088 T131049 RA000 XXXXPDSS R0100627 KEPT IEF285I VOL SER NOS SW8D12 IEA995I SYMPTOM DUMP OUTPUT USER COMPLETION CODE 0555 TIME 13 11 04 SEQ 00401 CPU 0000 ASID 002A PSW AT TIME OF ERROR 078D1000 00008B22 ILC 2 INTC OD ACTIVE LOAD MODULE ADDRESS 00007000 OFFSET 00001B22 NAME SLUPCOPY DATA PSW 00008 1 00181610 OAODBFBF 00050 0 GR 0 C0000000 1 C000022B 2 00009A20 3 006CFCCC 4 0000
92. Heartbeat record If the CDS s needs to be renamed use the HSC BACKup and RESTore utilities as described in the rename procedure below Do not use MVS TSO ISPF or third party utilities to rename the CDS s without running the BACKup and RESTore utilities 30 Managing HSC and VTCS April 2011 Revision 01 E22915 01 Relocating a CDS To relocate a CDS 1 Disable the CDS you want to relocate on all hosts For example CDS DISABLE DSN ACS DBASECPY 2 Allocate a new data set with the appropriate CDS attributes For more information see Configuring HSC and VTCS 3 Enable the CDS the data set allocated in Step 2 For example CDS ENABLE DSN ACS DBASENEW NEWLOC Note MVS uses catalog services to resolve the volume and unit definitions if not specified If a rename or relocate operation fails CDS definitions are restored to what they were before the command was issued Modify the CDSDEF control statement to keep it consistent with the active CDS Relocating an Uncataloged CDS Copy Assume that ACS DBASECPY has been disabled and deleted or uncataloged and ACS NOTCATLG has been allocated and cataloged The following command relocates an uncataloged CDS copy CDS ENABLE DSN ACS NOTCATLG NEWVOL HSCO01 NEWUNIT ABC Modify the CDSDEF control statement to make it consistent with the CDS definitions in this command If a rename or relocate operation fails CDS definitions are restored to what they were before the c
93. ICE TYPE DDNAME S S 4310 5 DASD 3390 STEPLIB S S 2000 1 DASD 3390 SLSCNTL S S 2001 0 DASD 3390 SLSCNTL2 S S 3573 0 DASD 3390 SYSMDUMP S S 3565 0 DASD 3390 SYS00002 S S 3566 0 DASD 3390 SYS00003 S S 3572 0 DASD 3390 SYS00004 S S 350A 0 DASD 3390 SYS00005 S S 355E 0 DASD 3390 SYS00006 S S 3553 0 DASD 3390 SYS00007 S S 3551 0 DASD 3390 SYS00008 S S 3569 0 DASD 3390 SYS00009 S S 356E 0 DASD 3390 SYS00010 S S 3567 0 DASD 3390 SYS00011 S S 2000 3 DASD 3390 SYS00012 S S 2001 3 DASD 3390 SYS00013 S S 3679 3 DASD 3390 SYS00001 S S EXCP I ALT 15 BANDSTATIONER 0 S SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS IEF3731 STEP DFDSS START 2007024 1306 IEF3741 STEP DFDSS STOP 2007024 1306 CPU OMIN 00 11SEC SRB OMIN 00 00SEC VIRT 1956K SYS 380K EXT 904K SYS 10908K JJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJ J JOB NAVN HSCFLASH DATO 24 01 07 MASKINE D22B MAX STORAGE 1956 K J J OPGAVE NR 5292100 07024 MVS SP7 1 6 3033N 0 MIN 1 40 SEK J J KORSELS NR XXXXXXXLUT TID 13 06 03 DC VERSION EXCP ALT 15 J J START TID 13 06 01 SYSIN KORT 17 J J B NDSTATIONER 0 J JJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJgJJJJJJJJJJJJJJJJJ IEF3751 JOB HSCFLASH START 2007024 1306 IEF3761 JOB HSCFLASH STOP 2007024 1306 CPU OMIN 00 11SEC SRB OMIN 00 00SEC COPY DATASET INCLUDE XXXXHSC SLS DBASEPRM XXXXHSC SLS DBASESHD x RENUNC XXXXH
94. IEF285I IEF285I IEF285I IEF285I IEF285I IEF285I IEF285I IEF285I IEF285I IEF285I IEF285I IEF285I IEF285I IEF285I IEA995I 2 COPY EXEC PGM SLUPCOPY REGION 4M PARM HSCX COPY DSS STEPLIB DD DSN XXXX LINKLIB DISP SHR SLSCNTL DD DSN XXXX SOS610 SLSCNTL DISP SHR 3 4 5 SYSPRINT DD SYSOUT 6 SYSMDUMP DD DSN XXXX SLUPCOPY SYSMDUMP DISP DELETE CATLG UNIT SYSALLDA SPACE CYL 100 RLSE VOL SER SW8D12 7 SYSIN DD ALLOC FOR XXXXPDSS COPY 3EC4 ALLOCATED TO STEPLIB 8A45 ALLOCATED TO SLSCNTL JES2 ALLOCATED TO SYSPRINT 8D12 ALLOCATED TO DDNAME JES2 ALLOCATED TO SYSIN SYSMDUMP 8D12 ALLOCATED TO SYS00001 3CF1 ALLOCATED DDNAME 3EF1 ALLOCATED TO DDNAME 3DAC ALLOCATED TO DDNAME 3EF1 ALLOCATED TO DDNAME 3CF1 ALLOCATED TO DDNAME 3DAC ALLOCATED TO DDNAME 3EF1 ALLOCATED TO DDNAME 3DAC ALLOCATED TO DDNAME 3DAC ALLOCATED TO DDNAME 3EF1 ALLOCATED TO DDNAME SYS00002 SYS00003 SYS00004 SYS00005 SYS00006 SYS00007 SYS00008 SYS00009 SYS00010 SYS00011 8A45 ALLOCATED TO SYS00012 SYS07088 T130413 RA000 VOL SER NOS WORKO1 SYS07088 T130414 RA000 VOL SER NOS WORKO8 SYS07088 T130414 RA000 VOL SER NOS WORK02 5 507088 130414 000 VOL SER NOS WORKO8 SYS07088 T130415 RA000 VOL SER NOS WORKO1 SYS07088 T130415 RA000 VOL SER NOS WORKO2 SYS07088 T130416 RA000 VOL SER NOS WORKO8 SYS07088 T130416 RA000 VOL SER NOS WORKO2 5 507088 130417
95. ILE hlq CDSLOG1 hlq CDSLOG2 36 Managing HSC and VTCS April 2011 Revision 01 E22915 01 5 Run the LOGUTIL command to generate a data set with the AUDIT MVC commands required for recovery and run the commands in that data set In the following example assume that last known good CDS backup was taken on 5 12 2009 at 10 p m The LOGIN statement specifies a DD statement for each offload log file beginning with the log file created with the last known good backup and ending with the log file that you created in Step 2 LOGUTIL GENAUDIT specifies RECVCMD as the DD name of the data set that contains the commands for recovery of the VSM data JOBLOGR job account programmer REGION 1024k S1 EXEC PGM SLUADMIN PARM execution parameters STEPLIB DD DSN hlq SEALINK DISP SHR LOGIN DD DSN offload dataset name 2 DISP OLD DD DSN offload dataset name 1 DISP OLD DD DSN offload dataset name 0 DISP OLD RECVCMD DD DSN offload dataset genaudit DISP CATLG DELETE UNIT SYSDA SPACE SLSPRINT DD SYSOUT SLSIN DD LOGUTIL 2009 5 12 22 00 00 LOGDD LOGIN GENAUDIT COMMANDS RECVCMD 6 If LOGPOL REQUIRED is currently specified in the VTCS configuration Specify LOGPOL OPTIONAL in the CONFIG GLOBAL statement and run CONFIG to temporarily disable logging in the VTCS configuration This is required to successfully execute the MVCM
96. INGS 5 04 48 JOBO7749 JOBNAME STEPNAME PROCSTEP RC EXCP CPU SRB CLOCK SERV PG 04 48 JOB07749 XXXXPDSS COPY 00555 12128 01 00 6 18938 0 04 48 JOBO7749 IEF4041 XXXXPDSS ENDED TIME 13 04 48 04 48 JOBO7749 XXXXPDSS ENDED NAME XXXXXXXX TOTAL CPU TIME 04 48 JOBO7749 HASP395 XXXXPDSS ENDED JES2 JOB STATISTICS 29 MAR 2007 JOB EXECUTION DATE 27 CARDS READ 221 SYSOUT PRINT RECORDS 0 SYSOUT PUNCH RECORDS 14 SYSOUT SPOOL KBYTES 0 68 MINUTES EXECUTION TIME 1 XXXXPDSS JOB XXXXXX XXXXXXXX CLASS A MSGCLASS 1 Managing HSC and VTCS April 2011 JOB07749 PAGING COUNTS PAGE SWAP 44 0 01 TOTAL ELAPSED Revision 01 VIO SWAPS 0 0 E22915 01 Last Backup Date and Time and Error Recovery Considerations Each CDS contains values for the last backup date and time as well as the last restore date and time Consequently each CDS backup created by SLUADMIN BACKUP contains these values and this information 1s updated within the backup copy to reflect the actual date and time of the backup The DISPLAY CDS command in HSC 6 1 and later has been enhanced to display the last backup date and time and the last restore date and time of the CDSs currently in use SLUPCOPY does not in any way modify the PIT copy created by SnapShot DFSMSdss or but it does update the last backup date and time in the Primary CDS before performing the PIT copy so that the
97. INT RECORDS 0 SYSOUT PUNCH RECORDS 14 SYSOUT SPOOL KBYTES 0 69 MINUTES EXECUTION TIME 1 XXXXPDSS JOB XXXXXX XXXXXXXX CLASS A MSGCLASS 1 PAGING COUNTS SERV PG PAGE SWAP VIO SWAPS 19504 0 44 0 0 0 01 TOTAL ELAPSED TIME 6 JOB07755 E22915 01 Revision 01 Appendix B 185 2 COPY EXEC PGM SLUPCOPY REGION 4M PARM HSCX COPY DSS 3 STEPLIB DD DSN XXXX LINKLIB DISP SHR 4 SLSCNTL DD DSN XXXX SOS610 SLSCNTL DISP SHR 5 SYSPRINT DD SYSOUT 6 SYSMDUMP DD DSN XXXX SLUPCOPY SYSMDUMP DISP DELETE CATLG UNIT SYSALLDA SPACE CYL 100 RLSE VOL SER SW8D12 7 SYSIN DD ICH700011 XXXX LAST ACCESS AT 13 10 13 ON THURSDAY MARCH 29 2007 IEF236I ALLOC FOR XXXXPDSS COPY IEF2371 3EC4 ALLOCATED TO STEPLIB IEF2371 8A45 ALLOCATED TO SLSCNTL IEF2371 JES2 ALLOCATED TO SYSPRINT IGD1001 8D12 ALLOCATED TO DDNAME SYSMDUMP DATACLAS IEF2371 JES2 ALLOCATED TO SYSIN IEF2371 8D12 ALLOCATED TO SYS00001 IGD100I 3DAC ALLOCATED TO DDNAME SYS00002 DATACLAS IGD100I 3EF1 ALLOCATED TO DDNAME SYS00003 DATACLAS IGD100I 3CF1 ALLOCATED TO DDNAME SYS00004 DATACLAS IGD100I 3CF1 ALLOCATED TO DDNAME SYS00005 DATACLAS IGD100I 3CF1 ALLOCATED TO DDNAME SYS00006 DATACLAS IGD100I 3EF1 ALLOCATED TO DDNAME SYS00007 DATACLAS IGD100I 3EF1 ALLOCATED TO DDNAME SYS00008 DATACLAS IGD100I 3DAC ALLOCATED TO DDNAME SYS00009 DATACLAS IGD100I 3DAC ALLOCATED TO DDNAME SYS00010 DATACLAS I
98. IS III IIIT I III ICI GIGI III ICICI SII I II ICI II I I I I I I A E22915 01 Revision 01 Appendix B 165 F373 STEP COPY START 2007088 1301 3741 STEP COPY STOP 2007088 1301 CPU OMIN 00 11SEC SRB OMIN 00 01SEC VIRT 680K SYS 324K EXT 2716K SYS 7536K 75 JOB XXXXPSNP START 2007088 1301 IEF3761 JOB XXXXPSNP STOP 2007088 1301 CPU OMIN 00 115 SRB OMIN 00 01SEC ISIB07151 SVAA 3 1 0 SIBBATCH invoked on Thu Mar 29 2007 13 01 33 SIB07001 13 01 33 XXXX SIBSTK00 x SIB07001 13 01 33 SET ECAMDEVICE 8800 SIB0700I 13 01 34 SET SSNAME SVAA SIB07151 3 1 0 SIBBATCH invoked on Thu Mar 29 2007 13 01 34 SIBO700I 13 01 34 SNAP DATASET INDDNAME SLSCNTL OUTDDNAME OUTSNAP SIBO700I 13 01 34 HOSTCOPYMODE SHARED REPLACE YES TOLENQF Y 51846171 13 01 37 SnapShot completed 0 166 Managing HSC VTCS April 2011 Revision 01 E22915 01 Example 2 Successful DFSMSdss FlashCopy PIT Copy on a JES3 System HSCFLASH JOB XXXXXXX XXXXXXX XXXXXXX MSGCLASS T REGION 0M MSGLEVEL 1 1 NOTIFY XXXXXXX MAIN CLASS D22 k k k k k k k k k k k k k k k k k k k k k k K k K K KOK KOK R KOR KOR KOK R R R KOR KOR R RK OR KOR KOR RK KK SLUPCOPY CDS FLASHCOPY J BR k k k k k k k k k k k k k ko k k k k k K k K OR TOR K R K R KOK RK K oko ek ke Kok R KOR koe OK K OK ke OK OK K K DFDSS E
99. Ifthe source and target devices are not in the same subsystem FDRSNAP issues a User 502 abend and message FDR230 with Reason A 2 The volume label of the target volume is not modified by FDRSNAP in this case FDRSNAP is not normally used by itself a second step is usually added to the procedure JCL to create an online backup of the offline PIT copy using FDR FDRDSF or FDRCOPY Refer to Section 26 in the Fast Dump Restore FDR User Manual for more information E22915 01 Revision 01 Chapter2 23 24 Using the BACKup Utility to Back Up the CDS Running the BACKup utility Allocate the SLSBKUP data set It should be slightly larger than the CDSs The size depends upon the number of discrepancies found However a recommended size is five percent larger than the current CDS The backup data set is formatted as RECFM F BLKSIZE 4096 The logical record length may be LRECL 0 In this case LRECL 0 indicates to default to the block size Run the BACKup utility The CDS is placed in a reserve state only long enough for the data to be copied to the SLSBKUP data set No other functions can access the CDS data sets during backup processing If HSC is not active you must identify the primary secondary and standby CDSs to be used for the backup by specifying the SLSCNTL SLSCNTL2 and SLSSTBY DD statements in the JCL Ifthe HSC is active and you identify the primary secondary and standby CDSs to be used for the backup by s
100. LAS SCSTD MGMTCLAS MCMINBU DATACLAS VOL SER NOS SIP037 IEF237I JES3 ALLOCATED TO SYSIN SLS7100I SLUPCOPY VERSION X XX PROCESSING BEGINS SLS70281 HSC SUBSYSTEM NAME HSCO SLS70281 COPY FUNCTION IS IN EFFECT SLS70281 DFSMSDSS METHOD IS IN EFFECT SLS70281 ABEND OPTION IS ENABLED SLS70701 READ JFCB SUCCESSFUL FOR SLSCNTL DD SLS70101 SSCVT LOCATED FOR SUBSYSTEM HSCO SLS70111 ASCB FOR HSC JOB NAME HSCD22 HAS ASID 0086 SLS71021 HSC QNAME STKALSQN SLS70251 PRIMARY CDS NAME XXXXHSC SLS DBASEPRM SLS70151 JCL CDS NAME MATCHES PRIMARY CDS NAME SLS70711 OPEN SUCCESSFUL FOR SLSCNTL DD SLS70721 RESERVE SUCCESSFUL FOR SLSCNTL DD SLS70731 READ SUCCESSFUL FOR SLSCNTL DD SLS70211 JCL CDS NAME MATCHES DHB CDS NAME SLS70741 ATTACH SUCCESSFUL IEF2371 3679 ALLOCATED TO SYS00001 IGD1011 SMS ALLOCATED TO DDNAME SYS00002 DSN SYS07024 T130601 RA000 HSCFLASH R0152617 STORCLAS SCTEMP MGMTCLAS DATACLAS VOL SER NOS SIP023 IGD1011 SMS ALLOCATED TO DDNAME SYS00003 DSN SYS07024 T130601 RA000 HSCFLASH R0152618 STORCLAS SCTEMP MGMTCLAS DATACLAS VOL SER NOS SIP024 IGD1011 SMS ALLOCATED TO DDNAME SYS00004 DSN SYS07024 T130601 RA000 HSCFLASH R0152619 STORCLAS SCTEMP MGMTCLAS DATACLAS VOL SER NOS SIP036 IGD1011 SMS ALLOCATED TO DDNAME SYS00005 DSN SYS07024 T130601 RA000 HSCFLASH R0152620 STORCLAS SCTEMP MGMTCLAS DATACLAS VOL SER NOS D2PR02 IGD1011 SMS ALLOCATED TO DDNAME SYS00006
101. LINKLIB KEPT IEF285I VOL SER NOS 50020 IEF2851 XXXX SOS610 SLSCNTL KEPT IEF285I VOL SER NOS SW8A45 IEF2851 XXXX XXXXPDSS JOB07749 D0000102 SYSOUT IEF2851 XXXX SLUPCOPY SYSMDUMP CATALOGED IEF285I VOL SER NOS SW8D12 285 XXXX XXXXPDSS JOB07749 D0000101 SYSIN DEVICE DEVICE EXCP DDNAME CLASS ADDRESS COUNT ghee eum G uc STEPLIB DASD 3EC4 00000002 SLSCNTL DASD 8A45 00000004 SYSPRINT JES2 00000000 SYSMDUMP DASD 8D12 00011417 SYSIN JES2 00000000 SYS00002 DASD 3CF1 00000000 SYS00003 DASD 00000000 SYS00004 DASD 3DAC 00000000 SYS00005 DASD 00000000 SYS00006 DASD 3CF1 00000000 SYS00007 DASD 3DAC 00000000 SYS00008 DASD 00000000 SYS00009 DASD 3DAC 00000000 SYS00010 DASD 3DAC 00000000 SYS00011 DASD 00000000 SYS00012 DASD 8A45 00000003 SYS00001 DASD 8D12 00000003 IEF3731 STEP COPY START 2007088 1304 784K IEF3741 STEP COPY STOP 2007088 1304 CPU OMIN 00 65SEC SRB OMIN 00 16SEC VIRT 1868K SYS 400K EXT SYS 7484K IEF375I JOB XXXXPDSS START 2007088 1304 IEF376I JOB XXXXPDSS STOP 2007088 1304 CPU OMIN 00 65SEC SRB OMIN 00 16SEC 1PAGE 0001 5695 DF175 DFSMSDSS V1R05 0 DATA SET SERVICES 2007 088 13 04 COPY DATASET INCLUDE XXXX SOS610 SLSCNTL RENUNC XXXX SOS610 SLSCNTL XXXX S08610 DFSMSDSS FASTR
102. ME SCHSCDS NO DATACLAS AND MGMTCLAS MCRAPP DATA SET XXXXHSC SLS DBASESHD COPIED USING A FAST REPLICATION OADR801I 001 DDDS 01 DATA SET FILTERING IS COMPLETE 2 2 DATA SETS WERE SELECTED 0 OTHER REASONS THE FOLLOWING DATA SETS WERE SUCCESSFULLY PROCESSED XXXXHSC SLS DBASEPRM XXXXHSC SLS DBASESHD 2007 024 13 06 02 EXECUTION ENDS 2007 024 13 06 02 TASK COMPLETED WITH RETURN CODE 0000 XXXXHSC SLS DBASEPRM PER USING FUNCTION XXXXHSC SLS DBASESHD PER USING FUNCTION FAILED SERIALIZATION AND 0 FAILED 2007 024 13 06 02 DFSMSDSS PROCESSING COMPLETE HIGHEST RETURN CODE IS 0000 170 Managing HSC and VTCS April 2011 Revision 01 E22915 01 Example 3 Successful DFSMSdss SnapShot PIT Copy JES2 JOB LOG SYSTEM XXXX NODE 13 02 47 20 07747 THURSDAY 29 MAR 2007 13 02 47 JOBO7747 IRRO10I USERID XXXX IS ASSIGNED TO THIS JOB 13 02 48 JOBO7747 ICH700011 XXXX LAST ACCESS AT 13 01 25 ON THURSDAY MARCH 29 2007 13 02 48 JOBO7747 HASP373 XXXXPDSS STARTED INIT CLASS A SYS XXXX 13 02 48 20 07747 403 XXXXPDSS STARTED TIME 13 02 48 13 02 50 20 07747 SLS71001 SLUPCOPY VERSION 6 20 PROCESSING BEGINS 13 02 50 JOBO7747 SLS70281 HSC SUBSYSTEM NAME 5 13 02 50 20 07747 SLS70281 COPY FUNCTION IS IN EFFECT 13 02 50 20 07747 SLS70281 DFSMSDSS METHOD IS IN EFFECT 13 02 50 20 07747 SLS70281 PIT COPY WTOR OPTION IS ENABLED 13 02 50 JOBO7747 SLS70281 A
103. Managing HSC and VTCS April 2011 Revision 01 E22915 01 12 Run scratch synchronization Run SLUCONDB to synchronize HSC scratch status with the TMS s For more information see ELS Command Control Statement and Utility Reference If you are using LCM see LCM User s Guide for the equivalent LCM utilities 13 If you are using logging audit affected MVCs using the recovery commands from the data set created in Step 5 JOBRMVC job account programmer REGION 1024k S1 EXEC PGM SLUADMIN PARM execution parameters STEPLIB DD DSN hlq SEALINK DISP SHR SLSIN DD DSN offload dataset genaudit DISP SHR SLSPRINT DD SYSOUT If you are not using logging contact StorageTek Software Support for assistance in determining which MVCs need to be audited 14 Start HSC on all hosts 15 Restart tape activity E22915 01 Revision 01 Chapter2 39 40 Managing HSC and VTCS April 2011 Revision 01 E22915 01 CHAPTER 3 Managing a TapePlex In general managing a TapePlex is similar to managing VTCS which is to 1 periodically and continuously keep tabs on the health of your TapePlex es and 2 do as needed chores as the need for them occurs In this chapter however we ll intermix period and as needed tasks as we talk about the physical elements of a TapePlex and what you need to do to keep them operating normally SMC HSC VTCS is server software so it s designed to be self correcting Similarly there s
104. O THIS JOB 04 06 JOBO7749 ICH700011 XXXX LAST ACCESS AT 13 02 53 ON THURSDAY MARCH 29 2007 04 07 JOBO7749 HASP373 XXXXPDSS STARTED INIT AA CLASS A SYS XXXX 04 07 JOBO7749 IEF4031 XXXXPDSS STARTED TIME 13 04 07 04 09 JOBO7749 SLS71001 SLUPCOPY VERSION 6 20 PROCESSING BEGINS 04 09 JOBO7749 SLS7028I HSC SUBSYSTEM NAME HSCX 04 09 JOBO7749 SLS70281 COPY FUNCTION IS IN EFFECT 04 09 JOBO7749 SLS70281 DFSMSDSS METHOD IS IN EFFECT 04 09 JOBO7749 SLS70281 PIT COPY WTOR OPTION IS ENABLED 04 09 JOBO7749 SLS70281 ABEND OPTION IS ENABLED 04 09 JOBO7749 SLS70281 RESERVE RETRY WTOR OPTION IS ENABLED 04 09 JOBO7749 SLS70701 READ JFCB SUCCESSFUL FOR SLSCNTL DD 04 09 JOBO7749 SLS70101 SSCVT LOCATED FOR SUBSYSTEM HSCX 04 09 JOBO7749 SLS70111 ASCB FOR HSC JOB NAME HSCX HAS ASID 001D 04 09 JOBO7749 SLS71021 HSC QNAME HSCXLSON 04 09 JOBO7749 SLS70251 PRIMARY CDS NAME XXXX SOS610 SLSCNTL 04 09 JOBO7749 SLS7015I JCL CDS NAME MATCHES PRIMARY CDS 04 09 JOBO7749 0030 SLS7090A REPLY Y TO INITIATE POINT IN TIME COPY 04 12 JOBO7749 R 30 Y 04 12 JOBO7749 SLS70711 OPEN SUCCESSFUL FOR SLSCNTL DD 04 12 20 07749 SLS71041 UCB LOCATED SUCCESSFULLY 04 12 JOBO7749 SLS70721 RESERVE SUCCESSFUL FOR SLSCNTL DD 04 12 JOBO7749 SLS70731 CDS DHB READ SUCCESSFUL 04 12 JOBO7749 SLS70211 JCL CDS NAME MATCHES DHB CDS NAME 04 12 JOBO7749 SLS71701 CDS DPV READ SUCCESSFUL 04 12 JOBO7749 SLS71061 ORIGINAL LAST BACKUP DATE AND TIME 200
105. PIT copy contains the correct last backup date and time In the event of an unsuccessful PIT copy the last backup date and time in the Primary CDS is restored to the original value to maintain accuracy If SLUPCOPY is cancelled by operator command after the last backup date and time in the Primary CDS is updated SLUPCOPY cannot restore last backup date and time to the correct value Examples Typical message sequences for last backup date and time processing are shown below messages prior to 7072 are not shown in some examples Successful PIT copy 51570721 RESERVE SUCCESSFUL FOR SLSCNTL DD SLS70731 CDS DHB READ SUCCESSFUL SLS70211 JCL CDS NAME MATCHES DHB CDS NAME 51571701 CDS DPV READ SUCCESSFUL SLS71061 ORIGINAL LAST BACKUP DATE AND TIME 2007032913 10 13 5157171 CDS DPV WRITE SUCCESSFUL 51571071 UPDATED LAST BACKUP DATE AND TIME 2007032914 07 09 51 57074 ATTACH SUCCESSFUL SLS70751 TCB USER CC 0000 SYSTEM CC 0000 SLS70761 DETACH SUCCESSFUL SLS70771 MAINLINE DEQ SUCCESSFUL FOR SLSCNTL DD SLS70781 MAINLINE CLOSE SUCCESSFUL FOR SLSCNTL DD SLS70311 POINT IN TIME COPY SUCCESSFUL SLS7111I SLUPCOPY VERSION 6 20 PROCESSING ENDS No action is required since the PIT copy was successful the last backup date and time in the Primary CDS reflects the date and time of the PIT copy E22915 01 Revision 01 AppendixB 177 178 Message 7180 before OPEN and RESERVE An error occurs before the CDS is opened and reserved and bef
106. RE 6 3 POLICY commands for Workload Grouping E22915 01 Revision 01 ChapterG 125 126 Finally FIGURE 6 4 consists of TAPEREQ statements that assign policies as follows Data sets with qualifiers of PAYROLL are assigned policy PPAY Data sets with qualifiers of ACCOUNTS are assigned policy PACCOUNT All other data sets are assigned policy PPROD TAPEREQ DSN PAYROLL POLICY PPAY TAPEREQ DSN ACCOUNTS POLICY PACCOUNT TAPEREQ DSN MEDIA VIRTUAL POLICY PPROD FIGURE 6 4 TAPEREQ Statements for Workload Grouping Once an MVC is used for a Storage Class it remains exclusively assigned to that Storage Class while it contains current VTV copies This grouping of VTVs on MVCs will be retained even after the MVCs undergo reclamation processing Caution You cannot use the default Storage Class the name of the last VTSS that wrote to the MVC for reclamation or migration to group workloads Managing HSC and VTCS April 2011 Revision 01 E22915 01 Segregating Individual Workloads on Separate Sets of MVCs You can use Storage and Management Classes to segregate individual workloads on separate sets of MVCs For example the STORclas statements in FIGURE 6 5 define Storage Classes LOC CUSTA and CUSTBI and CUSTB2 STORCLAS NAME LOC ACS 00 MEDIA STK1R STORCLAS NAME CUSTA ACS 00 MEDIA STK1R STORCLAS NAME CUSTB1 5 00 MEDIA STK1R STORCLAS NAME CUSTB2 ACS 01 MEDIA STK2P
107. RH interval extended Operator Response Required For Mount Dismount Move and Swap For mount dismount move and swap requests the operator is prompted by the message ORH ABORT EXTEND Respond with one of the following ABORT the task that requested the operation is notified that the request has been abnormally terminated by ORH This removes the volume from selected status and lets you issue HSC Mount or DISMount commands as necessary to keep the work moving EXTEND the adds another ten minute increment to the request and leaves it on the same queue that it is currently on There is no limit to the number of extensions you can request E22915 01 Revision 01 Chapter3 71 Using Software Diagnostics Some problems are beyond your ability to resolve by yourself and usually result in a call to StorageTek Software Support who may ask you to use one or more of the HSC software diagnostic tools described in TABLE 3 2 TABLE3 2 HSC Software Diagnostic Tools Diagnostic Tool Description Generalized Trace Facility GTF Tracing GTRACE The Generalized Trace Facility GTF provides a low level history of the recent past The HSC issues GTRACE requests for significant events during operation Format ID and Event ID FID and EID are specified as parameters on the EXEC statement PARM of the HSC JCL procedure refer to Creating an HSC START Procedure in the HSC Configuration Guide for an exam
108. RN CODE IS 0008 FROM TASK 001 SIR ok kk ek IK IO IK ec kk ko IK ke kk kk IK IK ke kk IK IK IK I ec ko ke ko ke kk IK IK ko ek oko IK ke kk oko IK ke kk oko ke ko ke kk oko ke ko ke kk oko ke kk ek IK IK I ek FOR IO I ek TOR IO RIOR ek ke RK RK ee SLUPCOPY VERSION 6 20 A0300000 SYSTEM NAME XXXX LPAR NAME VM NAME XXXXXMVS SUBSYSTEM NAME HSCX 40000000 kk ek FR IK ec koe kk ek IK ke kk ek ke kk kk ek ke kk kk koe kk kk ko ke ko ke kc k e koe ko koe k oko 08 0 FAILED SERIALIZATION AND 0 INC ALL RIGHTS RESERVED RUN TIME 13 11 04 COPYRIGHT 2006 2007 StorageTek VITAL DIAGNOSTIC INFO RUN DATE 03 29 07 JES NAME JES2 CVT PRODN SP7 0 5 FMID HBB7708 DFAR 03010500 FT14 FF7F737F FT56 JES TYPE JES2 ECVT PNAM z OS VRM 010500 PSEQ 01010500 PROC P302A CPID FFXXXXXX2084 SUSE 433B1000 SUS2 2445D4C7 FLG1 LVT ADDR 433B1000 SSCT ADDR 00963124 SSVT 433040 0 E22915 01 Revision 01 AppendixB 187 Example 7 Failed FDRSNAP PIT Copy target volume not offline JES2 JOB LOG SYSTEM XXXX NODE 13 06 19 JOB07750 THURSDAY 29 MAR 2007 13 06 19 JOBO7750 IRRO10I USERID XXXX IS ASSIGNED TO THIS JOB 13 06 20 20 07750 700011 LAST ACCESS AT 13 04 13 ON THURSDAY MARCH 29 2007 13 06 20 JOBO7750 HASP373 XXXXPFDR STARTED INIT CLASS A SYS XXXX 13 06 20 20 07750 403 XXXXPFDR STARTED TIME 13
109. Revision 01 E22915 01 Converting a Single VTV by Specifying Its Volser and Block ID FIGURE 7 3 shows example JCL to run the RTV utility to convert VTV VTV200 at block ID X 8EA484AB on MVC 001 which will be mounted on a 3490E transport The output converted VTV VTV200 goes to the output volume mounted on transport 480 JOBVRECJOB account programmer RUNRTV EXEC PGM SWSRTV PARM MIXED STEPLIB DD DSN hlq SEALINK DISP SHR SLSPRINTDD SYSOUT A SLSIN DD RTV 001 INUNIT 3490E VTV VTV200 BLOCK 8EA484AB OUTUNIT 480 FIGURE 7 3 Example JCL to run the RTV utility single VTV by volser and block ID E22915 01 Revision 01 Chapter7 151 152 Managing HSC and VTCS April 2011 Revision 01 E22915 01 APPENDIX A LCM Control Statements TABLE 1 LCM Control Statements LCM Control Statement Status HSC VTCS Utility Command ACTION CONSOLIDATE Enhanced CONSOLIDATE ACTION DRAIN New MVCDRAIN ACTION EJECT Enhanced EJECT ACTION EXPORT Enhanced EXPORT ACTION MIGRATE Enhanced MIGRATE ACTION MOVE Enhanced MOVE ACTION RECALL Enhanced RECALL ACTION RECLAIM New RECLAIM ACTION SCRATCH New SCRATCH ACTION UNSCRATCH New UNSCRATCH REPLACEALL DATASET Enhanced LOCATION Unchanged MANAGE PHYSICAL Unchanged MANAGE VIRTUAL Unchanged METHOD Enhanced OPTIONS Enhanced OPTIONS SYNC and SYNCVTV Un
110. S control Note Because the RTV utility must be capable of rewriting the tape standard labels on the output unit and positioning over label information on the input unit Dynamic Allocation is used to invoke bypass label processing BLP on the tape volumes This requires that the library that contains the SWSRTV executable code be APF authorized E22915 01 Revision 01 Chapter7 149 JCL Examples Listing the VTVs on an MVC FIGURE 7 1 shows example JCL to lists the VTVs on MVC MVC001 JOBVRECJOB account programmer RUNRTV EXEC PGM SWSRTV PARM MIXED STEPLIB DD DSN hlq SEALINK DISP SHR SLSPRINTDD SYSOUT A SLSIN DD RTV MVC MVCOO1 INUNIT 1AB4 LISTONLY FIGURE 7 1 Example JCL to run the RTV utility LISTONLY run Converting a Single VTV by Specifying Its Volser FIGURE 7 2 shows example JCL to run the RTV utility to convert VTV VTV200 on MVC MVCOOI which will be mounted on a 3490E transport The output converted VTV VTV200 goes to the output volume mounted on transport 280 and RTV copies the VTV VOLID from the VTV to the output volume JOBVRECJOB account programmer RUNRTV EXEC PGM SWSRTV PARM MIXED STEPLIB DD DSN hlq SEALINK DISP SHR SLSPRINT DD SYSOUT A SLSIN DD RTV MVC MVCO01 INUNIT 3490E VTV VTV200 CPYVOLID OUTUNIT 280 FIGURE 7 2 Example JCL to run the RTV utility single VTV by volser 150 Managing HSC and VTCS April 2011
111. S71881 ESTAE ROUTINE PROCESSING ENDS TEA995I SYMPTOM DUMP OUTPUT 724 Message 7182 is issued indicating that the last backup date and time in the Primary CDS needs to be restored to its original value as previously displayed by message 7106 Message 7186 is issued indicating that the ESTAE recovery routine successfully restored the last backup date and time in the Primary CDS to its original value and that no further action needs to be taken Message 7181 An error occurs after the last backup date and time 1s updated and after the PIT copy 51570721 RESERVE SUCCESSFUL FOR SLSCNTL DD SLS70731 CDS DHB READ SUCCESSFUL 5157021 JCL CDS NAME MATCHES DHB CDS NAME 51571701 CDS DPV READ SUCCESSFUL SLS71061 ORIGINAL LAST BACKUP DATE AND TIME 2007032914 07 09 5157171 CDS DPV WRITE SUCCESSFUL 51 571071 UPDATED LAST BACKUP DATE AND TIME 2007032914 11 35 SLS70741 ATTACH SUCCESSFUL SLS70751 TCB USER CC 0000 SYSTEM CC 0000 51 570811 ESTAE ROUTINE SDWA PRESENT 5157181 ESTAE ROUTINE DPV RESTORE NOT REQUIRED PIT COPY SUCCESSFUL SLS70821 ESTAE ROUTINE DEQ SUCCESSFUL 51 57083 ESTAE ROUTINE CLOSE SUCCESSFUL SLS71881 ESTAE ROUTINE PROCESSING ENDS IEA995 SYMPTOM DUMP OUTPUT 791 E22915 01 Revision 01 AppendixB 179 Message 7181 is issued indicating that the ESTAE recovery routine determined that the last backup date and time in the Primary CDS did not need to be restored to its original value as previously displayed by message 710
112. SC SLS DBASEPRM XXXXHSC SLS DBASEPRM PER XXXXHSC SLS DBASESHD XXXXHSC SLS DBASESHD PER FASTREPLICATION REQUIRED CANCELERROR SHARE TOL ENQF TGTALLOC CYL OUTDYNAM XX3679 CATALOG E22915 01 Revision 01 AppendixB 169 AGE 0001 5695 DF175 COPY DATASET INCLUDE RENUNC CANCELERROR SHARE TOL ENQF TGTALLOC CYL OUTDYNAM XX3679 CATALOG ADR1011 R I RIO1 01 ADR109I R I RIO1 01 ADRO16I 001 PRIME 01 OADROO6I 001 STEND 01 OADR7111 001 NEWDS 01 STORCLAS OADR806I 001 TOMI 01 OADR7111I 001 NEWDS 01 STORCLAS OADR806I 001 TOMI 01 FOR OADR454I 001 DDDS 02 0 0 OADROO6I 001 STEND 02 OADRO131 001 CLTSK 01 OADRO121 SCH DSSU 01 DFSMSDSS V1R06 0 DATA SET SERVICES 2007 024 13 06 XXXXHSC SLS DBASEPRM XXXXHSC SLS DBASESHD XXXXHSC SLS DBASEPRM XXXXHSC SLS DBASEPRM PER XXXXHSC SLS DBASESHD XXXXHSC SLS DBASESHD PER FASTREPLICATION REQUIRED 2 TASKID 001 HAS BEEN ASSIGNED TO COMMAND COPY 2007 024 13 06 01 INITIAL SCAN OF USER CONTROL STATEMENTS COMPLETED RACF LOGGING OPTION IN EFFECT FOR THIS TASK 2007 024 13 06 01 EXECUTION BEGINS DATA SET XXXXHSC SLS DBASEPRM HAS BEEN ALLOCATED WITH NEWNAME SCHSCDS NO DATACLAS AND MGMTCLAS MCRAPP DATA SET XXXXHSC SLS DBASEPRM COPIED USING A FAST REPLICATION DATA SET XXXXHSC SLS DBASESHD HAS BEEN ALLOCATED WITH NEWNA
113. SCNTL 13 08 22 20 07751 SLS7015I CDS NAME MATCHES PRIMARY CDS NAME 13 08 22 20 07751 SLS7071I OPEN SUCCESSFUL FOR SLSCNTL DD 13 08 22 20 07751 51571041 UCB LOCATED SUCCESSFULLY 13 08 22 20 07751 SLS7072I RESERVE SUCCESSFUL FOR SLSCNTL DD 13 08 22 20 07751 SLS7073I CDS DHB READ SUCCESSFUL 13 08 22 20 07751 SLS7021I JCL CDS NAME MATCHES DHB CDS 13 08 22 20 07751 SLS7170I CDS DPV READ SUCCESSFUL 13 08 22 20 07751 51571061 ORIGINAL LAST BACKUP DATE AND TIME 2007032913 02 53 13 08 22 20 07751 SLS71711 CDS DPV WRITE SUCCESSFUL 13 08 22 20 07751 SLS7107I UPDATED LAST BACKUP DATE AND TIME 2007032913 08 22 13 08 22 20 07751 51570741 ATTACH SUCCESSFUL 13 08 23 20 07751 SLS7075I TCB USER CC 0000 SYSTEM CC 0000 13 08 23 20 07751 51570761 DETACH SUCCESSFUL 13 08 23 20 07751 SLS7077I MAINLINE DEQ SUCCESSFUL FOR SLSCNTL DD 13 08 23 20 07751 SLS7078I MAINLINE CLOSE SUCCESSFUL FOR SLSCNTL DD 13 08 23 JOB07751 SLS70311 POINT IN TIME COPY SUCCESSFUL 13 08 23 20 07751 51571111 SLUPCOPY VERSION 6 20 PROCESSING ENDS 13 08 23 20 07751 SYSTEM RELEASE SP7 0 5 HBB7708 13 08 23 JOB07751 TIMINGS MINS PAGING COUNTS 13 08 23 20 07751 JOBNAME STEPNAME PROCSTEP RC EXCP CPU SRB CLOCK SERV PG PAGE SWAP VIO SWAPS 13 08 23 20 07751 XXXXPFDR COPY 00 134 00 00 0 808 0 0 0 0 0 13 08 23 20 07751 IEF4041 XXXXPFDR ENDED TIME 13 08 23 13 08 23 20 07751 XXXXPFDR ENDED NAME XXXXXXXX TOTAL CPU TIME 00
114. SCNTL DD 13 11 04 20 07755 SLS7078I MAINLINE CLOSE SUCCESSFUL FOR SLSCNTL DD 13 11 04 20 07755 SLS7035E POINT IN TIME COPY INVALID 13 11 04 20 07755 51571121 SLUPCOPY VERSION 6 20 ABENDED BY REQUEST 13 11 19 JOB07755 IEA995I SYMPTOM DUMP OUTPUT 224 224 USER COMPLETION CODE 0555 224 TIME 13 11 04 SEQ 00401 0000 ASID 002A 224 PSW AT TIME OF ERROR 07801000 00008B22 ILC 2 INTC OD 224 ACTIVE LOAD MODULE ADDRESS 00007000 OFFSET 00001B22 224 NAME SLUPCOPY 224 DATA AT PSW 00008B1C 00181610 OAODBFBF 00050 0 224 GR 0 C0000000 1 C000022B 224 2 00009A20 3 006 224 4 00009488 5 000097B3 224 6 00009000 7 0000 000 224 8 006 9 00000064 224 00008000 OOOOAB4A 224 00007000 D 0000 000 224 E 500080EE F 00000000 224 END OF SYMPTOM DUMP 13 11 19 JOB07755 IEA9931 SYSMDUMP TAKEN TO XXXX SLUPCOPY SYSMDUMP 13 11 19 JOB07755 IEFA450I XXXXPDSS COPY ABEND S000 U0555 REASON 00000000 226 226 TIME 13 11 19 13 11 20 JOB07755 SYSTEM RELEASE SP7 0 5 HBB7708 13 11 20 JOB07755 TIMINGS MINS 13 11 20 JOB07755 JOBNAME STEPNAME PROCSTEP RC EXCP CPU SRB CLOCK 13 11 20 JOB07755 XXXXPDSS COPY 00555 12228 01 00 6 13 11 20 20 07755 404 XXXXPDSS ENDED 13 11 20 13 11 20 20 07755 XXXXPDSS ENDED NAME XXXXXXXX TOTAL CPU TIME 13 11 20 20 07755 HASP395 XXXXPDSS ENDED JES2 JOB STATISTICS 29 MAR 2007 JOB EXECUTION DATE E 27 CARDS READ x 218 SYSOUT PR
115. SL8500 lib 3 SL8500 lib 4 129 30 71 81 129 80 61 21 i e FIGURE 3 1 Dual LC Configuration 44 Managing HSC and VTCS April 2011 Revision 01 E22915 01 The following rules apply to a dual LC configuration Both LCs Should be connected to all hosts Can be powered on at all times and 2 Must be connected to both LAN 0 and LAN In the event of a failure from the active LC an automated switch will occur and the standby assumes the active LC role The HSC is informed and notifies the operator of the switch Most outstanding requests are re driven and all future library requests are sent to the newly activated LC Once the failed LC is repaired and powered on it assumes the standby role An operator SWitch command is provided for those occasions when it becomes desirable to dynamically activate a standby LC The operator issues the Switch command and the standby LC assumes the active LC role after instructing the former active LC to initiate a reboot If the former active LC reboots successfully it assumes the standby LC role Note Warnings and precautions apply to operating in a dual LC environment See Redundant LC Operational Overview on page 47 and become familiar with these requirements Network connections must be specified for both the active and standby LCs when the HSC is installed SL8500 Redundant Electronics Environment Library requests cannot be automated if all networ
116. SLUPCOPY ends with an RC 12 ASIBCTRAN or CTRANS DD is required if the SACLINK library is not in the system linklist If SAS C transient libraries are present for other software products remove the CTRANS DD and specify the SIBCTRAN DD only See SVAA Version 3 1 for OS 390 Installation Customization and Maintenance Ifnot using the INDDNAME parameter make sure that data set name on the SLSCNTL DD statement matches the data set name on the SOURCE parameter Also if not using the INDDNAME parameter the HOSTCOPYMODE SHARED parameter is required on the SnapShot command otherwise one of the following will occur timestamp values will differ If TOLENQF Y is specified SIB4701W Unable to obtain EXCLUSIVE control on datasetname SIBA4617I 09 35 00 SnapShot completed rc 4 If TOLENQF N is specified or defaulted to SIB4632E Dynamic allocation failed rc 4 reason 020C0000 smscode 00 SIB46331 IKJ562411 DATA SET datasetname NOT ALLOCATED SIBA4633I IKJ562411 DATA SET IS ALLOCATED TO ANOTHER JOB OR USER SIB4627E Unable to allocate the resource datasetname SIBA4617I 09 33 53 SnapShot completed rc 8 Both of the above result in a Point In Time copy invalid message SLS7035E and an RC 12 Ifthe SnapShot target data set is pre allocated in an earlier job step and the OUTDDNAME parameter is used specify the HSC Primary CDS name on the LIKE parameter on the OUTDDNAME DD statement to avoid the following SI
117. SP SHR SLSVDI DD SYSOUT SYSPRINT DD SYSOUT SYSMDUMP DD DSN HSC SLUPCOPY SYSMDUMP DISP DELETE CATLG UNIT SYSALLDA SPACE CYL 100 RLSE VOL SER VVVVVV 1 DD DUMMY SYSIN DD DSN HSC LIB CNTL PITFDRI DISP SHR HSC LIB CNTL PITFDRI SNAP TYPE FDR DSNENQ NONE MOUNT VOL TTTTTT SNAPUNIT DDDD FIGURE 2 5 SLUPCOPY FDRSnap JCL Example The requirements for SLUPCOPY with FDRSnap are 2 FDRSNAP must be in the system linklist The HSC CDS must reside on SVA hardware with the SnapShot feature enabled to be eligible for a FDRSNAP operation Volume copy only is supported No check is made for a minimum level of FDRSNAP dummied DD is required The DSNENQ NONE parameter is required 2 This prevents FDRSNAP from issuing a SYSDSN ENQ on the HSC CDS IfDSNENQ NONE is not specified the PIT copy is not performed and SLUPCOPY ends with an RC 12 A FDR158 message and User 801 abend also occur but these are issued by FDRSNAP not SLUPCOPY The ENQ OFF parameter is strongly recommended This prevents FDRSNAP from issuing a SYSVTOC ENQ and RESERVE on the HSC CDS volume The VOL parameter must specify the online device of the HSC CDS that is the SnapShot source The SNAPUNIT parameter must specify the offline device that is the SnapShot target Ifthe target device is not offline FDRSNAP issues a User 502 abend and message FDR230 with Reason 8
118. STBY DD DSN standby dataset name DISP SHR SLSPRINT DD SYSOUT A SLSIN DD OFFLOAD LOGFILE This automatically causes HSC to switch to the new log files 26 Managing HSC and VTCS April 2011 Revision 01 E22915 01 Manually Switching to Another CDS Copy As described in Backing Up the CDS on page 10 if you specify multiple CDS copies HSC automatically switches to another CDS copy if the Primary CDS fails So why would you want to manually switch to another CDS copy Basically you would do so in either of the following situations You want to move the CDS and or expand it After an HSC automatically switches CDS copies you want to delete the old Primary reallocate it and repopulate it Once you enable the reallocated Primary CDS HSC will recopy the valid CDS data to it from a backup copy You use the CDS ENABLE DISABLE commands to switch expand or move CDS copies For more information see ELS Command Control Statement and Utility Reference E22915 01 Revision 01 Chapter2 27 Expanding the CDS You can use the CDS EXpand command to add VOLPARM data VTCS CONFIG data or vaulted volume data to the CDS To make other configuration changes that may require increasing the size of the CDS such as adding new ACSs and LSMs when the LIBGEN did not use the FUTRACS and FUTRLSM parameters you must use other methods instead of CDS EXpand See Reconfiguring a TapePlex in Configuring HSC an
119. STEPLIB DD DSN HSC LINKLIB DISP SHR SLSCNTL DD DSN HSC PRIMARY CDS DISP SHR SLSVDI DD SYSOUT SYSPRINT DD SYSOUT SYSTERM DD SYSOUT SIBCTRAN DD DSN HSC SACLINK DISP SHR CTRANS DD DSN HSC SACLINK DISP SHR SYSMDUMP DD DSN HSC SLUPCOPY SYSMDUMP DISP DELETE CATLG UNIT SYSALLDA SPACE CYL 100 RLSE VOL SER VVVVVV OUTSNAP DD DSN HSC PITSNAP CDS LIKE HSC PRIMARY CDS DISP CATLG DELETE VOL SER TTTTTT UNIT SYSALLDA SPACE CYL NNN SYSIN DD DSN HSC LIB CNTL PITSNPI DISP SHR HSC LIB CNTL PITSNPI SNAP DATASET INDDNAME SLSCNTL OUTDDNAME OUTSNAP HOSTCOPYMODE SHARED REPLACE YES TOLENOF Y FIGURE 2 2 SLUPCOPY SVAA SnapShot JCL Example The requirements for SLUPCOPY with SVAA SnapShot are 2 Ensure that you have completed Step 2 Step 3 Step 4 on on page 13 The HSC CDS must reside on SVA hardware with the SnapShot feature enabled to be eligible for a native SnapShot operation The source and target data sets must be on the same SVA otherwise a physical copy is attempted Both source and target volumes must be online Volume or data set copy is supported but a data set copy is recommended See Software Pre Requisites in Chapter 1 of SVAA Version 3 1 for OS 390 Installation Customization and Maintenance for the list of software pre requisites for using SnapShot No check is made for a minimum level of SIBBATCH Verify that all ne
120. SUCCESSFUL 13 03 11 20 07747 SLS71111 SLUPCOPY VERSION 6 20 PROCESSING ENDS 13 03 11 20 07747 SYSTEM RELEASE SP7 0 5 HBB7708 13 03 11 20 07747 TIMINGS 5 PAGING COUNTS 13 03 11 JOB07747 JOBNAME STEPNAME PROCSTEP RC EXCP CPU SRB CLOCK SERV PG PAGE SWAP VIO SWAPS 13 03 11 JOB07747 XXXXPDSS COPY 00 739 00 00 wd 3588 0 0 0 0 0 13 03 11 JOBO7747 IEFA4041 XXXXPDSS ENDED TIME 13 03 11 13 03 11 20 07747 XXXXPDSS ENDED NAME XXXXXXXX TOTAL CPU TIME 00 TOTAL ELAPSED TIME 3 13 03 11 JOBO7747 HASP395 XXXXPDSS ENDED 0 JES2 JOB STATISTICS 29 MAR 2007 JOB EXECUTION DATE 27 CARDS READ 171 SYSOUT PRINT RECORDS E 0 SYSOUT PUNCH RECORDS 11 SYSOUT SPOOL KBYTES 0 39 MINUTES EXECUTION TIME 1 XXXXPDSS JOB XXXXXX XXXXXXXX JOB07747 CLASS A MSGCLASS 1 DSS PIT COPY At cnc ER BE Gas PEER ere 2 COPY EXEC PGM SLUPCOPY REGION 4M PARM HSCX COPY DSS 3 STEPLIB DD DSN XXXX LINKLIB DISP SHR 4 SLSCNTL DD DSN XXXX SOS610 SLSCNTL DISP SHR 5 SYSPRINT DD SYSOUT 6 SYSMDUMP DD DSN XXXX SLUPCOPY SYSMDUMP DISP DELETE CATLG UNIT SYSALLDA SPACE CYL 100 RLSE VOL SER SW8D12 7 SYSIN DD ICH700011 XXXX LAST ACCESS AT 13 01 25 ON THURSDAY MARCH 29 2007 IEF236I ALLOC FOR XXXXPDSS COPY IEF2371 3EC4 ALLOCATED TO STEPLIB IEF2371 8A45 ALLOCATED TO SLSCNTL IEF2371 JES2 ALLOCATED TO
121. SYSPRINT IGD1001 8D12 ALLOCATED TO DDNAME SYSMDUMP DATACLAS IEF2371 JES2 ALLOCATED TO SYSIN IEF237I 8D12 ALLOCATED TO SYS00001 IGD1001 3EF1 ALLOCATED TO DDNAME SYS00002 DATACLAS IGD1001 3DAC ALLOCATED TO DDNAME SYS00003 DATACLAS IGD1001 3CF1 ALLOCATED TO DDNAME SYS00004 DATACLAS IGD1001 3DAC ALLOCATED TO DDNAME SYS00005 DATACLAS IGD1001 3DAC ALLOCATED TO DDNAME SYS00006 DATACLAS E22915 01 Revision 01 AppendixB 171 D100I 3EF1 ALLOCATED TO DDNAME SYS00007 DATACLAS IGD100I 3EF1 ALLOCATED TO DDNAME SYS00008 DATACLAS IGD100I 3EF1 ALLOCATED TO DDNAME SYS00009 DATACLAS IGD100I 3CF1 ALLOCATED TO DDNAME SYS00010 DATACLAS IGD100I 3CF1 ALLOCATED TO DDNAME SYS00011 DATACLAS IEF2371 8A45 ALLOCATED TO SYS00012 IEF2851 SYS07088 T130254 RA000 XXXXPDSS R0100581 DELETED IEF285I VOL SER NOS WORKO8 IEF285I SYS07088 T130254 RA000 XXXXPDSS R0100582 DELETED IEF285I VOL SER NOS WORKO2 IEF285I SYS07088 T130255 RA000 XXXXPDSS R0100583 DELETED IEF285I VOL SER NOS WORKO1 2851 SYS07088 T130255 RA000 XXXXPDSS R0100584 DELETED IEF285I VOL SER NOS WORKO2 IEF285I SYS07088 T130255 RA000 XXXXPDSS R0100585 DELETED IEF285I VOL SER NOS WORKO2 IEF285I SYS07088 T130256 RA000 XXXXPDSS R0100586 DELETED IEF285I VOL SER NOS WORKO8 IEF285I SYS07088 T130256 RA000 XXXXPDSS R0100587 DELETED IEF285I VOL SER NOS WORKO8 IEF285I 8YS07088 T130257 RA000 XXXXPDSS R0100588 DELETED IEF
122. T Copy 174 Example 5 Failed DFSMSdss SnapShot PIT Copy SVAA not initialized 176 Last Backup Date and Time and Error Recovery Considerations 177 Example 6 Failed DFSMSdss SnapShot PIT Copy Duplicate Target Data Set 185 Example 7 Failed FDRSNAP PIT Copy target volume not offline 188 Index 191 E22915 01 Revision 01 CHAPTER 1 The Toolkit s TABLE 1 1 and TABLE 1 2 on page 6 describe the tools you need to manage HSC and VTCS grouped by the interface For more information about the tools see ELS Command Control Statement and Utility Reference E22915 01 Revision 01 The HSC Toolkit TABLE 14 The HSC Toolkit This tool does the following and is used to do these tasks HSC Operator Commands which includes hardware statuses for the ACSs LMUS and stations and scratch volumes and free cells CDS ENABLE DISABLE Switches expands or moves CDS Manually Switching to Another CDS copies Copy on page 27 COMMPATH Changes communications settings Restoring Host To Host Communications Services on page 70 DISPLAY ACS Displays the status of your ACSs Managing ACSs on page 42 based on subpools available DISPLAY ALL All of DISPLAY ACS plus LSM and CDS status DISPLAY CAP Displays CAP information Managing CAPs on page 52 DISPLAY EXCEPTNS Displays library hardware problems Managing Library Hardware on page 42 DISPLAY LSM Displays LSM
123. TEP COPY START 2007088 1310 IEF3741 STEP COPY STOP 2007088 1311 CPU OMIN 00 67SEC SRB OMIN 00 16SEC VIRT SYS 7484K IEF375I JOB XXXXPDSS START 2007088 1310 IEF376I JOB XXXXPDSS STOP 2007088 1311 CPU OMIN 00 67SEC SRB OMIN 00 16SEC 1 0001 5695 DF175 DFSMSDSS V1R05 0 DATA SET SERVICES 2007 088 13 10 COPY lt DATASET INCLUDE XXXX SOS610 SLSCNTL RENUNC XXXX SOS610 SLSCNTL XXXX S08610 DFSMSDSS FASTREPLICATION REQUIRED 1868K SYS 400K EXT 788K CANCELERROR SHARE TOL ENQF TGTALLOC CYL OUTDYNAM 548012 CATALOG ADR1011 R I RIO1 01 TASKID 001 HAS BEEN ASSIGNED TO COMMAND ADR109I R I RIO1 01 2007 088 13 10 49 INITIAL SCAN OF USER CONTROL STATEMENTS COMPLETED ADRO16I 001 PRIME 01 RACF LOGGING OPTION IN EFFECT FOR THIS TASK OADROOGI 001 STEND 01 2007 088 13 10 49 EXECUTION BEGINS OADR472E 001 NEWDS 11 UNABLE TO SELECT A TARGET VOLUME FOR DATA SET XXXX SOS610 SLSCNTL OADR801I 001 DDDS 01 DATA SET FILTERING IS COMPLETE 1 OF 1 DATA SETS WERE SELECTED FAILED FOR OTHER REASONS OADR455W 001 DDDS 02 THE FOLLOWING DATA SETS WERE NOT SUCCESSFULLY PROCESSED 0 XXXX S0S610 SLSCNTL OADROOGI 001 STEND 02 2007 088 13 11 04 EXECUTION ENDS OADRO131 001 CLTSK 01 2007 088 13 11 04 TASK COMPLETED WITH RETURN CODE 0008 OADRO121 SCH DSSU 01 2007 088 13 11 04 DFSMSDSS PROCESSING COMPLETE HIGHEST RETU
124. TER 00 00 02 SCRATCH Note If all CAPs are currently in use for ejects you can use the SENter command to schedule a CAP for cartridge entry 4 Enter the cartridges per the Operator 5 Guide for your LSM type E22915 01 Revision 01 Chapter3 61 Ejecting Volumes As described in the following sections there are basically three reasons why you want to eject volumes 2 You defined too many scratch volumes and temporarily need some room for specific volumes see Ejecting Scratch Volumes on page 62 You have specific volumes that are no longer in use and you want to vault them For more information see ELS Disaster Recovery and Offsite Data Management Guide You have specific 9x40 volumes that are nearing end of Media Warranty Life FIGURE 3 2 on page 55 shows a volume report with the MWL column on the extreme right This column shows the percentage of Media Warranty Life used for the volume where 96100 means the volume has exceeded its Media Warranty Life Note For 9x40 volumes the Media Information Record MIR stores the number of times the cartridge has been mounted during its lifetime During dismount processing HSC uses the mount count value read from the MIR to compute the MWL For HSC to report MWL for a library resident volume the volume must have been mounted and dismounted at least once after it was entered into the library When a volume is ejected the associated CDS VAR record is deleted
125. TIL FOR LOSTMVC statement to recover VTVs that resided on lost or damaged MVCs How does the LOGUTIL FOR LOSTMVC statement work and how do you use it most effectively Well as follows The FOR LOSTMVC utility scans the CDS and the log file structure if necessary to identify all VTVs on the lost or damaged MVCs whose volsers you specify and to determine the recovery method from an alternate VTV copy as described in TABLE 5 2 on page 115 LOGUTIL FOR LOSTMVC generates a report showing all VTVs that existed on the lost or damaged MVCs and how they will be recovered plus summary information for each lost or damaged MVC 114 Managing HSC and VTCS April 2011 Revision 01 E22915 01 TABLE 5 2 Alternate VTV Copy and Recovery Process Alternate VTV Copy Category Recovery Process Category 1 Currently VTSS resident Recovery is from the resident copy If you requested recovery commands VTVMAINT ULINKMVC commands are generated to unlink the VTV from the lost or damaged MVCs Category 2 Currently linked to one or more alternate MVC copies Recovery is from the best alternate MVC based on four factors Does an MVC record exist in the CDS for the MVC Is the MVC in lost status Is the MVC in broken status Has a data check occurred on the MVC If you requested recovery commands VTVMAINT ULINKMVC and RECALL commands are generated to unlink the VTV from the lost or damaged MVCs and then recall the MVC
126. TOTAL ELAPSED TIME 0 13 08 23 JOBO7751 HASP395 XXXXPFDR ENDED JES2 JOB STATISTICS 29 MAR 2007 JOB EXECUTION DATE 19 CARDS READ c 125 SYSOUT PRINT RECORDS 0 SYSOUT PUNCH RECORDS 8 SYSOUT SPOOL KBYTES 0 05 MINUTES EXECUTION TIME 1 XXXXPFDR JOB XXXXXX XXXXXXXX JOB07751 CLASS A MSGCLASS 1 FDRSNAP PIT COPY 2 COPY EXEC PGM SLUPCOPY REGION 4M PARM HSCX COPY FDR OPT RR 3 STEPLIB DD DSN XXXX LINKLIB DISP SHR SLSCNTL DD DSN XXXX S0S610 SLSCNTL DISP SHR 5 SYSPRINT DD SYSOUT 6 SYSMDUMP DD DSN XXXX SLUPCOPY SYSMDUMP DISP DELETE CATLG UNIT SYSALLDA SPACE CYL 100 RLSE VOL SER SW8D12 7 1 DD DUMMY 8 SYSIN DD ICH700011 XXXX LAST ACCESS AT 13 06 20 ON THURSDAY MARCH 29 2007 IEF236I ALLOC FOR XXXXPFDR COPY IEF2371 3EC4 ALLOCATED TO STEPLIB IEF2371 8A45 ALLOCATED TO SLSCNTL IEF2371 JES2 ALLOCATED TO SYSPRINT IGD1001 8D12 ALLOCATED TO DDNAME SYSMDUMP DATACLAS IEF2371 DMY ALLOCATED TO TAPE1 IEF2371 JES2 ALLOCATED TO SYSIN IEF2371 8A45 ALLOCATED TO D SW8A45 IEF2371 8A45 ALLOCATED TO T SW8A45 IEF285I YS07088 T130822 RA000 XXXXPFDR R0100612 KEPT IEF285I VOL SER NOS SW8A45 IEF285I YS07088 T130822 RA000 XXXXPFDR R0100613 KEPT IEF285I VOL SER NOS SW8A45 IEF1421 XXXXPFDR COPY
127. TVMAINT to logically dismount VTVs in the offline VTSS turn off the mounted bit in the CDS then recall the VTV to an alternate VTSS VTCS records each successful dismount the SMF14STA field of the SMF Subtype 14 record The VTVRPT UNAVAIL option reports the status of unavailable V TVs in an offline VTSS For more information see ELS Command Control Statement and Utility Reference Don t dismount an unavailable VTV in an offline VTSS unless you are absolutely sure that the MVC copies if any of the VTV are identical in content to the unavailable VTV Otherwise you risk recalling a VTV with back level data to an alternate VTSS For example a VTV mounted for read is probably safe to dismount for recall to an alternate VTSS A VTV mounted for write however is probably not safe to dismount because it has probably been updated and the MVC copies are therefore back level The following procedure provides the general steps you use to logically dismount a VTV and access that VTV from a different VTSS To logically dismount a VTV and access that VTV from a different VTSS 1 Vary the VTSS offline to VTCS with the following command VT VARY VTSS name OFFLINE If I O was active and the VTSS failed MVS should box the VTDs and dismount any mounted VTVs from the MVS perspective However if communication with the VTSS failed before the VTSS actually dismounted any mounted VTVs they may still be online to VTCS Therefore you first
128. Tek however does not recommend these methods Disk mirroring can impact ELS performance or data integrity DFSMSdss and Innovation FDR or their functional equivalents do not absolutely guarantee proper serialization and data integrity of the backup Third party Point In Time Copy software does not create true point in time copies and does not absolutely guarantee serialization and data integrity Instead StorageTek recommends the following for CDS backup SLUPCOPY requires other system facilities such as DFSMSdss SnapShot to create the backup snapshot If you have the prerequisites for SLUPCOPY use SLUPCOPY which versus BACKUP significantly reduces the time required to make a CDS back up copy and better ensures the integrity of the copy Ifyou do not have the SLUPCOPY requirements StorageTek recommends that you use HSC SLUADMIN BACKUP Frequency of Backup StorageTek recommends that you back up the CDS at least daily If using CDS Logging you should also run a Log File Offload immediately after you back up the CDS so that during recovery you can select the log offload file that corresponds to the backup file you use for recovery You should also back up the CDS before configuration changes and other significant events including but not limited to Running the SLUADMIN SET utility Running the VTCS CONFIG utility Moving a CDS Expanding a CDS Merging CDSs 10 Managing HSC and VTCS April 2011 Revisi
129. VC SUMMARY RECORD VTV COUNT 22 FOR MVC EVS102 FIGURE 4 12 Example MVC detailed report additional fields Here s some detailed information about the VTVs on an MVC that you can do some diagnostic work with if necessary Just as is now available with the VTV Report you can also do either of the following with the MVC Report Generate output in either Structured XML Comma Separated Variables CSV XML as described in ELS Programming Reference 2 Use the corresponding LCM reports as described in LCM Control Statements on page 153 So In Closing that s about all there is to using VTCS Dashboard Sure there s a bunch of other tasks you could do and probably will do such as but not limited to running MVC Pool Reports if you used Named MVC Pools But that s information for As Needed management tasks The main thing you should learn from this chapter is do your dailies per Checking Virtual Tape Status Daily on page 74 and Checking Nearline Tape Status Daily on page 78 and your weeklies per Looking at the Big Picture Weekly on page 82 and you ll keep your VTCS system running properly 86 Managing HSC and VTCS April 2011 Revision 01 E22915 01 E22915 01 Revision 01 Chapter4 87 88 Managing HSC and April 2011 Revision 01 E22915 01 CHAPTER 5 Working the VTCS Must Do Sometime Chores List Welcome to the VTCS Must Do Sometimes Chores List
130. VTSOCT1 TSOCAT DATA SET FILTERING IS COMPLETE 1 OF 1 DATA SETS WERE SELECTED 0 FAILED SERIALIZATION AND 0 OTHER REASONS THE FOLLOWING DATA SETS WERE SUCCESSFULLY PROCESSED XXXX SOS610 SLSCNTL 2007 088 13 03 10 EXECUTION ENDS 2007 088 13 03 10 TASK COMPLETED WITH RETURN CODE 0000 2007 088 13 03 10 DFSMSDSS PROCESSING COMPLETE HIGHEST RETURN CODE IS 0000 E22915 01 Revision 01 Appendix B 173 Example 4 Successful FDRSNAP PIT Copy JES2 JOB LOG SYSTEM XXXX NODE XXXXXXXX 13 08 20 20 07751 THURSDAY 29 MAR 2007 13 08 20 JOBO7751 IRRO10I USERID XXXX IS ASSIGNED TO THIS JOB 13 08 20 JOBO7751 ICH700011 XXXX LAST ACCESS AT 13 06 20 ON THURSDAY MARCH 29 2007 13 08 20 JOBO7751 HASP373 XXXXPFDR STARTED INIT CLASS A SYS XXXX 13 08 20 20 07751 IEF4031 XXXXPFDR STARTED TIME 13 08 20 13 08 22 20 07751 51571001 SLUPCOPY VERSION 6 20 PROCESSING BEGINS 13 08 22 20 07751 SLS7028I HSC SUBSYSTEM NAME 5 13 08 22 20 07751 SLS7028I COPY FUNCTION IS IN EFFECT 13 08 22 20 07751 51570281 FDRSNAP METHOD IS IN EFFECT 13 08 22 20 07751 SLS7028I RESERVE RETRY WTOR OPTION IS ENABLED 13 08 22 20 07751 SLS7070I READ JFCB SUCCESSFUL FOR SLSCNTL DD 13 08 22 20 07751 SLS7010I SSCVT LOCATED FOR SUBSYSTEM 5 13 08 22 20 07751 51570111 ASCB FOR HSC JOB NAME HSCX HAS ASID 001D 13 08 22 20 07751 SLS7102I HSC QNAME HSCXLSQN 13 08 22 20 07751 51570251 PRIMARY CDS NAME XXXX SOS610 SL
131. XEC PGM SLUPCOPY REGION 4M PARM HSCO COPY DSS OPT AB STEPLIB DD DISP SHR DSN DMMBASE SLUPCOPY LINKLIB SLSCNTL DD DISP SHR DSN XXXXHSC SLS DBASEPRM SLSCNTL2 DD DISP SHR DSN XXXXHSC SLS DBASESHD SYSPRINT DD SYSOUT SYSMDUMP DD DSN XXXXXXX SLUPCOPY SYSMDUMP DISP CATLG f SPACE CYL 100 100 RLSE UNIT SYSALLDA SYSIN DD 6140 JOB ORIGIN FROM GROUP ANYLOCAL DSP IR DEVICE INTRDR 0000 13 06 00 IAT6853 THE CURRENT DATE IS WEDNESDAY 24 JAN 2007 IRRO10I USERID XXXXXXX IS ASSIGNED TO THIS JOB 13 06 01 IAT4401 LOCATE FOR STEP DFDSS DD STEPLIB DSN DMMBASE SLUPCOPY LINKLIB 13 06 01 IAT4402 STORCLAS BASE MGMTCLAS STANDARD 13 06 01 IAT4401 LOCATE FOR STEP DFDSS DD SLSCNTL DSN XXXXHSC SLS DBASEPRM 13 06 01 IAT4402 STORCLAS SCHSCDS MGMTCLAS MCRAPP 13 06 01 IAT4401 LOCATE FOR STEP DFDSS DD SLSCNTL2 DSN XXXXHSC SLS DBASESHD 13 06 01 IAT4402 STORCLAS SCHSCDS MGMTCLAS MCRAPP 13 06 01 IAT6312 THE FOLLOWING 000001 MESSAGES MAY BE LOGGED OUT OF SEQUENCE 13 06 01 ICH700011 XXXXXXX LAST ACCESS AT 12 48 58 ON WEDNESDAY JANUARY 24 2007 13 06 01 2000 JOB HSCFLASH JOB23890 SELECTED D22 GRP DEDICATE 13 06 01 ICH700011 XXXXXXX LAST ACCESS AT 13 06 01 ON WEDNESDAY JANUARY 24 2007 13 06 01 403 HSCFLASH STARTED TIME 13 06 01 13 06 01 SLS7100I SLUPCOPY VERSION X XX PROCESSING BEGINS 13 06 01 SLS7028I HSC SUBSYSTEM NAME HSCO 13 06 01 SLS7028I COPY FUNCTION IS IN EFFECT 13 06 01
132. Y LINKLIB SLSCNTL DD DISP SHR DSN XXXXHSC SLS DBASEPRM SLSCNTL2 DD DISP SHR DSN XXXXHSC SLS DBASESHD SYSPRINT DD SYSOUT SYSMDUMP DD DSN XXXXXXX SLUPCOPY SYSMDUMP DISP CATLG SPACE CYL 100 100 RLSE UNIT SYSALLDA SYSIN DD 1 HSCFLASH JOB XXXXXXX XXXXXXX XXXXXXX MSGCLASS T REGION 0M MSGLEVEL 1 1 MAIN CLASS D22 E22915 01 Revision 01 Appendix B 167 CECI Ck k k k k k k k k k k k K k ke k k k k K k K K KOK kk R K R KOR kk R K R KOR Kok R R OR KOR KOR OR RK OR KOR K www w w SLUPCOPY CDS FLASHCOPY RR k k k k k k k k k k k k k k k k k k k K k K K K K KOK K K R KOR KOR KOR R KOR KOR KOR R K OR KOR KOR OK KK 2 DFDSS EXEC PGM SLUPCOPY REGION 4M PARM HSCO COPY DSS OPT AB 3 STEPLIB DD DISP SHR DSN DMMBASE SLUPCOPY LINKLIB SLSCNTL DD DISP SHR DSN XXXXHSC SLS DBASEPRM 5 SLSCNTL2 DD DISP SHR DSN XXXXHSC SLS DBASESHD 6 SYSPRINT DD SYSOUT 7 SYSMDUMP DD DSN XXXXXXX SLUPCOPY SYSMDUMP DISP CATLG SPACE CYL 100 100 RLSE UNIT SYSALLDA 8 SYSIN DD ICH700011 XXXXXXX LAST ACCESS AT 13 06 01 ON WEDNESDAY JANUARY 24 2007 IEF236I ALLOC FOR HSCFLASH DFDSS IGD103I SMS ALLOCATED TO DDNAME STEPLIB IGD103I SMS ALLOCATED TO DDNAME SLSCNTL IGD103I SMS ALLOCATED TO DDNAME SLSCNTL2 IEF2371 JES3 ALLOCATED TO SYSPRINT IGD101I SMS ALLOCATED TO DDNAME SYSMDUMP DSN XXXXXXX SLUPCOPY SYSMDUMP STORC
133. ading of the entire MVC is necessary to insure that only the most current copy of a VTV is decompressed 148 Managing HSC and VTCS April 2011 Revision 01 E22915 01 General Usage Guidelines The output volume that contains the converted VTV s must be at least the size of your maximum VTV size 400 Mb 800 Mb 2 Gb or 4 Gb to ensure that it can contain an individual VTV The VTCS MVC and VTV reports provide information to specify which copy of a VTV you want RTV to recover Ensure that you have a current copy of these reports before you run the RTV utility In addition to help identify the VI Vs you want to convert you can use the LISTONLY parameter to produce a list of the VTVs on an MVC Because multiple copies of the same VTV can exist on the same or different MVCs study carefully your VTV and MVC reports and LISTONLY listings to ensure that you are using the correct MVC to convert the most current copy of a VTV The RTV utility does not update the system catalog or TMC with information about the converted volumes you must do this manually Security Considerations You must have read access both to the VIVs you want to convert and to the MVC that contains these VTVs or your system s security application cannot be running Otherwise the conversion will fail Ensure that you APF authorize RTV utility load library RTV makes no attempts to bypass any TMS protection All RTV tape mounts are subject to full TM
134. aging Scratch Volumes on page 59 WARN Establishes scratch warning threshold Managing Scratch Volumes on values page 59 HSC PARMLIB Control Statements CDSDEF Specifies data set names of CDS Expanding the CDS on page 28 copies Renaming a CDS on page 30 Relocating a CDS on page 31 HSC Utilities SLUADMIN unless indicated otherwise BACKUP Backs up the primary CDS Using the BACKup Utility to Back Up the CDS on page 24 FMTLOG Pre formats log files Managing CDS Logging on page 25 LOGUTIL Uses log files to help recover the Restoring the CDS from a Backup CDS Copy on page 34 OFFLOAD LOGFILE Offloads transactions from any current log files and activates new log files Managing CDS Logging on page 25 SET LOGFILE volumes between specified LSMs in an ACS Provides an option to balance by subpool Specifies log file data sets RESTORE Restores the CDS from a backup Restoring the CDS from a Backup copy Copy on page 34 Scratch Updates the HSC scratch list from the Managing Scratch Volumes on Conversion SLUCONDB TMS scratch list page 59 SCREDIST Balances the number of scratch Managing Scratch Volumes on page 59 Managing CDS Logging on page 25 SET VOLPARM Defines all types of volumes and pools Adding Scratch Volumes on page 60 Defining Nearline Volumes on page 60 Adding Volumes to An Existing LSM on page 60
135. and fix it You can also use the VTCS MVCMAINT utility to set LOST OFF for the following events LOST ON was set due to LSM failures or drive errors that have been resolved LOST ON was set because the MVC was outside the ACS and has been reentered MARKED FULL The MVC is full and is not a candidate for future migrations MOUNTED The MVC is mounted on an RTD NOT INITIALIZED The MVC has been defined via the CONFIG utility but has not ever been used READ ONLY The MVC has been marked read only because of one of the following conditions The MVC being the target of an export or consolidation process The read only state protects the MVC from further updates The MVC media is set to file protect Correct the error and use the MVCMAINT utility to set READONLY OFF The MVC does not having the appropriate SAF rules set to enable VTCS to update the MVC Correct the error for more information see Defining A Security System User ID for HSC SMC and VTCS in Installing ELS and use the MVCMAINT utility to set READONLY OFF BEING AUDITED The MVC is either currently being audited or has been the subject of a failed audit If the audit failed VTCS will not use the MVC for migration To clear this condition rerun the AUDIT utility against this MVC LOGICALLY EJECTED The MVC has either been the subject of an MVCDRain Eject or the MVC was ejected for update by a RACROUTE call The MVC will not be used again for migration or reca
136. aning After the clean operation is completed the float option determines whether the cartridge is returned to its home cell float off or assigned a new home cell in the current LSM float on Setting float on reduces pass thru operations and thus enhances performance MNTD FLOAT Ejecting Cleaning Cartridges The POOLPARM MAXCLEAN parameter specifies the maximum number of cleaning operations for a given set of cleaning cartridges For ELS to automatically eject cleaning cartridges that have exceeded their MAXCLEAN value enter MNTD EJCTAUTO ON If you are running ExLM you may prefer letting ExLM manage ejecting cleaning cartridges on a scheduled basis In this case set auto eject off This is very useful for a lights out datacenter Without ExLM auto ejection is the recommended technique otherwise you have to manually schedule cleaning with the CLEAN command and manually eject the cartridge when it s used up spent as described in Manually Ejecting Used Cleaning Cartridges on page 65 Auto ejection requires an available CAP If a CAP is not available a manual eject is required Newer drives identify spent cleaning cartridges and will notify ELS regardless of the MAXCLEAN usage count If auto eject is on the cartridge is ejected when the library detects the spent condition Otherwise ExLM can be used to schedule the ejection of spent cleaning cartridges After you eject a cleaning cartri
137. as readonly and broken so that they E22915 01 Revision 01 Chapter5 115 FOR LOSTMVC Recovery Procedure Note In this procedure the JCL examples do not show DD statements for the CDS copies which is valid if HSC is active and you want to use the active CDS on the system where you are running LOGUTIL Otherwise you must specify the DD statements for the CDS copies To recover VTVs using FOR LOSTMVC 1 First run the LOGUTIL FOR LOSTMVC command with only the volsers of the lost or damaged MVCs For example the following example shows The logging data set is LOGIN Note You can run LOGUTIL FOR LOSTMVC with a dummy LOGDD specified to allow recovery on systems where CDS Logging has not been activated The recovery is limited to the data in the CDS but may still be useful if all VTVs are either resident on an alternate MVC copy or exported via Cross Tape Replication The volser of the damaged MVC is DMV509 The recovery commands are logged in data set RECVCMD JOBLOGR job account programmer REGION 1024k S1 EXEC PGM SLUADMIN PARM MIXED STEPLIB DD DSN hlq SEALINK DISP SHR LOGIN DD DSN FEDB VSMLMULT LOGFILE OFFLOAD 2 DISP OLD DD DSN FEDB VSMLMULT LOGFILE OFFLOAD 1 DISP OLD DD DSN FEDB VSMLMULT LOGFILE OFFLOAD 0 DISP OLD RECVCMD DD DSN FEDB VSMLMULT RECVCMD DISP CATLG DELETE UNIT SYSDA SPACE CYL 1 1 RLSE DCB RECFM FB LRECL 80 BLKSIZE 27920
138. assumes that the first RTD is in error Message SLS6662A indicates that an RTD is in maintenance mode and this status is also reported on Display RTD output An RTD in maintenance mode is typically in error and requires assistance from your hardware operations or service personnel Note that an RTD in recovery mode is initializing when varied online for example and typically is not in error If a failed RTD cannot be quickly repaired or if the failed RTD is attached to a remote ACS you may want to remove the RTD from your configuration to prevent attempts to allocate that RTD Remove the RTD statement for the RTD and rerun CONFIG Caution In a dual ACS configuration two ACSs connected to a single VTSS ensure that you do not allow all RTDs in either ACS to be unavailable to the VTSS for an extended period If no RTDs are available in that ACS migrates to or recalls from that ACS cannot occur and the VTSS space can fill up In addition this condition can also cause stalled migrations to RTDs in the other ACS In a dual ACS configuration therefore if you must make all RTDs in an ACS unavailable for an extended period remove the RTDs from the configuration as described above E22915 01 Revision 01 Chapter7 143 Okay It s a Bad MVC but how bad Let s say you ran through the check list for RTD problems above and that s not the problem You also did all the things you can reasonably do to make more MVC space availab
139. ate the new linklist using a SET PROG xx command and wait for the IEE536I response 3 Issue a F LLA REFRESH command to refresh the linklist and wait for the CSV210I response 4 Issue a SETPROG LNKLST UPDATE ASID 01 command to refresh the Master Scheduler address space and wait for the CSV505I response as shown below CSV500I LNKLST SET LLSETXX HAS BEEN ACTIVATED CSV505I ASID 0001 IS NOW USING THE CURRENT LNKLST SET IEE5361 PROG VALUE XX NOW IN EFFECT F LLA REFRESH CSV210I LIBRARY LOOKASIDE REFRESHED SETPROG LNKLST UPDATE ASTD 01 CSV505I ASID 0001 IS NOW USING THE CURRENT LNKLST SET 4 Initialize SVAA 1 Start SVAA and wait for the 51829061 initialization complete message 2 Issue a C ANTMAIN command to restart the ANTMAIN address space The ANTMAIN address space only needs to be restarted once after the SnapShot and SVAA libraries have been dynamically added to the system linklist 3 An ANTM6001I SNAPSHOT WORKING SPACE DATASETS BEING REFRESHED message should be issued during the restart This may be followed by an ANTM6002W ERROR REFRESHING SNAPSHOT WORKING SPACE DATASETS RC nnnn REAS n message The ANTM6002W message can be ignored because Concurrent Copy should not be used to perform the PIT copy 5 Run the SLUPCOPY utility For more information see General JCL Requirements All PIT Methods on page 14 E22915 01 Revision 01 Chapter2 13 General JCL Requirements All PIT Methods PITCOPY PROC
140. breaks down into two separate cases 2 Populating a New LSM on page 60 Adding Volumes to An Existing LSM on page 60 In both cases you first need to create POOLPARM VOLPARM definitions for the new volumes as described in Defining Nearline Volumes on page 60 Defining Nearline Volumes To define Nearline volumes 1 Create a POOLPARM statement to define the volume scratch pool For example to define a scratch pool for use by hosts MVS1 and MVS2 POOLPARM NAME SYS19840P22 TYPE SCRATCH HOSTID MVS1 MVS2 LABEL SL 2 Create a VOLPARM statement to define the volumes For example to define a range of 9840C volumes VOLPARM VOLSER C2000 C2999 MEDIA STK1R RECTECH STK1RC 3 Enter a SET VOLPARM command to apply the volume definitions SET VOLPARM APPLY YES Populating a New LSM After you have done your POOLPARM VOLPARM definitions to populate a new LSM use one of the following methods Set one or more CAPs to automatic mode and repeatedly open and fill the CAP with new cartridges Ifthe LSM is a non Streamline library and is large enough for you to enter 1 Open the LSM access door Manually place cartridges into the storage cells in the LSM Close and lock the access door Be dp qo Run an HSC Audit on the LSM A full LSM audit can take considerable time but so can entering cartridges through the CAP so you have to judge which method is faster Adding Volumes to An Existing LSM After yo
141. cally dismounts specified VTVs in an offline VTSS This is best explained in Logically Dismounting VTVs in an Offline VTSS on page 108 Managing VTVs Replicated via Cross TapePlex Replication CTR on page 109 Note And don t forget running VTVMAINT also produces a VTV report of the volumes affected by the VTVMAINT job Changing VTV Management Class and Unlinking VTVs from MVCs You can use VTVMAINT to change a VIV s Management Class If the new Management Class specifies a different Storage Class the VTV s current location on MVCs is incorrect The following procedure tells how to use VTVMAINT to change a Management Class and Storage Class To change a VTV s Management Class and unlink it 1 Recall the VTV The VTV must be VTSS resident for the unlink to succeed in Step 2 2 Use VTVMAINT ULINKMVC to unlink the VTV from the MVC s where it is located 3 Use VTVMAINT MGMTelas to assign a new management class 4 Remigrate the to place it on the correct MVCs or see Changing VTV Storage Class with RECONcil on page 110 for procedures for moving VTVs to MVCs ad hoc E22915 01 Revision 01 Chapter5 107 Logically Dismounting VTVs in an Offline VTSS If a VTV is mounted when a VTSS goes offline and a copy of the VTV exists on an MVC VTCS will not recall the migrated VTV to an alternate VTSS because the VTV is in mounted status on the offline VTSS In this situation you can use the V
142. case of Native SnapShot verify that all necessary ECAM devices are online verify that the SIBSTK00 member is correct verify dynamically add the SnapShot and SVAA libraries to the system linklist and initialize a SVAA subsystem Make sure that the CDS name on the SLSCNTL DD matches the data set names on the INCLUDE parameter and the first RENUNC sub parameter on the DFSMSdss COPY command The SHARE parameter is required This avoids an ADR411W message and an RC 4 from the COPY which then causes a Point In Time copy invalid message SLS7035E and an RC 12 E22915 01 Revision 01 Chapter2 19 The FASTREPLICATION REQUIRED parameter is strongly recommended 2 FASTREPLICATION PREFERRED is the default for COPY command override the default to avoid performing a physical copy The FASTREPLICATION REQUIRED and CONCURRENT parameters are mutually exclusive 2 The CONCURRENT parameter is strongly discouraged since it may result in a physical copy Remember this is supposed to be a Point In Time copy TOLERATE ENQFAILURE parameter is optional If specified it makes no difference as long as the SHARE parameter is also specified 20 Managing HSC and April 2011 Revision 01 E22915 01 DFSMSdss FlashCopy JCL Example PITDSS PROC COPY EXEC PGM SLUPCOPY REGION 4M PARM SSSS COPY DSS OPT AB STEPLIB DD DSN HSC LINKLIB DISP SHR SLSCNTL DD DSN HSC PRIMARY CDS DISP SHR SLSVDI DD SYSOUT
143. cessary ECAM devices are online on the SVA subsystems containing the HSC CDSs Verify that the SIBSTK00 member in SYSx PARMLIB specifies the device addresses of all necessary online ECAM devices otherwise a SIB1814E message will be issued indicating that the specified device is not a supported 3390 3 DASD and SLUPCOPY will end with an RC 12 Verify that the SnapShot and SVAA libraries are in the system linklist and if not dynamically add them 16 Managing HSC and VTCS April 2011 Revision 01 E22915 01 Initialize a SVAA subsystem before running SLUPCOPY 2 If the SnapShot and SVAA libraries not in the system linklist the following message and an RC 12 is issued SLS7062E SIBBATCH LOAD FAILED R1 00000806 R15 00000004 SVAA subsystem must be initialized before a valid SnapShot PIT copy can be created If SVAA is not initialized the following messages and an RC 12 is issued 19555 A SVAA VERSION 3 1 SUBSYSTEM HAS NOT BEEN INITIALIZED SIB43008 THE SVAA SUBSYSTEM HAS NOT BEEN LOCATED Either a SYSPRINT or SYSTERM DD is required Ifonly a SYSPRINT DD is supplied the SIB0764E message for the SYSTERM DD statement can be ignored 2 Ifonly a SYSTERM DD is supplied the 5 0764 message for SYSPRINT DD statement can be ignored If both SYSPRINT and SYSTERM DD statements are supplied output is directed to the SYSTERM DD 2 neither DD is provided the PIT is not performed and
144. changed SLUCONDB and MANAGE PHYSICAL and MANAGE VIRTUAL SMC equivalent PULLLIST Unchanged REPORT CELLCNT Unchanged REPORT CONSOLIDATE Unchanged REPORT DATASET Unchanged E22915 01 Revision 01 153 TABLE 1 LCM Control Statements LCM Control Statement Status ASUNT S UUU Command REPORT EJECT Unchanged REPORT ENTER Unchanged REPORT EXPORT Unchanged REPORT LSM Enhanced REPORT MIGRATE Unchanged REPORT MULTIPLE New MVCRPT REPORT NONSCRCNT Unchanged REPORT OPERATOR Unchanged REPORT PHYSICAL New VOLRPT REPORT RECALL Unchanged REPORT SCRCNT Unchanged REPORT SUMMARY Unchanged REPORT VIRTUAL New VTVRPT REPORT VOLUME Enhanced SET METHOD Enhanced SUBPOOL Enhanced SUBPOOL and MANAGE PHYSICAL BALSCR Unchanged SCRATCH REDISTRIBUTION TMS CAI Enhanced TMS COMMON Enhanced TMS CTT Enhanced TMS CUSTOM Enhanced TMS OPEN Enhanced TMS RMM Enhanced TMS TLMS Enhanced UNMANAGED Enhanced 154 Managing HSC and VTCS April 2011 Revision 01 E22915 01 APPENDIX B Additional SLUPCOPY Information This appendix provides additional information about SLUPCOPY E22915 01 Revision 01 155 SLUPCOPY Processing During normal operation HSC periodically issues a RESERVE on the Primary CDS volume HSC also holds an allocation and a shared enqueue on all copies of the CDS while it is active even at BASE service level Any backup of
145. chive Policies different ARCHAge and ARCHPol values and use POLICY dd to view the Archive Policy and resource use for each scenario The RECONcil utility looks like ARCHive because RECONCil also moves VTVs from one Storage Class to another that is moves them from one MVC media to another and or moves them from one ACS to another Think of ARCHive as proactive and RECONCcil as reactive and you ll see the difference as described in Reconciling VTV Media and Location on page 131 So let s say the 365 days is up and the internal auditors haven t shown up Time to go to archive FIGURE 6 10 shows example JCL to run ARCHive as follows Archive VTVs in Management Classes COMPLY to 9940 media in the remote ACS Set MAXMVC to 60 CONMVC to 8 and ELAPSE to 60 for the ARCHive job ARCHIVE EXEC PGM SLUADMIN STEPLIB DD DSN hlq SEALINK DISP SHR SLSPRINTDD SYSOUT SLSIN DD ARCH MGMT COMPLY MAXMVC 60 CONMVC 8 ELAPSE 360 MOVEVTV FIGURE 6 10 Example JCL for the ARCHive utility Tip The MOVEVTV parameter also gives you a report so you can see how well or not you did If your tuning parameters didn t archive the everything you wanted to archive then adjust your job and rerun 130 Managing HSC and VTCS April 2011 Revision 01 E22915 01 Reconciling VTV Media and Location Using RECONCil to reconcile media and location basically means moving VTVs from one Storage Class to another Is
146. copy 51570721 RESERVE SUCCESSFUL FOR SLSCNTL DD SLS70731 CDS DHB READ SUCCESSFUL 5157021 JCL CDS NAME MATCHES DHB CDS NAME SLS71701 CDS DPV READ SUCCESSFUL SLS71061 ORIGINAL LAST BACKUP DATE AND TIME 2007032914 07 09 51 570811 ESTAE ROUTINE SDWA PRESENT 51 57180 ESTAE ROUTINE DPV RESTORE NOT REQUIRED DPV NEVER UPDATED SLS70821 ESTAE ROUTINE DEQ SUCCESSFUL 51 57083 ESTAE ROUTINE CLOSE SUCCESSFUL SLS71881 ESTAE ROUTINE PROCESSING ENDS IEA995 SYMPTOM DUMP OUTPUT 658 Managing HSC and VTCS April 2011 Revision 01 E22915 01 Message 7180 is issued indicating that the ESTAE recovery routine determined that the last backup date and time in the Primary CDS did not need to be restored to its original value as previously displayed by message 7106 because the Primary CDS was never updated Message 7182 7186 An error occurs after the last backup date and time is updated but before the PIT copy 51570721 RESERVE SUCCESSFUL FOR SLSCNTL DD SLS70731 CDS DHB READ SUCCESSFUL 5157021 JCL CDS NAME MATCHES DHB CDS NAME SLS71701 CDS DPV READ SUCCESSFUL SLS71061 ORIGINAL LAST BACKUP DATE AND TIME 2007032914 07 09 5157171 CDS DPV WRITE SUCCESSFUL 51 571071 UPDATED LAST BACKUP DATE AND TIME 2007032914 10 53 51 570811 ESTAE ROUTINE SDWA PRESENT SLS71821 ESTAE ROUTINE DPV RESTORE REQUIRED SLS7186I ESTAE ROUTINE DPV RESTORE SUCCESSFUL SLS70821 ESTAE ROUTINE DEQ SUCCESSFUL 51 57083 ESTAE ROUTINE CLOSE SUCCESSFUL SL
147. covery commands in the COMMANDS file in the following order 1 All EEXPORT ULINKMVC commands 2 All MVCMAINT READONLY ON commands 3 All AUDIT commands 4 If there were EEXPORT ULINKMVC or AUDIT commands then re run FOR LOSTMVC With the new run there should be no EEXPORT or AUDIT commands in the newly generated COMMANDS file If there are then return to Step 1 MVCMAINT READONLY ON ERROR ON commands All ULINKMVC commands OV WN All RECALL commands 8 The RECONcil utility MVCMAINT commands are generated for all specified lost or damaged MVCs that exist in the CDS and that have at least one qualifying VTV on them The MVCMAINT commands will set the readonly and error broken bits on for the lost or damaged MVCs to prevent them from being allocated for recalls or migrates A maximum of approximately 3000 MVCs is included on each MVCMAINT command E22915 01 Revision 01 Chapter5 117 4 Run the RECONcil utility to ensure the correct number of MVC copies are created for each VTV For example JOBLOGR job account programmer REGION 1024k S1 EXEC PGM SLUADMIN PARM MIXED STEPLIB DD DSN hlq SEALINK DISP SHR LOGIN DD DSN FEDB VSMLMULT LOGFILE OFFLOAD 2 DISP OLD DD DSN FEDB VSMLMULT LOGFILE OFFLOAD 1 DISP OLD DD DSN FEDB VSMLMULT LOGFILE OFFLOAD 0 DISP OLD RECVCMD DD DSN FEDB VSMLMULT RECVCMD DISP CATLG DELETE UNIT SYSDA SPACE CYL 1 1 RLSE
148. d VTCS for more information Caution StorageTek recommends backing up all CDS copies prior to issuing the CDS EXpand command Failures during the expand operation usually cause the CDS to become unusable It is important to back up the CDS before invoking the CDS EXpand command to make sure that the latest copy of the CDS is available in case of a failure during the expand operation The following are guidelines for CDS EXpand 2 HSC must be active and tape activity can be ongoing when using CDS EXpand Do not issue CDS Enable and or Disable commands simultaneously from multiple hosts Doing so can cause the HSC to issue error messages If this occurs refer to ELS Messages and Codes to determine if user action is required Update your CDSDEF control statement in the HSC PARMLIB as necessary to make it consistent with the results of any expand operation Restoring the CDS to a larger pre allocated data set can t be used to dynamically expand a CDS the additional space is not formatted and can t be used as is StorageTek recommends that all CDSs be allocated with the same amount of DASD space The usable space in the CDS is determined by the number of 4096 byte blocks that fit in the CDS with the smallest DASD space allocation To expand all CDSs 1 Disable each CDS one at a time with the CDS DISABLE command 2 Reallocate each CDS with a larger primary space quantity Do not specify a secondary space quantity all
149. d to a VTSS and then remigrated to a new error free MVC This logically removes the MVC from the MVC pool Note 2 Due to the error status of the MVC VTCS recalls VTVs from alternate MVCs if possible If VTVs must be recalled from the MVC in error no other copies available then VTVs before the data check area are recalled in ascending block ID order WTVs after the data check area are recalled in descending block ID order 3 Determine if any VTVs could not be recovered from the MVC Run an MVC Detail report for the MVC If any VTVs are still reported as being on the MVC then these VTVs are not recoverable you must use other methods to recover your data 4 Manage the defective MVC by doing one of the following 2 Replace the defective MVC with an initialized tape volume with the same internal and external labels a HSC EJECT the defective MVC b HSC ENTER the replacement MVC c Initialize the tape as required d HSC AUDIT the new MVC e Run an MVCDRAIN no EJECT to return the MVC to the MVC pool 2 Remove the MVC from the system a HSC EJECT the defective MVC b Edit the MVC pool definitions to remove the defective MVC from the pool c Enter a VT MVCDEF on all active hosts to activate the new MVC pool definitions E22915 01 Revision 01 Chapter7 147 Using the RTV Utility The RTV utility is another item you re probably only going to use after talking with StorageTek service because RTV
150. dge you will usually want to enter a new cartridge to replace the used one If you want to enter a cleaning cartridge whose volser is not yet defined to ELS see Configuring HSC and VTCS for information on defining cleaning cartridges 64 Managing HSC and VTCS April 2011 Revision 01 E22915 01 Manually Ejecting Used Cleaning Cartridges To replace used cleaning cartridges 1 Verify that the LSM where you want to eject the cartridges is online For example to see the status of LSM 00 00 DISPLAY LSM 00 00 If you get an 51 500541 message that says LSM 00 00 now online you re all set Otherwise you have to figure out what the problem is and at a minimum enter a MODIFY LSM aa cc ONLINE command to get it back online 2 Use EJECT to start the eject operation For example to eject a range of 9840 cleaning cartridges EJECT CLN300 CLN310 SEQ YES WAITCAP YES is the default and the volumes are placed in sequence in the CAP so when you get operator messages to empty the CAP 3 Remove the cleaning cartridges from the CAP 4 Check the CAP mode of the CAP where you want to enter the replacement cleaning cartridges For example to see the status of the PCAP on LSM 00 00 DISPLAY CAP 00 00 02 If the CAP mode is Automatic go to Step Otherwise continue with Step 5 5 If the CAP mode is Manual you have two choices depending on your site s practices Change the CAP mode to Automatic For example for the P
151. e and a VTV as the virtual counterpart of a Nearline volume and it s easy to see why it s important to make sure all your VTSSs VTDs and VTVs are operating normally To check Virtual Tape status 1 Enter a Display VTSS command You should see something like FIGURE 4 1 VTSSNAME DBU HI LOW VTV MX MN DEF AUTOMIG STATE MB AMT AMT COUNT MT MT ACS HBVTSS16 56 209 55 80 60 2440 6 3 02 ONLINE HBVTSS17 56 209 50 80 60 2180 6 3 02 ONLINE HBVTSS18 56 209 52 80 60 2288 6 3 01 ONLINE HBVTSS19 93 184 45 80 60 1900 6 3 01 ONLINE FIGURE 4 1 Example output from Display VTSS Good VTSS status FIGURE 4 1 shows the status of four operating correctly VTSSs First all VTSSs are online which is usually good The LAMTS are all 60 and the HAMTS are all 80 which are good ranges for optimizing VTSS usage and promoting effective automatic migration The DBUs are all well lower than the HAMT which means there s still space to grow on the VTSS before auto migration starts You might even consider routing more work to these VTSSs to optimize your investment in virtual tape Let s assume you have 8 RTDs connected to each VTSSs The MX MTs maximum migration tasks are set at 6 and the MN MTs minimum migration tasks are set at 3 which are good numbers The max of 6 leaves 2 RTDs for recalls reclaims and the minimum of 3 ensures that if a bunch of migrations suddenly star
152. e 90 Draining MVCs on page 100 Poor VTV Mount Performance on page 138 Poor Migration Performance on page 139 RTD MVC Failures on page 143 What the RTV Utility Can Recover on page 148 MIGRATE Demand migrates VTVs to MVCs Doing Demand VTV Migrations on page 91 MVCDRAIN Recalls all current and scratched Draining MVCs on page 100 VTVs from an MVC and optionally virtually ejects the MVC makes it unavailable for VSM use without physically ejecting it from the library MVCMAINT Sets MVC attributes Changing MVC Attributes with MVCMAINT on page 101 MVCPLRPT Manages your MVCPOOLS and ELS Command Control Statement Storage Classes and Utility Reference MVCRPT Reports the status of your VSM Looking at the Big Picture system s MVCs and is Primary Weekly on page 82 Wellness Meter 2 Draining MVCs on page 100 Restoring the CDS on page 33 Using the RTV Utility on page 148 RECALL Does demand VTV recalls Doing Demand VTV Recalls on page 91 6 Managing HSC and VTCS April 2011 Revision 01 E22915 01 TABLE 1 2 The VTCS Toolkit moves VTVs from one Storage Class to another This tool does the following and is used to do these tasks RECLAIM Does demand MVC space Doing Demand MVC Space reclamation Reclamations on page 90 RECONCIL Reconciles VTV media and location Changing VTV Storage Class with RECONcil on page 110 The
153. eboot switch on the active LC is pressed When the active LC is powered off E22915 01 Revision 01 Chapter3 47 Consequences of an LC Switch When a LC switch occurs a series of console messages track the changing status of the active and standby LCs Critical status changes appear as highlighted messages which remain on the screen until the condition is corrected or the message is superseded The following message is displayed when status changes and the standby LC is ready ACS AA RE LIBID C1 is configured Active is y Standby is ready The following message is displayed if there is a status change and a LC error occurs ACS AA RE LIBID C1 Is Not configured Active Is y Standby is not ready The following message is displayed if there is a status change and the standby LC is not ready ACS AA RE LIBID C1 Is configured Active Is y Standby is not ready In the messages above y is the configured LC identifier A or When a LC switch occurs the HSC interrogates each LC to determine the current status The status of each station is maintained as online offline standby pending online pending offline or pending force offline Use the Display Acs acsid command to determine the status of each station and LC Note Auto mode CAPs are locked during a LC switch until the LSM completes initialization Automatic LC Switch LC microcode detects reports and reacts to LC failures as necessary to keep
154. econcile in minutes on the ELAPSE parameter Note that there are several limiting factors that influence reconciliations for example MAXMVC and ELAPSE VTCS enforces the strictest limiting factor For example if you run RECONcil and specify ELAPSE equal to 5 hours and MAXMVC equal to 10 and VTCS reconciles 10 MVCs in one hour then VTCS terminates the reconciliations before the ELAPSE value expires By not specifying the MOVEVTV parameter you can get a report only that is a valuable what if picture of how many VTVs MVCs and total MBs you will process with a reconcile request StorageTek strongly recommends therefore that you first run RECONCcil without MOVEVTYV then adjust the job as needed before specifying MOVEVTV For more information see ELS Command Control Statement and Utility Reference 132 Managing HSC and VTCS April 2011 Revision 01 E22915 01 2 and HSC must be active to process a RECONCII request except when you specify the POLICY dd parameter POLICY dd which forces report only mode also provides an enhanced what if capability You can create one or more alternate MGMTclas statements with different reconciliation scenarios different MIGpol values and use POLICY dd to view the VTVs reconciled and resource use for each scenario HSC must be active to process a RECONcil request E22915 01 Revision 01 Chapter6 133 134 Named MVC Pools or Not Named MVC Pools a
155. ed Storage Class es Scans the MVCs currently in the Storage Classes Does the MVC ACS and media match the Storage Class definition If not list the MVCs VTVs in error MVC Specifies a list or range of RECONcil does the following Determines the actual ACS and media for the specified MVCs Does the actual MVC ACS media match the Storage Class definition for the MVC If not list the MVCs VTVs in error MGMTelas Specifies one or more Management Classes RECONcil does the following Looks up the ACS and media definition as specified on the MGMTclas MIGpol parameter Scans the VTVs currently in the specified Management Classes Is the VTV on an MVC with ACS media that matches the MGMTclas MIGpol specification If not list the VTVs on the MVCs in error list or range of VTVs RECONcil does the following Determines the Management Class es for the specified VTVs Looks up the ACS and media definition as specified on the MGMTclas MIGpol parameter Scans the VTVs currently in the specified Management Classes Is the VTV on an MVC with ACS media that matches the MGMTclas MIGpol specification If not list the VTVs on the MVCs in error Note And as you can imagine if you do not specify any of the selection parameters VTCS validates all VTVs and we ll talk more about that in Step 2 2 Accept the default when you first run RECONcil Which is to generate a report only which as you can imagine
156. ed tape resources available To support nonlibrary VSM configurations you must define manual RTDs in a nonexistent ACS To define manual RTDs 1 Generate LIBGEN macros to define a nonexistent ACS The SLIDRIVS macro defines the device address for the manual RTDs Note The LSM in the nonexistent ACS can be defined as an SL8500 or SL3000 to take advantage of the MODIFY CONFIG command 2 Run the SLICREAT utility to format a new CDS 3 Run SET SLIDRIVS utility to set the MODEL for the manual RTDs for example SET SLIDRIVS 400 401 402 403 MODEL T9840C Note Manual RTDs on the same panel must be the same drive type 4 Run the VTCS CONFIG utility to define the VSM system 5 Use the VTCS IMPORT utility to import MVCs into the new CDS to use with the manual RTDs These MVCs are treated as nonlibrary volumes E22915 01 Revision 01 Chapter3 53 Managing Library Volumes Managing library volumes has a wide range of tasks ranging from using a Volume Report where we ll start through managing cleaning cartridges Using a Volume Report The VOLRPT utility provides volume information that can help you manage the physical volumes in your library The VOLRPT utility function uses the Unified User Interface and therefore provides output formats of either text XML or Comma Separated Values CSV See ELS Command Control Statement and Utility Reference and ELS Programming Reference for more information about how
157. eject or mount an errant volume will cause HSC to look for the volume in its home cell its last known source location and its last known destination location If the volume is not in any of these locations you may need to run an audit of the ACS to locate the volume 54 Managing HSC and April 2011 Revision 01 E22915 01 Unmatched VOLPARM and External Label Status Sample VOLRPT control card VOLRPT INCLUDE NONMEDEQ This request produces a report of all volumes for which the media label on the cartridge does not match the VOLPARM media type The character preceding the Media indicates the type of mismatch detected The character means that the label did not match the VOLPARM media code The character means that there was no VOLPARM matching the volume Note that these volumes also have a scratch subpool of NON VOLPARM The character means that the volume had no physical media label Sample output of this command is shown in FIGURE 3 2 SLUADMIN 7 1 0 TIME 11 41 12 Volume Serial Media VOL111 STKIR VOL222 STKIR VOL333 STK1R VOL444 STK1R VOL555 GSTK1R 0SLSO155I Condition code for utility function is 0 StorageTek Enterprise Library Software Utility PAGE 00003 Volume Report Utility DATE 2010 06 29 Cell Loc Err Ext Cln Inserted Last Used Times MWL amp Rectech AA LL Pa Ro Co Scr Sel Lbl Use Subpool ID Date Time Date Time Selected STK1R 03 00 00 31 00 x R GENERAL 20050607 1
158. es to manage RTDs otherwise an RTD can be brought online to both MVS and VSM which can cause data loss If the RTD is defined to MVS however you can use Vary RTD to vary the RTD offline to VSM then use the MVS VARY command to vary the transport online to MVS Note however that varying RTDs offline to VSM can impact migration recall and reclaim processing especially during peak VSM workloads Similarly if a transport is defined to MVS and also defined to VSM as an RTD you can vary it offline to MVS then online to VSM Each VTSS must have a minimum of two library attached transports as RTDs for each media type used for MVCs Tip You may want to define additional RTDs as backups up to the limit of 8 RTDs per VTSS and vary them offline to VSM until needed If an online RTD malfunctions you can vary it offline and vary a backup RTD online until the malfunctioning RTD is repaired or replaced You can also vary backup RTDs online for peak load VTV migration or recall processing When a transport is online to VSM as an RTD the logrec type OBR and MDR records for the RTD always show a channel path ID of 00 which has no meaning to the host because the transport is not online to MVS 94 Managing HSC and VTCS April 2011 Revision 01 E22915 01 Working with MVCs As you already know it s somewhat difficult to limit a discussion to any one of your virtual entities MVCs contain VTVs so it s hard to talk about either in isolat
159. fferent SVAs SIBA4617I 11 45 42 SnapShot completed rc 8 This results in a Point In Time copy invalid message SLS7035E and an RC 12 18 Managing HSC and VTCS April 2011 Revision 01 E22915 01 DFSMSdss SnapShot JCL Example PITDSS PROC COPY EXEC PGM SLUPCOPY REGION A4M PARM SSSS COPY DSS OPT AB STEPLIB DD DSN HSC LINKLIB DISP SHR SLSCNTL DD DSN HSC PRIMARY CDS DISP SHR SLSVDI DD SYSOUT SYSPRINT DD SYSOUT SYSMDUMP DD DSN HSC SLUPCOPY SYSMDUMP DISP DELETE CATLG UNIT SYSALLDA SPACE CYL 100 RLSE VOL SER VVVVVV SYSIN DD DSN HSC LIB CNTL PITDSSI DISP SHR HSC LIB CNTL PITDSST COPY DATASET INCLUDE HSC PRIMARY CDS RENUNC HSC PRIMARY CDS HSC PITDSS CDS FASTREPLICATION REQUIRED CANCELERROR SHARE TOL ENQF TGTALLOC CYL OUTDYNAM TTTTTT CATALOG FIGURE 2 3 SLUPCOPY DFSMSdss SnapShot JCL Example The requirements for SLUPCOPY with DFSMSdss SnapShot are 2 ADRDSSU must be in the system linklist The HSC CDS must reside on SVA hardware with the SnapShot feature enabled to be eligible for a DFSMSdss SnapShot operation The source and target data sets must be on the same SVA otherwise a physical copy is attempted Both source and target volumes must be online Volume or data set copy is supported but a data set copy is recommended DFSMSdss must be at DFSMS 1 3 or later this corresponds roughly to OS 390 VIR3 As in the
160. g log files involves an analysis of the log data and construction of the required MVC audit statements to restore access to the latest versions of data This does not recover the CDS to its exact state before the failure For example a VTV can exist on multiple MVCs The audit recovers access to all copies of that VTV but the copies may not be on exactly the same MVCs as before a CDS loss The objective of CDS logging is to recover access to data which is not a bit by bit CDS recovery Periodically Offloading Log Files You need to periodically offload log files to keep them from filling up which stops logging Here are some Best Practices for doing so Setup a PROC to periodically offload the log files Experimenting for a while to see how long it takes for the log file to fill under normal or peak operations and then run log offload at that interval Also consider setting up your auto ops package to intercept the SLS1781W message which is displayed starting at 70 full for the Log File data sets 2 You should also schedule a log file offload to be run when you run your periodic CDS backup so that during recovery you can select the log offload file that corresponds to the backup file you use for recovery Ifthe CDS is lost all three copies are gone or unreliable for any reason do not attempt to offload the log file instead see Restoring the CDS on page 33 E22915 01 Revision 01 Chapter2 25 Expanding or Reallocating L
161. geTek Software Support as described in Customer Support on page 440 to ensure that restoring the CDS from a backup is actually required and to assist if necessary with the restore process Note The RESTORE process is identical whether you have used SLUPCOPY or SLUADMIN BACKUP to create the CDS backup Before doing a restore you should either do a new backup of the corrupt CDS or rename all the current CDS copies to preserve them for later analysis E22915 01 Revision 01 Chapter2 33 Restoring the CDS from a Backup Copy To restore the CDS from a backup copy 1 If HSC is still active on any host stop the active HSC systems If logging is enabled continue with Step 2 to resynchronize VSM data Otherwise go to Step 3 2 If the CDS c an be accessed run the normal log file offload job This offload is to capture the VSM activity since your last offload JOBOFFL job account programmer 51 EXEC PGM SLUADMIN PARM execution parameters STEPLIB DD DSN hlq SEALINK DISP SHR SLSOFFLD DD DSN offload dataset name 41 DISP NEW CATLG DELETE UNIT SYSDA SPACE SLSCNTL DD DSN primary dataset name DISP SHR SLSCNTL2 DD DSN secondary dataset name DISP SHR SLSSTBY DD DSN standby dataset name DISP SHR SLSPRINT DD SYSOUT A SLSIN DD OFFLOAD LOGFILE If the CDS cannot be accessed offload the log file using the LOGDSN parameter The normal CDS logging
162. h of its supported modes and why you should use QUIESCED over OFFline if at all possible TABLE 5 1 VTSS States If you specify the following Vary VTSS parameter The VTSS first goes to state And then goes to state state the offline process has started but has not completed on all hosts VTCS immediately shuts down the VTSS and interrupts and purges all active tasks and purges all queued tasks The VTSS server task terminates and no longer accepts new front end and back end work VTCS creates new VTVs and mounts dismounts existing VTVs only on alternate VTSSs if they are available ONline Online Pending In online pending Online In online state the VTSS is state the online process has started but online available and accepts both has not completed on all hosts front end and back end work If the VTSS was offline when it goes online VTCS issues a warning message recommending a VTSS audit QUIESCED Quiescing In quiescing state VTCS Quiesced In quiesced state the does not direct any DD allocation to the VTSS continues to accept and VTSS which still accepts pending process back end work for mounts to allow those long running jobs example migrates recalls and with unit aff chains to complete When audits That is you can use the all VTDs are no longer in use their recall and migrate commands and UCBs are not allocated on MVS the utilities to do these operations using the VTSS goe
163. hange your Storage Class definition or both If you specify an MVC media on a Storage Class STORCLAS NAME stor clas name MEDIA media type VTCS checks that the MVC Pool contains media of type media type if a Named MVC Pool is not specified DEFAULTPOOL is implied If not message VTCS issues message SLS6849W Ensure that the media type exists in the corresponding pool change your Storage Class definition or both If you specify an ACS and media type on a Storage Class STORCLAS NAME stor clas name ACS acs id MEDIA media type VTCS checks that there are RTDs in the specified ACS compatible with the specified media type If not message VTCS issues message SLS6851W Ensure that required RTD type exists in the specified ACS change your Storage Class definition or both If you specify media type without a specific ACS on a Storage Class STORCLAS NAME stor clas name MEDIA media type VTCS checks that there are RTDs in the configuration compatible with the specified media type If not message VTCS issues message SLS6851W Ensure that required RTD type s exist in the configuration change your Storage Class definition or both 142 Managing HSC and VTCS April 2011 Revision 01 E22915 01 RTD MVC Failures At first you may not know if you re looking at a media or drive failure That is if VTCS detects read write errors on an MVC VTCS swaps the MVC to another RTD If VTCS detects no further read write errors on the MVC VTCS
164. held SLUPCOPY provides two functions a COPY function that performs actual PIT copy a TEST function that only simulates a PIT copy SLUPCOPY processing proceeds generally as follows 1 OPEN RESERVE and READ the first 4K block of the HSC Primary CDS the READ insures the RESERVE takes effect immediately in SYNCHRES NO environments 2 READ the second 4K block of the HSC Primary CDS 3 For the COPY function only update the last backup date and time in the second block and WRITE the block back to the Primary CDS 4 LOAD and DELETE either SIBBATCH ADRDSSU or FDRSNAP to verify that the program is accessible via the system linklist 5 For the COPY function only invoke SIBBATCH ADRDSSU or FDRSNAP to perform the PIT copy 6 DEQ and CLOSE the HSC CDS 7 For the COPY function only if the PIT copy is not successful re WRITE the second 4K block back to the Primary CDS to restore the last backup date and time to its original value 156 Managing HSC and VTCS April 2011 Revision 01 E22915 01 How do I prevent a SnapShot target data set from being allocated when running the PITSNP sample JCL using the TEST function Either comment out or dummy the OUTSNAP DD in the sample JCL or use the PITSNP2 and PITSNPI2 members to dynamically allocate the target data set Since the TEST function does not invoke the PIT copy program SIBBATCH in this case the target data set is never allocated SLUPCOPY Return Codes SLUPCOPY ret
165. ight tool for the job Note that if you do not specify one of these parameters space reclamation selects MVCs from the Named MVC Pool if implemented or media type for multiple MVC media environments most in need of free space The parameters MAXMVC max MVCs processed by a single space reclamation task THRESH MVC s fragmented percentage that make it a reclaim candidate and CONMVC the maximum number of MVCs that VTCS concurrently processes for both drain and reclaim let you override the corresponding CONFIG RECLAIM global parameters for the demand reclamation This gives you the ability to tune your demand migrations to be more or less aggressive than your automatic migrations NOWAIT is a way of speeding up the process and CONMVC is another tuning method for influencing the number of MVCs processed at a time see ELS Command Control Statement and Utility Reference for details ELAPSE is a way to detect if no demand reclaims have happened within an interval you specify If there are no reclaims in this period the job stops Also note that VTCS enforces the strictest limiting factor For example if you run RECLAIM and specify ELAPSE equal to 5 hours and MAXMVC equal to 10 and VTCS reclaims 10 MVCS in one hour then VTCS terminates the reclaim before the ELAPSE value expires VTCS and HSC must be active to process a RECLAIM request 90 Managing HSC and VTCS April 2011 Revision 01 E22915 01 Doing Demand VTV Migration
166. in FIGURE 4 4 SUBPOOL NAMI VIROOO VIROO02 VIRTUAL VIRTUAL1 SCRATCH COUNT 14 364 13 582 19 132 9 905 FIGURE 4 4 Example output from Display SCRATCH In FIGURE 4 4 what you re seeing are VTV scratch counts for HSC subpools If you don t use HSC subpools for VTVs you ll see VTV scratch counts for all VTVs defined to your system There are no good or bad numbers for scratch counts as long as you have some scratch VTVs available The right number of available scratches depends on your shop s needs and workload Let s say that FIGURE 4 4 showed 50 or fewer scratches available for each subpool You might be a little concerned right If this happens you can do one or more of the following 2 Free VTV volsers by scratching VTVs with data that is not current This is the move to make if you have enough total VTVs in your system but there aren t enough scratch volumes available 76 Managing HSC and VTCS April 2011 Revision 01 E22915 01 Actually you don t do the scratching it s your TMS that s supposed to do the work and the initial configuration should have defined your VTV volsers to your TMS If that didn t happen go back and do it More likely you may have added VTV ranges via the VTCS CONFIG statement and forgot to define the new ranges to your TMS so go back and fix that problem This is all described in Installing ELS Note however that marking VTVs as scratch
167. ion because you inevitably end up talking about the other and if you re discussing VTVs you re also talking about VTSSs and VTDs Having said that the following sections are some basic procedures for doing fairly typical as needed tasks with MVCs that are done for a number of reasons For example you might add MVCs because you re running out of space per the scenario described previously or because you re being proactive and don t want to get into trouble Adding MVCs If you haven t heard ELS 7 0 just made adding volumes a whole lot easier You now use the HSC VOLPARM and POOLPARM statements to define all volumes and their pools native Nearline volumes cleaning cartridges MVCs and VTVs and the HSC SET VOLPARM utility to load them For more information seem Configuring HSC and VTCS and ELS Command Control Statement and Utility Reference To add MVCS 1 Create a VOLPARM statement to define the MVCs For example to define a range of T10000 Full volumes to be encrypted VOLPARM VOLSER T10K2000 T10K2999 MEDIA T10000T1 RECTECH T1AE 2 Create a POOLPARM statement to define the MVC pool For example to define the T10000 MVC Pool with reclaim parameters POOLPARM SYS1MVCT1 MVCFREE 40 MAXMVC 4 THRESH 60 START 70 3 Create update your MGMTCLAS STORCLAS statements as needed For example if you added a new MVC media type follow the recommendations in Configuring HSC and VTCS
168. is designed to read VTV data directly from an MVC without any assistance from VTCS for example in the case that you really have lost the CDS RTV is a standalone utility and the way it works is to read a VTV from an MVC decompress the VTV then write the data to a single output tape real tape volume so the data can be read by user applications Because RTV utility is a stand alone utility you can run RTV when VSM is down but the MVS system is up What the RTV Utility Can Recover The RTV utility can recover All or specified VTVs from a specified MVC If you do not know the location of the most current version of a VTV on the MVC specify only the VTV volser and RTV will convert the most current version of the VTV it finds on this MVC VTV at a specified block ID on a specified MVC The LISTONLY parameter listing supplies a Block ID value that you can use as input to the RTV utility to convert a VTV to a Nearline volume Specifying the volser and Block ID speeds positioning time A VTV specified by logical data set number on a specified MVC Specifying the volser and logical data set number will have a much longer positioning time compared to specifying volser and Block ID Using volser and Block ID is the preferred method to access a single VTV Note If more than one VTV is specified or if no BLOCKid or FILEnum parameter is specified the entire MVC will be read and the MVC contents displayed as part of the output Re
169. is required E22915 01 Revision 01 Chapter2 21 This avoids an ADR411W message and an RC 4 from the COPY which then causes a Point In Time copy invalid message SLS7035E and an RC 12 The FASTREPLICATION REQUIRED parameter is strongly recommended FASTREPLICATION PREFERRED is the default for a COPY command override the default to avoid performing a physical copy The FASTREPLICATION REQUIRED and CONCURRENT parameters are mutually exclusive The CONCURRENT parameter is strongly discouraged since it may result in a physical copy Remember this is supposed to be a Point In Time copy The TOLERATE ENQFAILURE parameter is optional If specified it makes no difference as long as the SHARE parameter is also specified Keep it simple Use a background copy the default so that the FlashCopy relationship terminates automatically when the copy is complete Don t specify the FCNOCOPY or FCWITHDRAW parameters on the DFSMSdss COPY command Don t use an Incremental FlashCopy relationship since this is only supported at the volume level Don t use Persistent FlashCopy Don t use multiple FlashCopy relationships Don t use a FlashCopy Consistency Group 22 Managing HSC and VTCS April 2011 Revision 01 E22915 01 FDRSNAP JCL Example PITFDR PROC COPY EXEC PGM SLUPCOPY REGION 4M PARM SSSS COPY FDR OPT AB STEPLIB DD DSN HSC LINKLIB DISP SHR SLSCNTL DD DSN HSC PRIMARY CDS DI
170. issue the following command to determine 1f SVAA is initialized D GRS RES SYSZSVAA Ifa NO REQUESTORS FOR RESOURCE SYSZSVAA response is received the problem is that SVAA is not initialized Perform the procedure in Initialize SVAA on page 13 then rerun the PIT copy Ifthe response indicates that SVAA is active do the following 1 Issue a C ANTMAIN command to restart the ANTMAIN address space The ANTMAIN address space only needs to be restarted once after the SnapShot and SVAA libraries have been dynamically added to the system linklist 2 An ANTM6001I SNAPSHOT WORKING SPACE DATASETS BEING REFRESHED message should be issued during the restart This may be followed by an ANTM6002W ERROR REFRESHING SNAPSHOT WORKING SPACE DATASETS RC nnnn REAS n message The ANTM6002W message can be ignored because Concurrent Copy is strongly discouraged 3 Rerun the PIT copy If both modules are not found in the system linklist perform the procedure in Dynamically add the SnapShot and SVAA Libraries to the System Linklist on page 13 next perform Initialize SVAA on page 13 then rerun the PIT copy 158 Managing HSC and VTCS April 2011 Revision 01 E22915 01 Message ADR735W with Reason Code 14 and SDM diagnostic information 17A70000 00000000 SnapShot and SVAA libraries are not in the system linklist Perform the procedure in Dynamically add the SnapShot and SVAA Libraries to the System Linklist o
171. ixB 163 Example 1 Successful SnapShot PIT Copy JES2 LOG SYSTEM XXXX NODE 13 01 25 40 07746 THURSDAY 29 MAR 2007 13 01 25 JOB07746 IRRO10I USERID XXXX IS ASSIGNED TO THIS JOB 13 01 25 JOB07746 ICH700011 XXXX LAST ACCESS AT 12 05 57 ON THURSDAY MARCH 29 2007 13 01 25 JOB07746 HASP373 XXXXPSNP STARTED INIT AA CLASS A SYS XXXX 13 01 26 JOB07746 IEF4031 XXXXPSNP STARTED TIME 13 01 26 13 01 31 JOBO7746 51571001 SLUPCOPY VERSION 6 20 PROCESSING BEGINS 13 01 31 JOBO7746 51570281 HSC SUBSYSTEM NAME HSCX 13 01 31 JOBO7746 SLS70281 COPY FUNCTION IS IN EFFECT 13 01 31 JOBO7746 51570281 SNAPSHOT METHOD IS IN EFFECT 13 01 31 JOBO7746 SLS70281 RESERVE RETRY WTOR OPTION IS ENABLED 13 01 31 JOBO7746 SLS70701 READ JFCB SUCCESSFUL FOR SLSCNTL DD 13 01 31 JOBO7746 SLS70101 SSCVT LOCATED FOR SUBSYSTEM HSCX 13 01 31 JOBO7746 SLS70111 ASCB FOR HSC JOB NAME HSCX HAS ASID 001D 13 01 31 JOBO7746 SLS71021 HSC QNAME HSCXLSQN 13 01 31 JOBO7746 51570251 PRIMARY CDS XXXX SOS610 SLSCNTL 13 01 31 JOBO7746 51570151 JCL CDS NAME MATCHES PRIMARY CDS NAME 13 01 31 JOBO7746 SLS70711 OPEN SUCCESSFUL FOR SLSCNTL DD 13 01 31 JOBO7746 SLS71041 UCB LOCATED SUCCESSFULLY 13 01 31 70807746 51570721 RESERVE SUCCESSFUL FOR SLSCNTL DD 13 01 31 JOBO7746 SLS70731 CDS DHB READ SUCCESSFUL 13 01 31 JOBO7746 SLS70211 CDS NAME MATCHES DHB CDS NAME 13 01 31 JOBO7746 51571701 CDS DPV READ SUCCESSFUL 13 01 31 JOBO
172. k connections paths are offline to the LC or if all network connection paths are inoperative In a Redundant Electronics environment if all network connection paths to the active LC are inoperative use the HSC SWitch command to move the workload to the standby LC E22915 01 Revision 01 Chapter3 45 SL8500 LC Operation The Library Controller LC responds to mount and dismount requests from the host through the HSC and passes each request to the appropriate LSM to perform the physical action requested The following procedures are described in this section 2 Displaying ACS Status on page 46 Operating an LC Redundant LC Configuration on page 47 Note When you reboot an LC error messages appearing before the message ACS AA LSM LL ready can be ignored Do not ignore error messages that are displayed after the message Refer to the appropriate StorageTek hardware operator s guide for a description of the library control panel and information on how to power on off and boot a Library Controller in both stand alone LC and redundant LC configurations Displaying ACS Status To determine the status of the LC issue the following command Display Acs acsid The command response lists the following Current status of the ACS Current status of the Redundant LC if configured including HSC LC compatibility levels 2 Active LCs 2 Standby LCs Online offline or standby status of each LC 46 Managi
173. ld RTDs offline to VTCS 3 If the new RTD devices use new MVS device addresses do the following Define the new addresses to MVS Run DECOM to output your CONFIG statements Edit the CONFIG statements to change the RTD addresses to the new values Run CONFIG RESET Caution Do not vary the new transports online to MVS Otherwise they can be allocated as Nearline transports Install the new RTDs Vary the LSM s where transports were replaced to offline status Vary the LSM s where transports were replaced to online status Vary the new RTDs online to VTCS If necessary add For more information see Adding MVCs on page 95 E22915 01 Revision 01 Chapter5 93 Sharing Transports Between VSM and MVS VSM does not support dynamic sharing of transports between VSM and MVS That is a transport cannot simultaneously be online to both MVS and to VSM as an RTD But what you can do is have an RTD that is online to VTCS vary it offline to VSM then MVS vary it online to MVS to use as a pure Nearline drive Or vice versa There are of course some considerations see below Caution Note the following You must have physical connectivity from VSM and MVS to support sharing transports between the two For example you can use an ESCON director to allow both MVS and VSM to physically connect to the same RTD Do not therefore use MIM JES3 or tape autoswitch or similar faciliti
174. le and compared the volsers on the MVC Summary Report to an HSC Volume Report no problem the MVCs actually were in the in the ACS otherwise you would have either reentered or replaced any MVCs not listed on the HSC Volume Report So it really does look like a media problem You ll see what kind of media problem via the MVC and VTV reports described in Checking Nearline Tape Status Daily on page 78 and in that section we ve talked about some of the fixes for the most straightforward MVC anomalies The following is an exhaustive list of the MVC statuses you don t want to see on your MVC and VTV reports and what to do about them BROKEN This is a generic error that indicates the MVC drive or combination of the two has a problem VTCS attempts to de preference MVCs with this state In general to clear this state If the MVC caused the problem use a DRAIN EJECT command to remove the MVC from service If the RTD caused the problem use the MVCMAINT utility to reset the MVC state Note also that one or more of the following messages is issued for BROKEN status SLS6686 SLS6687 SLS6688 SLS6690 For detailed recovery procedures for these messages see VTCS Messages and Codes DATA CHECK A data check condition has been reported against this MVC VTCS attempts to de preference MVCs with this state To clear this state If all VTVs on the MVC are duplexed use MVCDRain on the MVC without the Eject option This recove
175. ll To clear this condition use MVCDRain against the MVC without the Eject option RETIRED The MVC is retired VTCS will recall from but not migrate to the MVC Replace the MVC as soon as possible WARRANTY HAS EXPIRED The MVC s warranty has expired VTCS continues to use the MVC You should start making plans to replace the MVC when it reaches Retired state E22915 01 Revision 01 Chapter7 145 INVALID MIR VTCS has received status from an RTD to indicate the MIR media information record for a 9x40 media is invalid An invalid MIR does not prevent access to data but may cause significant performance problems while accessing records on the tape The MVC is not capable of high speed searches on areas of the tape that do not have a valid MIR entry VTCS attempts to de preference MVCs with this condition For recalls if the VTV resides on multiple MVCs VTCS selects MVCs with valid MIRs ahead of MVCs with invalid MIRs VTCS avoids using MVCs with invalid MIRs for migration unless the migration is at the beginning of the tape Migrating from the beginning of tape will correct the MIR VTCS detects the invalid MIR condition at either mount time or dismount time If detected at mount time and the operation can be completed with another MVC VTCS dismounts the first MVC and selects the alternate MVC Note that VTCS has only a limited ability to switch to an alternate MVC That is it is mainly used for migrate and virtual mount For
176. lumes with non current data or enter more scratch volumes into the ACS If you re seeing excessive passthru activity or long mount times for nonscratch volumes you can use LCM to redistribute nonscratch volumes 58 Managing HSC and April 2011 Revision 01 E22915 01 Managing Scratch Volumes Managing scratch volumes basically means having enough scratch volumes but not too many and having them in the right place preferably in an LSM with sufficient drives types compatible with the volume media TABLE 3 1 describes the scratch volume management tasks and associated tools TABLE3 1 Scratch Volume Management Tasks and Tools Task Tool Notes Maintain Sufficient Warn command establishes In general Quantities of Scratch Cartridges scratch warning threshold values Display THReshld command displays scratch count and scratch threshold information by subpool name ACS id LSM id media and recording technique Use the Warn command to set scratch warning thresholds and the Display THReshld command to monitor scratch volume levels versus the threshold If you re running low on scratch volumes run scratch synchronization redistribute scratch volumes and then add more scratch volumes in that order For more information see Adding Scratch Volumes on page 60 Synchronizing CDS Scratch Status with TMS Status HSC SLUCONDB scratch conversion utility with SMC Tape Management Extract Utilit
177. mally 2 Ensure that you have sufficient VTSS space 2 Check to see if your system is running out of available MVCs or usable MVC space 2 Raising the low AMT tends to keep more VTVs resident in VTSS space which may help prevent virtual mounts from failing Ifa VTV mount fails even if VTDs are online use the MVS VARY command to vary VTDs online use the MVS UNLOAD command to clear the VTDs then use the HSC MOUNT and DISMOUNT commands to retry the operation Poor Migration Performance If VTV migration occurs very slowly check the following Start with Display MIGrate which will show you in broad strokes how well or poorly your various migration tasks are doing You may be able to rearrange the furniture for example raise the MAXMIG MINMIG values to get things moving Ensure that your supply of RTDs and is in good shape as described in Checking Nearline Tape Status Daily on page 78 If you want to get down to bits and bytes also use Display Queue DETail to check the status of queued processes If many processes are waiting for RTDs and you are sharing RTDs with MVS you may want to vary transports offline to MVS and online to VSM Note In the JES3 environment VTV mounts may fail if you have not created and installed the correct User Exit modifications E22915 01 Revision 01 Chapter7 139 Migration Failures There s only one thing worse than poor migration performance and that s no migration at all
178. n media that matches its importance to the business enterprise and its pattern of reuse Active important data goes on fast access media and has multiple copies while inactive less important data is archived to high capacity cheaper media Automating this process is the most cost effective way to manage data storage Archiving implements ILM by letting you archive inactive data Using VTCS archiving you can move VTVs to different media for example from fast access 9840 media to high capacity 9940 media and a different location for example from a local ACS to a remote ACS for ejection vaulting For the details see Archiving Data on page 129 Reconciling VTV Media and Location on page 131 Think of archiving as a proactive move You put the data on the right media at the beginning of the ILM cycle then move it to other media as the data ages What happens if the data ends up on the wrong media Answer use the RECONcil utility to move it from one Storage Class to another Controlling Migration ELS allows very fine control over migration including deleting scratch VTVs from the VTSS buffer specifying the immediate migrate delay interval and specifying the maximum VTV residency interval For more information see Configuring HSC and VTCS and ELS Disaster Recovery and Offsite Data Management Guide 124 Managing HSC and VTCS April 2011 Revision 01 E22915 01 Grouping Multiple Workloads on Shared MVCs
179. n page 13 next perform Initialize SVAA on page 13 then rerun the PIT copy Region Problem Symptoms and Remedies Increase the REGION size 4 megabytes should be sufficient on the SLUPCOPY step if the following messages are received the module name will reflect the choice of PIT copy method IEW4000I FETCH FOR MODULE ADRDSSU FROM DDNAME LNKLST FAILED BECAUSE INSUFFICIENT STORAGE WAS AVAILABLE CSV031I LIBRARY ACCESS FAILED FOR MODULE ADRDSSU RETURN CODE 24 REASON CODE 26080021 DDNAME LNKLST SLS7060E ADRDSSU LOAD FAILED R1 00000106 R15 0000000C E22915 01 Revision 01 AppendixB 159 Advanced Diagnostic Techniques 2 If SLUPCOPY issues an error message but no abend consider a rerun of SLUPCOPY with the AB option specified to Generate a User 555 abend and a machine readable dump an undummied SYSMDUMP DD must be present for an eligible error conditions see AB Option on page 161 Generate a Vital Diagnostic Information report To prevent the possibility of a hanging RESERVE a RESERVE without a corresponding DEQ SLUPCOPY attempts to DEQ and CLOSE the Primary CDS when an eligible non abend error condition occurs see AB Option on page 161 For abends other than the User 555 the ESTAE recovery routine in SLUPCOPY always attempts to DEQ and CLOSE the Primary CDS before control is returned to the operating system If these attempts fail the operating system itself should free these resources
180. nerated if the AB option is specified and one of the eligible error conditions occur 2 DCB characteristics are LRECL 132 BLKSIZE 27984 RECFM FB Either a SYSPRINT or SYSTERM DD is required 2 DFSMSdss and FDRSNAP require a SYSPRINT DD SIBBATCH requires a SYSPRINT or SYSTERM DD both can be specified if desired 2 SYSMDUMP DD is strongly recommended This machine readable dump will speed up problem resolution 2 primary space allocation of 100 cylinders with the RLSE parameter is recommended Specify DISP DELETE CATLG to delete the data set when there is no problem and to keep and catalog the data set when there is a problem 2 If SYSMDUMP DD DUMM Y is present in the JCL this suppresses all dumps including SYSUDUMP so comment out the SYSMDUMP DD instead of dummying it out to allow a SYSUDUMP to be created SYSIN DD is required for command input Although SLUPCOPY requires that the JCL include a DD statement for the Primary CDS a PIT copy of all Primary Secondary and Standby CDSs can be created at the same time by specifying multiple commands in the SYSIN DD input for SnapShot and FDRSNAP or by specifying multiple data set names on the INCLUDE and RENUNC parameters of the DFSMSdss COPY command SIBBATCH must be in the system linklist E22915 01 Revision 01 Chapter2 15 SVAA SnapShot JCL Example PITSNP PROC COPY EXEC PGM SLUPCOPY REGION 4M PARM SSSS COPY SNP OPT AB
181. nership of the CAP until the cartridges are removed This is normal behavior of the SL8500 library Procedure to resolve Use the procedure in the SL8500 Operator s Guide to manually remove the cartridges from the CAP with the SLC Issuea Display aa ll cc command for the specific cap affected Ifthe CAP is offline issue the Modify CAP online command Re issue the EJECT vol list or vol range aa ll cc command or restart the eject utility to eject the balance of the cartridges Ifthe CAP was automatic prior to the eject function issue the CAPP x aa ll cc manual and then re issue is as CAPP x aa ll cc auto to reset it to automode A switch occurs when CAPs are set to automatic mode When a switch occurs and CAPs are set to automatic mode when the switch completes message SLS0699 may be presented with a return reason code of 07 05 error from the library during a reserve of the CAP This is because the CAPs have not initialized completely after the switch has completed This is normal behavior of the SL8500 library Procedure to resolve Wait until the message 51 506681 for the last LSM the library switched is issued Issuea CAPPref prefvalue aa ll cc MANual for each automatic CAP Issuea CAPPref prefvalue aa ll cc AUTO for each CAP to become automatic E22915 01 Revision 01 Chapter3 51 Managing CAPs DISPLAY CAP shows you CAP settings and status MODIFY CAP changes the CAP state DISPLAY CAP in additi
182. nformation on Named MVC Pools STORCLAS to drain the MVCs a Storage Class See ELS Command Control Statement and Utility Reference for more information on Storage Classes You can use the MVCDRain to override the CONFIG RECLAIM CONMVC setting You can run the MVCDRain from each host which starts drain tasks on that host equal to the CONMVC value These drain tasks can run concurrently with drain tasks initiated by other hosts 100 Managing HSC and VTCS April 2011 Revision 01 E22915 01 Changing MVC Attributes with MVCMAINT MVCMAINT is a similarly handy tool in VSM Land and we ll describe its abilities by looking at its parameters 2 First MVC volser range list individual volser or MANIFEST are your two MVC selection criteria MVC volser makes sense but why manifest Well you create a manifest file list of MVCS and the VTVs they contain when you run EXPORT which is something you might want to do when you re moving MVCs from one system to another When you import the MVCS into the new system it d probably be a good idea if they started their new lives in read only mode so they don t get overwritten until you can define them properly READONLY ON or OFF See the previous bullet Also remember the discussion about adding MVCs to the pool You might want to enter them into the ACS in scratch status but some shops bring everything in as non scratch and then sort things out When you need to make writeable the new
183. ng HSC and VTCS April 2011 Revision 01 E22915 01 Operating an LC Redundant LC Configuration Redundant LC Operational Overview Redundant Electronics configurations provide a backup LC which can take over if the active LC fails Refer to Dual Library Controller Configuration on page 43 for a description of the dual LC option Both LCs are capable of being the active but only one can be the active at any given moment Each LC regularly checks the status of the other LC over the LAN HSC directs all I O to the active LC When an LC is powered on in a dual LC configuration it places itself in a standby status and checks for an active LC If an active LC exists the second L C remains ready as the standby If an active LC does not exist the first LC to be fully initialized assumes the active role If both LCs power on successfully the following HSC message is displayed ACS AA RE LIBID C1 is configured Active is y Standby is ready where y is the configured LC identifier A or B LC Switch Overview The active LC functionality can be switched in the following ways 2 An automatic switch from self detected failure or power supply problem in the active LC An operator initiated switch using the SWitch command after all online stations become incapable of communication An operator initiated switch using the SWitch command while online stations remain capable of communication with the active LC 2 When the r
184. ng set to read only or by the security package not allowing VTCS to write to the volume Reset the thumb wheel or change the rules in the security package to allow the MVC to be written to Abad block ID has been detected and you have to VTCS audit the MVC to try to correct the condition After you correct the error condition as described use MVCMAINT to reset the MVC status to ERROR OFF EJECT ON or OFF specifies the logical eject status of the MVC How does this status get set and why might you want to change it If you explicitly drain an MVC using MVCDRAIN it s probably because you think the media is bad and so you depreference it by setting on the logical eject status You then really eject the MVC run some tests find out it s just fine and reenter it At that point use MVCMAINT to set EJECT OFF Next you have a group of MVC attributes specific to T9840 T9940 media all with ON OFF switches E22915 01 Revision 01 Chapter5 101 2 WARRANTY VTCS also detects media warranty expiration and sets the WARRANTY status to ON Alternatively you can use SMF LOGREC data or your MVC and VTV reports to detect MVCs approaching end of life and use the MVCMAINT to manually set WARRANTY ON Knowing that the warranty has expired lets you plan for media replacement before media end of life occurs see next bullet What if you know an MVC was erroneously marked as warranty expired Answer Just use MVCMAINT to reset the wa
185. nostic commands Display 72 restoring host to host communications 70 how to clear CAP status of RECOVERY 68 L labels entering cartridges with missing or unreadable labels 67 Library Storage Module LSM entering cartridges with missing or unreadable labels 67 entering duplicate VOLSERs 67 M migration demand 90 missing or unreadable labels 67 move CDS with rename 30 MVC pools VT Display command 80 81 MVCs space reclamation demand 90 ORH See Overdue Response Handler Overdue Response Handler ORH operator response required for mount dismount move and swap requests 71 overview 71 R recovery clearing RECOVERY status on Display Cap command 68 freeing an allocated CAP 69 restoring host to host communications 70 RECOVERY status on a CAP clearing 68 recovery utility 148 relocating a CDS 30 191 renaming control data sets 30 reports BACKup utility 11 24 resolving common problems 138 RESTore utility reasons for running 34 restoring host to host communications services 70 RTDs managing 94 sharing 94 varying online and offline 94 RTV utility 148 S scratch volumes insufficient in ACS 5 scratch subpools VT Display command 76 SET command SET SLIDRIVS procedure 53 114 sharing RTDs 94 transports 94 space reclamation demand 90 swapping a CDS 32 T transports sharing 94 varying online and offline 94 U utilities BACKup 11 24 V VSM managing demand migrations recalls and
186. nt to do it by VTV volser or all VTVs E22915 01 Revision 01 Chapter6 129 By not specifying the MOVEVTV parameter you can get a report only that is a valuable what if picture of how many VTVs MVCs and total MBs you will process with an archive request StorageTek strongly recommends therefore that you first run ARCHIve without MOVEVTV then adjust the job as needed before specifying MOVEVTV For more information see ELS Command Control Statement and Utility Reference Because demand archive can be resource intensive you typically run ARCHIve during non peak processing periods You can also use the ARCHIve utility to override the CONFIG RECLAIM THRESHLD MAXMVC and CONMVC settings to optimize archive performance You can also specify the maximum time for the archive in minutes on the ELAPSE parameter Note that there are several limiting factors that influence archives for example MAXMVC and ELAPSE VTCS enforces the strictest limiting factor For example if you run ARCHIve and specify ELAPSE equal to 5 hours and MAXMVC equal to 10 and VTCS archives 10 in one hour then terminates the archive before the ELAPSE value expires VTCS and HSC must be active to process a ARCHIve request except when you specify the POLICY dd parameter POLICY dd which forces report only mode also provides an enhanced what if capability You can create one or more alternate MGMTclas statements with different Ar
187. ntal regulations As such the use duplication disclosure modification and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract and to the extent applicable by the terms of the Government contract the additional rights set forth in FAR 52 227 19 Commercial Computer Software License December 2007 Oracle USA Inc 500 Oracle Parkway Redwood City CA 94065 This software or hardware is developed for general use in a variety of information management applications It is not developed or intended for use in any inherently dangerous applications including applications which may create a risk of personal injury If you use this software or hardware in dangerous applications then you shall be responsible to take all appropriate fail safe backup redundancy and other measures to ensure the safe use Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications Oracle is a registered trademark of Oracle Corporation and or its affiliates Oracle and Java are registered trademarks of Oracle and or its affiliates Other names may be trademarks of their respective owners AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license
188. ntrol statements in the SYSIN DD input that create a tape copy this increases the time the HSC CDS RESERVE is held If a tape copy is needed pass the PIT disk copy to a second job step in the SLUPCOPY procedure JCL 2 SLUPCOPY supports the following PIT copy methods 2 StorageTek SVAA SnapShot SIBBATCH 2 DFSMSdss SnapShot DFSMSdss FlashCopy ADRDSSU 2 FDR invoked SnapShot FDRSNAP 12 Managing HSC and VTCS April 2011 Revision 01 E22915 01 SLUPCOPY Procedure Running the SLUPCOPY utility 1 Allocate the SLSBKUP data set It should be slightly larger than the CDSs The size depends upon the number of discrepancies found However a recommended size is five percent larger than the current CDS The backup data set is formatted as RECFM F BLKSIZE 4096 The logical record length can be LRECL 0 which indicates to default to the block size If you are using SVAA SnapShot continue with Step 2 Otherwise go to Step 5 2 Verify that the SnapShot and SVAA Libraries are in the System Linklist Issue the following z OS commands SETPROG LNKLST TEST NAME CURRENT MODNAME SIBFVP SETPROG LNKLST TEST NAME CURRENT MODNAME SIBLLAPI If both modules are found then the SnapShot and SVAA libraries are in the system linklist If not found continue with Step 3 3 Dynamically add the SnapShot and SVAA Libraries to the System Linklist 1 Set up a PROGxx member in SYSx PARMLIB that includes the SnapShot and SVAA libraries 2 Activ
189. og Files If you need to expand your log files or re allocate them for any reason do the following 1 Create and format new log files The size of the allocated log files depends on the number of transactions your system generates as well as the frequency of performing the offload StorageTek suggests you allocate and activate some test log files and determine the rate at which they fill before determining the size of the production log files Sample JCL FMTLOG JOB account REGION 1024K S1 EXEC PGM SLUADMIN PARM MIXED STEPLIB DD DSN hlq SEALINK DISP SHR SLSLOG1 DD DSN hlq CDSLOG1 DISP CATLG DELETE UNIT SYSDA SPACE CYL 100 SLSLOG2 DD DSN hlq CDSLOG2 DISP CATLG DELETE UNIT SYSDA SPACE CYL 100 SLSPRINT DD SYSOUT SLSIN DD FMTLOG 2 Run SET LOGFILE to stage the new log files Sample JCL SETLOG JOB account REGION 1024K S1 EXEC PGM SLUADMIN PARM MIXED STEPLIB DD DSN hlq SEALINK DISP SHR SLSPRINT DD SYSOUT SLSIN DD SET LOGFILE hlq CDSLOG1 hlg CDSLOG2 3 Run OFFLOAD LOGFILE to offload the old log files JOBOFFL job account programmer S1 EXEC PGM SLUADMIN PARM MIXED STEPLIB DD DSN hlq SEALINK DISP SHR SLSOFFLD DD DSN offload dataset name 1 DISP NEW CATLG DELETE UNIT SYSDA SPACE SLSCNTL DD DSN primary dataset name DISP SHR SLSCNTL2 DD DSN secondary dataset name DISP SHR SLS
190. ok at your VTCS Dashboard and the fixes often reside in your as needed tasks Before we begin with VTV mount performance problems let s emphasize that these are common problems that you can generally diagnose and fix on your own After making a reasonable effort however if things still aren t working out it s time to call for help as described in Customer Support on page 440 There are also some tools that we don t talk about here like traces because you basically only want to use them under the direction of StorageTek service Poor VTV Mount Performance If VTV mounts occur very slowly or not at all check the following Are mounts failing on a single VTD This usually occurs because a host requests a mount of an MVC resident VTV that VSM cannot recall If so do the following Enter a Display Queue DETail command to check the queued recalls If a recall is queued waiting for an MVC it may be in use by another VTCS process which you can check with Display Active DETail 2 Ifthe MVC is not in use next enter an HSC DISPLAY VOLUME command Is the MVC actually in the ACS If not you must reenter the MVC to complete the recall Next are RTDs available to mount the MVC to recall the Enter Display RTD to check RTD availability If no RTDs are available use Display on all hosts to check active and queued processes If necessary use Cancel to cancel processes and free an RTD so the recall can complete Wi
191. ommand was issued E22915 01 Revision 01 Chapter2 31 Swapping a CDS In contrast with relocating a CDS using HSC commands or utilities there are a number of third party software products that allow disk data sets to be swapped from one location to another without affecting the users of those data sets The HSC has been enhanced to dynamically update the unit address information stored in the CDS within a few seconds after a TDMF FDRPAS or P DAS swap operation takes place so that HSC and VTCS utilities always use the new CDS location This enhancement does not provide an unrestricted ability to move a CDS Moving a CDS by a means other than a PPRC or swap operation requires a change to the VOLSER of the CDS The traditional process of a SLUADMIN BACKup and RESTore of the CDS must be used to reset both unit address and volume serial information if the VOLSER of the CDS changes 32 Managing HSC and VTCS April 2011 Revision 01 E22915 01 Restoring the CDS If all copies of the CDS fail that is you lose the Primary Secondary and Standby copies you must restore the CDS from a backup If you lose a single copy of the CDS and you have multiple copies you can use the CDS ENABLE DISABLE commands to continue running on the valid copy and recreate the copy that has the error For more information see Manually Switching to Another CDS Copy on page 27 Caution If you think you have lost all copies of the CDS contact Stora
192. on 01 E22915 01 Using the SLUPCOPY Utility to Back Up the CDS Requirements 2 SLUPCOPY can be run only on z OS systems with an active HSC subsystem SLUPCOPY must reside in an APF authorized library Only one SLUPCOPY can be run at a time across all systems that share a given HSC CDS The CDS is placed in a reserve state only long enough for the data to be copied to the SLSBKUP data set No other functions can access the CDS data sets during backup processing 2 If HSC is not active you must identify the primary secondary and standby CDSs to be used for the backup by specifying the SLSCNTL SLSCNTL2 and SLSSTBY DD statements in the JCL Ifthe HSC is active and you identify the primary secondary and standby CDSs to be used for the backup by specifying the SLSCNTL SLSCNTL2 and SLSSTBY DD statements in the JCL the DD statements are used even if HSC is active on the host where the utility is being executed If the HSC is active and these DD statements are omitted the data sets used by the active HSC on the host where the utility is being executed are used Ifan COPYMOD operation is attempted on the library containing SLUPCOPY IEB1751 and IEB19CI messages are issued and SLUPCOPY will not be successfully reblocked to the target library of the COPYMOD operation 2 SLUPCOPY can be run as a batch job or as a started task a started task may be preferable as this can avoid delays in waiting for a batch initiato
193. on to basic status provides some other valuable information that helps you decide whether you want to change CAP state and if so when 2 CAPid CAP size PCAP priority CAP 21 cell or 14 cell 9740 standard CAP 40 cell enhanced CAP 20 cell 9360 CAP 30 cell 9360 optional CAP or 39 cell SL8500 CAP Host ID of the host owning the CAP Priority CAP preference value 2 CAP mode cleaning draining ejecting entering or idle 2 CAP status active automatic mode manual mode offline online and or recovery needed The CAPPREF command lets you set the CAP mode manual or automatic and preference for selection 0 9 where 9 is the highest preference CAPs in manual mode require an ENTER command to unlock them CAPs in automatic mode do not In general you specify CAP modes and preferences in a CAPPREF command at configuration in the HSC PARMLIB Member and run with these settings If you do need to change a CAP s setting you can do it dynamically by entering a CAPPREF command For example If your systems is experiencing high levels of enters and ejects you may want to bump up the CAP preferences for enhanced CAPs The caveat on CAP preferencing is that Priority CAPs PCAPs always have a priority of 0 never selected unless specifically requested so that they remain generally available 52 Managing HSC and VTCS April 2011 Revision 01 E22915 01 Defining Manual RTDs In a DR situation you may have no automat
194. ore the last backup date and time is updated and before the PIT copy SLS70151 JCL CDS NAME MATCHES PRIMARY CDS NAME 51 570811 ESTAE ROUTINE SDWA PRESENT SLS7180I ESTAE ROUTINE DPV RESTORE NOT REQUIRED DPV NEVER UPDATED SLS71881 ESTAE ROUTINE PROCESSING ENDS IEA995 SYMPTOM DUMP OUTPUT 536 Message 7180 is issued indicating that the ESTAE recovery routine determined that the last backup date and time in the Primary CDS did not need to be restored to its original value because the Primary CDS was never updated Message 7180 after OPEN but before RESERVE An error occurs after the CDS is opened but before the CDS is reserved and before the last backup date and time is updated and before the PIT copy SLS70151 JCL CDS NAME MATCHES PRIMARY CDS NAME 51570711 OPEN SUCCESSFUL FOR SLSCNTL DD SLS7104I UCB LOCATED SUCCESSFULLY 51 570811 ESTAE ROUTINE SDWA PRESENT SLS7180I ESTAE ROUTINE DPV RESTORE NOT REQUIRED DPV NEVER UPDATED 51 57083 ESTAE ROUTINE CLOSE SUCCESSFUL SLS71881 ESTAE ROUTINE PROCESSING ENDS IEA9951 SYMPTOM DUMP OUTPUT 593 Message 7180 is issued indicating that the ESTAE recovery routine determined that the last backup date and time in the Primary CDS did not need to be restored to its original value because the Primary CDS was never updated Message 7180 after OPEN and RESERVE An error occurs after the CDS is opened and reserved but before the last backup date and time is updated and before the PIT
195. ou now have all RTDs fully engaged in migration on all VTSSs Keep it that way until you get the DBU under control then go back to something like 6 max 3 minimum You also changed the AMTs to 40 low 70 high This will get you out of trouble and the next time around migration will start sooner and bring the buffer to a lower DBU Next enter a Display VTD to get a picture of your system s VTDs E22915 01 Revision 01 Chapter4 75 FIGURE 4 3 shows an example of Display VTD output DRIVE A800 A801 A802 A803 LOCATION VIV STATUS HBVTSS16 X00778 MOUNTED HBVTSS16 X00775 MOUNTED HBVTSS16 AVAILABLE HBVTSS16 AVAILABLE FIGURE 4 3 Example output from Display VTD Operating Correctly Once again we re in good shape in FIGURE 4 3 with some VTDs in use and others ready to be used What if all VTDs showed VTVs mounted Not so good because then you risk job allocation failures if no drives are available If it s because of something like the problem that occurred in Step 2 then just accept it and vow that in the future you ll arrange workloads to let your VTDs better handle the influx of data If this is a long term problem however you may need a more power more VTSSs or upgrades to VTSSs with more capacity and more VTDs 3 Now it s time to see if you have enough scratch VTVs on hand by entering a Display SCRATCH command which produces the output shown
196. pecifying the SLSCNTL SLSCNTL2 and SLSSTBY DD statements in the JCL the DD statements are used even if HSC is active on the host where the utility is being executed If the HSC is active and these DD statements are omitted the data sets used by the active HSC on the host where the utility is being executed are used Example JCL for backing up the up Primary Secondary and Standby CDSs JOBBKUP job account programmer S1 EXEC PGM SLUADMIN PARM MIXED STEPLIB DD DSN hlq SEALINK DISP SHR SLSBKUP DD DSN backup dataset name 4 1 DISP NEW CATLG DELETE UNIT SYSDA SPACE SLSCNTL DD DSN primary dataset name DISP SHR SLSCNTL2 DD DSN secondary dataset name DISP SHR SLSSTBY DD DSN standby dataset name DISP SHR SLSPRINT DD SYSOUT A SLSIN DD BACKUP Managing HSC and VTCS April 2011 Revision 01 E22915 01 Managing CDS Logging The HSC Transaction Logging Service is an internal HSC service that records information into one or optionally two Log Files If all copies of the CDS fail that is you lose the Primary Secondary and Standby copies recovery from a backup can be time consuming When recovering from a backup CDS logging can aid in resynchronizing the CDS with the data content of the VSM subsystem If you are initially setting up logging in your configuration see Configuring HSC and VTCS The following sections tell how to manage CDS Logging Note Note that recovery usin
197. ple procedure Supervisor Call SVC Dump SDUMP and Abnormal End ABEND Dumps Error Recording Data Sets ERDS LIst Command Display Command SVC and ABEND dumps are taken where appropriate to diagnose software failures Do not use SYSUDUMP SYSMDUMP or SYSABEND DD statements in HSC JCL These ABEND types do not provide enough information on the HSC address space Software failures are logged into these error recording data sets 4480 Cartridge Subsystem and 3278 Terminal Subsystem Error Recording Data Set ERDS records are written by MVS routines The LIst command is used to display an HSC data structure and to provide for diagnostic support for the HSC Use this command under the direction of StorageTek support personnel The Display command offers several options that are useful for diagnostic purposes 72 Managing HSC and VTCS April 2011 Revision 01 E22915 01 CHAPTER 4 Using the VTCS Dashboard Using the VTCS Dashboard is basically about reviewing your MVC and VTC reports The main pieces and parts of your virtual tape configuration are VTSSs VTDs VTVs RTDs and MVCS and so it s not surprising that a lot of your daily and weekly routine is making sure they re all operating normally E22915 01 Revision 01 73 Checking Virtual Tape Status Daily Think of a VTSS as the virtual counterpart of a Nearline ACS a VTD as the virtual counterpart of a Nearline real tape driv
198. process uses log information stored in the CDS If the CDS is inaccessible then you need to use the logging information that is in the current log file which you specify with the LOGDSN parameter JOBOFFL job account programmer 51 EXEC PGM SLUADMIN PARM execution parameters STEPLIB DD DSN hlq SEALINK DISP SHR SLSOFFLD DD DSN offload dataset name 41 DISP NEW CATLG DELETE UNITZ SYSDA SPACE SLSPRINT DD SYSOUT A SLSIN DD OFFLOAD LOGFILE LOGDSN hsc 1log1 Note If the CDS cannot be accessed note that if you attempt to run OFFLOAD LOGFILE uti lity after restoring the CDS but without using the LOGDSN option the offload may not succeed or may create an erroneous log offload file 34 Managing HSC and VTCS April 2011 Revision 01 E22915 01 3 Restore the CDS from the last good backup JOBREST job account programmer 51 EXEC PGM SLUADMIN PARM execution parameters STEPLIB DD DSN hlq SEALINK DISP SHR SLSBKUP DD DSN backup dataset name 0 DISP SHR SLSCNTL DD DSN primary dataset name DISP SHR SLSCNTL2 DD DSN secondary dataset name DISP SHR SLSSTBY DD DSN standby dataset name DISP SHR SLSPRINT DD SYSOUT A SLSIN DD RESTORE Caution It is critical that your RESTORE specifies all HSC data sets in use Primary Secondary Standby For more information see ELS Command Control Statement
199. r to become available All JCL PARM options AB PC and RR are considered disabled unless explicitly specified WTORs are not issued and operator interaction is not required for normal operation Ifthe RESERVE on the HSC CDS cannot be obtained within 10 seconds and the RR option is not specified SLUPCOPY ends without performing a PIT copy If the RR option is specified reply Y to the WTOR to retry the RESERVE 2 For the COPY function the OPEN RESERVE READs WRITE PIT copy DEQ and CLOSE of the CDS are performed unless the PC option is specified and the operator reply requested that the copy be aborted or unless the RESERVE could not be obtained For the TEST function the OPEN RESERVE READs DEQ and CLOSE operations of the CDS are performed unless the PC option is specified and the operator reply requested that the copy be aborted or unless the RESERVE could not be obtained The WRITE and actual PIT copy execution are never performed For both the COPY and TEST functions a LOAD of ADRDSSU SIBBATCH or FDRSNAP is performed unless the PC option is specified and the operator reply requested that the copy be aborted or unless the RESERVE could not be obtained The system dump options for SYSMDUMP should include all of the following NUC SQA LSQA SWA TRT RGN LPA CSA SUM GRSQ The current SYSMDUMP options can be displayed using the D D O system command E22915 01 Revision 01 Chapter2 11 Do not put co
200. re are carts in the CAP after the switch completes The library retains ownership of the CAP until the cartridges are removed This is normal behavior of the SL8500 library Procedure to resolve 2 Use the procedure in the SL8500 Operator s Guide to manually remove the cartridges from the CAP with the SLC Issue Display Cap aa ll cc command for the specific cap affected If the CAP is offline issue the Modify CAP aa ll cc online command Issue the ENter aa ll cc command to restart the enter function for the CAP If CAP is automatic issue CAPP xaa ll cc MANual CAPP xaa ll cc AUTO to reset it to auto mode Insert the balance of the cartridges removed from the previous Enter into the CAP If an SLSO251E message that states that volser is a duplicate run the Unselect utility to unselect the volser Afterwards the volser may be entered into the LSM When entering the volser a message SLS0694D is displayed to ask you what you want to do with the duplicate you should respond logically delete 50 Managing HSC and April 2011 Revision 01 E22915 01 A switch occurs when an Eject function is active When a switch occurs and an eject function is active after the switch completes the cartridges in the LSM to be moved to the CAP receive an SLS0699I message 03 01 error from the library for the move operation The library reserves the CAP because there are carts in the CAP after the switch completes The library retains ow
201. re the right tool for the job for all of you service groups You can use Named MVC Pools to give an application ownership of the MVCs in the named pool For example a service group might elect to use Named MVC Pools where its customers have legal requirements to buy and own a group of MVCs However if you do not have a specific requirement for Named MVC Pools but you do want to group or segregate client data on MVCs StorageTek strongly advises that you do not use Named MVC Pools Instead use the methods described in the following sections Grouping Multiple Workloads on Shared MVCs on page 125 Segregating Individual Workloads on Separate Sets of MVCs on page 127 The above sections tell how to use Storage Classes to group or segregate data on MVCs that are selected from the system wide MVC pool In this case you need to manage a only a single MVC pool If you create Named MVC Pools you must explicitly manage each pool which includes ensuring that each pool has sufficient free MVCs and available MVC space and potentially includes setting different policies for each pool using the MVCPool MVCFREE MAXMVC THRESH and START parameters If you do elect to use Named MVC Pools go to Creating and Using Named MVC Pools on page 135 Managing HSC and VTCS April 2011 Revision 01 E22915 01 Creating and Using Named MVC Pools To create and use Named MVC Pools do the following 1 Modify existing POOLPARM statements and or
202. reclamations 90 resolving common problems 138 sharing transports with MVS 94 VTSSs 82 VTV migration demand 91 VTV recall demand 91 VTCS utilities AUDIT 110 129 recovery 148 RTV 148 E22915 01 Revision 01 VTV migration demand 91 VTDs VT Display command 76 VTSSs managing 82 VTVs demand migrations 90 migration poor performance 139 poor migration performance 139 poor mount performance 138 recall demand 90 192 E22915 01 Revision 01 193
203. redundancy and resilience built into the library hardware itself So as long as you frequently check the status of the software and hardware and fix any problems that ll take care of the bulk of your TapePlex management tasks E22915 01 Revision 01 41 Managing Library Hardware One of your best status tools is the innocuously named DISPLAY EXCEPTNS command where exceptions are less than optimal hardware conditions The command output you want to see is a series of messages that say No name of hardware component problems were detected If you re experiencing system problems this kind of output tells you that the hardware is fine but there might be software problems If on the other hand you get output such as CAP Not Operational Robot Hand needs Maintenance and LSM is Offline you need more information to determine if the problem is with the software or hardware Therefore if you get any of these messages look them up in ELS Messages and Codes where you ll find detailed explanations and user responses In some cases the response is pretty obvious and straightforward If a robot hand needs maintenance you put in a call to the CSE Sometimes the response is not so clear however If an LSM is offline the obvious move is to modify it back online unless the LSM is down for maintenance or you re changing drive unit addresses in which case you wait until the work is done before bringing the LSM back online So
204. rious library activities Optimizing Mount Performance on page 58 Scratch Redistribution utility Redistributes scratch volumes across the LSMs within a specific ACS Optimizing Mount Performance on page 58 Managing Scratch Volumes on page 59 WARN command Establishes thresholds which control when HSC notifies the operator of an insufficient quantity of scratch cartridges in an ACS Managing Scratch Volumes on page 59 CAPPREF command Specifies preference values for CAPs Managing CAPs on page 52 SMF records Logs ACS activity and performance data for analysis Optimizing Mount Performance on page 58 E22915 01 Revision 01 Chapter 1 5 The VTCS Toolkit TABLE 1 2 The VTCS Toolkit This tool does the following and is used to do these tasks AUDIT Updates the MVC and VTV Changing RTD Device Types information in the HSC CDS on page 93 Changing MVC Attributes with MVCMAINT on page 101 Logically Dismounting VTVs in an Offline VTSS on page 108 DELETSCR Deletes scratch VTVs from VTSSs Deleting Scratch VTVs on and unlinks any migrated VTVs from page 105 MVCs DISPLAY Displays the status of All Things Checking Virtual Tape Status VTCS and as such is one of your Daily on page 74 Primary tools Checking Nearline Tape Status Daily on page 78 Doing Demand MVC Space Reclamations on pag
205. rol path downtime caused by a Library Controller LC failure by automating a Library Controller switch In this configuration a second Library Controller is cabled to the local area network connecting it to the LSM s HSC directs all work to one Library Controller called the active LC while the second LC called the standby remains powered on as a ready backup Designation of active and standby LC is dynamic and their roles change according to environmental conditions For information about the commands and utilities discussed in this section see ELS Command Control Statement and Utility Reference Dual Library Controller Configuration For this implementation a dual LC configuration is one pair of LCs installed and network connected to one library in a string This is the only valid configuration FIGURE 3 1 on page 44 shows an example of this configuration E22915 01 Revision 01 Chapter3 43 LMUPATH ACS 00 LMUADDR 129 80 71 81 129 80 61 81 MVShost LMUADDR LMUADDR LMUPATH LC A Port 2B 129 80 71 81 LMUPATH LC B Port 2B 128 80 61 81 OSA G merne G J merma 7 part 1 poet 81 por C1 port D1 129 80 16 238 129 80 18 238 129 80 20 238 128 80 22 238 ZIPBZMVS ZIPB3MVS ZIPBAMVS ZIPBSMVS CHPID 02 CHPID 03 CHPID 04 CHPID 05 129 80 22 SUBNET 129 80 16 SUBNET 2 x SUBNET s 129 80 18 5 mx o lt i 129 80 61 SUBNET
206. rranty expired status 2 RETIRED VTCS also automatically detects media end of life and sets the RETIRED status to ON As above you can use SMF LOGREC data or your MVC and VTV reports to detect MVCs approaching end of life and use the MVCMAINT to manually set RETIRED ON or reset the status to RETIRED OFF for MVCs erroneously marked as retired 2 VTCS automatically detects an invalid Media Information Region MIR and sets the INVLDMIR status to ON You can recover the MIR by using either the utility available through the operator panel for the transport or by using the utility available through MPST After you recreate the MIR you can use the MVCMAINT to set INVLDMIR OFF for the MVC Note Running MVCMAINT also produces an MVC report of the volumes affected by the MVCMAINT job 102 Managing HSC and VTCS April 2011 Revision 01 E22915 01 Working with VTSSs The main thing you can do as needed with VTSSs is use the VTCS Vary VTSS command utility to vary a VTSS online offline or to quiesced state It probably goes without saying but we ll say it anyway Always know what you re doing and why when you vary a VTSS offline or to quiesced state The why is probably that the VTSS needs maintenance or you re going to remove it from the configuration which we ll talk about in Finding and Fixing VTCS Problems on page 137 First however we ll provide you with a handy chart that shows what happens when you vary a VTSS into eac
207. rs all VTVs and removes the MVC from service If all VTVs on the MVC are not duplexed VTCS AUDIT the MVC The audit will probably fail After the audit do an MVCDRAIN no eject This recalls the VTVs before the data check area in ascending block id order and the VTVs after the data check area in a descending block id order Processing the VTVs in this sequence ensures that VTCS recovers as many VTVs as possible from the media You then need to recreate the data for any VTVs still on the MVC After clearing data checks remove and replace MVCs with data check errors as described in Permanently Removing MVCs on page 98 This procedure also tells how to remove an MVC from VTCS use and return it to Nearline operations DRAINING The MVC is either currently being drained or has been the subject of a failed MVCDRain IN ERROR An error occurred while the MVC was mounted INITIALIZED the MVC has been initialized 144 Managing HSC and VTCS April 2011 Revision 01 E22915 01 LOST FAILED TO MOUNT VTCS attempted to mount an MVC and the mount did not complete within a 15 minute time out period VTCS is attempting to recover from a situation that may be caused by hardware problems HSC problems or by the MVC being removed from the ACS VTCS attempts to de preference MVCs with this state If VTCS does perform a subsequent successful mount of an MVC with LOST ON state VTCS sets the state to LOST OFF Determine the cause of the error
208. s 3 Online LSMs perform quick init 4 As each LSM becomes ready the HSC issues the message ACS AA LSM LL Ready Temp Outage Queue Will Be ReDriven 5 If the former active LC completes reboot successfully it assumes the standby LC role If the SWitch command is issued while processing is active cartridges may be in transit in various LSMs Recovery procedures occur automatically as described in Automatic LC Switch on page 48 Upon receiving the LC Ready signal HSC waits for the LSMs to complete a quick init and then re drives the requests through processing the Temp Outage Queue E22915 01 Revision 01 Chapter3 49 CAP Manual Recovery When the LC Switch occurs and certain CAP functions are processing requests enter eject manual intervention for recovery is required after the switch has completed Below are various CAP scenarios with an appropriate procedure to resolve for each A switch occurs when an Enter function is active When a switch occurs and an enter function is active after the switch completes two possible events can occur simultaneously or individually A cartridge is selected by HSC ELS but not moved to an LSM home cell when the switch occurred After the switch completes the cartridge is selected and cannot be moved to an LSM cell The cartridges in the CAP to be moved to the LSM receives message SLS0699I 03 01 error from the library during a move The library reserves the CAP because the
209. s As we already noted VTCS ELS is basically a server For example VSM automatically manages VTSS space and migrates VTVs to ensure a balance of optimum data availability resource use and data protection That s great for a stable environment but what if you find out your VSM system is about to receive a whole lot of application data Answer It might be time to run a demand migration batch job to free VTSS space before the aforementioned peak tape processing event occurs You do demand migrates with of course MIGRATE which provides the following options You can migrate VTVs by volser repeats allowed Management Class or and this is really effective the data set name associated with the VTV There s also a DELETE YES option that you may want to employ that deletes the VTV from VTSS space after a successful migration You typically use DELete YES the default for VTVs not likely to be reaccessed As an alternative you can specify DELete NO to ensure that critical data is available and quickly migrated for VTVs likely to be reaccessed The NOWAIT option helps you speed up the process That s all using MIGRATE Format 1 see ELS Command Control Statement and Utility Reference for details As an alternative you can use MIGRATE Format 2 to do a demand migrate to threshold for all or specific VTSSs That s a nice tool for getting your DBU where you want it and VTCS deals with the details Also note that with SET MIGopt
210. s 1 Verify that the LSM where you want to eject the volumes is online For example to see the status of LSM 00 00 62 Managing HSC and VTCS April 2011 Revision 01 E22915 01 DISPLAY LSM 00 00 If you get 51 500541 message that says LSM 00 00 now online you re all set Otherwise you have to figure out what the problem is and at a minimum enter a MODIFY LSM aa cc ONLINE command to get it back online 2 Use EJECT to start the eject operation For example to eject 100 scratch volumes with media STK1R and rectech STK1RC from pool 5 519840 1 EJECT SCRTCH SUBPOOL SYS19840P1 VOLCNT 100 MEDIA STK1R RECTECH STK1RC WAITCAP YES is the default so when you get operator messages to empty the CAP 3 Remove the volumes from the CAP E22915 01 Revision 01 Chapter3 63 Managing Cleaning Cartridges Hopefully you defined sufficient cleaning cartridges when you configured ELS If not Configuring HSC and VTCS tells you how After you define the cleaning cartridges enter them per Entering Cartridges on page 61 There are some additional things you can do with MNTD either via PARMLIB member or command to manage cleaning cartridges Cleaning Cartridge Selection To automatically select a cleaning cartridge when a drive needs cleaning set the auto clean option on MNTD AUTOCLN ON The drive cleaning process will select a cleaning cartridge in the LSM that is closest to the drive that needs cle
211. s to quiesced state In quiesced VTSS quiescing state the VTSS continues to accept and process back end work for example migrates recalls and audits OFFline Offline Pending In offline pending Offline In offline state The VTSS is offline to all hosts and does not accept either front end or back end work If a copy of a VTV is resident on an offline VTSS and also on an MVC and a job requires the VTV VTCS automatically recalls the VTV to an alternate VTSS if available Note In a client server environment MVS CSC and LibraryStation or SMC HTTP server on client hosts VTCS cannot determine if long running jobs are active on client hosts After a VTSS goes to offline state therefore you should still either a explicitly vary its VTDs off line to MVS or b ensure that virtual tape activity on the client host has ceased In Clustered VTSS or Cross TapePlex Replication CTR configurations the Clinks to the VTSS should be varied offline to stop replication and electronic export processing E22915 01 Revision 01 Chapter5 103 Removing a VTSS Here s the scenario for removing a VTSS You have two separate VSM systems the workload for one grows while the workload diminishes for the other Solution take a VTSS out of System A and give it to System The how to add a VTSS is covered in Installing ELS so we ll confine this section to what you do to remove a VTSS Toremove a VTSS 1 Before you remove
212. se one or more copies of the CDS Managing a TapePlex on page 41 describes the periodic and as needed tasks required to manage a TapePlex Using the VTCS Dashboard on page 73 talks about the tasks you need to do on an ongoing basis In addition to monitoring the health of your VTCS system there are several key items you ll want to put in place such as a Demand MVC Space Reclamation batch job Working the VTCS Must Do Sometime Chores List on page 89 consists of items you do for VTCS well as they need to be done There s some overlap between periodic and as needed management just as there s some overlap between these two categories and resolving problems Most likely if you re scrupulous about your management tasks you won t have to resolve many problems and vice versa Periodic and As Needed are two general boxes and you have to adjust according to the needs of your shop Leading Edge Solutions with Management and Storage Classes on page 119 is about Management and Storage Classes which are the basics of anything leading edge in VTCS land Finding and Fixing VTCS Problems on page 137 is about what to do when problems occur LCM Control Statements on page 153 is a handy cross reference of things you can do with HSC that you can also do with LCM Additional SLUPCOPY Information on page 155 provides more information about this utility iv Managing HSC and VTCS April 2011 Revision 01
213. status Entering Cartridges on page 61 DISPLAY SCRATCH Displays scratch count information Managing Scratch Volumes on page 59 DISPLAY THRESHLD Displays threshold values set by the Warn command Managing Scratch Volumes on page 59 and automatic ejection of cleaning cartridges that have exceeded their MAXCLEAN value DISPLAY VOLUME Displays physical volume Errant and Selected Volumes on information page 54 EJECT Ejects up to 9999 cartridges Ejecting Volumes on page 25 ENTER Enters one or more volumes Entering Cartridges on page 24 MNTD AUTOCLN EJCTAUTO Determines automatic drive cleaning Managing Cleaning Cartridges on page 64 duplicate volumes RELEASE Releases a CAP and makes it available for use MODIFY Changes LSM and CAP state Managing ACSs on page 42 Managing CAPs on page 52 OPTION ENTDUP Determines the response to entering Entering Duplicate Volumes on page 67 Freeing An Allocated CAP on page 69 2 Managing HSC and VTCS April 2011 SMC RESYNCH Redrive lost mounts Resolving Possible Lost Mount Requests on page 71 SCRATCH Scratches specific volumes Managing Scratch Volumes on page 59 Revision 01 E22915 01 TABLE 1 4 HSC Toolkit This tool does the following and is used to do these tasks UNSCRATCH Unscratches specific volumes Man
214. t there are enough tasks to handle the load 74 Managing HSC and VTCS April 2011 Revision 01 E22915 01 What if Display VTSS doesn t look so good Maybe something like FIGURE 4 2 VTSSNAM CAPACI DBU HI LOW VIV MX MN DE AUTOM STATE E TY MB F IG AMT AMT COUNT MT MT AC S HBVTSS1 56 209 90 80 60 27 88 4 2 02 ONLINE 6 8 HBVTSS1 56 209 92 80 60 28 97 4 2 02 ONLINE 7 4 HBVTSS1 56 209 90 80 60 22 00 4 2 01 ONLINE 8 5 HBVTSS1 93 184 92 80 60 26 00 4 2 01 ONLINE 9 9 FIGURE 4 2 Example Output from Display VTSS VTSSs with Major Operational Issues FIGURE 4 2 shows the status of four VTSSs that have some major operational issues At least they re all online if not unless you know a reason why they ought to be offline or in maintenance mode enter some Vary VISS commands to get them back online The DBUs are all too high Anything in the 90 plus range means the VTSSs are struggling to auto migrate VTVs which isn t surprising because again lets assume you have 8 RTDs connected to each VTSSs The MX MTs maximum migration tasks are set at 4 and the MN MT minimum migration tasks are set at 2 which is definitely a little light for the current migration load To fix the problem go to Step 2 2 If you didn t like what you saw in Step 1 tune up your operating parameters First get some more migration tasks going set migopt vtss vtssname maxmig 8 minmig 8 high 70 low 40 Y
215. t Performance 58 Managing Scratch Volumes 59 Adding Scratch Volumes 60 2 Populating a New LSM 60 Ejecting Volumes 62 Ejecting Scratch Volumes 62 Managing Cleaning Cartridges 64 Cleaning Cartridge Selection 64 E22915 01 Revision 01 30 vi Ejecting Cleaning Cartridges 64 Manually Ejecting Used Cleaning Cartridges 65 Solving Problems 66 Recovering Errant Cartridges 66 Entering Duplicate And Unreadable VOLSERS 67 Entering Duplicate Volumes 67 Entering Cartridges With Missing or Unreadable External Labels 67 Clearing Recovery Status On A CAP 68 Freeing An Allocated CAP 69 Restoring Host To Host Communications Services 70 Resolving Possible Lost Mount Requests 71 Resolving Lost Mount Responses 71 Overdue Response Handler 71 Operator Response Required For Mount Dismount Move and Swap 71 Using Software Diagnostics 72 4 Using the VTCS Dashboard 73 Checking Virtual Tape Status Daily 74 Tocheck Virtual Tape status 74 Checking Nearline Tape Status Daily 78 2 Tocheck Nearline Tape status 78 Looking at the Big Picture Weekly 82 Using Report 82 Using the MVC Report 85 So In Closing 86 5 Working the VTCS Must Do Sometime Chores List 89 Doing Demand Space Reclamations Migrations and Recalls 90 Doing Demand MVC Space Reclamations 90 Doing Demand VTV Migrations 91 Doing Demand Recalls 91 Working with RTDs 92 Changing RTD Device Types 93 Sharing Transports Between VSM and MVS 94 E2
216. t which Storage Classes represent these MVCs which Management Classes correspond to these Storage Classes maybe scratch some VTVs by Management Class 80 Managing HSC and VTCS April 2011 Revision 01 E22915 01 What if Display MVCPool showed you something like FIGURE 4 8 ACS 00 00 00 01 01 01 NON 1 LIB NON 1 LIB MEDIA TOTAL TOTAL STK2P TOTAL MVCPOOL INFORMATION FREE MVCS VOLS 310 120 430 10 115 22 22 GB 248 192 440 15 100 115 1100 1100 RECLAIM MVCS VOLS 4 a 35 20 55 GB 1 2 18 2 511 3 529 5 USED MVCS VOLS 300 250 350 382 53 365 12 12 GB 65 400 465 585 1675 1160 1565 1565 FIGURE 4 8 Example output from Display MVCPool Problem in ACSOI As you can see things have gotten worse in ACS 01 What do you do now Well consider the following probably in this order F Do demand reclamation to free space for more information see Doing Demand MVC Space Reclamations on page 90 Add MVCs as described in Adding MVCs on page 95 Find out which Storage Classes represent these MVCs which Management Classes correspond to these Storage Classes maybe scratch some VTVs by Management Class As a follow up review your current policies and adjust as needed You may be able to create free MVCs or free space
217. th Cancel VTCS tries to stop processes without affecting system resources or information therefore the cancellation may not occur immediately For example VTCS may wait for hardware time out periods before terminating a process using a specific RTD Note If you cancel a parent request you stop the parent and all child requests If you cancel a child request the parent request continues processing Caution If you cancel a task associated with migration scheduler either with the MIGrate parameter or by specific process ID this task will terminate but migration scheduler will start another migration task at its next timer interval You can however use migrate to threshold to stop automigration by specifying a value greater than the current DBU Tip Setting the MGMTclas statement IMMEDmig parameter to either KEEP or DELETE preferences migration processing and RTD use for migration and may increase I O to the RTDs 138 Managing HSC and VTCS April 2011 Revision 01 E22915 01 Also note that you can change the CONFIG MAXMIG and MINMIG parameter settings to rebalance automatic migration tasks with other tasks such as recall and reclaim for the RTDs you have defined for each VTSS Are the mounts failing on multiple VTDs If so check the following 2 Check VTD status with Display VTD Enter Display Active If there are no active processes ensure that VTCS HSC all VTSSs and all communications are functioning nor
218. th the release 1 Verify that the CAP is not in use by visually inspecting the CAP issuing the Display Cap command on other hosts and checking with other personnel 2 Reply Y to the message Another message confirms the CAP is released E22915 01 Revision 01 Chapter3 69 70 Restoring Host To Host Communications Services The COMMPath command and control statement lets you define a tiered communications service between HSC hosts With this type of service in place HSC automatically performs a path switch if a host receives an error trying to send a message over the current communications path Depending on the paths defined an automatic switch can be to an equivalent path type from one LMU path to another or to a lower performance method for example from VTAM to LMU HSC notifies you when a switch occurs by issuing the following message to the console on both hosts A communications path switched from XXXX1 to XXXX2 where XXXXI specifies the previous communications path XXXX2 specifies the current communications path The message also identifies the host that either initiated the switch or experienced the failure After HSC performs a downward switch you can make an upward switch only with the COMMPath command To make an upward switch Find and correct the problem which prompted the switch Return to the previous communications method by issuing the command COMMPATH HOSTID host id METHOD
219. the ACS operational Note that this happens automatically so some work may be in process within the LC When the standby LC assumes the active role it notifies HSC of its changed status and sends the LC Ready signal HSC reads the recovery information provided by the new active LC concerning in transit cartridges within the various LSMs in the ACS HSC then Modifies or marks completed the queued requests reflecting the current locations of in transit cartridges Sends all incomplete requests to the active LC Marks cartridges as errant when requests cannot be completed successfully Note Enter and eject operations may have to be restarted after a LC switch Operator Initiated LC Switch Before initiating a LC switch if some network connections are communicating determine if the need to switch LCs is immediate or if processing can be completed prior to initiating the switch If the need to switch LCs is not critical wait until the LSMs are relatively idle Initiate an LC switch for a Library ID by issuing the following command 48 Managing HSC and VTCS April 2011 Revision 01 E22915 01 SWitch Acs acsid LIB libid The command is routed through the standby LC to the disconnected LC causing it to reboot The following sequence of events occurs 1 HSC issues the message ACS AA Switch initiated expect notification in 20 seconds 2 The standby LC assumes the active LC role ACTIVE indicator illuminate
220. the CDS is therefore fuzzy unless all updates to the CDS can be prevented during the time it takes to make a PIT copy SLUPCOPY accomplishes this necessary serialization by acquiring the same RESERVE on the HSC CDS but since the PIT copy can be created in seconds instead of minutes the backup is significantly less disruptive to the operation of the HSC Why not just use SnapShot DFSMSdss or FDRSNAP directly For the serialization of volumes DFSMSdss issues a RESERVE using the SYSVTOC QNAME so this only prevents VTOC updates and DADSM functions Allocate Delete Extend Rename etc and does not ensure integrity at the data set level See Volume Serialization in the z OS VIR8 0 DFSMS Storage Administration Reference for DFSMShsm DFSMSdss DFSMSdfp For the serialization of data sets DFSMSdss issues an ENQ using the SYSDSN QNAME and the data set name as the RNAME If the SHARE keyword is not specified an exclusive ENQ is issued but this will conflict with HSC s shared ENQ if the SHARE keyword is specified a shared ENQ is issued but this is insufficient to insure data consistency A RESERVE on the HSC CDS is therefore required but since SnapShot DFSMSdss and FDRSNAP cannot issue a RESERVE with the correct QNAME and RNAME the only way to insure the consistency of the backup is for an application program SLUPCOPY to use the correct HSC QNAME and RNAME for the RESERVE DEQ sequence and invoke the PIT copy while the RESERVE is
221. this at all like archiving data with ARCHive In terms of data movement yes In terms of the reasons why you re doing it it s a reactive rather than proactive move You typically reconcile VTVs when are on the wrong media in the wrong ACS or both An ACS is unavailable for a considerable period of time then is brought back online In this case you would first change the MIGpol parameter on the MGMTclas statement for the affected VTVs to point to a different ACS and media if desired When the original ACS comes back online you then change the MIGpol parameter on the MGMTclas statement to point to the original ACS and run RECONcil specifying the updated MGMTcelas or STORclas statement s to move the VTVs to the original ACS For details of the reconciling process see RECONcil Example on page 131 RECONcil Example Let s say you want to reconcile VTVs that are on the wrong media and in the wrong ACS How would you know this Well you peruse your VTV reports on a weekly basis as described in Managing HSC and VTCS This week I notice that all the VTVs in my production PROD Management Class are on the wrong media and in the wrong ACS And the Storage Class doesn t look like the correct one either How could this have happened I thought I did the following STORCLAS NAME LOC ACS 00 MEDIA STK1R STORCLAS NAME CUSTA ACS 00 MEDIA STK1R STORCLAS CUSTB1 ACS 00 MEDIA STK1R STORCLAS
222. tical balancing act and we already talked about the operating parameters you can use to adjust this mix in Checking Virtual Tape Status Daily on page 74 In addition to adjusting the RTD operating parameters the other main tool you have with RTDs is the VTCS Vary RTD command which you use to change RTD states You can vary RTDs online offline or into maintenance mode if you need to do maintenance on the RTD The major as needed tasks you re likely to encounter are related and the first two use Vary RTD 2 Changing RTD Device Types on page 93 which is basically how to do a technology upgrade of some or all of your system s RTDs There is a special use of varying RTDs offline online and we describe that in Sharing Transports Between VSM and MVS on page 94 You need to consider the way you specify MVC media Yes I know these are really MVC considerations They come about however because of a change of RTD device types for more information see Configuring HSC and VTCS 92 Managing HSC and VTCS April 2011 Revision 01 E22915 01 Changing RTD Device Types Use the following procedure to change RTD device types Note that changing RTD device types requires you to stop VTCS on all hosts To change RTD device types do the following 1 Review your VSM policies For example you may want to review your Management Class and Storage Class definitions if this RTD device type is used for migrations 2 Vary the o
223. tion see Creating and Using VIT CS Management and Storage Classes The Basics on page 122 5 Specify the Management Class name to VTCS on any of the following The SMC TAPEREQ statement SMS routines that you write to the StorageTek DFSMS interface for more information see SMC Configuration and Administration Guide Note If you specify a Management Class on a TAPEREQ statement and an SMS routine the Management Class on the SMS routine takes precedence E22915 01 Revision 01 Chapter6 135 136 Managing HSC and VTCS April 2011 Revision 01 E22915 01 CHAPTER 7 Finding and Fixing VTCS Problems This section is about what to do when things go wrong Okay you ve already done your dailies per Using the VTCS Dashboard on page 73 and your as neededs per Doing the HSC Basic Chores on page 23 and things are still not going well Here is the place where you find out how to get VICS working again when problems occur starting with the simple problems you ll probably run across in Fixing Common Problems on page 138 Note Recovering the CDS is primarily an HSC task but it also has a VSM side For more information see Restoring the CDS on page 33 E22915 01 Revision 01 137 Fixing Common Problems Common in this context just means things that are likely to go wrong despite your best efforts The way you find out about trouble often doubles back to taking another lo
224. tions do the following 2 VTCS Management Classes specify how VTCS manages VTVs The HSC MGMTclas control statement defines a Management Class and its attributes For example the DELSCR parameter of the MGMTclas statement specifies whether VTCS deletes scratched VTVs from the VTSS Management Classes can also point to VTCS Storage Classes which specify where migrated VTVs reside The HSC STORclas control statement defines a Storage Class and its attributes For example MGMT NAME PAYROLL MIGPOL LOCAC REMAC STORCLAS NAME LOCAC ACS 00 MEDIA STK1R STORCLAS NAME ACS 01 MEDIA STK2P ZCART This combination of Management and Storage Classes says For Management Class PAYROLL migrate duplexed to separate MVCs in the local and remote ACSs In the local ACS put it on 9840 media so I can get it back in a hurry if I need it In the remote ACS prefer 9940 over ZCART media but definitely put it in Deep Storage there Let s start with Creating and Using VTCS Management and Storage Classes The Basics on page 122 which is a basic procedure you can adjust for any of your business s needs Next it s on to Leading Edge Techniques You Can Do with Management and Storage Classes on page 124 Think of this section as a gallery where you get to see a variety of options then pick out the one that works best for you E22915 01 Revision 01 ChapterG 121 Creating and Using VTCS Management and Storage
225. to separate MVCs in the local and remote ACSs In the local ACS put it on 9840 media so I can get it back in a hurry if I need it In the remote ACS prefer 9940 over ZCART media for deep storage on high capacity media Giving two critical jobstreams payroll and accounting access to these Management Storage Classes Result all your payroll and accounting data is duplexed local and remote grouped on the same set of MVCs of the appropriate media per the Storage Class specifications Production data is also critical but we want it on a separate set of MVCs from the ones used for payroll and accounting data No problem just create another Management Class Storage Class combination for production data and you re done Segregating Individual Workloads on Separate Sets of MVCs on page 127 All you service groups study this one carefully because you ll probably use it a lot Ever want to give each of your clients his her own set of resources for billing security purposes Segregating workloads is the key Archiving Data on page 129 In this scenario you can use VTCS to mimic HSM in the StorageTek automated tape virtual tape environment only That is you can use the ARCHAge and ARCHPol parameters of the MGMTclas statement to set an Archive Policy for VTVs in a Management Class Information Lifecycle Management ILM a StorageTek storage management strategy has as its central concept the idea that data should be stored o
226. u have done your POOLPARM VOLPARM definitions enter the cartridges as described in Entering Cartridges on page 61 60 Managing HSC and VTCS April 2011 Revision 01 E22915 01 Entering Cartridges Cartridges are just cartridges until they get entered into the ACS then they become volumes in the CDS You can enter scratch cartridges non scratch cartridges cartridges to be used as MVCs or cleaning cartridges To enter cartridges 1 Verify that the LSM where you want to enter the cartridges is online For example to see the status of LSM 00 00 DISPLAY LSM 00 00 If you get an 51 500541 message that says LSM 00 00 now online you re all set Otherwise you have to figure out what the problem is and at a minimum enter a MODIFY LSM aa cc ONLINE command to get it back online 2 Check the CAP mode For example to see the status of the PCAP on LSM 00 00 DISPLAY CAP 00 00 02 If the CAP mode is Automatic go to Step 4 Otherwise continue with Step 3 3 If the CAP mode is Manual you have two choice depending on your site s practices 2 Change the CAP mode to Automatic For example for the PCAP in Step 2 to set the CAP preference to zero always required for PCAPs and mode to Automatic CAPPREF 0 00 00 02 AUTO Use ENTER to make the CAP ready for cartridge entry mode stays Manual For example for the PCAP in Step 2 to make the CAP ready for entry and set scratch status on for the entered cartridges EN
227. urn codes are described in TABLE B 1 TABLE B 41 SLUPCOPY Return Codes 0 Normal completion 4 Reserved not currently issued 8 JCL PARM validation errors 12 Logic errors data value errors no match errors 16 IBM service failures 20 Operator requested abort of Point In Time copy E22915 01 Revision 01 AppendixB 157 SLUPCOPY Problem Reporting Determination and Resolution Problem Reporting Procedure Report SLUPCOPY problems and send all required SLUPCOPY output and the SYSMDUMP data set to StorageTek Support Common Problem Symptoms and Remedies DFSMSdss SnapShot Problem Symptoms and Remedies Message ADR472E with Reason Code 08 indicating that DFSMSdss was unable to select a target volume Reason Code 08 indicates that the target data set name is a duplicate Change the target data set name or use the REPLACE keyword but if REPLACE is used be sure the correct target data set name is specified to avoid overlaying the wrong data set 2 Message ADR918I with Return Code 5 plus message ADR938E indicating that fast replication could not be used or message ADR918I with Return Code 3 and QFRVOLS Reason Code C8 plus message ADR938E indicating that fast replication could not be used Perform the procedure in Verify that the SnapShot and SVAA Libraries are in the System Linklist on page 13 to search for the SIBFVP and SIBLLAPI modules If both modules are found in the system linklist
228. use you have nothing else to do If you have to manually delete scratch VTVs it s because you guessed it you re in trouble to the tune of the scenario on page 81 To prevent inadvertent VTV deletion via operator command DELETSCR is a SLUADMIN utility only and has the following capabilities You can specify VTVs by volser individual volser list or range Management Class or HSC Scratch Pool Using your MVC and VTV reports you should already have a good idea of the best way to identify the candidates and apply the corresponding DELETSCR option You can only specify one option VTVid MGMTclas or SCRpool and if you don t specify anything DELETSCR deletes all eligible VTVs which may be what you want but think before you go for that method The mandatory NOTREF parameter specifies the days since a VTV was referenced 1 999 NOTREF is effectively a grace period any VTV referenced within the specified grace period is not deleted There is a handy optional MAXVTV parameter that specifies the maximum number of VTVs that DELETSCR deletes Note that this is a maximum not a target If you re running DELETSCR proactively during a non peak period you might not care about MAXVTV If you re in trouble you most certainly will Note that the range for MAXVTV is 0 999 What happens if you specify 0 In this case DELETSCR does not delete any VTVs but the summary report shows how many VTVs would have been deleted at the point at
229. wait until things quiet down If however you do have other RTDs available for example RTDs that you are sharing manually with MVS and VSM by all means vary them offline to MVS and use Vary RTD to make them available to VTCS 2 Next see how your MVCs are doing with a Display MVCPool command E22915 01 Revision 01 Chapter4 79 FIGURE 4 7 shows an example of Display MVCPool output with no MVC pool name specified so you see information for all your system s MVCs MVCPOOL INFORMATION ACS MEDIA FREE MVCS RECLAIM MVCS USED MVCS VOLS GB VOLS GB VOLS GB 00 ECAR 310 248 4 1 2 100 65 00 ZCART 120 192 1 9 5 250 400 00 TOTAL 430 440 5 1 4 350 465 01 ECAR 90 144 15 6 2 322 485 01 ZCART 35 700 3 11 3 43 675 01 TOTAL 125 844 18 17 5 365 1160 NON LIB STK2P 22 1100 0 0 12 1565 NON LIB TOTAL 22 1100 0 0 12 1565 FIGURE4 7 Example output from Display MVCPool no pool name specified FIGURE 4 7 shows that your MVC collection is in good condition There appear to be plenty of Free MVCs 100 usable space no migrated VTVs and plenty of free space across multiple ACSs and MVC media types Numbers for MVCs eligible for reclaim are relatively low meaning that automatic space reclamation probably won t get in the way of migrate recall activity Used MVCs looks okay in proportion to Free MVCs except maybe in ACS 01 ECART and ZCART media For these MVCs you might want to do some investigation find ou
230. which you ran DELETSCR that is the report is just a snapshot Finally you can see the results of your work via the DELETSCR reports standard or detailed via the DETAIL parameter E22915 01 Revision 01 Chapter5 105 DELTSCR JCL Example FIGURE 5 2 shows example JCL to run the DELETSCR to delete scratch VTVs in Management Class MCI not referenced within 60 days up to a maximum of 800 VTVs and produce a detailed report DELETSCR EXEC PGM SLUADMIN PARM MIXED STEPLIB DD DSN hlq SEALINK DISP SHR SLSPRINTDD SYSOUT SLSIN DD DELETSCR MGMTCLAS MC1 NOTREF 60 MAXVTV 800 DET FIGURE 5 2 DELETSCR utility example 106 Managing HSC and VTCS April 2011 Revision 01 E22915 01 Changing VTV Attributes with VTVMAINT VTVMAINT is another handy tool this time for VTV maintenance which does the following Selects VTVs by volser range list individual volser your choice 2 Unlinks VTVs from MVCs which I would want to do because Answer It s likely you re going to want to do this if you change a VTV s Management Class as described in Changing Management Class and Unlinking VTVs from on page 107 Change the VTV s Management Class which you do when you want to be managed differently There are other ways to do this but the best tool is clearly VTVMAINT as described in Changing Management Class and Unlinking VTVs from on page 107 Logi
231. y SMCUDBX for client server configurations OR LCM OPTIONS SYNC parameter process As described above scratch synchronization can free scratch volumes Typically you do scratch synchronization after your daily TMS run Redistributing Scratch Volumes Use the HSC Scratch Redistribution utility or LCM to redistribute scratch volumes across the LSMs within a particular ACS As described in Optimizing Mount Performance on page 58 poor scratch distribution can inhibit optimum library performance Scratch redistribution balances the number of scratch volumes between specified LSMs in an ACS and can be done by subpool Scratching Specific Volumes The HSC SCRAtch command scratches one or more volumes The HSC UNSCratch command unscratches one or more volumes Yes if you have the command authorization you can actually scratch and unscratch specific volumes In general however don t explicitly scratch specific volumes unless you really know what you re doing Let the TMS manage volume scratch status and do scratch synchronization instead Displaying Scratch Subpool Information Display SCRatch This only displays scratch subpool information for the host the command is executed on to display all scratch subpool information use the VOLRPT utility E22915 01 Revision 01 Chapter3 59 Adding Scratch Volumes Adding scratch volumes to the library is a general task that
232. you ve used DISPLAY EXCEPTNS as your first diagnostic tool and either found no problems or found problems and resolved them and you re using the Activities and ACS daily Reports to tune up the library performance What s next in terms of managing the library hardware In the following sections we get more granular with status commands and responses to the conditions they show Managing ACSs Two other commands you should know and use are DISPLAY ACS and DISPLAY ALL DISPLAY ACS shows you the status of your ACSs which includes hardware statuses for the ACSs LMUS and stations and scratch volumes and free cells available DISPLAY ALL tells you all that plus LSM and CDS status You may see components that are not in an online or operational state ACSs disconnected stations offline or in standby mode LSMs offline and so forth You use the MODIFY command to change the state of LSMs and CAPs and the VARY command to change ACS state But per the above discussion know why you re changing hardware states and how to do it before you enter the appropriate command If you need to modify an LSM offline for maintenance make sure you ve quiesced tape activity to that LSM before you do so and correspondingly make sure the maintenance is complete before you vary online the LSM 42 Managing HSC and VTCS April 2011 Revision 01 E22915 01 Managing SL8500 Redundant Electronics A Redundant Electronics option is available to minimize cont

Managing HSC and VTCS 7.1

Contents

Download Pdf Manuals

Related Search

Related Contents