The reports can be analyzed to determine the total capacity of the data on tapes. In addition, by segmenting the capacity according to program, it is possible to identify the capacity of data used for archive and backup.
Step 2: Current mainframe tape configuration (Required)
Please provide a description of the tape configuration, similar to the example below. The CHPIDs are required to process SMF type 73 records.
Step 3: Copy the tape management catalog (Required for traditional VTL analysis)
Create a copy of the tape management system control data set. Select any of Control-T, ZARA, TMS, TLMS, or RMM control data sets. Repeat this for all Plexes.
It is not compulsory to send all SMF record types listed here, however, more SMF data will result in a more detailed analysis.
SMF 73: RMF data (Required)
If the amount of data becomes too large, limit the time to, for example 1 week, instead of 1 month of data.
SMF 30 Type 2 (Required)
System task CPU data
SMF 21: Tape mount activity data (Optional)
SMF 241: HSM activity (Optional)
SMF 94: VTS data (Optional)
SMF 194: TS7700 data (Optional)
Step 5: Collect VSM data (Optional)
Click here to expand...
VSM capacity data - (MVC, VTV and VOL Report)
This applies to a tape configuration with VSM systems with RTD's, maybe combined with some tape drives in the tape library directly connected to MF (i.e. some tape drives are not RTD's behind VSM, but they are in the same tapelib). This is data extracted from the Oracle (HSC/ELS) CDS (Control DataSet). Please collect one report for each CDS.
HSM activity data - (HSM FSR SMF type 241 records, all LPARs)
This is data extracted (using the IBM utility IFASMFDP) from the SMF datasets of record type 241 (241 is the HSM FSR record default value, it can be changed by the customer). See the ARCCMDxx member for each HSM. If there is no SETSYS SMF(nnn), the default value is 241. If there is a SETSYS SMF(nnn), add 1 to nnn for the FSR record number. For example, if the ARCCMDxx member shows SETSYS SMF(200), the HSM FSR record number would be 200+1=201.
This data must be prepared for transmission if it is to be sent to mainstorconcept via FTP (see FTP instructions). SMF files are variable in format and must be converted to fixed format using the IBM TRSMAIN (terse) utility before the file can be sent (binary) by FTP. Collect seven to thirty days of data for analysis.
HSM parameters, tape use
Copy the active ARCCMDxx member to a text file. The file can be sent to mainstorconcept via FTP (text mode). Execute HSEND QUERY SETSYS to see run time parameters. Copy the command output to a text file. The file can be sent to mainstorconcept via FTP (text mode). Perform HSEND LIST TTOC SELECT(BOTH) ODS(TTOC.OUTPUT) command (use ISPF panel 6 to enter the command). Copy the command output to a text file. The file can be sent to mainstorconcept via FTP (text mode).
HSM MCDS & BCDS data - point-in-time (DCOLLECT "M" and "B" records, all HSM plexes)
This is IDCAMS DCOLLECT data. The DCOLLECT data is variable in length and must be "tersed" before FTP to mainstorconcept. Use the following JCL to gather the DCOLLECT data:
Tersing the Data sets helps to ensure that the data is not corrupted at any point during the transfer out of the mainframe and to our systems. Tersed files are also easier to transfer due to their compressed size. These files can be further compressed by x86 tools like zip to reduce the transfer file size even more.
Use TRSMAIN program (TERSE) with PACK option to compress the data: