Corroborating SMF 70 is a good source for this - as we use it in our code, too.
Cheers, Martin Martin Packer Systems Investigator & Performance Troubleshooter, IBM +44-7802-245-584 email: martin_pac...@uk.ibm.com Twitter / Facebook IDs: MartinPacker Blog: https://mainframeperformancetopics.com Mainframe, Performance, Topics Podcast Series (With Marna Walle): https://anchor.fm/marna-walle Youtube channel: https://www.youtube.com/channel/UCu_65HaYgksbF6Q8SQ4oOvA From: Al Sherkow <a...@sherkow.com> To: IBM-MAIN@LISTSERV.UA.EDU Date: 05/12/2020 05:33 Subject: [EXTERNAL] Re: Group Capacity setting dropped Sent by: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> Bob The "GCLGCHNG: Change in LPAR Groups" report in LCS should show you the timestamp that any LPAR was added or removed from a group. Also if there were any changes to the group capacity limit. From this you'll have the timestamp the changes occurred. I wrote the report and tested it with a site that was changing settings as they were learning Group Capacity Limits back in 2008. I assume since LCS is looking at the RMF 70 data that any dynamic changes made by WLM as mentioned by Attila will be reported also. This would give you the timestamps per LPAR when the change occurred for further investigation. None of my customers have discussed a similar issue with me. Best regards, Al Sherkow ---------------------------------------------------------------------- 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
