I do also, every place has their own process and if it's a standard practice that works, that's great. I've worked at places that did as you, update live link listed libraries on a Friday afternoon before a scheduled IPL, crossing their fingers an in prompt-u IPL is not done before, or, oh well, my changes are in :) I've been in client sites that will not allow you to Stage changes prior to your downtime, this controlled by a change managment monitoring tool, if you do make a change beforehand, you're toast. I've been at site that control changes by keeping 2 sets of SMP/E target environments, and you flip from one to the other, this is done for CICS and DB2 and MQ and...... this strategy worked best IMHO but a lot of folks don't like the thought of managing 2 target environments. so I think this time you (team) got burnt. tons of explanation here on how PDS's allocation should be done and what happens when a PDS is emptied/reloaded or compressed without an LLA refresh, all good stuff, I'll continue what works for me and NOT allocation secondary space for a link listed library and ensure my primary space is adequate for the install + maint, if possible. my .00002 cents
Carmen Vitullo ----- Original Message ----- From: "Eileen Barkow" <ebar...@doitt.nyc.gov> To: IBM-MAIN@LISTSERV.UA.EDU Sent: Tuesday, October 2, 2018 10:42:25 AM Subject: Re: S106 abends after copying into LINKLIST I agree that this maintenance strategy is no good but the MVS group does not want to have to change parmlib for new maintenance, so We now have to do the updates right before an IPL - usually about 4am on Sunday mornings. We used to at least keep separate linklist/lpa datasets for different releases of CICS - now the same datasets get overlaid for new releases as well as maintenance. -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Seymour J Metz Sent: Tuesday, October 02, 2018 11:29 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: S106 abends after copying into LINKLIST > Perhaps someone can offer a plausible explanation for this, so that > the MVS group will stop blaming the CICS group for the problem. An explanation will not stop the MVS group from blaming the CICS group for a problem caused by the CICS group. Your current maintenance strategy is dangerous and is the cause of the problem. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <IBM-MAIN@listserv.ua.edu> on behalf of Barkow, Eileen <ebar...@doitt.nyc.gov> Sent: Monday, October 1, 2018 10:09 AM To: IBM-MAIN@listserv.ua.edu 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 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
