Same dataset name, different volume makes (in my past experience) LLA and 
LNKLST unhappy. Been a long time, but I try not to do that one. 

Dave Gibney
Information Technology Services
Washington State University


> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of baby eklavya
> Sent: Wednesday, July 10, 2013 2:28 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: LLA refreshed automatically with SETPROG ACTIVATE command
> 
> Hi all ,
> 
>   We have an issue with LLA after activating new linklist set . There are 2
> different scenarios given below
> 
> Scenario 1 : The current linklist set is LNKLST00 . We added a new dataset
> by copying to LNKLST01 and activated LNKLST01 . With SETPROG
> LNKLST,ACTIVATE ,NAME=LNKLST01 command , LLA was automatically
> refreshed .
> I didnt have to issue F LLA,REFRESH ,instead it got refreshed automatically
> with SETPROG ACTIVATE command .Is this normal ?
> 
> Scenario 2: I removed a dataset from LNKLST00 , moved it to a different
> volume and added the same dataset back using LNKLST01 and activated
> LNKLST01 with the command SETPROG LNKLST,ACTIVATE,NAME=LNKLST01
> .But this
> time , LLA didn't pick it up automatically .
> 
> I don't understand why LLA didn't pick up the dataset automatically in
> Scenario # 2 . Any thoughts on this ?
> 
> Regards,
> baby
> 
> ----------------------------------------------------------------------
> 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