And don't try to use the same name on a different volume in the new
set, cause it won't work.
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Imbriale, Donald (Exchange)
Sent: Wednesday, February 21, 2007 2:01 PM
To: IBM-MAIN@BAMA.UA.EDU
On Wed, 21 Feb 2007 16:13:59 -0600, Matthew Stitt [EMAIL PROTECTED] wrote:
As was pointed out by Mark, the LNKLST is accessed through LLA. VLF only
does the memory storage based on LLA requests.
So even though you restarted VLF, you must also restart LLA. This might
make your changes available
On Wed, 21 Feb 2007 17:07:41 -0600, Tom Schmidt
[EMAIL PROTECTED] wrote:
On Wed, 21 Feb 2007 16:13:59 -0600, Matthew Stitt wrote:
As was pointed out by Mark, the LNKLST is accessed through LLA. VLF only
does the memory storage based on LLA requests.
So even though you restarted VLF, you must
Mark is absolutely correct on this too.
Raj
---
In the case of renaming current to old and new to current on the
same volume, I think LLA would restart without complaining. LLA just
wouldn't be managing the new library since the LNKLST still has the
old one.
I miss the beginning of this thread, so I am not sure what the
original question was. But if it is a matter of renaming a loadlib
in the LNKLST and hope that all will be well I believe that it
will not be the case. It is my opinion that LLA will come up without
an issue, but an I/O error
Hi All,
Could someone please enlighten me on the below query ? :
Q. I have renamed a LNKLSTed load library ( say , ABC.LOAD on VOLSER =
XX ) to ABC.LOAD.OLD . I have then named a new version of the same
product load library to the same name ( ABC.LOAD.NEW on VOLSER=XX
to ABC.LOAD
-Original Message-
From: IBM Mainframe Discussion List
[mailto:[EMAIL PROTECTED] On Behalf Of Rajesh Dharia
Sent: Wednesday, February 21, 2007 11:49 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: UPDATING VLF data objects without an IPL --a query
for the list, please
Hi All,
Could
Thanks for your response , John :-) .
You are right . I know, the proper way would have been to update the
LNKLST with a new loadlib name or a different VOLSER ,at least .
Considering the situation that a dynamic LNKLST change is not to be made
, do you think IPLing the system will be
On Thu, 22 Feb 2007 02:35:11 +0530, Rajesh Dharia [EMAIL PROTECTED] wrote:
Thanks for your response , John :-) .
You are right . I know, the proper way would have been to update the
LNKLST with a new loadlib name or a different VOLSER ,at least .
Considering the situation that a dynamic
Hi Mark,
Not local rules, really. I could update the LNKLST dynamically.However,
that won't be useful unless it is backed by the same changes done
statically (which will be taking effect during the next IPL ). The problem
is ... the change management procedures come into the scene here and I
There are numerous threads in the archives of IBM-Main which discuss
manipulation of linklist. The basic procedure is:
Define a new linklist set, copying the current one
Add the new data set to the new linklist set
Delete the old data set from the new linklist set
Activate the new linklist set
As was pointed out by Mark, the LNKLST is accessed through LLA. VLF only
does the memory storage based on LLA requests.
So even though you restarted VLF, you must also restart LLA. This might
make your changes available to the system.
On Wed, 21 Feb 2007 17:01:13 -0500, Imbriale, Donald
On Wed, 21 Feb 2007 16:13:59 -0600, Matthew Stitt wrote:
As was pointed out by Mark, the LNKLST is accessed through LLA. VLF only
does the memory storage based on LLA requests.
So even though you restarted VLF, you must also restart LLA. This might
make your changes available to the system.
13 matches
Mail list logo
