You should never stage anything to active linklist datasets that you do not 
want to be placed into use.   Your prior method of staging new datasets into 
the LINKLIST parmlib member to be picked up with IPL would be the proper method.

Is the dataset PDSE?

-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of 
Barkow, Eileen
Sent: Monday, October 01, 2018 10:22 AM
To: [email protected]
Subject: Re: S106 abends after copying into LINKLIST

**CAUTION EXTERNAL EMAIL**

**DO NOT open attachments or click on links from unknown senders or unexpected 
emails**

The  whole idea was not to have to refresh LLA - we wanted to wait until the 
IPL.
Why should LLA have to be refreshed if we did not want the changes to take 
effect?

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of ITschak Mugzach
Sent: Monday, October 01, 2018 10:19 AM
To: [email protected]
Subject: Re: S106 abends after copying into LINKLIST

You need to refresh lla.

בתאריך יום ב׳, 1 באוק׳ 2018, 16:10, מאת Barkow, Eileen ‏<
[email protected]>:

> 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 **CAUTION EXTERNAL 
EMAIL**

**DO NOT open attachments or click on links from unknown senders or unexpected 
emails**

This e-mail transmission contains information that is confidential and may be 
privileged.   It is intended only for the addressee(s) named above. If you 
receive this e-mail in error, please do not read, copy or disseminate it in any 
manner. If you are not the intended recipient, any disclosure, copying, 
distribution or use of the contents of this information is prohibited. Please 
reply to the message immediately by informing the sender that the message was 
misdirected. After replying, please erase it from your computer system. Your 
assistance in correcting this error is appreciated.


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to