> 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

Reply via email to