Perhaps a lack of maintenance? I couldn't find anything in a quick problem search. I suggest opening a case with IBM.
-----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Matt Hogstrom Sent: Friday, September 20, 2019 9:18 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: *MASTER* enqueue on SYS1.LOGREC Tried on my local system. Here are my results … this is a 2.4 system NC0000000 TVT7050 19263 10:15:09.28 IBMUSER 00000290 D GRS,C MR0000000 TVT7050 19263 10:15:11.91 IBMUSER 00000090 ISG343I 10.15.09 GRS STATUS 069 DR 069 00000090 NO ENQ RESOURCE CONTENTION EXISTS DR 069 00000090 NO REQUESTS PENDING FOR ISGLOCK STRUCTURE ER 069 00000090 NO LATCH CONTENTION EXISTS NC0000000 TVT7050 19263 10:16:15.96 IBMUSER 00000290 SETLOGRC IGNORE N 0000000 TVT7050 19263 10:16:16.04 00000290 IEF196I IEF237I 0500 ALLOCATED TO SYS00006 N 0000000 TVT7050 19263 10:16:16.04 00000290 IEF196I IEF285I SYS1.LOGREC KEPT N 0000000 TVT7050 19263 10:16:16.04 00000290 IEF196I IEF285I VOL SER NOS= T70501. MR4040000 TVT7050 19263 10:16:16.04 IBMUSER 00000090 IFB097I LOGREC RECORDING MEDIUM CHANGED FROM DATASET TO IGNORE 078 NC0000000 TVT7050 19263 10:16:26.75 IBMUSER 00000290 SETLOGRC DATASET N 0000000 TVT7050 19263 10:16:26.76 00000290 IEF196I IEF237I 0500 ALLOCATED TO SYS00007 MR4040000 TVT7050 19263 10:16:26.76 IBMUSER 00000090 IFB097I LOGREC RECORDING MEDIUM CHANGED FROM IGNORE TO DATASET 081 NC0000000 TVT7050 19263 10:16:36.70 IBMUSER 00000290 D GRS,C MR0000000 TVT7050 19263 10:16:37.21 IBMUSER 00000090 ISG343I 10.16.36 GRS STATUS 083 DR 083 00000090 NO ENQ RESOURCE CONTENTION EXISTS DR 083 00000090 NO REQUESTS PENDING FOR ISGLOCK STRUCTURE ER 083 00000090 NO LATCH CONTENTION EXISTS Matt Hogstrom m...@hogstrom.org +1-919-656-0564 PGP Key: 0x90ECB270 Facebook <https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffacebook.com%2Fmatt.hogstrom&data=02%7C01%7Callan.staller%40HCL.COM%7Cd72fa38ef89847a2df8a08d73dd56b05%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637045859178025753&sdata=kyRBS2%2Bl5V%2BQ0uBThUDMCrcegGKzd7bdrdrAiMYHOHA%3D&reserved=0> LinkedIn <https://linkedin/in/mhogstrom> Twitter <https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftwitter.com%2Fhogstrom&data=02%7C01%7Callan.staller%40HCL.COM%7Cd72fa38ef89847a2df8a08d73dd56b05%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637045859178025753&sdata=TwIPLpv9Q7qSfiU70t%2BuXDvoHXlJU1qZrsTEUuxehlQ%3D&reserved=0> “It may be cognitive, but, it ain’t intuitive." — Hogstrom > On Sep 20, 2019, at 10:04 AM, J Ellis > <0000020d5fbe36e0-dmarc-requ...@listserv.ua.edu> wrote: > > While testing a fix for a job that had previously filled logrec, I > shut recording off : SETLOGRC IGNORE once testing once over, I turned > recording back on: SETLOGRC DATASET Now however the MASTER A/S has a share on > it, which prevented the daily logrec dump/clear job from running. > > I was sure I had done this before with no issues, that is, no MASTER enqueue > left on logrec. > > has anyone encountered this and know of a way, short of an IPL to clear get > the MASTER enqueue to release ? > > D GRS,C > ISG343I 07.36.44 GRS STATUS 091 > S=SYSTEM SYSDSN SYS1.LOGREC.SYST > SYSNAME JOBNAME ASID TCBADDR EXC/SHR STATUS > SYST *MASTER* 0001 00AB37C0 SHARE OWN > SYST SYEREPT 009E 00AEE588 EXCLUSIVE WAIT > > D GRS,RES=(*,SYS1.LOGREC.SYST) > ISG343I 07.38.06 GRS STATUS 114 > S=SYSTEM SYSDSN SYS1.LOGREC.SYST > SYSNAME JOBNAME ASID TCBADDR EXC/SHR STATUS > SYST *MASTER* 0001 00AB37C0 SHARE OWN > > ---------------------------------------------------------------------- > 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 ::DISCLAIMER:: ________________________________ The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. ________________________________ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
