One simple rule is that every SMS managed dataset must be cataloged. So, unless technical tricks are exploited, an SMF record 61 must have been produced to Catlog-Define the dataset. So a first check should be if all relevant SMF records are being recorded. A second check could be to see if the dataset was created on another LPAR, as suggested before.
Kees. > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Ron Hawkins > Sent: 27 August, 2019 15:54 > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: SMF PUZZLE > > Shmuel, > > I am a novice when it comes to some of the deep dive stuff that you guys > meander off, and into. > > I was thinking a GTF SSCH trace off a volume allocating a data set with > IEFBR14 may be a starting point, along with looking for any SMF records > generated at the time of allocation would be a good starting point to test > the hypotheses. > > Do you have any additional ideas that would add to what and how SMF > recording occurs when allocating a file with IEFBR14? > > Ron > > > RON HAWKINS > Director, Ipsicsopt Pty Ltd (ACN: 627 705 971) > m+61 400029610| t: +1 4085625415 | f: +1 4087912585 > > -----Original Message----- > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf > Of > Seymour J Metz > Sent: Tuesday, 27 August 2019 03:38 > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: [IBM-MAIN] SMF PUZZLE > > If you are configured for automatic EOF, then Allocation will write an EOF > regardless of the program name; there's nothing special about IEFBR14 > except > for a performance tweak. There is no OPEN involved. > > > -- > Shmuel (Seymour J.) Metz > http://mason.gmu.edu/~smetz3 > > > ________________________________________ > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf > of > Clark Morris <cfmt...@uniserve.com> > Sent: Saturday, August 24, 2019 5:54 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: SMF PUZZLE > > [Default] On 24 Aug 2019 13:41:23 -0700, in bit.listserv.ibm-main > martin_pac...@uk.ibm.com (Martin Packer) wrote: > > >Allocation doesn't cause SMF 14/15 to be written. CLOSE (and therefore > >OPEN) does. > > If a data set is allocated by IeFBr14 on an SMS disk, as I understand it, > it > will have an EOF record as its first record. Thus it can be read (as a > zero > record file) by a subsequent program or job and deleted thus from an SMF > point of view a file can be read and deleted without ever having been > created. > > Clark Morris > > > >I guess, from the original post, data is written so presumably some > >form of OPEN took place. > > > >Cheers, Martin > > > >Martin Packer > > > >zChampion, Systems Investigator & Performance Troubleshooter, IBM > > > >+44-7802-245-584 > > > >email: martin_pac...@uk.ibm.com > > > >Twitter / Facebook IDs: MartinPacker > > > >Blog: > >https://secure-web.cisco.com/1jWfMC4FDTdzncrPWLkLBC97mhpriVujWYooUizSQ6 > >hb0k9sN_oOVeg_WgS7GzM5YpYMYtZp-nnbEDiUw-EiD_OHn9QfBsrSqe_ImSMiG31ra9yfP > >AKUDO05uAmHYthKUHaVBrfwEeROqG-WIELMpqDHuKRv8kVKLMqhdEKAUDrpYV9DHZXZ-0OU > >wiNug5NoU_--dlnI8GGbV16C0r0eIpD408r2exKQiMLt9N_lvB1-DehKvsvhBCv-pNqRvUn > >E7KCKxVJsXSaBl4TzvUhgoawSvaqvIbVuu3koAvZ5BlDLfaLlacfawRWmzJ1QtVNtACHvb0 > >a9SXZvdHjy_B9u1v5t5l-QIF6pOxwaepas8xdB44mVkbr0rn98BFivnfVvuwSi94lP63Xxj > >Ylwb2q5PwrF7_hhdQ30WFCftH1szu91swRPCtGtwhYIxOmYJLfy9/https%3A%2F%2Fwww. > >ibm.com%2Fdeveloperworks%2Fmydeveloperworks%2Fblogs%2FMartinPacker > > > >Podcast Series (With Marna Walle): > https://secure- > web.cisco.com/1yhNrHArR0hNFGwHN0qBqalN1WcEEZiI_aRSlqBs8tumOw9 > lf_q4tgH_CIKjxvULkgukqhvEv6i_SPyGGT3gLSQRyV4splC5NE73vPb0WAFrSjtXrnOpXkon6 > CP > 64pGjB9Ljwt2lX7dckT8nz- > ne7qQci7WWHL7FG1HWQ9UqqBaG1WmEfMYd_d49r81HzdLvkVcMrP0 > X1WIuVgsQiENPM5KNuKnIlUkckvt0dqjLV6r- > ERIteEtdwuIxTrLiT4aWA_Gy04iLU85zhTLsQi5 > g8MILX6vEQ67nzVe2IEiWIQnxBXX9TnONUxqi9OZgaqN_faxWQTWH9oWnqasqa9XlteUhIt0km > nA > c8CMikcnMKd2OqgpCyAgh1EUxe-iazvu3mIgeOJPT40iT0_77fxBjLJF- > rHOltCE7N1OkCoyEz73 > Z8LMx6SjRfPHLYku3cTxh-/https%3A%2F%2Fdeveloper.ibm.com%2Ftv%2Fmpt%2F or > > > >https://secure-web.cisco.com/1W9EfBzfL20vS0dm4Oso2UK0eyDeYRwOuEe-o4U1w8 > >_DiX-llP5CA4n_Zs3Yd1S9vNtL1UvCv6w5dPFkMDxS_p0UB57f4hauVw8vPCuCPt09vx2DD > >y3Xov42l6fSafLc96QKFEJURN0tyg3VKXnGLnnvW8q4rhePIT48WgQU2DrLE-wFj_KesthA > >uhbYEaEQjVrN8k0nicbrGTbEjKznyIs4RUAHWPNRUukA-sueWDq4_MUrMiFIWAj8vlzvNGj > >mtsn_6jFw2GS7tmdCwHXB7BNf9pag8xghXcp6YkrDw8pyym_PYTUN-F4GeI9YX-yvuUzGj7 > >u5IOWG3Fd5jJu4Ppikdh85_V7kPjjLqpdiQWKgs9bTYLqLvfy5Sp9W2VmBA08KQAMVOazDe > >SyFcUBYV1A7WgNaYgWlP92w02ADvhXyo7fFZK3h87wALc014bMJt/https%3A%2F%2Fitun > >es.apple.com%2Fgb%2Fpodcast%2Fmainframe-performance-topics%2Fid11279435 > >73%3Fmt%3D2 > > > > > >Youtube channel: > >https://www.youtube.com/channel/UCu_65HaYgksbF6Q8SQ4oOvA > > > > > > > >From: Charles Mills <charl...@mcn.org> > >To: IBM-MAIN@LISTSERV.UA.EDU > >Date: 24/08/2019 21:23 > >Subject: Re: SMF PUZZLE > >Sent by: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> > > > > > > > >SMF only captures what you tell it to (with SMFPRMxx). Some shops, for > >example, exclude STC's from certain SMF types "to avoid a performance > >impact on CICS" or some similar reason. The whole "how to read SMFPRMxx" > >thing is beyond the scope of an e-mail. D SMF,O will give you a > >not-quite-trivial-to-parse summary. > > > >SMF 15 shows "opened for output and then closed" (for those subsystems > >for which it is configured, per the above). Harking back to the IEFBR14 > >discussion here a week or so ago, I wonder if a basic "create a DSN > >with > >IEFBR14 DISP=(NEW,CTALG)" shows up in SMF 15 (because it does not close > >the dataset). Others may well know. > > > >Charles > > > > > >-----Original Message----- > >From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > >On Behalf Of willie bunter > >Sent: Saturday, August 24, 2019 10:30 AM > >To: IBM-MAIN@LISTSERV.UA.EDU > >Subject: SMF PUZZLE > > > >Good Day, > >I am trying to find the user/job which created a dsn. I run my > >trustworthy SMF job which looks for recids 05 14 15 17 18 61 62 63 64 > >65 > >66 67 68 136 139 163. The job showed the job which read the dsn & > >deleted it but it doesn't show who or which job created it.According to > >the LISTCAT the creation date of the dsn was Thursday Aug. 22. I read > >the SMF tape for the previous week and subsequent days including Aug 22 & > 23. > >I was thinking if the dsn was created by a FTP or an UNIX upload > >process which may not be trapped by SMF Any thoughts? Any suggestions > > > >---------------------------------------------------------------------- > >For IBM-MAIN subscribe / signoff / archive access instructions, send > >email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > > > > > > >Unless stated otherwise above: > >IBM United Kingdom Limited - Registered in England and Wales with > >number 741598. > >Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 > >3AU > > > > > >---------------------------------------------------------------------- > >For IBM-MAIN subscribe / signoff / archive access instructions, send > >email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email > to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email > to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ******************************************************** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ******************************************************** ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
