Re: LLA refreshed automatically with SETPROG ACTIVATE command
baby eklavya wrote: 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 ? Yes. As documented (Partial snippet): Use the SETPROG LNKLST command to: Activate a LNKLST set as the LNKLST concatenation for the system But if I were you, I would do F LLA,REFRESH anyways and also SETPROG LNKLST,UPDATE,JOB=* Of course I would insert SETPROG LNKLST,TEST,... for checking. 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 . If you do that stunt in that specific sequence + omitted steps as described, I'm not that surprised. How did you 'removed a dataset from LNKLST00' in the first place? Did you UPDATE, REFRESH, etc and then after that, moved your dataset? I don't understand why LLA didn't pick up the dataset automatically in Scenario # 2 . Any thoughts on this ? WAD. I think you should RTFM the book 'MVS System Commands' again. Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: LLA refreshed automatically with SETPROG ACTIVATE command
Hi Elardus , Thanks for the response Scenario 2 happened in a diffferent z/os system altogether . It was done using the below commands SETPROG LNKLST,DEFINE,NAME=LNKLST02,COPYFROM=LNKLST00 SETPROG LNKLST,DELETE,NAME=LNKLST02,DSNAME=X.Y.Z SETPROG LNKLST,ACTIVATE,NAME=LNKLST02 SETPROG LNKLST,UPDATE,JOB=* I didn't do an LLA refresh here , because i was expecting that LNKLST,ACTIVATE would do the refresh automatically and also subsequent D LLA didn't show X.Y.Z in its output Then , i moved X.Y.Z to another volume and i wanted to add the same dataset back to the linklist . so , i used the below commands SETPROG LNKLST,DEFINE,NAME=LNKLST01,COPYFROM=LNKLST02 SETPROG LNKLST,ADD,NAME=LNKLST01,DSNAME=X.Y.Z SETPROG LNKLST,ACTIVATE,NAME=LNKLST01 SETPROG LNKLST,UPDATE,JOB=* After that , when i do a D LLA , it still doesnt show X.Y.Z in its output Thanks in Advance , Baby On Thu, Jul 11, 2013 at 12:01 PM, Elardus Engelbrecht elardus.engelbre...@sita.co.za wrote: baby eklavya wrote: 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 ? Yes. As documented (Partial snippet): Use the SETPROG LNKLST command to: Activate a LNKLST set as the LNKLST concatenation for the system But if I were you, I would do F LLA,REFRESH anyways and also SETPROG LNKLST,UPDATE,JOB=* Of course I would insert SETPROG LNKLST,TEST,... for checking. 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 . If you do that stunt in that specific sequence + omitted steps as described, I'm not that surprised. How did you 'removed a dataset from LNKLST00' in the first place? Did you UPDATE, REFRESH, etc and then after that, moved your dataset? I don't understand why LLA didn't pick up the dataset automatically in Scenario # 2 . Any thoughts on this ? WAD. I think you should RTFM the book 'MVS System Commands' again. Groete / Greetings Elardus Engelbrecht -- 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
Re: LLA refreshed automatically with SETPROG ACTIVATE command
Hi all , . It looks like the volume doesnt matter . Its the dataset name which is creating this problem . We are on Z/os 1.10 . I tested without moving to a different volume I did the whole thing once again .This time i tested a different dataset A.B.C . I removed it from the current linklist via LNKLST04 as u suggested . Then did an LLA update to remove it from LLA management .Everything works normal till this point .D LLA confirms that A.B.C is removed from LLA Then , i defined LNKLST05 with the same dataset A.B.C added back and activated LNKLST05 . But , it looks like LLA is not picking it up automatically with the SETPROG ACTIVATE . I had to manually add it to LLA management using F LLA,UPDATE When am adding a new dataset , LLA picks it up . But when a dataset which is already there is removed and re-added , LLA doesnt pick it automatically . The manuals doent say any restriction of this kind Is this a bug in Z/os 1.10 . Anyone faced this problem before ? Thanks in Advance, baby -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: LLA refreshed automatically with SETPROG ACTIVATE command
To quibble: LLA is not refreshed on a LNKLST activate. But it is updated. LLA will still be providing directory information for users of the old LNKLST (using the old information) as well as users of the new LNKLST (using the updated information). 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 LLA does not understand uncataloged data sets. And if your LNKLST is built with a data set that is not in the catalog that LLA uses you are asking for trouble. The system tries to alert you of such a situation. But I don't fully grasp the scenario. Unless LNKLST00 was first activated after IPL, if you activate LNKLST01, LNKLST00 is still active. You can't add or remove a data set from an active LNKLST set. If you happened to remove the data set from LLA management via the REMOVE statement of CSVLLAxx, that data set will not be added back in automatically, honoring the removal that you requested for whatever reason. Peter Relson z/OS Core Technology Design -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: LLA refreshed automatically with SETPROG ACTIVATE command
On Thu, 11 Jul 2013 01:31:26 -0500, Elardus Engelbrecht elardus.engelbre...@sita.co.za wrote: But if I were you, I would do F LLA,REFRESH anyways and also SETPROG LNKLST,UPDATE,JOB=* On a busy (with applications up and running), production system, I wouldn't. On a test system, or a system where applications have been quiesced, and hence an IPL would not cause the business owners heartburn, I might, and I have. The books warn of the dangers of performing an UPDATE JOB=*, and I, for one, take that advice seriously. I've never had an UPDATE=* crash a system, but then, I've not performed it during full-tilt-boogie production, nor have I tried to remove or relocate SYS1.LINKLIB, for example. Even UPDATE JOB=jobname can impact that one job. All it takes is one ill-timed fetch, and it's take two IPLs, call me in the morning... But, as wise man (or is that wise guy) has said, It's not my dog. Regards, Art Gutowski Compuware Corporation -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: LLA refreshed automatically with SETPROG ACTIVATE command
In 7676108221436477.wa.elardus.engelbrechtsita.co...@listserv.ua.edu, on 07/11/2013 at 01:31 AM, Elardus Engelbrecht elardus.engelbre...@sita.co.za said: But if I were you, I would do F LLA,REFRESH anyways and also SETPROG LNKLST,UPDATE,JOB=* It's not my dog. -- Shmuel (Seymour J.) Metz, SysProg and JOAT Atid/2http://patriot.net/~shmuel We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: LLA refreshed automatically with SETPROG ACTIVATE command
Hello Peter, That was perfect . the dataset was not added back automatically because of REMOVE statement of CSVLLAxx . To confirm that , i did the exercise once again in my sandbox lpar by removing another dataset and this time , i didnt remove the entry from LLA using CSVLLAxx , instead i recycled LLA and when it started , dataset was not displayed in D LLA . I added the same dataset back to the linklist again and SETPROG ACTIVATE updated LLA as well . Instead of creating this mess , all i should have done was an LLA refresh/update after the adding the dataset back to the linklist . Thanks a lot for your inputs and it helped me understand the function of LLA better Once again , thanks to everyone who commented on this post , Regards, baby On Thu, Jul 11, 2013 at 6:45 PM, Peter Relson rel...@us.ibm.com wrote: To quibble: LLA is not refreshed on a LNKLST activate. But it is updated. LLA will still be providing directory information for users of the old LNKLST (using the old information) as well as users of the new LNKLST (using the updated information). 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 LLA does not understand uncataloged data sets. And if your LNKLST is built with a data set that is not in the catalog that LLA uses you are asking for trouble. The system tries to alert you of such a situation. But I don't fully grasp the scenario. Unless LNKLST00 was first activated after IPL, if you activate LNKLST01, LNKLST00 is still active. You can't add or remove a data set from an active LNKLST set. If you happened to remove the data set from LLA management via the REMOVE statement of CSVLLAxx, that data set will not be added back in automatically, honoring the removal that you requested for whatever reason. Peter Relson z/OS Core Technology Design -- 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
Re: LLA refreshed automatically with SETPROG ACTIVATE command
Yes . When you activate a new LNKLST , LLA gets refreshed automatically . https://www.google.co.in/url?sa=trct=jq=esrc=ssource=webcd=8cad=rjaved=0CF8QFjAHurl=http%3A%2F%2Fschunk-it.com%2FPresentations%2FShare095%2Fs2855ssa.pdfei=ntXdUcDvK8r5rAenkoHwBwusg=AFQjCNGmcl7LdMqRb9Y5_671PSn2_9IE4wsig2=wCDiXpE743dHZ-gBbCP4nw Thanks !Bob Date: Thu, 11 Jul 2013 02:58:25 +0530 From: baby.ekla...@gmail.com Subject: LLA refreshed automatically with SETPROG ACTIVATE command To: IBM-MAIN@LISTSERV.UA.EDU 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
Re: LLA refreshed automatically with SETPROG ACTIVATE command
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
