Not allowing secondary allocation for linklisted libraries is definitely
a good practice.  It can help to avoid so many headaches, such as the
potential one described by the OP.  With DASD "cheap" today, it's good
practice to just over-allocate linklisted libraries so maintenance can
be applied or new modules introduced without causing new extents to be
taken.  This is especially true for those shops where IPLs are few and
far between.  Otherwise you're looking at creating new linklist sets and
activating them and facing the issue of different tasks using different
linklist sets which can possibly be 'fixed' with the potentially
dangerous SETPROG LNKLST,UPDATE,JOB=xxxx command.

The only time you might be able to get away with a linklisted library
going into extents, is to compress it and hope it goes back to the
original number of extents which existed when the linklist set was
activated.

Don Imbriale

>-----Original Message-----
>From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf
>Of Ted MacNEIL
>Sent: Wednesday, May 03, 2006 8:00 PM
>To: [email protected]
>Subject: Re: LINKLST into EXTENTS
>
>>LLA refresh does not pick up new LNKLST extents. Only
>building/activating/updating a new LNKLST set can do that.
>
>Okay.
>Any day you learn something new is a good day.
>
>I can't believe I didn't know that.
>
>At the Bank I used to work at, we didn't allow for secondary extents in
link list
>libraries.


***********************************************************************
Bear Stearns is not responsible for any recommendation, solicitation, 
offer or agreement or any information about any transaction, customer 
account or account activity contained in this communication.
***********************************************************************

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to