DDLIST just calls ISRDDN. Use whichever your finger macros like. Just remember that the default is to only search the link list.
Alas, I don't have read access to the link list libraries. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר ________________________________________ From: IBM Mainframe Discussion List on behalf of David Spiegel Sent: Friday, May 16, 2025 1:40 PM To: [email protected] Subject: Re: DFRMM S0C4/SF13 ABEND: EDGI100I being issued spuriously? External Message: Use Caution ... or DDLIST On 2025-05-16 12:58, Seymour J Metz wrote: > ISRDDN is an easy tool for checking that sort of issue. > > -- > Shmuel (Seymour J.) Metz > http://mason.gmu.edu/~smetz3 > עַם יִשְׂרָאֵל חַי > נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר > > > > ________________________________________ > From: IBM Mainframe Discussion List on behalf of Jay Maynard > Sent: Friday, May 16, 2025 11:38 AM > To: [email protected] > Subject: Re: DFRMM S0C4/SF13 ABEND: EDGI100I being issued spuriously? > > > External Message: Use Caution > > > Fixed. Turns out we had an old, old version of EDGSOCE get put in a library > ahead of SYS1.LINKLIB on the linklist, and it finally bit us. (From 2004! > How the hell it ran this long, I ahven't got the first clue.) Gteting rid > of it and reIPLing fixed it. Yay! > > On Fri, May 16, 2025 at 9:47 AM Allan Staller < > [email protected]> wrote: > >> Classification: Confidential >> >> SF13 abend says SVC 19 (x'13') is having some sort of problem( HALT IO). >> Very weird! >> >> -----Original Message----- >> From: IBM Mainframe Discussion List <[email protected]> On Behalf >> Of Jay Maynard >> Sent: Friday, May 16, 2025 8:28 AM >> To: [email protected] >> Subject: Re: DFRMM S0C4/SF13 ABEND: EDGI100I being issued spuriously? >> >> [CAUTION: This Email is from outside the Organization. Unless you trust >> the sender, Don’t click links or open attachments as it may be a Phishing >> email, which can steal your Information and compromise your Computer.] >> >> An update: We've now removed not one, but two, copies of EDGUX100 in the >> QA system. (There were none in the production system.) The EDGI100I message >> is gone, but we're still getting the ABEND. Have a case open with IBM now. >> >> On Thu, May 15, 2025 at 11:09 AM Seymour J Metz <[email protected]> wrote: >> >>> SMP? >>> >>> -- >>> Shmuel (Seymour J.) Metz >>> http://mason/ >>> .gmu.edu%2F~smetz3&data=05%7C02%7Callan.staller%40hcltech.com%7C9e023a >>> f6e28845ec714e08dd947d9022%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0% >>> 7C638829989239616703%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsI >>> lYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C >>> 0%7C%7C%7C&sdata=wwKiw60yEEW8V1uaOHd3UmiG0oS%2F%2BJcvAome72iBFPM%3D&re >>> served=0 >>> עַם יִשְׂרָאֵל חַי >>> נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר >>> >>> >>> >>> ________________________________________ >>> From: IBM Mainframe Discussion List on behalf of Jay Maynard >>> Sent: Thursday, May 15, 2025 11:11 AM >>> To: [email protected] >>> Subject: Re: DFRMM S0C4/SF13 ABEND: EDGI100I being issued spuriously? >>> >>> >>> External Message: Use Caution >>> >>> >>> Yes, I've searched the entire linklist and LPA, and EDGUX100 does not >>> exist. >>> >>> On Thu, May 15, 2025 at 10:10 AM rpinion865 < >>> [email protected]> wrote: >>> >>>> Have you verified that EDGUX100 is not being loaded/used? I read >>>> ALL of your first post, and you specifically said that EDGUX100 and >>>> UXTB had been converted. Sorry for not taking the time to read ALL >>>> of your post :) >>>> >>>> Current Data Set Allocation Member >> was >>>> found >>>> Command ===> Scroll >>> ===> >>>> CSR >>>> >>>> Message Act DDname Data Set Name Actions: B E V M F >> C >>> I >>>> Q >>>> Member: EDGUX100 > LINKLIST SYS1.LINKLIB >>>> >>>> > SYS1.MIGLIB >>>> >>>> > SYS1.CSSLIB >>>> >>>> >>>> >>>> >>>> "Confidentially doc, I am the wabbit." >>>> >>>> Bugs Bunny >>>> >>>> Sent with Proton Mail secure email. >>>> >>>> On Thursday, May 15th, 2025 at 11:01 AM, rpinion865 < >>>> [email protected]> wrote: >>>> >>>>> If you do a D SSI from the console do you see anything about UXTB? >>>>> >>>>> SUBSYS=UXTB >>>>> DYNAMIC=YES STATUS=INACTIVE COMMANDS=REJECT >>>>> >>>>> >>>>> >>>>> "Confidentially doc, I am the wabbit." >>>>> >>>>> Bugs Bunny >>>>> >>>>> Sent with Proton Mail secure email. >>>>> >>>>> >>>>> On Thursday, May 15th, 2025 at 10:35 AM, Jay Maynard >>>> [email protected] wrote: >>>>>> It is in production. We get the EDGI100I message there, and yet >>> things >>>> run >>>>>> fine. >>>>>> >>>>>> On Thu, May 15, 2025 at 9:34 AM rpinion865 < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Looks like things have changed from the examples I shared. My >>>> examples >>>>>>> come from an OS/390 2.10 system. >>>>>>> >>>>>>> A more modern z/OS talks about EDGDEFxx. >>>>>>> >>>>>>> >>> https://www/. >>> ibm.com%2Fdocs%2Fen%2Fzos%2F2.4.0%3Ftopic%3Dedgdefxx-converting-from-u >>> sing-uxtable-using-defaults-table&data=05%7C02%7Callan.staller%40hclte >>> ch.com%7C9e023af6e28845ec714e08dd947d9022%7C189de737c93a4f5a8b686f4ca9 >>> 941912%7C0%7C0%7C638829989239637722%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU >>> 1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldU >>> IjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=qek0OEJUlNMHpt8Q0Jnd%2FhIsdnKa5QfJ6gph >>> d9diZFQ%3D&reserved=0 >>>>>>> But you are seeing abends that are related to the UXTB. Do you >>>>>>> know >>>> if >>>>>>> the new functionality can run with the UXTB? >>>>>>> >>>>>>> "Confidentially doc, I am the wabbit." >>>>>>> >>>>>>> Bugs Bunny >>>>>>> >>>>>>> Sent with Proton Mail secure email. >>>>>>> >>>>>>> On Thursday, May 15th, 2025 at 10:24 AM, Jay Maynard < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> Is this still necessary if the same function is done in >>>>>>>> EDGDEF00, >>>> though? >>>>>>>> On Thu, May 15, 2025 at 9:16 AM rpinion865 < >>>>>>>> [email protected]> wrote: >>>>>>>> >>>>>>>>> I would search for something, might be run as job as >>>>>>>>> opposed to >>>> a STC, >>>>>>>>> that executes this. >>>>>>>>> >>>>>>>>> VIEW OS390.PROCLIB(EDGCVRSP) - 01.01 Columns 00001 >>>>>>>>> 00072 >>>>>>>>> Command ===> Scroll ===> >>>>>>>>> CSR >>>>>>>>> 000038 //LOADUXTB EXEC >>>> PGM=EDGCVRSL,REGION=4096K,PARM='&SSN.,&TAB.' >>>>>>>>> "Confidentially doc, I am the wabbit." >>>>>>>>> >>>>>>>>> Bugs Bunny >>>>>>>>> >>>>>>>>> Sent with Proton Mail secure email. >>>>>>>>> >>>>>>>>> On Thursday, May 15th, 2025 at 10:10 AM, rpinion865 < >>>>>>>>> [email protected]> wrote: >>>>>>>>> >>>>>>>>>> Perhaps, the UXTB is being created with a STC that does >>>>>>>>>> not >>>> use the >>>>>>>>>> IBM >>>>>>>>>> EDG* name. From the system where a UXTB is created, >>>>>>>>>> these are the messages you should >>>> see. The >>>>>>>>>> EDGX102I message indicates the UXTB has been created. >>>>>>>>>> >>>>>>>>>> STC32987 00000090 $HASP373 EDGCVRSP STARTED >>>>>>>>>> STC32986 00000290 IEF695I START LMSINIT WITH JOBNAME >>>>>>>>>> LMSINIT >>> IS >>>>>>>>>> ASSIGNED >>>>>>>>>> TO >>>>>>>>>> , GROUP PROCGRP >>>>>>>>>> STC32987 00000090 IEF403I EDGCVRSP - STARTED - >>>>>>>>>> TIME=11.31.16 >>>>>>>>>> STC32986 00000090 $HASP373 LMSINIT STARTED >>>>>>>>>> STC32986 00000090 IEF403I LMSINIT - STARTED - >>>>>>>>>> TIME=11.31.16 >>>>>>>>>> 00000290 IEF196I IEF237I 0301 ALLOCATED TO SYS00002 >>>>>>>>>> STC32987 00000090 EDGX102I DATA TABLE LOADED O.K. >>>>>>>>>> >>>>>>>>>> "Confidentially doc, I am the wabbit." >>>>>>>>>> >>>>>>>>>> Bugs Bunny >>>>>>>>>> >>>>>>>>>> Sent with Proton Mail secure email. >>>>>>>>>> >>>>>>>>>> On Thursday, May 15th, 2025 at 9:57 AM, Jay Maynard >>>>>>>>>> [email protected] wrote: >>>>>>>>>> >>>>>>>>>>> EDGCVRSP, that is. And no, that doesn't exist either. >>>>>>>>>>> >>>>>>>>>>> On Thu, May 15, 2025 at 8:54 AM Jay Maynard >>>> [email protected] >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> The IBM webpage calls for that, in STC EDGVRSP. That >>>> started task >>>>>>>>>>>> proc >>>>>>>>>>>> doesn't exist on either system. >>>>>>>>>>>> >>>>>>>>>>>> On Thu, May 15, 2025 at 8:51 AM rpinion865 < >>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> I think you need to run a DFRMM STC which will set >>>>>>>>>>>>> up >>>> the UXTB. >>>>>>>>>>>>> Off the >>>>>>>>>>>>> top of my head, I cannot remember what STC does >>>>>>>>>>>>> that. Maybe my suggestion will >>>> ring a >>>>>>>>>>>>> bell >>>>>>>>>>>>> for >>>>>>>>>>>>> you. If not, I can find out what STC you need to >>>>>>>>>>>>> run. >>>>>>>>>>>>> >>>>>>>>>>>>> "Confidentially doc, I am the wabbit." >>>>>>>>>>>>> >>>>>>>>>>>>> Bugs Bunny >>>>>>>>>>>>> >>>>>>>>>>>>> Sent with Proton Mail secure email. >>>>>>>>>>>>> >>>>>>>>>>>>> On Thursday, May 15th, 2025 at 9:47 AM, Jay >>>>>>>>>>>>> Maynard < >> [email protected]> wrote: >>>>>>>>>>>>>> We're having a weird problem. On our QA LPAR, >>>>>>>>>>>>>> trying >>>> to do a >>>>>>>>>>>>>> tape mount >>>>>>>>>>>>>> (for an FDRABR restore operation) results in the >>>> following >>>>>>>>>>>>>> messages >>>>>>>>>>>>>> after the IEF455D for the tape mount: >>>>>>>>>>>>>> >>>>>>>>>>>>>> EDGI100I SUBSYSTEM UXTB NOT DEFINED OR NO TABLE >>> LOADED >>>>>>>>>>>>>> EDG2003E ABEND S0C4 U0000 RSN 0017 DURING >>>>>>>>>>>>>> DFSMSrmm >>>> SUBSYSTEM >>>>>>>>>>>>>> PROCESSING >>>>>>>>>>>>>> AT >>>>>>>>>>>>>> 4C0DFA IN MODULE K j~ EDG4003E DFSMSrmm DETECTED >>>>>>>>>>>>>> CONTROL BLOCK ERROR 20, >>> 4084 >>>>>>>>>>>>>> DURING >>>>>>>>>>>>>> OPEN FOR >>>>>>>>>>>>>> VQ0002 BY TXNWABRR, UTABRRES, TAPE# >>>>>>>>>>>>>> >>>>>>>>>>>>>> Everything we can find about the EDGI100I >>>>>>>>>>>>>> message >>>> talks about >>>>>>>>>>>>>> using >>>>>>>>>>>>>> EDGUX100 to set up processing for tape >>>>>>>>>>>>>> expiration. We >>>> had, at >>>>>>>>>>>>>> some >>>>>>>>>>>>>> point in >>>>>>>>>>>>>> the past, had that exit in place and the >>>>>>>>>>>>>> associated >>>> table, >>>>>>>>>>>>>> but >>>>>>>>>>>>>> during >>>>>>>>>>>>>> the >>>>>>>>>>>>>> installation of a previous z/OS, converted that >>>>>>>>>>>>>> to >>>> using the >>>>>>>>>>>>>> EDGDEF00 member to accomplish the same goal and >>>> removed the >>>>>>>>>>>>>> exit >>>>>>>>>>>>>> and the >>>>>>>>>>>>>> table. >>>>>>>>>>>>>> >>>>>>>>>>>>>> The annoying thing about this is that this all >>>>>>>>>>>>>> works perfectly in our production LPAR. We've >>>>>>>>>>>>>> compared definitions and >>> modules >>>>>>>>>>>>>> between >>>>>>>>>>>>>> the two >>>>>>>>>>>>>> LPARs, and they're the same. >>>>>>>>>>>>>> >>>>>>>>>>>>>> So...anyone have any suggestions as to where we >>>>>>>>>>>>>> can >>>> look? Why >>>>>>>>>>>>>> does RMM >>>>>>>>>>>>>> issue EDGI100I if the exit is not in use? I've >>>>>>>>>>>>>> tried >>>> looking >>>>>>>>>>>>>> at >>>>>>>>>>>>>> the 0C4 >>>>>>>>>>>>>> dump, and it wasn't very enlightening. We've >>> contacted >>>> BMC >>>>>>>>>>>>>> just >>>>>>>>>>>>>> to make >>>>>>>>>>>>>> sure it's not FDR that's the culprit, and they >>>>>>>>>>>>>> found >>>> that >>>>>>>>>>>>>> it's >>>>>>>>>>>>>> the >>>>>>>>>>>>>> victim, >>>>>>>>>>>>>> and pointed us to the same web page we keep >>>>>>>>>>>>>> tripping >>>> over at >>>> https://ibm.com/support/pages/rmm-message-edgi100i-issued . >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> Jay Maynard >>>>>>>>> >>>> -------------------------------------------------------------------- >>>> -- >>>>>>>>>>>>>> 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 >>>>>>>>>>>> -- >>>>>>>>>>>> Jay Maynard >>>>>>>>>>> -- >>>>>>>>>>> Jay Maynard >>>>>>> >>>> -------------------------------------------------------------------- >>>> -- >>>>>>>>>>> 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 >>>>>>>>> >>>> -------------------------------------------------------------------- >>>> -- >>>>>>>>> For IBM-MAIN subscribe / signoff / archive access >>>>>>>>> instructions, send email to [email protected] with >>>>>>>>> the message: INFO >>>> IBM-MAIN >>>>>>>> -- >>>>>>>> Jay Maynard >>>>>>>> >>>>>>>> >>>> -------------------------------------------------------------------- >>>> -- >>>>>>>> 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 >>>>>> -- >>>>>> Jay Maynard >>>>>> >>>>>> >>> ---------------------------------------------------------------------- >>>>>> 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 >>>> -------------------------------------------------------------------- >>>> -- For IBM-MAIN subscribe / signoff / archive access instructions, >>>> send email to [email protected] with the message: INFO >>>> IBM-MAIN >>>> >>> >>> -- >>> Jay Maynard >>> >>> ---------------------------------------------------------------------- >>> 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 >>> >> >> -- >> Jay Maynard >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, send email >> to [email protected] 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 [email protected] with the message: INFO IBM-MAIN >> > > -- > Jay Maynard > > ---------------------------------------------------------------------- > 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 ---------------------------------------------------------------------- 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
