Skip to Content

Data extraction

(BMC.AMISTG.SPE2201)

BMC AMI Storage Reporting views display various record types, such as Tape records, Space records, HSM records, and Performance records. There are multiple records within each record type. For example, there are 8 different Space records, and 15 different Tape records. Each record is related to one or more BMC AMI Storage views. When you invoke a view, the related record is requested for display. The data for the entire record is collected, but only the elements defined in the view are displayed. 

Related topics

Batch-reporting

SETSRM-command

SMMSYSxx-PARMLIB-parameter-quick-reference

SMMSYSxx-PARMLIB-parameter-explanations

The data extraction process works in a similar manner except that when a view is invoked, the entire record is returned and written to the extraction file. For example, the view SPVOLPU (Volume space by percent used) is the S13 record. The S13 record contains 179 elements, and SPVOLPU is one of the 21 BMC AMI Storage views that displays this record. Each of these 21 views displays various elements from this record, and no single view displays all the elements. However, when you extract the data for the S13 record, all 179 elements are written to the extraction file.

Warning

Important

The record contains base elements only. During view display, MVI can generate calculated fields. The elements of these fields are not included in the record written to the file.

The SMP/E distributed library BBMAP contains the SVWUBASE member. This member contains the list of view names, their related record-IDs, view descriptions, and the member in BBMAP that contains the record map. The record map member describes the elements that are in the extracted file. The records listed in SVWUBASE are the only records that are available for extraction. The parameters that are used to create the extraction file are valid only in the listed views, and these parameters are ignored in all other views. To obtain additional view records, submit an enhancement request to BMC Support.

Data extraction parameters

The data extraction process uses four SMMSYSxx parameters and two SETSRM parameters.

SMMSYSxx parameters

The following four SMMSYSxx parameters are used in data extraction:

  • EXTR_OINDX=—The EXTR_OINDX= parameter must be coded with the desired prefix (High Level Qualifiers) of the output data set name that contains the extracted data. This High Level Qualifier (HLQ) is appended with the mid qualifier EXTR combined with the record ID requested EXTRrecID. The suffix of this data set is Date.Time of the data set creation, or GnnnnVnn depending on the value placed in the SETSRM parameter that is used in the request. These mid and low qualifiers are defined by the process and cannot be changed.

The following parameters determine where the data set created by the extraction process is allocated.

SETSRM parameters

The following two SETSRM parameters are used in data extraction:

  • EXTRGDG—The EXTRGDG parameter causes the data to be written to the sequential file instead of displaying it in view format. The options for EXTRGDG are Y and N.  
    • Coding N indicates that the data set being created is not a Generation Data Group (GDG) data set, and has a low-level qualifier containing the date and time of the data set creation. 
    • Coding Y indicates that the data set being created has to be a GDG data set. 
      If Y is coded, you must have a previously created entry in the catalog for the GDG base name, otherwise the allocation fails. A GDG entry must be created for each BMC AMI Storage record that is going to use a GDG. The GDG entry that is created must match the prefix defined to the EXTR_OINDX parameter combined with the mid qualifier created by the process.
  • EXTRFMT—The EXTRFMT parameter determines the format of the extracted data. Currently, only raw R data (EXTRFMT(R)) is available, which is also the default. 
    For more information, see SETSRM-command. 

The following is an example of output data set name when extracting the S13 (SPVOLPU) Record.

The SMMSYSxx member contains: 

EXTR_OINDX=SYS3.SRMDATA

The SETSRM command contains:

EXTRGDG(N):  SYS3.SRMDATA.EXTRS13.D170502.T232593
EXTRGDG(Y):  SYS3.SRMDATA.EXTRS13.G0001V00 

Data extraction process

To extract BMC AMI Storage data, we recommend using MVI batch processing. The data extraction process can be invoked in an online session, but the session is engaged until the process completes. For more information, see Batch-reporting and Accessing the BMC AMI Ops Batch Reports panel. 

In the data extraction process, you can use MVI view parameters such as TIME and CONTEXT. SETSRM parameters, that provide filtering criteria can also be used. 

Example

To display the CAPSMRMS view (S21 record) for capacity planning summary by group, the command is as follows: 

SETSRM RESTYPE(G);CAPSMRMS

The parameters represent:

  • RESTYPE—Resource Type: G = Groups/Pools
  • CAPSMRMS—View Name requested: Capacity Planning Summary Record

The result is the CAPSMRMS view displaying groups and pools. 

To extract that same record to a file, the command is as follows:

SETSRM RESTYPE(G) EXTRFMT(R) EXTRGDG(N);CAPSMRMS

The parameters represent:

  • RESTYPE—Resource Type: G = Groups/Pools
  • EXTRFMT—Extract Format: R = Raw Data (default, optional)
  • EXTRGDG—Output Data Set Low Level Qualifier: N = Date.Time
  • CAPSMRMS—View Name requested: Capacity Planning Summary Record

The result is the S21 record consisting of groups and pools that is written to a sequential file. 

When EXTRGDG is utilized within the SETSRM command either online or in batch, no record data is returned to the online session, or to the output in the batch report. Instead, a message is displayed indicating the view requested, the record-ID, extraction type, GDG indicator, the number of records returned, and the full data set name where the data is written. 

We do not recommend the online process, however, if you are executing in an online session, once the information about the extraction is displayed, press PF3 to exit. Pressing enter will cause the view to display in your session.

An example of the message displayed is as follows: 

VIEW: CAPSMRMS REC: S21 FMT:R GDG:N REC#:  10073
DSN: SYS3.SRMDATA.EXTRS21.D170514.T242553
IF EXECUTING ONLINE, PRESS END (PF3) TO EXIT  

To extract data from a BMC AMI Storage record

  1. Define the output DSN prefix in the SMMSYSxx parameter using the EXTR_OINDX parameter.
    1. Define allocation information using EXTR_SCLAS, EXTR_VOL, and EXTR_OUNIT.
    2. Refresh SMMSYSxx.
  2. Identify the view data that you want to extract. Find the view name in SVWUBASE and make note of the record ID.

  3. If you want a GDG output data set, use IDCAMS to define the GDG base name to the catalog. 
    The GDG base name is the prefix defined to the EXTR_OINDX parameter combined with EXTRrecid.
    For example, SYS3.SRMDATA.EXTRS13.

    Warning

    Important

    For more information about creating GDG, see IBM's DFSMS Access Method Services Commands documentation.

  4. From the BMC AMI Storage Main Menu under the Tools & Menus, select Batch Reporting.
  5. From Batch Reporting, select MVI Batch Report:
    1. Assuming that option 0 (SETUP) is complete, select option 1 (Generate).
    2. In the Generate option, complete the fields as described.
  6. Enter the following command:
    SETSRM EXTRGDG(?) EXTRFMT(R) parm parm parm; viewname
    Here:
    • EXTRGDG can be Y or N.
    • EXTRFMT has R as default and is optional.
    • Add any additional SETSRM filter parameters (parm) for the view, followed by a semicolon ( ; ) and the view name.
  7. Press PF3 to save and generate the JCL.
  8. Submit the JCL.
    The output of the job contains information related to the extraction data set that is created.

Processing the extracted data

The map member (SVWUrecID) of the record that is extracted contains the element names, offset, length, type (Binary, Character, and so on), and description.

This information along with the extracted file can be used as input to a subsequent facility or program for further processing.  



                                               

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI Storage Reporting 8.2