Transforming historical z/OS Connect EE detail data into CSV files (PTF BPF0457 applied)

BMC AMI Ops Monitor for Java Environments can extract historical z/OS Connect EE detail data from active NGL logsets and transform the extracted data into comma-separated values (CSV) format. You can then analyze the extracted CSV data in off-mainframe data analytics tools, such as Excel or Splunk.

BMC AMI OpsMJE extracts the data by using the MJE9NGEX utility and transforms the data into CSV format by using the BMC AMI Ops Infrastructure Data Transformation utility (BBM9MD75). The MJE9NGEX utility is similar to the BMC AMI Ops Infrastructure History File Extraction utility (BBM9MD73).

To run MJE9NGEX, customize and submit the MJENGLEX BBSAMP member. MJE9NGEX creates a data set containing the extracted data. The data set is formatted with the common header, and includes data from the following OREC DSEC fields:

• ORECTIME
• ORECRTIN
• ORECSYS
• ORECISID
• ORECOTYP
• ORECRES

This data set is used as the input for the BBM9MD75 utility. To run BBM9MD75, customize and submit the MJENGL75 BBSAMP member. MJENGL75 creates a data set containing the transformed CSV data. This process is explained in the following procedures.

For more information about extracting and transforming history data for BMC AMI Ops Infrastructure products, seeWorking with historical data.

Before you begin

Make sure that the BMC Execution Component for z/OS (DBC) and the Next Generation Logger (NGL) agent are up and running.

To extract the data

Customize and submit the MJENGLEX member in BBSAMP as follows:

1. Insert a valid JCL job card.

2. Replace the variables in the following DD statements:

   DD statement	Variable	Description
   STEPLIB	?BBLINK?	MJE BBLINK library
   	?XXLINK?	MJE XXLINK library
   OUTPUT	?OUTPUTDSN?	Output data set to send the z/OS Connect EE detailed data in normalized format

3. Specify the following parameters: 

   Parameter	Description
   TYPE=[CD0 | ZC1 | ZCD | S79 | S80 ]	(Required) Type of record to extract CD0—All JVM CPU detail ZC1—z/OS Connect EE API Requester detail ZCD—z/OS Connect EE SMF123 API Provider detail S79—JZOS and IMS SMF 121-1 & 29-2 detail S80—JZOS CPU SMF detail Important To select multiple record types, submit the MJENGLEX JCL separately for each record type and concatenate the output data sets into a single data set. Then, specify that data set as input for the MD73IN DD statement in the MJENGL75 JCL.
   DBCSSID=dbcSsid	(Required) Database collector SSID
   NGLPIID=nglPiid	(Required) NGL PIID for the NGL agent
   STARTTIME=[DDMMMYYYY-HH:MM:SS | YESTERDAY]	(Optional) Date and time from which to start extracting NGL records Important The STARTTIME and ENDTIME parameters enable you to limit the number of extracted records to NGL records created during the specified time period. If you don't specify values for STARTTIME and ENDTIME, all records are extracted. If you specify YESTERDAY, records are extracted between 00:00—24:00 on the previous day. If you specify YESTERDAY, you cannot specify a value for ENDTIME.
   ENDTIME=DDMMMYYYY-HH:MM:SS	(Optional) Date and time to stop extracting NGL records

   
   

   Examples

   The following example extracts SMF123 API Provider detail data from 00:00—24:00 on the previous day:

   //MJE9NGEX EXEC PGM=MJE9NGEX,REGION=0M                  
              //SYSIN     DD  *                                       
                         TYPE=ZCD,                                    
                         DBCSSID=SNDC,                                
                         NGLPIID=SNNG,                                
                         STARTTIME=YESTERDAY                          
   /*

   The following example extracts API Requester detail data from April 01, 2021 to April 22, 2021:

   //MJE9NGEX EXEC PGM=MJE9NGEX,REGION=0M                  
              //SYSIN     DD  *                                       
                         TYPE=ZC1,                                    
                         DBCSSID=SNDC,  
                         NGLPIID=SNNG,                                 
                         STARTTIME=01APR2021-00:00:00,                 
                         ENDTIME=22APR2021-23:59:59                    
   /*

4. Submit the JCL by typing SUB on the command line.

   The data is extracted to the specified OUTPUT data set in a normalized format. For extraction details, see the SYSPRINT DD card. If SYSPRINT contains return codes, see Return codes used by MJE9NGEX.

   Example

   MJENGX01I STARTING NGL EXTRACTING PROGRAM...                         
   MJENGX02I NGL CLIENT PROGRAM LOADED                                  
   MJENGX03I CONNECTION TO NGL ESTABLISHED                              
   MJENGX04I NUMBER OF NGL RECORDS EXTRACTED SUCCESSFULLY : .000671.....

To transform the data

Customize and submit the MJENGL75 member in BBSAMP as follows: 

1. Insert a valid JCL job card.

2. Replace the variables in the following DD statements:

   DD statement	Variable	Description
   OUT1	?OUTPUTCSV?	CSV data set
   STEPLIB	?BBLINK?	MJE BBLINK library
   MD73IN	?INPUTDSN?	Data set containing the generated output of the MJENGLEX JCL This is the OUTPUT data set specified in the MJENGLEX JCL. Alternatively, if you created multiple OUTPUT data sets for different record types, specify the concatenated data set.
   BBACTDEF	?BBACTDEF?	BBACTDEF library where MJFTDM resides
   BBSAMP	?BBSAMP?	BBSAMP library where the product's data maps reside
   BBMAP	?BBMAP?	BBMAP library where the product's data maps reside

   
   

3. Insert a SELECT query statement specifying the record entries (REs) that you want to filter, and the product data map that contains the REs.

   The following statement selects data the S123JOB, S123TYPE, and S123SYSN REs from the MJFUZCD0 data map:

   SELECT S123JOB, S123TYPE, S123SYSN
   FROM   MJFTDM.MJFUZCD0

   
   For more information about SELECT statements, seeTransforming historical data.

4. Submit the JCL by typing SUB on the command line.
   The CSV data is loaded into the specified OUT1 data set. You can use the FTP function to download the data set to your computer.

Return codes used by MJE9NGEX 

MJE9NGEX might issue the following return codes during processing. In general, any non-zero condition code is accompanied by a message that indicates the source of the error.