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
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
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
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
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
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.)
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
Yes . When you activate a new LNKLST , LLA gets refreshed automatically .
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
