I think I have to disagree.
Disagree is an interesting choice of words. What I stated is a fact.
Just because you have not seen it in no way means that it does not exist.
If there are fetches anywhere in process, they may fail in unpredictable
ways.
I think there would be a lot of angry
On Fri, Aug 22, 2014 at 7:21 AM, Peter Relson rel...@us.ibm.com wrote:
I think I have to disagree.
Disagree is an interesting choice of words. What I stated is a fact.
Just because you have not seen it in no way means that it does not exist.
If there are fetches anywhere in process, they may
In 0302225330497145.wa.brianwestermansyzygyinc@listserv.ua.edu,
on 08/21/2014
at 09:50 PM, Brian Westerman brian_wester...@syzygyinc.com said:
If that were the case, I think there would be a lot of angry people
opening problems with IBM support,
Even when the manual warns you that it is
And you would probably be asked, in a nice way, something that correlates
to can't you read? and the PMR would be closed.
You (and IBM support) asked me the same thing when the problem occured 36 hours
(!) after the setprog lnklst,update command (that I had not even issued). Thank
goodness
I think I have to disagree. I can't see where there is any evidence that
altering the LINKLIST while things are running would not work. If that were
the case, I think there would be a lot of angry people opening problems with
IBM support, and I would be one of the first on that list of
, on a sysprog sandpit it can be a matter of full steam
ahead, and damn the users. The users in that case being (only) us.
From: Brian Westerman brian_wester...@syzygyinc.com
To: IBM-MAIN@LISTSERV.UA.EDU
Date: 08/22/2014 12:15 AM
Subject: Re: PLPA entry (was PLPA enty)
Sent by: IBM Mainframe Discussion
(was PLPA enty)
On Tue, 19 Aug 2014 08:28:22 -0400, Peter Relson wrote:
The only thing that is truly safe is to let new address spaces and
jobs
use the new lnklst while old ones continue to use the old one.
This has always been my approach - protect the long running address
spaces
In 4708885082630749.wa.brianwestermansyzygyinc@listserv.ua.edu,
on 08/18/2014
at 09:14 PM, Brian Westerman brian_wester...@syzygyinc.com said:
(JOB=*)
But note IBM's warnings.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see
snip
You don't need to IPL to add or remove datasets from linklist.
You can create a new PROGxx member that uses another linklist name (other
than your default 00), and then issue the T PROG=xx that points to that
new linklist, then you can issue the SETPROG command to make the new
linklist
On Tue, 19 Aug 2014 08:28:22 -0400, Peter Relson wrote:
The only thing that is truly safe is to let new address spaces and jobs
use the new lnklst while old ones continue to use the old one.
This has always been my approach - protect the long running address spaces.
Of course, on a sysprog
-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of John McKown
Sent: Sunday, August 17, 2014 9:25 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: PLPA enty
I assume that you have IPL'd after changing PARMLIB. Did you review the IPL
messages? If IPL/NIP has some problem
Thanks that was it
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Norbert Friemel
Sent: Monday, August 18, 2014 2:51 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: PLPA enty
On Sun, 17 Aug 2014 22:37:48 -0400, MichealButz wrote:
Hi
You don't need to IPL to add or remove datasets from linklist.
You can create a new PROGxx member that uses another linklist name (other than
your default 00), and then issue the T PROG=xx that points to that new
linklist, then you can issue the SETPROG command to make the new linklist the
Hi,
I put my loadlib library in LPALSTXX or specifically 01 that is what is
pointed to by LPA member on the active IEASYS
When I use TASID to look at LPA libs I see all of them except the one I
added
Am I missing something
Thanks
I assume that you have IPL'd after changing PARMLIB. Did you review the IPL
messages? If IPL/NIP has some problem with your data set, it will just
issue a message and continue on. Some of the problems that I know off,
off-hard are:
(1) data set is not catalogued in the MASTER catalog _and_ the
Subject: Re: PLPA enty
I assume that you have IPL'd after changing PARMLIB. Did you review the IPL
messages? If IPL/NIP has some problem with your data set, it will just issue a
message and continue on. Some of the problems that I know off, off-hard are:
(1) data set is not catalogued
16 matches
Mail list logo
