What about setting up the SMF parms to tell SMF to ignore the 110-2 records?  
CICS will still create them but I would think SMF would just "throw them away" 
when it see them.  Before that happens would not an exit see the 110-2 records 
and then send them off to say Splunk?


Paul Feller
GTS Mainframe Technical Support

-----Original Message-----
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of 
Pommier, Rex
Sent: Monday, May 9, 2022 11:40 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Producing throwaway SMF? [EXTERNAL]

Hi Mike,

I believe that depends on what you mean by "not write them to the SMF 
datasets".  If you mean that you don't want them to go to the MANx datasets 
where SMF actually writes records, I believe the answer is no.  However, if you 
want them to not go to where your SMF DUMP process goes, absolutely.  You can 
do an SMF dump w/o clear to just pull the 110-2 records into a separate dataset 
then do a dump/clear of the MAN dataset to the SMF offload dataset excluding 
the 110-2 records.  But I don't think there's a way to tell CICS to send the 
110-2 records to someplace other than straight to the SMF MAN datasets.  

Rex

-----Original Message-----
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of 
MARTIN, MIKE
Sent: Monday, May 9, 2022 10:57 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Producing throwaway SMF?

Well, not exactly throwaway, but is there a way to produce SMF/RMF record types 
(say CICS 110-2's) for sending to a product like Splunk, but not write them to 
our SMF datasets (non-streams).

(I realize products like Splunk probably have a way to intercept/send the data) 
but we may not want to save the data to our SMF datasets with the 110-2 records 
if we turn them on.

Mike Martin

This email may contain confidential and privileged material for the sole use of 
the intended recipient. If you are not the intended recipient, please contact 
the sender and delete all copies. Any review or distribution by others is 
strictly prohibited. Personal emails are restricted by policy of the State 
Employees' Credit Union (SECU).  Therefore SECU specifically disclaims any 
responsibility or liability for any personal information or opinions of the 
author expressed in this email.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
The information contained in this message is confidential, protected from 
disclosure and may be legally privileged. If the reader of this message is not 
the intended recipient or an employee or agent responsible for delivering this 
message to the intended recipient, you are hereby notified that any disclosure, 
distribution, copying, or any action taken or action omitted in reliance on it, 
is strictly prohibited and may be unlawful. If you have received this 
communication in error, please notify us immediately by replying to this 
message and destroy the material in its entirety, whether in electronic or hard 
copy format. Thank you.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
Please note:  This message originated outside your organization. Please use 
caution when opening links or attachments.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to