@Pierre, I feel your pain. People suggesting SMF 30 solutions, or suggesting the problem is VB versus VBS, are well-intentioned but not on target. As are the folks suggesting the records are not "broken" -- "broken" is in fact the exact terminology that IBM uses. https://www.ibm.com/docs/en/zos/2.4.0?topic=rm-rmf-product-section-3
I think you said in another post that this was an IEFU8x environment? Re-assembling SMF records is tough enough in a batch program, and brutal in an exit environment. (The exit environment is tough enough on its own!) And no, you can't count on any particular constraints on the order in which things will occur, that X will always occur before Y, or that Z will never occur between X and Y -- unless the IBM documentation explicitly says so. It may work in 100 tests, but it will fail some day. I don't know the solution but have you considered the "reassembly area" and "reassembly area information block"? In what was is it inadequate to your needs? Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Pierre Fichaud Sent: Thursday, September 16, 2021 5:44 AM To: [email protected] Subject: Re: RMF SMF "broken" records Martin, Hence my original post. I have 3 "broken" records. I use the type,subtype, date and time in the SMF header to create a unique value relating the 3 records. But the time is only in 100ths of seconds. I don't think it's granular enough. Is there something extra I can use to make a unique key? Regards, Pierre. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
