Extracting historical data (PTFs BQY1950 and BQY2072 applied)

Use the History File Extraction utility (BBM9MD73) to extract historical data records for Record Entries (REs), such as address spaces, disk storage devices, and network connections from MainView products. You can then use third-party software programs and data analytics tools to access, sort, reformat, and utilize the extracted data. BBM9MD73 can extract historical data directly from the VSAM KSDS history data sets collected by each MainView product address space (PAS). This includes data that is segmented and spans more than one logical or physical record. BBM9MD73 can also extract historical data that was archived from the VSAM history data set using the IDCAMS utility. 

• You can reformat product-specific data to standard output files for use by MXG or other third-party applications. Superfluous, empty, or unused records and segments are removed during extraction.
• You can extract all of the historical data records in the history data set, or you can sort through the extracted data and select only specific REs. For more information about selecting specific REs, see Selecting records by specific product and record type ID number (RTIN) (PTFs BQY1950 and BQY2072 applied).
• You can use an automated operations tool, such as MainView AutoOPERATOR, to offload history data from the VSAM data sets after the data sets are filled and closed, or quiesced. BMC recommends doing this. For more information about automating the history extraction process, see Automating Historical Data Extraction (PTFs BQY1950 and BQY2072 applied).

Output records

Output records can be in either packed or unpacked format: 

• Packed includes multiple historical data records for each physical output record. It is the data format that best saves space. BMC recommends that you use packed format for products written in languages that can deal with repeated fields or segments of information (such as SAS(R)).
  
  
• Unpacked includes one historical data record for each physical output record. It enables data to be easily sorted and handled. BMC recommends that you use unpacked format for products written in languages that do not deal well with variable-length records, repeated fields, or segments of information. You would typically find the unpacked format in a flat (or flattened) file.
  
  Unpacked format makes it easy to sort and select individual REs during post-processing. You can then send those REs for warehousing or analysis by customer programs or OEM vendor products.
  
  Unpacked format results in more physical records and repeated record headers in the output data set and therefore consumes more space than packed format does.

The type of data in both formats is identical except for the quantity of individual historical data records included in the physical output record. For example, in packed format, BBM9MD73 includes as many historical data records as it is possible to fit in the supported output record. In unpacked format, only one historical data record is included in each output record (conventionally referred to as "flattening" the data). For more information about output records, see Headers in extracted history records (PTFs BQY1950 and BQY2072 applied).

To run BBM9MD73 

BBM9MD73 is intended to run in a batch job, submitted by an automation product in response to the following message from a PAS:

BBMEA054I Offload BBXXXXX  XXXXXX    0 BMC.MV.SYSA.XXXXX.HXXXXXnn

In this message:

• BBXXXXX is the jobname assigned to the PAS that issued the message.
• XXXXXX is the PAS type.
• 0 is the Interval recorder set ID.
• BMC.MV.SYSA.XXXXX.HXXXXXnn is the recently filled and closed or quiesed VSAM history data set name.

Sample JCL for batch jobs

The following examples show simple JCL that you can use to create batch jobs for BBM9MD73:

Extract historical data records from MainView for IP with a normal interval recording set

 //SAMPJOB1 JOB  …
 //MVIPX    EXEC PGM=BBM9MD73,PARM='PACK=Y,TYPE=MVIP,IRSID=0’         
 //STEPLIB   DD DISP=SHR,DSN=BMC.BBLINK                             
 //SYSPRINT  DD SYSOUT=*                                            
 //SYSUT1    DD DISP=SHR,DSN=BMC.SYSA.MVIP.HISTDS01    
 //SYSUT2    DD DISP=(NEW,CATLG),                                   
 //             DCB=(LRECL=32000,BLKSIZE=32760,RECFM=VB,DSORG=PS),  
 //             SPACE=(CYL,(100,50),RLSE),UNIT=SYSDA,               
 //             DSN=BMC.SYSA.MVIP.HST0DS(+1)                        
 //*

Extract historical data records from MainView for z/OS with a long-term interval recording set

 //SAMPJOB2 JOB  …
 //MVMVSX  EXEC PGM=BBM9MD73,PARM='PACK=N,TYPE=MVMVS,IRSID=1'       
 //STEPLIB   DD DISP=SHR,DSN=BMC.BBLINK                             
 //SYSPRINT  DD SYSOUT=*                                            
 //SYSUT1    DD DISP=SHR,DSN=BMC.SYSA.MVSPAS.HS1TDS01 
 //SYSUT2    DD DISP=(NEW,CATLG),                                   
 //             DCB=(LRECL=32000,BLKSIZE=32760,RECFM=VB,DSORG=PS),  
 //             SPACE=(CYL,(100,50),RLSE),UNIT=SYSDA,               
 //             DSN=BMC.SYSA.MVSPAS.HS1TDS(+1)                       
 //*

BBM9MD73 batch parameters

The following table describes the parameters you can use when defining a BBM9MD73 batch job.

Return codes issued by BBM9MD73 

BBM9MD73 might issue the following return codes during batch job processing. The JCL or caller of BBM9MD73 can test these codes and take any necessary action if an error or warning condition has been detected. In general, any non-zero condition code will be accompanied by a message to indicate the source of the error.