Procedure to configure the monitor service to call the CECSXSMF exit

The following steps provide an overview of the procedure to follow to configure the monitor service to call the CECSXSMF exit, extract the SMF records produced by the exit, and execution of the sample REXX script to produce a CSV output file.

1. Using Classic Data Architect or a z/OS® modify command, update the monitor service SMFEXIT configuration parameter to activate the CECSXSMF exit.
   The sample exit requires the following sub-parameters:

   RECTYPE=nnn

   This parameter contains a numeric value between 128 and 255.

   SYSID=xxxx

   The primary JES subsystem ID. SYSID can be a maximum of four characters.

   Assuming SMF record 250 is available and you decide to use CECS for the SYSID, the information provided on the SMFEXIT parameter is:

   CECSXSMF RECTYPE=250,SYSID=CECS

   An example of the modify command that would be issued to update this configuration parameter is:

   F server-name,set,config,service=monitor,smfexit=’CECSXSMF RECTYPE=250,SYSID=CECS’

2. Using Classic Data Architect or a z/OS modify command, update the monitor service SMFINTERVAL configuration parameter to identify how frequently the SMF exit is called to generate processing metrics for actively replicating subscriptions.
   For example, to collect processing metrics at 30-minute intervals, the following modify command needs to be issued:

   F server-name,set,config,service=monitor,smfinterval=30m

3. Stop and then restart the data server.
   When the data server restarts you should see the following message written to the console and JES log shortly after the CECMAA service completes initialization:

   CECSXSMF INITIALIZATION FUNCTION

4. Start replication for one or more subscriptions.

   Starting replication causes the SMF exit to be called to report state changes; however, to see processing metrics, wait at least for one SMFINTERVAL time (in this example 30 minutes) before SMF records containing processing metrics will be produced. An SMF record is produced for each actively replicating subscription at the interval specified on the SMFINTERVAL configuration parameter regardless of whether there is any activity for a subscription.

5. Identify the current SMF recording dataset and extract the SMF records produced by the exit to a sequential dataset.
   The following sample JCL extracts type 250 records from the MAN1 dataset and writes them to a new data set named CEC.SMFDATA:

   //*INSERT VALID JOB CARD HERE
   //STEP1 EXEC PGM=IFASMFDP
   //INDD1 DD DISP=SHR,DSN=SYS1.MAN1
   //OUTDD1 DD DISP=(NEW,CATLG),DSN=CEC.SMFDATA,
   // UNIT=SYSDA,VOL=SER=XXXXXX,SPACE=(TRK,(5,5),RLSE),
   // DCB=(LRECL=32760,BLKSIZE=27998,RECFM=VBS,DSORG=PS)
   //SYSPRINT DD SYSOUT=*
   //SYSIN DD *
   INDD(INDD1,OPTIONS(DUMP))
   OUTDD(OUTDD1,TYPE(250))
   

6. Run the sample REXX script to create the CSV file.
   The following sample JCL executes TSO in batch and runs the sample REXX script located in the USERSAMP library, reading the contents of the file produced in step 5, and creating a new CEC.CSV variable length sequential file containing the CSV output.

   //*INSERT VALID JOB CARD HERE
   //ISPFPROC EXEC PGM=IKJEFT01,DYNAMNBR=30                          
   //SYSTSPRT DD  SYSOUT=*                                           
   //CSV      DD  SYSOUT=*                                           
   //SYSTSIN  DD  DATA,DLM='*/'                                      
    EX 'HLQ.USERSAMP(CECRXSMF)' 'CEC.SMFDATA 250 CEC.CSV'
   */                                                                
   

   The script accepts the following input parameters:

   1. Name of the input file containing the extracted SMF records.
   2. The SMF record number produced by the CECSXSMF exit. The script ignores other record types.
   3. Name of the output CSV file to be created. If an output CSV file name is not provided, the CSV output is written to SYSTSPRT.