It probably includes a compress > -----Original Message----- > From: IBM Mainframe Discussion List <[email protected]> On > Behalf Of Lizette Koehler > Sent: Monday, October 01, 2018 7:53 AM > To: [email protected] > Subject: Re: S106 abends after copying into LINKLIST > > We use a process from the cbttape.org called PDSCLEAN. It can clear out PDS > or PDS/E but same caveats exits. Shut down the task before cleaning the > directories. > > > Lizette > > > > -----Original Message----- > > From: IBM Mainframe Discussion List <[email protected]> On > > Behalf Of Barkow, Eileen > > Sent: Monday, October 01, 2018 7:48 AM > > To: [email protected] > > Subject: Re: S106 abends after copying into LINKLIST > > > > Thanks Lizette. > > > > The dataset is was emptied/copied in a different lpar than where it is used. > > But as was explained, the pds directory got altered by the empty > > member procedure and no LLA REFRESH was done. > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:IBM- > [email protected]] > > On Behalf Of Lizette Koehler > > Sent: Monday, October 01, 2018 10:45 AM > > To: [email protected] > > Subject: Re: S106 abends after copying into LINKLIST > > > > What the Dataset where the modules were staged shared among Plexes or > > are just allocated to one Plex (but shared among any members in that > > Plex) > > > > PDS/E datasets can be very touchy. > > > > Did you find an S213 abends on the libraries prior to the S106? > > > > Check the first module indicated in the first S106. Did it have an > > I/O errors when you browse it? > > > > Can you do an IEBCOPY of the PDS to a new one and see if IEBCOPY shows > > any I/O Errors > > > > Can you do a IEBPDSE Copy of the PDS/E to a new one and see if there > > are any I/O errors? > > > > https://urldefense.proofpoint.com/v2/url?u=https- > 3A__www.ibm.com_support_knowledgecenter_en_SSLTBW- > 5F2.1.0_com.ibm.zos.v2r1&d=DwICAg&c=C3yme8gMkxg_ihJNXS06ZyWk4EJ > m8LdrrvxQb- > Je7sw&r=u9g8rUevBoyCPAdo5sWE9w&m=SSH0jhO6X7PmFrTFoUlzrgHfxMh > w78-yYm11eiLkzS8&s=Q2WQ12FSAwlkrSDKWIWKwTcy4- > 1tlVJA0mEoO2gowpY&e=. > > ida > > u100/pdse.htm > > > > > > Lizette > > > > > > > -----Original Message----- > > > From: IBM Mainframe Discussion List <[email protected]> > On > > > Behalf Of Barkow, Eileen > > > Sent: Monday, October 01, 2018 7:10 AM > > > To: [email protected] > > > Subject: S106 abends after copying into LINKLIST > > > > > > Hi MVS gurus. > > > Perhaps someone can offer a plausible explanation for this, so that > > > the MVS group will stop blaming the CICS group for the problem. > > > > > > Last friday morning we copied new CICS LINKLIST/LPA modules into the > > > existing LINKLIST/LPA loadlibs in use (a rather new scenario in use > > > here - we used to use alternative datasets), in anticipation of an > > > IPL to be done sunday morning. > > > anyway, around 6pm friday evening, an I/O error occured in linklist > > > and other jobs started abending with S106 abends. > > > the linklist library was not allocated with secondary extents and > > > there was no LLA refresh issued during the day. I cannot find > > > anything like this situation occurring on IBMLINK and we have no > > > dump of the > > original failure. > > > > > > Does anyone have any idea of what could have caused the I/O error. > > > both the input and output datasets have a max blksize of 32760. > > > > > > IEW4009I FETCH FAILED FOR MODULE DFHXCPRX FROM DDNAME - > LNKLST- > > > BECAUSE OF AN I/O ERROR. > > > IEW4005I FETCH FOR MODULE DFHXCPRX FROM DDNAME -LNKLST- > FAILED > > > BECAUSE IEWFETCH ISSUED RC 0F AND REASON 40 CSV031I LIBRARY > ACCESS > > > FAILED FOR MODULE DFHXCPRX, RETURN CODE 24, REASON CODE > 26080021, > > > DDNAME *LNKLST* > > > > > > > > > > > > > > > > > > ________________________________ > > > > > > This e-mail, including any attachments, may be confidential, > > > privileged or otherwise legally protected. It is intended only for > > > the addressee. If you received this e-mail in error or from someone > > > who was not authorized to send it to you, do not disseminate, copy > > > or otherwise use this e-mail or its attachments. Please notify the > > > sender immediately by reply e-mail and delete the e-mail from your > system. > > > > > > > > > -------------------------------------------------------------------- > > > -- 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
---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
